Hi Ricardo,
Ricardo Wurmus writes:
> Maxim Cournoyer writes:
>> I have a Python mass update branch I've been developing, holding it back
>> because I kept finding breakage (whether caused by my changes or
>> already there). There's now 200 commits in it, including an update to
>> virtualenv an
Tomas Volf <~@wolfsden.cz> writes:
> Felix Lechner via "Development of GNU Guix and the GNU System
> distribution." writes:
>
>> Hi Cayetano,
>>
>> On Wed, Dec 18 2024, Cayetano Santos wrote:
>>
>>> (more or less) official mirrors for main guix repo at savannah ?
>>
>> I maintain a lazy mirror on
Felix Lechner via "Development of GNU Guix and the GNU System
distribution." writes:
> Hi Cayetano,
>
> On Wed, Dec 18 2024, Cayetano Santos wrote:
>
>> (more or less) official mirrors for main guix repo at savannah ?
>
> I maintain a lazy mirror on Codeberg. [1] The effort is manual because
> Co
On 2024-12-15, Efraim Flashner wrote:
> On Fri, Dec 13, 2024 at 01:03:05PM +0100, Ricardo Wurmus wrote:
>> > - devel as the branch for developments, master for releases and
>> > security/bug fixes
>>
>> Changing the branching model is very difficult to do. I think it is
>> better to ignore bran
Suhail Singh writes:
> The issue, as I see it, is the time commitment required from the
> release-team.
Correction, the issues (IMO) are (in no particular order):
1. the timespan (several weeks)
2. uncertainty around total effort
3. amount of manual effort involved
It's unclear which of the thr
Ludovic Courtès writes:
> I believe what we need is a release team with rotating duties. That
> is, a bunch of 3–5 people commit to doing the work leading to 1.5.0;
> then a new team (possibly with overlap) takes over for the next
> version, and so on.
The issue, as I see it, is the time commit
Hello,
Felix Lechner via "Development of GNU Guix and the GNU System
distribution." skribis:
> On Wed, Dec 18 2024, Cayetano Santos wrote:
>
>> (more or less) official mirrors for main guix repo at savannah ?
>
> I maintain a lazy mirror on Codeberg. [1] The effort is manual because
> Codeberg n
Hi,
Maxim Cournoyer skribis:
> Efraim Flashner writes:
>
>> On Sun, Dec 15, 2024 at 03:21:44PM -0500, Suhail Singh wrote:
>>> Ricardo Wurmus writes:
>>>
>>> > Efraim Flashner writes:
>>> >
>>> >> Since, IMO, the major uses of the actual guix package is for the daemon
>>> >> and the installer,
>mer. 18 déc. 2024 at 06:49, Felix Lechner wrote:
> Hi Cayetano,
>
> On Wed, Dec 18 2024, Cayetano Santos wrote:
>
>> (more or less) official mirrors for main guix repo at savannah ?
>
> I maintain a lazy mirror on Codeberg. [1] The effort is manual because
> Codeberg no longer offers automatic
Hi Cayetano,
On Wed, Dec 18 2024, Cayetano Santos wrote:
> (more or less) official mirrors for main guix repo at savannah ?
I maintain a lazy mirror on Codeberg. [1] The effort is manual because
Codeberg no longer offers automatic pulls, but I can talk to them again.
The repo should really have
Hola Guix,
Have we ever consider the need of (more or less) official mirrors for
main guix repo at savannah ? I’m convinced this might be useful. I’m
thinking about a hook for pushing to additional mirrors on new
commits.
My concern is about automatically building container images remo
Hi,
Ludovic Courtès writes:
[...]
>> Perhaps we should set the default parallel-build? to #f in the
>> guile-build-system at least in the meantime, with a prominent comment as
>> to why and a reference to the upstream issue? Many Guile packages use
>> the gnu-build-system so that wouldn't cove
12 matches
Mail list logo
