GNU bug report logs -
#44782
Python and Gajim-OMEMO
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 44782 in the body.
You can then email your comments to 44782 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#44782
; Package
guix
.
(Sat, 21 Nov 2020 18:57:01 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Raghav Gururajan <rg <at> raghavgururajan.name>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Sat, 21 Nov 2020 18:57:01 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Hello Guix!
It appears that our python is incorrectly compiled or compiled with
missing component. Due to this, OMEMO plugin in gajim does not work.
Here is the output for `gajim -l gajim.p.omemo=DEBUG`:
*** START ***
Traceback (most recent call last):
File
"/gnu/store/5h0xfqysfddzc4283wcyr0j8jj2zaz9c-gajim-1.2.2/bin/..gajim-real-real",
line 4, in <module>
import re
File
"/gnu/store/09a5iq080g9b641jyl363dr5jkkvnhcn-python-3.8.2/lib/python3.8/re.py",
line 143, in <module>
class RegexFlag(enum.IntFlag):
AttributeError: module 'enum' has no attribute 'IntFlag'
*** END ***
Also, I am flagging this issue as 'important' as it affects
security/privacy of messaging in gajim application.
Regards,
RG.
[OpenPGP_signature (application/pgp-signature, attachment)]
Severity set to 'important' from 'normal'
Request was from
Raghav Gururajan <rg <at> raghavgururajan.name>
to
control <at> debbugs.gnu.org
.
(Sat, 21 Nov 2020 18:59:01 GMT)
Full text and
rfc822 format available.
Severity set to 'normal' from 'important'
Request was from
Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
to
control <at> debbugs.gnu.org
.
(Tue, 29 Dec 2020 04:10:01 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#44782
; Package
guix
.
(Tue, 29 Dec 2020 04:13:01 GMT)
Full text and
rfc822 format available.
Message #12 received at 44782 <at> debbugs.gnu.org (full text, mbox):
Hello Raghav,
Raghav Gururajan <rg <at> raghavgururajan.name> writes:
> Hello Guix!
>
> It appears that our python is incorrectly compiled or compiled with
> missing component. Due to this, OMEMO plugin in gajim does not work.
>
> Here is the output for `gajim -l gajim.p.omemo=DEBUG`:
>
> *** START ***
> Traceback (most recent call last):
> File
> "/gnu/store/5h0xfqysfddzc4283wcyr0j8jj2zaz9c-gajim-1.2.2/bin/..gajim-real-real",
> line 4, in <module>
> import re
> File
> "/gnu/store/09a5iq080g9b641jyl363dr5jkkvnhcn-python-3.8.2/lib/python3.8/re.py",
> line 143, in <module>
> class RegexFlag(enum.IntFlag):
> AttributeError: module 'enum' has no attribute 'IntFlag'
> *** END ***
>
> Also, I am flagging this issue as 'important' as it affects
> security/privacy of messaging in gajim application.
>
> Regards,
> RG.
It's not a problem with Python but with Gaijim or one of its dependency:
--8<---------------cut here---------------start------------->8---
$ guix environment --pure --ad-hoc python -- python3 -c 'import enum;print(enum.IntFlag)'
<enum 'IntFlag'>
--8<---------------cut here---------------end--------------->8---
Summarily searching on the interwebs it seems that python-enum34 may be
at cause. You should look if it's being propagated by any of the
dependencies of gajim or gajim-omemo, and probably get rid of those as
this package exists for backward compatibility for Python versions older
than our 3.8.2 on master.
Maxim
Information forwarded
to
bug-guix <at> gnu.org
:
bug#44782
; Package
guix
.
(Tue, 29 Dec 2020 04:32:02 GMT)
Full text and
rfc822 format available.
Message #15 received at 44782 <at> debbugs.gnu.org (full text, mbox):
Hello again,
Maxim Cournoyer <maxim.cournoyer <at> gmail.com> writes:
> Hello Raghav,
>
> Raghav Gururajan <rg <at> raghavgururajan.name> writes:
>
>> Hello Guix!
>>
>> It appears that our python is incorrectly compiled or compiled with
>> missing component. Due to this, OMEMO plugin in gajim does not work.
>>
>> Here is the output for `gajim -l gajim.p.omemo=DEBUG`:
>>
>> *** START ***
>> Traceback (most recent call last):
>> File
>> "/gnu/store/5h0xfqysfddzc4283wcyr0j8jj2zaz9c-gajim-1.2.2/bin/..gajim-real-real",
>> line 4, in <module>
>> import re
>> File
>> "/gnu/store/09a5iq080g9b641jyl363dr5jkkvnhcn-python-3.8.2/lib/python3.8/re.py",
>> line 143, in <module>
>> class RegexFlag(enum.IntFlag):
>> AttributeError: module 'enum' has no attribute 'IntFlag'
>> *** END ***
>>
>> Also, I am flagging this issue as 'important' as it affects
>> security/privacy of messaging in gajim application.
>>
>> Regards,
>> RG.
>
> It's not a problem with Python but with Gaijim or one of its dependency:
>
> $ guix environment --pure --ad-hoc python -- python3 -c 'import enum;print(enum.IntFlag)'
> <enum 'IntFlag'>
>
> Summarily searching on the interwebs it seems that python-enum34 may be
> at cause. You should look if it's being propagated by any of the
> dependencies of gajim or gajim-omemo, and probably get rid of those as
> this package exists for backward compatibility for Python versions older
> than our 3.8.2 on master.
Actually, I can't seem to reproduce, using:
guix environment --pure --ad-hoc gajim gajim-omemo -- gajim -l
gajim.p.omemo=DEBUG
Then I tried signing up with some random account, enabled the plugin and
I could see:
12/28/20 23:28:16 (I) gajim.p.omemo ($some-server) Generating OMEMO keys
12/28/20 23:28:21 (I) gajim.p.omemo ($some-server) Our device id: 1816266738
12/28/20 23:28:21 (I) gajim.p.omemo ($some-server) 100 PreKeys available
It seems like you may have 'pip3 install enum34' or have other things in
your environment that cause the issue?
If you can't reproduce in a clean environment, let's close it.
Thanks,
Maxim
Information forwarded
to
bug-guix <at> gnu.org
:
bug#44782
; Package
guix
.
(Tue, 29 Dec 2020 18:21:02 GMT)
Full text and
rfc822 format available.
Message #18 received at 44782 <at> debbugs.gnu.org (full text, mbox):
Hi Maxim!
> Actually, I can't seem to reproduce, using:
>
> guix environment --pure --ad-hoc gajim gajim-omemo -- gajim -l
> gajim.p.omemo=DEBUG
>
> Then I tried signing up with some random account, enabled the plugin and
> I could see:
>
> 12/28/20 23:28:16 (I) gajim.p.omemo ($some-server) Generating OMEMO keys
> 12/28/20 23:28:21 (I) gajim.p.omemo ($some-server) Our device id: 1816266738
> 12/28/20 23:28:21 (I) gajim.p.omemo ($some-server) 100 PreKeys available
>
> It seems like you may have 'pip3 install enum34' or have other things in
> your environment that cause the issue?
>
> If you can't reproduce in a clean environment, let's close it.
Oh, I sent an email to debbugs-control long ago to close this bug. It
seems like the email didn't go through. I'll retry.
After discussing with cbaines in IRC, the issue was resolved. It was
python2-enum in the environment that was messing with python-enum.
Regards,
RG.
Reply sent
to
Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
:
You have taken responsibility.
(Tue, 29 Dec 2020 18:24:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Raghav Gururajan <rg <at> raghavgururajan.name>
:
bug acknowledged by developer.
(Tue, 29 Dec 2020 18:24:02 GMT)
Full text and
rfc822 format available.
Message #23 received at 44782-done <at> debbugs.gnu.org (full text, mbox):
Hello Raghav,
Raghav Gururajan <rg <at> raghavgururajan.name> writes:
> Hi Maxim!
>
>> Actually, I can't seem to reproduce, using:
>> guix environment --pure --ad-hoc gajim gajim-omemo -- gajim -l
>> gajim.p.omemo=DEBUG
>> Then I tried signing up with some random account, enabled the plugin
>> and
>> I could see:
>> 12/28/20 23:28:16 (I) gajim.p.omemo ($some-server)
>> Generating OMEMO keys
>> 12/28/20 23:28:21 (I) gajim.p.omemo ($some-server) Our device id: 1816266738
>> 12/28/20 23:28:21 (I) gajim.p.omemo ($some-server) 100 PreKeys available
>> It seems like you may have 'pip3 install enum34' or have other
>> things in
>> your environment that cause the issue?
>> If you can't reproduce in a clean environment, let's close it.
>
> Oh, I sent an email to debbugs-control long ago to close this bug. It
> seems like the email didn't go through. I'll retry.
It seems your message hadn't reached Debbugs.
No worries, I'm closing it now, by replying in Cc: to
44782-done <at> debbugs.gnu.org.
Thanks for the report!
Maxim
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Wed, 27 Jan 2021 12:24:12 GMT)
Full text and
rfc822 format available.
This bug report was last modified 3 years and 90 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.