Segfault after deploy
Lars Bjørndal
After successfully deploying a site, I get the following error:
Scanning posts........done!
[1m[2021-06-08 07:17:01] INFO: deploy: => preset 'default'[0m
[1m[2021-06-08 07:17:01] INFO: deploy: ==> rsync -rav --delete output/ /var/www/html/saf-org[0m
sending incremental file list
./
archive.html
index-1.html
index-10.html
index-2.html
index-3.html
index-4.html
index-5.html
index-6.html
index-7.html
index-8.html
index-9.html
index.html
robots.txt
rss.xml
sitemap.xml
sitemapindex.xml
129/
...
wp-content/uploads/2014/09/
wp-content/uploads/2017/
wp-content/uploads/2017/05/
sent 5,380,147 bytes received 12,912 bytes 3,595,372.67 bytes/sec
total size is 8,500,286 speedup is 1.58
[1m[2021-06-08 07:17:02] INFO: deploy: Successful deployment[0m
Traceback (most recent call last):
File "/usr/lib/python3.9/site-packages/doit/doit_cmd.py", line 190, in run
return command.parse_execute(args)
File "/usr/lib/python3.9/site-packages/doit/cmd_base.py", line 150, in parse_execute
return self.execute(params, args)
File "/usr/lib/python3.9/site-packages/nikola/plugin_categories.py", line 145, in execute
return self._execute(options, args)
File "/usr/lib/python3.9/site-packages/nikola/plugins/command/deploy.py", line 99, in _execute
self._emit_deploy_event(last_deploy, new_deploy, clean, undeployed_posts)
UnboundLocalError: local variable 'clean' referenced before assignment
klrs@dalen:~/web/saf3\1[lrs@dalen saf3]$ exit
This is a site imported from WordPress. Any ideas on what's wrong here?
I'm using Nikola v8.1.2 officially Fedora package.
Lars
Chris Warrick
This is a mostly harmless bug that was fixed in v8.1.3. You can just
ignore the error and ~everything will work fine, or you can upgrade to
v8.1.3 (by installing in a venv, or perhaps by letting the Fedora
maintainers know their package is outdated).
PS. terminology note: this is not a segfault, a segfault is a specific
type of error, found most often in badly written C/C++ code - those
are super rare in Python (since those would be bugs in the
interpreter, or in third-party C libraries). What you’re seeing is a
Python traceback, caused by an exception. Or you can just say "error"
and avoid any confusion.
--
Chris Warrick <https://chriswarrick.com/>
PGP: 5EAAEA16
José Abílio Matos
On Tuesday, June 8, 2021 8:03:37 AM WEST Chris Warrick wrote:
> Hi,
>
> This is a mostly harmless bug that was fixed in v8.1.3. You can just
> ignore the error and ~everything will work fine, or you can upgrade to
> v8.1.3 (by installing in a venv, or perhaps by letting the Fedora
> maintainers know their package is outdated).
I will update the package in Fedora.
I have been busy with other issues and now it is a good time, now that in Fedora 35 (to be released in October) already has Python 3.10 (in pre-releases, of course).
Best regards,
--
José Matos
Lars Bjørndal
Thanks
Lars
José Abílio Matos
On Tuesday, 8 June 2021 19.29.21 WEST Lars Bjørndal wrote:
> Great! Is it possible that v8.1.3 will be available for Fedora 33 as well?
>
> Thanks
>
> Lars
Yes, I did it finally. :-(
https://bodhi.fedoraproject.org/updates/FEDORA-2021-1be3b3497d
It should be in updates-testing soon and if no problems show up it will be in updates one week after.
Lars Bjørndal
Lars
José Abílio Matos
On Thursday, 15 July 2021 09.48.24 WEST Lars Bjørndal wrote:
> Got it in todays update. Thank you very much!
>
> Lars
You are welcome. :-)
--
José Matos