corrupt file on mirror?
Hi,
I just came across this, not sure what to make of it:
Found valid signature for
/gnu/store/dhc2iy059hi91fk55dcv79z09kp6500y-gcc-5.4.0-lib
From
https://mirror.hydra.gnu.org/guix/nar/gzip/dhc2iy059hi91fk55dcv79z09kp6500y-gcc-5.4.0-lib
Downloading dhc2iy...-gcc-5.4.0-lib (30.1MiB installed)...
gcc-5.4.0-lib 189KiB/s 00:01 | 187KiB transferred
gzip: stdin: invalid compressed data--crc error
gzip: stdin: invalid compressed data--length error
guix substitute: error: corrupt input while restoring
'/gnu/store/dhc2iy059hi91fk55dcv79z09kp6500y-gcc-5.4.0-lib/lib/gcc/x86_64-unknown-linux-gnu/5.4.0/include/cilk/cilk_api.h'
from #{read pipe}#
Any ideas?
Thanks, ben
Re: trytond
Am 05.04.2017 um 22:03 schrieb Catonano: > > > Has the daemon environment anything to do with this ? Be the source with you;: https://hg.tryton.org/trytond/file/4.2.3/trytond/backend/sqlite/database.py#l261 So it seem the database name needs to be ":memory:" or or you need to use a full-qualified path to avoid the ned to configure the trytond. -- Regards Hartmut Goebel | Hartmut Goebel | h.goe...@crazy-compilers.com | | www.crazy-compilers.com | compilers which you thought are impossible |
Re: torsocks works with wget but fails git-clone: "unable to lookup symbols in libc.so.6"
Mekeor Melire transcribed 1.0K bytes: > > Problem > === > > This works fine: > > $ torsocks wget http://github.com/mekeor/config > > This fails: > > $ torsocks git clone http://github.com/mekeor/config > 1491426097 ERROR torsocks[25849]: Unable to lookup symbols in > libc.so.6((null)) (in init_libc_symbols() at torsocks.c:239) > > Torifying browsers like netsurf-gtk, surf, w3m either also fail or don't > succeed. Using "torify" instead of "torsocks" results in the same. > > > Information > === > > My config.scm contains: > > (tor-service) That's not enough for torify (torification? to use torsocks / the SOCKS5 of tor) of applications. As I told you earlier, you need a SOCKSPort, like so: (services (cons* (tor-service (plain-file "torrc" "SocksPort 127.0.0.1:9050\n" This can be extended any other values you can find in "man torrc" as long as you end the lines with "\n". The (tor-service) is mostly just usable for offering onion services, and we should document that the default is to leave it up to the person using the system to configure more behavior. > My whole config is available at: > > https://github.com/mekeor/config/blob/master/etc/guix/config.scm > > The error is printed on this line in the code of torsocks: > > https://github.com/dgoulet/torsocks/blob/master/src/lib/torsocks.c#L239 > > I'm using version 20170405.20 of Guix (on GuixSD). > > > Question > > > Why does torsocks work with wget but doesn't work with git-clone? What > does the error mean? What does it have to do with libc? Is anybody able > to reproduce this? > > -- > mekeor ~ EDD3 DFFA 76F6 11C0 145F 9A99 AC85 BAD8 A2F8 C868 >
torsocks works with wget but fails git-clone: "unable to lookup symbols in libc.so.6"
Problem === This works fine: $ torsocks wget http://github.com/mekeor/config This fails: $ torsocks git clone http://github.com/mekeor/config 1491426097 ERROR torsocks[25849]: Unable to lookup symbols in libc.so.6((null)) (in init_libc_symbols() at torsocks.c:239) Torifying browsers like netsurf-gtk, surf, w3m either also fail or don't succeed. Using "torify" instead of "torsocks" results in the same. Information === My config.scm contains: (tor-service) My whole config is available at: https://github.com/mekeor/config/blob/master/etc/guix/config.scm The error is printed on this line in the code of torsocks: https://github.com/dgoulet/torsocks/blob/master/src/lib/torsocks.c#L239 I'm using version 20170405.20 of Guix (on GuixSD). Question Why does torsocks work with wget but doesn't work with git-clone? What does the error mean? What does it have to do with libc? Is anybody able to reproduce this? -- mekeor ~ EDD3 DFFA 76F6 11C0 145F 9A99 AC85 BAD8 A2F8 C868
Re: trytond
Catonano transcribed 3.1K bytes:
> In trying to build trytond (mind the d) 4.2.3, tests fail and I see this
> message
Heh. I finally get what you tried to tell me a couple of weeks ago when
we talked about GNU Health.. so tryton is different from what I am
working on :)
> ==
> ERROR: setUpClass (trytond.tests.test_copy.CopyTestCase)
> --
> Traceback (most recent call last):
> File
> "/tmp/guix-build-python2-trytond-4.2.3.drv-1/trytond-4.2.3/trytond/tests/test_copy.py",
> line 15, in setUpClass
> activate_module('tests')
> File
> "/tmp/guix-build-python2-trytond-4.2.3.drv-1/trytond-4.2.3/trytond/tests/test_tryton.py",
> line 47, in activate_module
> create_db()
> File
> "/tmp/guix-build-python2-trytond-4.2.3.drv-1/trytond-4.2.3/trytond/tests/test_tryton.py",
> line 398, in create_db
> transaction.database.create(transaction.connection, name)
> File
> "/tmp/guix-build-python2-trytond-4.2.3.drv-1/trytond-4.2.3/trytond/backend/sqlite/database.py",
> line 269, in create
> with sqlite.connect(path) as conn:
> OperationalError: unable to open database file
>
> This "unable to open database file" appears tens of times
>
> The tests use pysqlite (which is python@2 only)
>
> Has the daemon environment anything to do with this ?
Most likely, I think the tests want to connect to an sqlite database.
But I see that you use an environmental variable already, so without
looking into the application itself I can't reply anything useful.
Someone else might have more insights.
> The package is here
> http://paste.lisp.org/display/343575
>
> Thanks in advance
trytond
In trying to build trytond (mind the d) 4.2.3, tests fail and I see this
message
==
ERROR: setUpClass (trytond.tests.test_copy.CopyTestCase)
--
Traceback (most recent call last):
File
"/tmp/guix-build-python2-trytond-4.2.3.drv-1/trytond-4.2.3/trytond/tests/test_copy.py",
line 15, in setUpClass
activate_module('tests')
File
"/tmp/guix-build-python2-trytond-4.2.3.drv-1/trytond-4.2.3/trytond/tests/test_tryton.py",
line 47, in activate_module
create_db()
File
"/tmp/guix-build-python2-trytond-4.2.3.drv-1/trytond-4.2.3/trytond/tests/test_tryton.py",
line 398, in create_db
transaction.database.create(transaction.connection, name)
File
"/tmp/guix-build-python2-trytond-4.2.3.drv-1/trytond-4.2.3/trytond/backend/sqlite/database.py",
line 269, in create
with sqlite.connect(path) as conn:
OperationalError: unable to open database file
This "unable to open database file" appears tens of times
The tests use pysqlite (which is python@2 only)
Has the daemon environment anything to do with this ?
The package is here
http://paste.lisp.org/display/343575
Thanks in advance
Re: mumble issues with pulseaudio
On 04/05/2017 11:57 AM, ng0 wrote: Aren't we just talking about GuixSD here? In most cases every non-GuixSD system will already have a profile set up. Just as a sidenote: ALSA also has global configuration files, e.g. here on ubuntu they live in: /usr/share/alsa/alsa.conf and /usr/share/alsa/alsa.conf.d/ On ubuntu the default ALSA device is routed through PA without a user having a ~/.asoundrc. That latter file is used for further customization by the user. It's been a while since I spent a lot of time studying the interplay of all of ALSA's config files, so where exactly ubuntu specifies the "pulse" virtual PCM device as "default" right now eludes me. Regards, Flo -- https://fps.io
Re: mumble issues with pulseaudio
Alex Kost transcribed 0.5K bytes: > Ludovic Courtès (2017-04-03 23:18 +0200) wrote: > > [...] > > I was talking of the account skeletons, i.e., the files that are > > automatically installed in the home directory of a newly-created account > > (see (gnu system shadow)). These files can always be modified or > > removed by the user afterwards. > > > > Still I understand that choosing a default is always difficult. :-) > > OTOH, AFAIK PulseAudio is the default choice on most distros these days, > so it's probably OK to default to it. > > -- > Alex > Aren't we just talking about GuixSD here? In most cases every non-GuixSD system will already have a profile set up.
Re: mumble issues with pulseaudio
Ludovic Courtès (2017-04-03 23:18 +0200) wrote: [...] > I was talking of the account skeletons, i.e., the files that are > automatically installed in the home directory of a newly-created account > (see (gnu system shadow)). These files can always be modified or > removed by the user afterwards. > > Still I understand that choosing a default is always difficult. :-) OTOH, AFAIK PulseAudio is the default choice on most distros these days, so it's probably OK to default to it. -- Alex
