Am 06.11.2017 um 22:29 schrieb Marius Bakke:
>> Seems like my message did not go through:
>>
>> This change will not solve out problem!
>>
>> PEP 552 proposes a new file-format for .pyc file and a hash-based
>> mechanism for checking if the .pyc file is recent. This means, you can
>> not backport t
Efraim Flashner skribis:
> /gnu/store/mivyzxijvxh44g2r39071sm89vm9h0n6-make-boot0-4.2.1/bin/make -C
> test/ tests
> make[1]: Entering directory '/tmp/guix-build-acl-2.2.52.drv-0/acl-2.2.52/test'
> *** malformed-restore.test ***
> Unescaped left brace in regex is illegal here in regex; marked by
Mark H Weaver skribis:
> Hi,
>
> l...@gnu.org (Ludovic Courtès) writes:
>
>> Dave Love skribis:
>>
>>> Efraim Flashner writes:
>>>
On Tue, Oct 31, 2017 at 02:00:35PM +0100, Vincent Legoll wrote:
> Hello,
>
> On Tue, Oct 31, 2017 at 1:35 PM, Dave Love wrote:
> > Why is lin
Am 07.11.2017 um 10:55 schrieb Eric Myhre:
> iirc there is even an env var you can set -- PYTHONDONTWRITEBYTECODE=anyvalue
> -- which will prevent these .pyc files from ever being generated.
>
> There are no ill effects to this I have ever noticed in several years of
> having it set in my bashrc.
Hello,
myglc2 skribis:
> My system recently broke when I did an upgrade. I reported what I
> thought was a bug (bug#29072) but it turned out that, because qemu
> package code had been moved, my system configuration had become broken
> ;-(
It should be noted that you were using a “developer setu
Dave Love skribis:
> Ludovic Courtès writes:
>
>>> It looks to me as if it would often help significantly, e.g. when a
>>> pkg-config file, or something else sucks in a load of stuff that's
>>> irrelevant for running the package. (Separating :lib and needing that
>>> for building means you need
No one else mentioned it after the acl tests were enabled
On November 7, 2017 11:54:47 AM GMT+02:00, l...@gnu.org wrote:
>Efraim Flashner skribis:
>
>> /gnu/store/mivyzxijvxh44g2r39071sm89vm9h0n6-make-boot0-4.2.1/bin/make
>-C test/ tests
>> make[1]: Entering directory
>'/tmp/guix-build-acl-2.2.52
Le 2017-11-07 02:56, myglc2 a écrit :
Please note: these replies are separated by topics in an effort to make
the
threads more topical ...
On 11/06/2017 at 17:16 Leo Famulari writes:
On Mon, Nov 06, 2017 at 03:12:11PM -0500, myglc2 wrote:
[...]
Guix config errors are reported as raw scheme
Am 07.11.2017 um 12:05 schrieb julien lepiller:
> Since we encourage users to use use-package-modules etc, I think it's
> better
> to catch this error and explain it to users as soon as it happens.
> It's more
> friendly for users than a troubleshooting section in the manual.
+1
Thanks for propos
To clarify, I haven't built anything on core-updates yet, so I don't know if
this will fail on x86_64. I'm still cherry picking things to master in order to
test.
Sorry for top-posting
Original Message
From: Efraim Flashner
Sent: November 7, 2017 6:05:19 AM EST
To: l...@gnu.
Le 2017-11-07 13:52, Hartmut Goebel a écrit :
Am 07.11.2017 um 12:05 schrieb julien lepiller:
Since we encourage users to use use-package-modules etc, I think it's
better
to catch this error and explain it to users as soon as it happens.
It's more
friendly for users than a troubleshooting sectio
Hello Guix!
Since we didn’t get a devroom this time in spite of the efforts of
Manolis and Pjotr, what about holding a Guix meeting let’s say on Friday
before FOSDEM (Feb. 2nd, in Brussels)?
We could meet for the whole day, in a place that remains to be defined,
to discuss about all things Guix{,
iirc there is even an env var you can set -- PYTHONDONTWRITEBYTECODE=anyvalue
-- which will prevent these .pyc files from ever being generated.
There are no ill effects to this I have ever noticed in several years of having
it set in my bashrc.
On 6 November 2017 12:47:03 CET, "Gábor Boskovits"
On 11/07/2017 at 14:13 julien lepiller writes:
> Le 2017-11-07 13:52, Hartmut Goebel a écrit :
>> Am 07.11.2017 um 12:05 schrieb julien lepiller:
>>> Since we encourage users to use use-package-modules etc, I think it's
>>> better
>>> to catch this error and explain it to users as soon as it happe
Ludovic Courtès transcribed 1.8K bytes:
> Hello Guix!
>
> Since we didn’t get a devroom this time in spite of the efforts of
> Manolis and Pjotr, what about holding a Guix meeting let’s say on Friday
> before FOSDEM (Feb. 2nd, in Brussels)?
>
> We could meet for the whole day, in a place that rem
Le 2017-11-07 14:39, l...@gnu.org a écrit :
Hello Guix!
Since we didn’t get a devroom this time in spite of the efforts of
Manolis and Pjotr, what about holding a Guix meeting let’s say on
Friday
before FOSDEM (Feb. 2nd, in Brussels)?
We could meet for the whole day, in a place that remains t
Am 07.11.2017 um 14:13 schrieb julien lepiller:
> This new version outputs something like this :
Thanks
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goe...@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
On 11/07/2017 at 14:39 Ludovic Courtès writes:
> Hello Guix!
>
> Since we didn’t get a devroom this time in spite of the efforts of
> Manolis and Pjotr, what about holding a Guix meeting let’s say on Friday
> before FOSDEM (Feb. 2nd, in Brussels)?
>
> We could meet for the whole day, in a place th
Le 2017-11-07 15:11, myglc2 a écrit :
On 11/07/2017 at 14:13 julien lepiller writes:
This new version outputs something like this :
guix system: error: failed to load 'vm-image.tmpl':
vm-image.tmpl:6:0: vm-image.tmpl:6:0: Package module "abc" does not
exist.
Check the "use-package-modules" li
On 11/07/2017 at 15:52 julien lepiller writes:
> Le 2017-11-07 15:11, myglc2 a écrit :
>> On 11/07/2017 at 14:13 julien lepiller writes:
>>>
>>> This new version outputs something like this :
>>>
>>>
>>> guix system: error: failed to load 'vm-image.tmpl':
>>> vm-image.tmpl:6:0: vm-image.tmpl:6:0:
Le 2017-11-07 16:59, myglc2 a écrit :
On 11/07/2017 at 15:52 julien lepiller writes:
Maybe that's too much?
Not for me. Looks great! Just a couple minor suggestions:
1) How about narrowing search to locations like this:
Hint: You may use `guix package --show=foo | grep location` to search
f
Count me in!
There are many cheap hotels in Brussels and also airbnb is fine in my
experience. Food is great too and, last but not least, FOSDEM is
plainly awesome. 30+ tracks means there is something for everyone. And
speakers and visitors are all hackers.
There may be a few Guix talks, but beca
Ludovic Courtès writes:
> Since we didn’t get a devroom this time in spite of the efforts of
> Manolis and Pjotr, what about holding a Guix meeting let’s say on Friday
> before FOSDEM (Feb. 2nd, in Brussels)?
> Who would be willing to join? (You can reply privately if you prefer.)
Yes, I'd like
I have seen, that several package definitions add write permissions to
files in the build.
I just had a package, where this issue came up. (python-networkx2)
The first issue I had was that in the build log the filenames were
truncated in the stacktrace.
Do we have any mean to avoid that? It would
Hartmut Goebel writes:
> Am 06.11.2017 um 22:29 schrieb Marius Bakke:
>>> Seems like my message did not go through:
>>>
>>> This change will not solve out problem!
>>>
>>> PEP 552 proposes a new file-format for .pyc file and a hash-based
>>> mechanism for checking if the .pyc file is recent. This
Ludovic Courtès writes:
> Hello Guix!
>
> Since we didn’t get a devroom this time in spite of the efforts of
> Manolis and Pjotr, what about holding a Guix meeting let’s say on Friday
> before FOSDEM (Feb. 2nd, in Brussels)?
>
> We could meet for the whole day, in a place that remains to be defin
Roel Janssen writes:
> Ludovic Courtès writes:
>
>> Hello Guix!
>>
>> Since we didn’t get a devroom this time in spite of the efforts of
>> Manolis and Pjotr, what about holding a Guix meeting let’s say on Friday
>> before FOSDEM (Feb. 2nd, in Brussels)?
>>
>> We could meet for the whole day, in
On 11/06/2017 at 17:16 Leo Famulari writes:
> On Mon, Nov 06, 2017 at 03:12:11PM -0500, myglc2 wrote:
>> My system recently broke when I did an upgrade.
[...] replied to separately
>> because qemu
>> package code had been moved, my system configuration had become broken
>> ;-(
>>
[...] replied to
Le Tue, 07 Nov 2017 13:06:41 -0500,
myglc2 a écrit :
> On 11/07/2017 at 17:25 julien lepiller writes:
>
> > Le 2017-11-07 16:59, myglc2 a écrit :
> >> On 11/07/2017 at 15:52 julien lepiller writes:
> >>>
> >>> Maybe that's too much?
> >>
> >> Not for me. Looks great! Just a couple minor su
With regard to talks we should limit the total time for that - say 2-3
hours total. And have the rest of the day free flowing discussion and
hacking. Talks are useful, but I think the real impact will be to be
together and sit down and inspire each other and flesh out next year's
projects and prior
Hello!
You’re too fast! :-)
julien lepiller skribis:
> +(define (import-error type module syntax)
> + (define package-hint
> +(string-append
> + "Hint: You may use `guix package --show=foo | grep location` to
> search\n"
> + "Hint: for foo's location.\n"
> + "Hint: If you
myglc2 skribis:
> I am thinking of coming from Boston on the cheap to finally put a face
> on all you helpful Guixers, and maybe go to FOSDEM.
>
> My personal interests are HPC, reproducible research, Cuirass, and
> "user-level" use of git pull instead of guix pull.
Cool!
> Are you saying there
On 11/07/2017 at 22:27 Julien Lepiller writes:
> Le Tue, 07 Nov 2017 13:06:41 -0500,
> myglc2 a écrit :
>
>> On 11/07/2017 at 17:25 julien lepiller writes:
>>
>> > Le 2017-11-07 16:59, myglc2 a écrit :
>> >> On 11/07/2017 at 15:52 julien lepiller writes:
>> >>>
>> >>> Maybe that's too much?
On 11/07/2017 at 23:47 Ludovic Courtès writes:
> Hello!
>
> You’re too fast! :-)
>
> julien lepiller skribis:
>
[...]
>
> I’d propose a variant of it, see below. With this, one gets a message
> like:
>
> /tmp/config.scm:6:0: module (gnu packages foobar) could not be found
>
> where line 6 is:
Ludovic Courtès writes:
> Who would be willing to join?
I’ll be there! All topics sound fun to me, and I find hacking sessions
very useful to fix annoying problems quickly.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
Hi Folks,
I'm having some trouble packaging Jitsi (a VoIP client written in Java).
The attached patch adds the package "jitsi", which completes the "build"
phase, but fails as below. Ignoring for now that Jitsi is bundling a whole lot
of dependencies, can someone help me understand what’s going on
On Tue, 07 Nov 2017 14:39:53 +0100
l...@gnu.org (Ludovic Courtès) wrote:
> Hello Guix!
>
> Since we didn’t get a devroom this time in spite of the efforts of
> Manolis and Pjotr, what about holding a Guix meeting let’s say on Friday
> before FOSDEM (Feb. 2nd, in Brussels)?
>
> We could meet for
37 matches
Mail list logo
