Update to new upstream version.
This update has been submitted for testing by stingray.
This update has been pushed to testing.
Upgrading from 2.2 and using its config files I have to report that version 2.3 hangs on start-up. I downgraded to 2.2 and weechat started normally. Upgraded to 2.3 and weechat hangs. Removing weechat and reinstalling made no difference.
But starting without scripts (weechat -s), without plug-ins (weechat -p) or creating a new config (weechat -d) seems to work. Still trying to work out what's in my config that prohibits weechat from starting up.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
Can you send me more info? maybe do an strace? I just updated it on my machine (from 2.2) and it started up okay. Thanks
Nothing new to add since my last message so I'm back on a fully working weechat 2.2.
I've uploaded the strace for weechat 2.3 to:
There's something wrong with your python install - I see it trying to load python plugin then trying to abrtd.
Thanks for your time stingray. That was a new install just four days old.
I've just reinstalled F29, installed all the updates and then weechat 2.2. weechat worked. I upgraded to weechat 2.3 and the same again. weechat hung. strace showed the same as before. I'm out of this one. Sorry for the trouble.
This update has reached 7 days in testing and can be pushed to stable now if the maintainer wishes
I went from Weechat 2.2 -> 2.3 and I get hangs on exit about 80% of the time. Also, all of my python scripts have errors that they didn't have in 2.2. I'm still digging into those python script errors but downgrading to 2.2 fixed them all.
Can it be because weechat 2.3 is built with python3, while 2.2 was using python2?
Working well now, nice one.
This update has been obsoleted by weechat-2.4-1.fc29.
Please login to add feedback.
Confirm request to re-trigger tests.
Copyright © 2007-2019 Red Hat, Inc. and
bodhi is Free Software.
if you have any problems. Read the documentation.