Bug#874791: [Pkg-gajim-maintainers] Bug#874791: gajim: Crash on startup with python-gnupg >= 0.4 without gpg1

2017-09-14 Thread W. Martin Borgert
On 2017-09-14 09:29, Antonio Ospite wrote: > I am afraid the fix in 0.16.8-4 is not complete. > > Now gajim sets GPG_BINARY to '/usr/bin/gpg2', but this binary is only > provided by the "gnupg2" package which is a transitional package and it > may not be always installed. Antonio, you are right: T

Bug#874791: gajim: Crash on startup with python-gnupg >= 0.4 without gpg1

2017-09-14 Thread Elena ``of Valhalla''
On 2017-09-14 at 09:29:48 +0200, Antonio Ospite wrote: > A workaround is to install the gnupg2 package (if this is your preferred > solution then gajim should depend on the gnupg2 package), but I am not > sure this is the right solution, maybe setting GPG_BINARY = 'gpg' is > better? The original re

Bug#874791: gajim: Crash on startup with python-gnupg >= 0.4 without gpg1

2017-09-14 Thread Antonio Ospite
Package: gajim Version: 0.16.8-4 Followup-For: Bug #874791 Dear Maintainer, I am afraid the fix in 0.16.8-4 is not complete. Now gajim sets GPG_BINARY to '/usr/bin/gpg2', but this binary is only provided by the "gnupg2" package which is a transitional package and it may not be always installed.

Bug#874791: gajim: Crash on startup with python-gnupg >= 0.4 without gpg1

2017-09-09 Thread W. Martin Borgert
Hi Enrico, thanks for your bug report! On 2017-09-09 17:56, Enrico Rossi wrote: > updating to python-gnupg 0.4.1-1 which let gajim run with only gpg2 > installed, it crash because it tries to lunch gpg1 binary hardcoded into > the gajim.py (see /usr/share/gajim/src/common/gajim.py line 162). I e

Bug#874791: gajim: Crash on startup with python-gnupg >= 0.4 without gpg1

2017-09-09 Thread Enrico Rossi
Package: gajim Version: 0.16.8-3 Severity: important Dear Maintainer, updating to python-gnupg 0.4.1-1 which let gajim run with only gpg2 installed, it crash because it tries to lunch gpg1 binary hardcoded into the gajim.py (see /usr/share/gajim/src/common/gajim.py line 162). 1st workaround: cre