WeeChat does not start

  • Done
  • quality assurance status badge
Details
7 participants
  • ng0
  • Luis Felipe López Acevedo
  • Leo Famulari
  • sirgazil
  • Ludovic Courtès
  • Marius Bakke
  • Cyril Roelandt
Owner
unassigned
Submitted by
Luis Felipe López Acevedo
Severity
normal
L
L
Luis Felipe López Acevedo wrote on 11 Nov 2015 15:06
(address . bug-guix@gnu.org)
1447250803.1579.3.camel@openmailbox.org
Hi,

I installed WeeChat 1.3 using Guix 0.9.0 on Debian 8, but It doesn't
start when I run it. I get this error instead:

Traceback (most recent call last):
File "/usr/lib/python2.7/site.py", line 563, in <module>
main()
File "/usr/lib/python2.7/site.py", line 545, in main
known_paths = addusersitepackages(known_paths)
File "/usr/lib/python2.7/site.py", line 272, in addusersitepackages
user_site = getusersitepackages()
File "/usr/lib/python2.7/site.py", line 247, in getusersitepackages
user_base = getuserbase() # this will also set USER_BASE
File "/usr/lib/python2.7/site.py", line 237, in getuserbase
USER_BASE = get_config_var('userbase')
File "/usr/lib/python2.7/sysconfig.py", line 582, in get_config_var
return get_config_vars().get(name)
File "/usr/lib/python2.7/sysconfig.py", line 528, in get_config_vars
_init_posix(_CONFIG_VARS)
File "/usr/lib/python2.7/sysconfig.py", line 412, in _init_posix
from _sysconfigdata import build_time_vars
File "/usr/lib/python2.7/_sysconfigdata.py", line 6, in <module>
from _sysconfigdata_nd import *
ImportError: No module named _sysconfigdata_nd

Thanks,


--
Luis Felipe López Acevedo
C
C
Cyril Roelandt wrote on 12 Nov 2015 13:18
(address . bug-guix@gnu.org)
5644837D.7090709@gmail.com
On 11/11/2015 03:06 PM, Luis Felipe López Acevedo wrote:
Toggle quote (27 lines)
> Hi,
>
> I installed WeeChat 1.3 using Guix 0.9.0 on Debian 8, but It doesn't
> start when I run it. I get this error instead:
>
> Traceback (most recent call last):
> File "/usr/lib/python2.7/site.py", line 563, in <module>
> main()
> File "/usr/lib/python2.7/site.py", line 545, in main
> known_paths = addusersitepackages(known_paths)
> File "/usr/lib/python2.7/site.py", line 272, in addusersitepackages
> user_site = getusersitepackages()
> File "/usr/lib/python2.7/site.py", line 247, in getusersitepackages
> user_base = getuserbase() # this will also set USER_BASE
> File "/usr/lib/python2.7/site.py", line 237, in getuserbase
> USER_BASE = get_config_var('userbase')
> File "/usr/lib/python2.7/sysconfig.py", line 582, in get_config_var
> return get_config_vars().get(name)
> File "/usr/lib/python2.7/sysconfig.py", line 528, in get_config_vars
> _init_posix(_CONFIG_VARS)
> File "/usr/lib/python2.7/sysconfig.py", line 412, in _init_posix
> from _sysconfigdata import build_time_vars
> File "/usr/lib/python2.7/_sysconfigdata.py", line 6, in <module>
> from _sysconfigdata_nd import *
> ImportError: No module named _sysconfigdata_nd
>

Seems like you are using weechat from Guix using Python 2.7 from Debian,
which is a bit weird. Also, _sysconfigdata_nd is Debian-specific. What
is your PYTHONPATH?

Cyril.
L
L
Ludovic Courtès wrote on 18 Nov 2015 18:06
(name . Luis Felipe López Acevedo)(address . felipe.lopez@openmailbox.org)(address . 21879@debbugs.gnu.org)
87oaerp78l.fsf@gnu.org
Hi!

Luis Felipe López Acevedo <felipe.lopez@openmailbox.org> skribis:

Toggle quote (7 lines)
> I installed WeeChat 1.3 using Guix 0.9.0 on Debian 8, but It doesn't
> start when I run it. I get this error instead:
>
> Traceback (most recent call last):
> File "/usr/lib/python2.7/site.py", line 563, in <module>
> main()

On closer inspection, this comes from the fact that Weechat looks for a
‘python’ executable in $PATH. See src/plugins/python/weechat-python.c
in Weechat.

In your case, it ended up running Debian’s Python, which then failed for
reasons that are unclear to me.

I believe this is fixed by a9346fa and 7be4a4b. Could you confirm?
You could run ‘guix pull’ or pull from a current ‘master’ checkout.

Thanks,
Ludo’.
L
L
Luis Felipe López Acevedo wrote on 18 Nov 2015 21:05
(address . ludo@gnu.org)(address . 21879@debbugs.gnu.org)
e29f9113c1f0ac7742ccba72582dd290@openmailbox.org
On 2015-11-18 12:06, ludo@gnu.org wrote:
Toggle quote (23 lines)
> Hi!
>
> Luis Felipe López Acevedo <felipe.lopez@openmailbox.org> skribis:
>
>> I installed WeeChat 1.3 using Guix 0.9.0 on Debian 8, but It doesn't
>> start when I run it. I get this error instead:
>>
>> Traceback (most recent call last):
>> File "/usr/lib/python2.7/site.py", line 563, in <module>
>> main()
>
> On closer inspection, this comes from the fact that Weechat looks for a
> ‘python’ executable in $PATH. See src/plugins/python/weechat-python.c
> in Weechat.
>
> In your case, it ended up running Debian’s Python, which then failed
> for
> reasons that are unclear to me.
>
> I believe this is fixed by a9346fa and 7be4a4b. Could you confirm?
> You could run ‘guix pull’ or pull from a current ‘master’ checkout.


In a different machine, but still Debian 8 and Guix 0.9.0:

1. I ran 'guix pull'
2. Installed weechat

I get the same error.


--
Luis Felipe López Acevedo
C
C
Cyril Roelandt wrote on 18 Nov 2015 21:44
(address . bug-guix@gnu.org)
564CE33C.6050407@gmail.com
On 11/18/2015 09:05 PM, Luis Felipe López Acevedo wrote:
Toggle quote (7 lines)
> In a different machine, but still Debian 8 and Guix 0.9.0:
>
> 1. I ran 'guix pull'
> 2. Installed weechat
>
> I get the same error.

On Debian Sid + Guix, I installed weechat in a "guix environment", and
could not reproduce the issue (weechat properly starts). However,
running "PATH=/usr/bin:$PATH weechat" leads to the same error you witnessed.

Could you post you PATH and PYTHONPATH?

Cyril.
L
L
Ludovic Courtès wrote on 18 Nov 2015 22:22
(name . Cyril Roelandt)(address . tipecaml@gmail.com)(address . 21879@debbugs.gnu.org)
871tbnj952.fsf@gnu.org
Cyril Roelandt <tipecaml@gmail.com> skribis:

Toggle quote (14 lines)
> On 11/18/2015 09:05 PM, Luis Felipe López Acevedo wrote:
>> In a different machine, but still Debian 8 and Guix 0.9.0:
>>
>> 1. I ran 'guix pull'
>> 2. Installed weechat
>>
>> I get the same error.
>
> On Debian Sid + Guix, I installed weechat in a "guix environment", and
> could not reproduce the issue (weechat properly starts). However,
> running "PATH=/usr/bin:$PATH weechat" leads to the same error you witnessed.
>
> Could you post you PATH and PYTHONPATH?

Could you double-check what’s happening, possibly running it through
strace to see if it’s actually executing /usr/bin/python?

Maybe my attempt was misguided and the problem is actually not in the
Python plugin but in some core part?

Thanks,
Ludo’.
C
C
Cyril Roelandt wrote on 18 Nov 2015 22:41
(name . Ludovic Courtès)(address . ludo@gnu.org)(address . 21879@debbugs.gnu.org)
564CF08A.7050404@gmail.com
On 11/18/2015 10:22 PM, Ludovic Courtès wrote:
Toggle quote (3 lines)
> Could you double-check what’s happening, possibly running it through
> strace to see if it’s actually executing /usr/bin/python?

I'm pretty sure it does that. It even loads libraries from the Debian
Python path, that is why it tries to import a Debian-specific module.

Cyril.
L
L
Ludovic Courtès wrote on 19 Nov 2015 10:41
(name . Cyril Roelandt)(address . tipecaml@gmail.com)(address . 21879@debbugs.gnu.org)
874mgifhr4.fsf@inria.fr
Cyril Roelandt <tipecaml@gmail.com> skribis:

Toggle quote (7 lines)
> On 11/18/2015 10:22 PM, Ludovic Courtès wrote:
>> Could you double-check what’s happening, possibly running it through
>> strace to see if it’s actually executing /usr/bin/python?
>
> I'm pretty sure it does that. It even loads libraries from the Debian
> Python path, that is why it tries to import a Debian-specific module.

Weird. Could you check with strace and/or GDB to confirm and see where
it’s coming from?

When I run it through strace, I don’t see any attempt to exec python.

TIA. :-)
Ludo’.
L
L
Ludovic Courtès wrote on 29 Nov 2015 12:01
(name . Cyril Roelandt)(address . tipecaml@gmail.com)
877fl1nk7n.fsf@gnu.org
Cyril Roelandt <tipecaml@gmail.com> skribis:

Toggle quote (7 lines)
> On 11/18/2015 10:22 PM, Ludovic Courtès wrote:
>> Could you double-check what’s happening, possibly running it through
>> strace to see if it’s actually executing /usr/bin/python?
>
> I'm pretty sure it does that. It even loads libraries from the Debian
> Python path, that is why it tries to import a Debian-specific module.

I tried this:

guix environment --container --ad-hoc weechat strace coreutils \
findutils sed grep less --expose=$(which false)=/usr/bin/python

which installs ‘false’ as /usr/bin/python, but it still works fine.

Felipe, could you report the values of the ‘PYTHONPATH’, ‘PATH’, and
‘LD_LIBRARY_PATH’ variables on your system?

Are you able to work around the problem with:

guix environment --ad-hoc weechat --pure -- weechat

?

TIA,
Ludo’.
L
L
Luis Felipe López Acevedo wrote on 29 Nov 2015 15:12
(address . ludo@gnu.org)
5cc2486456d0593d129219b3d804ebd6@openmailbox.org
On 2015-11-29 06:01, ludo@gnu.org wrote:
Toggle quote (20 lines)
> Cyril Roelandt <tipecaml@gmail.com> skribis:
>
>> On 11/18/2015 10:22 PM, Ludovic Courtès wrote:
>>> Could you double-check what’s happening, possibly running it through
>>> strace to see if it’s actually executing /usr/bin/python?
>>
>> I'm pretty sure it does that. It even loads libraries from the Debian
>> Python path, that is why it tries to import a Debian-specific module.
>
> I tried this:
>
> guix environment --container --ad-hoc weechat strace coreutils \
> findutils sed grep less --expose=$(which false)=/usr/bin/python
>
> which installs ‘false’ as /usr/bin/python, but it still works fine.
>
> Felipe, could you report the values of the ‘PYTHONPATH’, ‘PATH’, and
> ‘LD_LIBRARY_PATH’ variables on your system?
>

Oh, I didn't get Cyril's messages on the bug... But this is the
information:

PYTHONPATH and LD_LIBRARY_PATH are empty. PATH has this value:

/home/anonimo/.guix-profile/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games

Additional info:

$ guix package --search-paths
export PATH="/home/anonimo/.guix-profile/bin"


Toggle quote (6 lines)
> Are you able to work around the problem with:
>
> guix environment --ad-hoc weechat --pure -- weechat
>
> ?

WeeChat starts correctly if I run it that way.



--
Luis Felipe López Acevedo
L
L
Ludovic Courtès wrote on 29 Nov 2015 16:00
(name . Luis Felipe López Acevedo)(address . felipe.lopez@openmailbox.org)
87d1usluk2.fsf@gnu.org
Luis Felipe López Acevedo <felipe.lopez@openmailbox.org> skribis:

Toggle quote (2 lines)
> On 2015-11-29 06:01, ludo@gnu.org wrote:

[...]

Toggle quote (25 lines)
>> Felipe, could you report the values of the ‘PYTHONPATH’, ‘PATH’, and
>> ‘LD_LIBRARY_PATH’ variables on your system?
>>
>
> Oh, I didn't get Cyril's messages on the bug... But this is the
> information:
>
> PYTHONPATH and LD_LIBRARY_PATH are empty. PATH has this value:
>
> /home/anonimo/.guix-profile/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
>
> Additional info:
>
> $ guix package --search-paths
> export PATH="/home/anonimo/.guix-profile/bin"
>
>
>> Are you able to work around the problem with:
>>
>> guix environment --ad-hoc weechat --pure -- weechat
>>
>> ?
>
> WeeChat starts correctly if I run it that way.

What if you do:

guix package -i python-2
weechat

?

TIA,
Ludo’.
L
L
Luis Felipe López Acevedo wrote on 29 Nov 2015 16:44
(address . ludo@gnu.org)
0c9872eb09ab83e8259af73659aace90@openmailbox.org
On 2015-11-29 10:00, ludo@gnu.org wrote:
Toggle quote (37 lines)
> Luis Felipe López Acevedo <felipe.lopez@openmailbox.org> skribis:
>
>> On 2015-11-29 06:01, ludo@gnu.org wrote:
>
> [...]
>
>>> Felipe, could you report the values of the ‘PYTHONPATH’, ‘PATH’, and
>>> ‘LD_LIBRARY_PATH’ variables on your system?
>>>
>>
>> Oh, I didn't get Cyril's messages on the bug... But this is the
>> information:
>>
>> PYTHONPATH and LD_LIBRARY_PATH are empty. PATH has this value:
>>
>> /home/anonimo/.guix-profile/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
>>
>> Additional info:
>>
>> $ guix package --search-paths
>> export PATH="/home/anonimo/.guix-profile/bin"
>>
>>
>>> Are you able to work around the problem with:
>>>
>>> guix environment --ad-hoc weechat --pure -- weechat
>>>
>>> ?
>>
>> WeeChat starts correctly if I run it that way.
>
> What if you do:
>
> guix package -i python-2
> weechat
>

WeeChat starts correctly after doing that.


--
Luis Felipe López Acevedo
L
L
Ludovic Courtès wrote on 29 Nov 2015 19:20
(name . Luis Felipe López Acevedo)(address . felipe.lopez@openmailbox.org)
87wpt0is64.fsf@gnu.org
Luis Felipe López Acevedo <felipe.lopez@openmailbox.org> skribis:

Toggle quote (40 lines)
> On 2015-11-29 10:00, ludo@gnu.org wrote:
>> Luis Felipe López Acevedo <felipe.lopez@openmailbox.org> skribis:
>>
>>> On 2015-11-29 06:01, ludo@gnu.org wrote:
>>
>> [...]
>>
>>>> Felipe, could you report the values of the ‘PYTHONPATH’, ‘PATH’, and
>>>> ‘LD_LIBRARY_PATH’ variables on your system?
>>>>
>>>
>>> Oh, I didn't get Cyril's messages on the bug... But this is the
>>> information:
>>>
>>> PYTHONPATH and LD_LIBRARY_PATH are empty. PATH has this value:
>>>
>>> /home/anonimo/.guix-profile/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
>>>
>>> Additional info:
>>>
>>> $ guix package --search-paths
>>> export PATH="/home/anonimo/.guix-profile/bin"
>>>
>>>
>>>> Are you able to work around the problem with:
>>>>
>>>> guix environment --ad-hoc weechat --pure -- weechat
>>>>
>>>> ?
>>>
>>> WeeChat starts correctly if I run it that way.
>>
>> What if you do:
>>
>> guix package -i python-2
>> weechat
>>
>
> WeeChat starts correctly after doing that.

Hmm, hmm! In commit cb7bd0c, I fixed a build issue with the Python
plugin (it was statically linking libpython.a, which is undesirable.)

Could you check if that makes a difference, removing Python from your
profile?

Thanks for your help!

Ludo’.
L
L
Luis Felipe López Acevedo wrote on 5 Dec 2015 15:20
(address . ludo@gnu.org)
cb790adb2badbdb580ac97ac3fe5cf1c@openmailbox.org
On 2015-11-29 13:20, ludo@gnu.org wrote:
Toggle quote (54 lines)
> Luis Felipe López Acevedo <felipe.lopez@openmailbox.org> skribis:
>
>> On 2015-11-29 10:00, ludo@gnu.org wrote:
>>> Luis Felipe López Acevedo <felipe.lopez@openmailbox.org> skribis:
>>>
>>>> On 2015-11-29 06:01, ludo@gnu.org wrote:
>>>
>>> [...]
>>>
>>>>> Felipe, could you report the values of the ‘PYTHONPATH’, ‘PATH’,
>>>>> and
>>>>> ‘LD_LIBRARY_PATH’ variables on your system?
>>>>>
>>>>
>>>> Oh, I didn't get Cyril's messages on the bug... But this is the
>>>> information:
>>>>
>>>> PYTHONPATH and LD_LIBRARY_PATH are empty. PATH has this value:
>>>>
>>>> /home/anonimo/.guix-profile/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
>>>>
>>>> Additional info:
>>>>
>>>> $ guix package --search-paths
>>>> export PATH="/home/anonimo/.guix-profile/bin"
>>>>
>>>>
>>>>> Are you able to work around the problem with:
>>>>>
>>>>> guix environment --ad-hoc weechat --pure -- weechat
>>>>>
>>>>> ?
>>>>
>>>> WeeChat starts correctly if I run it that way.
>>>
>>> What if you do:
>>>
>>> guix package -i python-2
>>> weechat
>>>
>>
>> WeeChat starts correctly after doing that.
>
> Hmm, hmm! In commit cb7bd0c, I fixed a build issue with the Python
> plugin (it was statically linking libpython.a, which is undesirable.)
>
> Could you check if that makes a difference, removing Python from your
> profile?
>
> Thanks for your help!
>
> Ludo’.


- Removed Python and WeeChat from my profile.
- Did guix pull.
- Reinstalled WeeChat.

The error persists.


--
Luis Felipe López Acevedo
M
M
Marius Bakke wrote on 9 Feb 2017 01:05
(address . 21879@debbugs.gnu.org)
87wpd09qk3.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me
I noticed this as well on a foreign distro and pushed a workaround in
507809be152049dff26bffdb58e1a90b638f046b.

Didn't study the source enough to figure out why the substitution was
insufficient, but strace confirmed it was still looking in PATH even
though the strings were replaced.
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAlibskwACgkQoqBt8qM6
VPom6ggAgizSMfnllhvoIxUvSx1lmalHY7vGZd7zKjkRAZnndJH2oU4J9bQ4DTs3
RSNauo1nKACPNcz8CkiB4QqrU/0Iu2KpXuJhf7yAloXy4M/7/h8/H7bkh0ZweVoo
vsJwU7hoaVm1Ee0oyTf3UobrKl+S4mVcAR4a/PjaWuD2tF9LC3PhVwLmZ2c+yFyj
gRNuW4oolfG4LNaA7tt4dsXkbEX8OXn9xrRBYptiLXgLw3j7ECm6UzQwgoXcHrLS
TcLSpBEpuAhQO0MvL4t99NPsuUsQ7hwopnqy/1I8iLq45qTMl0XvUjJdeiQc29kq
dOrsaUNFbBrEq46e9/hp6ljEpfYV3A==
=oBDU
-----END PGP SIGNATURE-----

L
L
Ludovic Courtès wrote on 10 Feb 2017 13:52
(name . Marius Bakke)(address . mbakke@fastmail.com)(address . 21879-done@debbugs.gnu.org)
87inoidx8j.fsf@gnu.org
Marius Bakke <mbakke@fastmail.com> skribis:

Toggle quote (7 lines)
> I noticed this as well on a foreign distro and pushed a workaround in
> 507809be152049dff26bffdb58e1a90b638f046b.
>
> Didn't study the source enough to figure out why the substitution was
> insufficient, but strace confirmed it was still looking in PATH even
> though the strings were replaced.

Thanks for fixing it!

Make sure to email NNN-done@debbugs.gnu.org next time. ;-)

Ludo’.
Closed
S
S
sirgazil wrote on 25 Feb 2017 15:13
bug#21879: WeeChat does not start
(name . 21879@debbugs.gnu.org)(address . 21879@debbugs.gnu.org)
dwt16YcKGE1bjJLJls0XGvAGxrgvJwGFMc-ubqvaRgzoZhqU01QEHwVh0hNVmgp181kND2FU_EffsyBXwtrhHWqnz1YEqOnslResnWj9v4Y=@protonmail.com
Actually, I'm still experiencing this bug with Guix 0.12.0 on Debian 8.7.



---
Attachment: file
L
L
Leo Famulari wrote on 25 Feb 2017 16:59
(name . sirgazil)(address . lizagris@protonmail.com)(name . 21879@debbugs.gnu.org)(address . 21879@debbugs.gnu.org)
20170225155946.GA3496@jasmine
On Sat, Feb 25, 2017 at 09:13:48AM -0500, sirgazil wrote:
Toggle quote (2 lines)
> Actually, I'm still experiencing this bug with Guix 0.12.0 on Debian 8.7.

The commit that worked around the issue was applied after the 0.12.0
release. Have you updated your copy of Guix (with `guix pull`) since the
0.12.0 release?
S
S
sirgazil wrote on 25 Feb 2017 17:35
(name . Leo Famulari)(address . leo@famulari.name)(name . 21879@debbugs.gnu.org)(address . 21879@debbugs.gnu.org)
BCtKI_Etn6pyhn_1__Lc8M-8lqtfIthAaUG8kPxtyzFGq6Tdm8IGdldPoN4l8s-bF2tACbibhAGhKhJZPUF_r-XUEBMUbWhWWIAf9zxyWyQ=@protonmail.com
-------- Original Message --------
Subject: Re: bug#21879: WeeChat does not start
Local Time: 25 de febrero de 2017 10:59 AM
UTC Time: 25 de febrero de 2017 15:59
From: leo@famulari.name
To: sirgazil <lizagris@protonmail.com>
21879@debbugs.gnu.org <21879@debbugs.gnu.org>

On Sat, Feb 25, 2017 at 09:13:48AM -0500, sirgazil wrote:
Toggle quote (2 lines)
> Actually, I'm still experiencing this bug with Guix 0.12.0 on Debian 8.7.

The commit that worked around the issue was applied after the 0.12.0
release. Have you updated your copy of Guix (with `guix pull`) since the
0.12.0 release?

Thanks, Leo. I installed WeeChat after "guix pull" and it worked.
Attachment: file
N
N
ng0 wrote on 25 Feb 2017 17:54
(name . sirgazil)(address . lizagris@protonmail.com)
20170225165346.6t5kacewgjvjmht7@wasp
On 17-02-25 11:35:45, sirgazil wrote:
Toggle quote (17 lines)
> -------- Original Message --------
> Subject: Re: bug#21879: WeeChat does not start
> Local Time: 25 de febrero de 2017 10:59 AM
> UTC Time: 25 de febrero de 2017 15:59
> From: leo@famulari.name
> To: sirgazil <lizagris@protonmail.com>
> 21879@debbugs.gnu.org <21879@debbugs.gnu.org>
>
> On Sat, Feb 25, 2017 at 09:13:48AM -0500, sirgazil wrote:
> > Actually, I'm still experiencing this bug with Guix 0.12.0 on Debian 8.7.
>
> The commit that worked around the issue was applied after the 0.12.0
> release. Have you updated your copy of Guix (with `guix pull`) since the
> 0.12.0 release?
>
> Thanks, Leo. I installed WeeChat after "guix pull" and it worked.

A while ago Leo or someone else uponed a bug on improving the
Documentation about the relevance and usage of package+system updates.

It seems to me as if that's the case here, the documentation not being
clear enough.
Do you have any improvement suggestions?

Thanks.
S
S
sirgazil wrote on 1 Mar 2017 20:41
(name . ng0)(address . contact.ng0@cryptolab.net)
U3iX2546oIDma4vbWotPYGQKG-IDO_TwAepdzWXZ9J6o3FTbeE7femGoFrLAaYybfJ7pCIS_lNxYXbmKejDwp5jc5DvKxxpZ_ZOpmfiO_W4=@protonmail.com
-------- Original Message --------
Subject: Re: bug#21879: WeeChat does not start
Local Time: 25 de febrero de 2017 11:52 AM
UTC Time: 25 de febrero de 2017 16:52
From: contact.ng0@cryptolab.net
To: sirgazil <lizagris@protonmail.com>
Leo Famulari <leo@famulari.name>, 21879@debbugs.gnu.org <21879@debbugs.gnu.org>

On 17-02-25 11:35:45, sirgazil wrote:
Toggle quote (17 lines)
> -------- Original Message --------
> Subject: Re: bug#21879: WeeChat does not start
> Local Time: 25 de febrero de 2017 10:59 AM
> UTC Time: 25 de febrero de 2017 15:59
> From: leo@famulari.name
> To: sirgazil <lizagris@protonmail.com>
> 21879@debbugs.gnu.org <21879@debbugs.gnu.org>
>
> On Sat, Feb 25, 2017 at 09:13:48AM -0500, sirgazil wrote:
> > Actually, I'm still experiencing this bug with Guix 0.12.0 on Debian 8.7.
>
> The commit that worked around the issue was applied after the 0.12.0
> release. Have you updated your copy of Guix (with `guix pull`) since the
> 0.12.0 release?
>
> Thanks, Leo. I installed WeeChat after "guix pull" and it worked.

A while ago Leo or someone else uponed a bug on improving the
Documentation about the relevance and usage of package+system updates.

It seems to me as if that's the case here, the documentation not being
clear enough.
Do you have any improvement suggestions?

Thanks.

Good! Documentation is one part. I'll read the bug you mention (https://debbugs.gnu.org/cgi/bugreport.cgi?bug=25852)and see if I have anything to contribute.

Thank you, ng0.
Attachment: file
?