Hi,
On Wed, 05 Oct 2022 at 12:03, Ludovic Courtès wrote:
> Ricardo Wurmus skribis:
>
>> In my scenario I have two machines, one building stuff the other only
>> substituting. The serving machine would be the one deciding whether to
>> enforce substitutability or not.
>
> An is it too expensive
Ludovic Courtès writes:
> We need to plan and coordinate. Releases have to be a group effort;
> some of the most important work won’t be coding but coordination.
> Coordination is key. I don’t think I should be spearheading that
> effort, but I’m happy to be part of it.
>
> Who’s ready to comm
On 06-10-2022 20:34, Maxime Devos wrote:
-- I miss
Nevermind this, just some writing error during composing the message
OpenPGP_0x49E3EE22191725EE.asc
Description: OpenPGP public key
OpenPGP_signature
Description: OpenPGP digital signature
zimoun skribis:
> In the same spirit, I have:
[...]
> (defun-bug->url my/guix-issues "http://issues.guix.gnu.org/issue/";
> "Add URL of bug NUMBER to `kill-ring'.")
> (defun-bug->url my/guix-debbugs
> "https://debbugs.gnu.org/cgi/bugreport.cgi?bug=";
> "Add (old) URL of bug
Hi,
Julien Lepiller skribis:
> I'll take care of the cranslations (notifying translators, ensuring string
> freeze is respected, …)
Great, thanks.
> We need to be careful not to start the stsing freeze step too early. Last
> time (or previous?) we started a week before the scheduled release
Hi,
Maxime Devos skribis:
> I have some unapplied security patches (from before the latest release
> (1.3.0) (!)) (more precisely, some patches that prepare for actually
> being able to write the security patches, once the preparation patches
> are merged, the actual security fixes should be rel
On 07-10-2022 11:50, Ludovic Courtès wrote:
Hi,
Maxime Devos skribis:
I have some unapplied security patches (from before the latest release
(1.3.0) (!)) (more precisely, some patches that prepare for actually
being able to write the security patches, once the preparation patches
are merged
Hi,
Efraim Flashner skribis:
> I'd like to comment on armhf for a moment. My memory is a but rusty, but
> I'm pretty sure that in December of 2021 mesa was bumped from 21.2.x to
> 21.3.x, and at that time it stopped building on/for armhf. I noticed in
> May of 2022 (5 months later) and got the b
Hi,
Christopher Baines skribis:
> Ludovic Courtès writes:
>
>> We need to plan and coordinate. Releases have to be a group effort;
>> some of the most important work won’t be coding but coordination.
>> Coordination is key. I don’t think I should be spearheading that
>> effort, but I’m happy
It depends on the language, I'd say a week is good, maybe less as long as we
can include a week-end (maybe it's personal, but I find more time to contribute
in the week-ends).
Le 7 octobre 2022 11:49:21 GMT+02:00, "Ludovic Courtès" a écrit :
>Hi,
>
>Julien Lepiller skribis:
>
>> I'll take care
Hi,
On jeu., 15 sept. 2022 at 19:10, jgart wrote:
> Hi does anyone know why guix import does not insert newlines anymore?
You mean this,
--8<---cut here---start->8---
(define-public rust-snafu-0.7
[...]
(license (list license:expat license:asl2.0
(d
On Fri, 07 Oct 2022 13:24:17 +0200 zimoun wrote:
> Right?
Yup!
zimoun writes:
> On Wed, 05 Oct 2022 at 12:03, Ludovic Courtès wrote:
>> Ricardo Wurmus skribis:
>>
>>> In my scenario I have two machines, one building stuff the other only
>>> substituting. The serving machine would be the one deciding whether to
>>> enforce substitutability or not.
>>
>> An
Hi,
What's are policy for packaging docs deps?
For example, this package has docs deps:
https://github.com/m-lundberg/simple-pid/blob/master/docs/requirements.txt
Should those be packaged and included also in the Guix package definition?
Is our policy for packaging docs deps documented somewhe
I don't think there's a specific policy, but our packages tend to enable most
optional dependencies and docs are always useful, so I'd package doc
dependencies too.
Le 8 octobre 2022 05:08:34 GMT+02:00, jgart a écrit :
>Hi,
>
>What's are policy for packaging docs deps?
>
>For example, this pack
15 matches
Mail list logo
