On Sat, 2021-03-06 at 06:09 +0100, Léo Le Bouter wrote:
> Hello!
>
> After commit:
> https://git.savannah.gnu.org/cgit/guix.git/commit/?id=6f873731a030dd7ecbd8a5e756b38b26306f6966
>
> This happened:
> https://ci.guix.gnu.org/build/369538/details
>
> I made the commit, and not sure what to do
Hello!
After commit:
https://git.savannah.gnu.org/cgit/guix.git/commit/?id=6f873731a030dd7ecbd8a5e756b38b26306f6966
This happened:
https://ci.guix.gnu.org/build/369538/details
I made the commit, and not sure what to do here.
The test suite seems to fail on i686..?
Sorry for any inconvenience
Hi Leo,
On Fri, 05 Mar 2021 at 15:19, Leo Famulari wrote:
> On Wed, Mar 03, 2021 at 01:51:51PM -0500, Leo Famulari wrote:
>> * Update tzdata
>>
>> * Ungraft
>
> I've pushed commits that accomplish these tasks to a 'wip-next-release'
> branch:
Cool!
>
Hi Leo,
On Fri, 05 Mar 2021 at 15:58, Leo Famulari wrote:
> Now, ci.guix.gnu.org is working well, and we can work more quickly and
> confidently. However, my experience in the past tells me that 6 weeks is
> not quite long enough to complete the branch and validate it for a
> release. But, it
Hey,
This has been on my mind for a while, as I wonder what effect it has on
users fetching substitues.
The narinfo caching as I understand it works as follows:
Default success TTL => 36 hours
Negative TTL=> 1 hour
Transient error TTL => 10 minutes
I'm ignoring the success TTL, I'm
On Fri, Mar 05, 2021 at 06:54:05AM +0100, Bengt Richter wrote:
> Hi,
>
> Not so usual to be switching rc kernels for guix I suppose, but
> this looked worth mentioning anyway:
>
> LWN archive link [1]
>
>
On Fri, Mar 05, 2021 at 09:20:10PM +0100, zimoun wrote:
> On #guix, I proposed [1] without an answer (yet :-)):
>
> what is the current blocking for merging core-updates? I mean
> the last merge seems from May 2020. If all the branch is not in
> a state to be mergeable,
Hi,
On Fri, 05 Mar 2021 at 14:27, Leo Famulari wrote:
> On Fri, Mar 05, 2021 at 03:31:22PM +0100, Andreas Enge wrote:
>> it would be nice if core-updates could be part of the release. I have
>> been waiting for gmp, mpfr and mpc to appear in master. In particular
>> mpfr-4.1.0 has been released
On Wed, Mar 03, 2021 at 03:16:29PM +0100, Ludovic Courtès wrote:
> zimoun skribis:
>
> > I would like to propose to release on April 18th (anniversary of the
> > "Initial commit."). It could be 1.2.1 or 1.3. Well, from my
> > understanding, if core-updates is merged it makes sense to have 1.3
On Wed, Mar 03, 2021 at 01:51:51PM -0500, Leo Famulari wrote:
> * Update tzdata
>
> * Ungraft
I've pushed commits that accomplish these tasks to a 'wip-next-release'
branch:
https://git.savannah.gnu.org/cgit/guix.git/log/?h=wip-next-release
For now, the branch is a "work in progress" (WIP) and
On Fri, Mar 05, 2021 at 03:31:22PM +0100, Andreas Enge wrote:
> it would be nice if core-updates could be part of the release. I have
> been waiting for gmp, mpfr and mpc to appear in master. In particular
> mpfr-4.1.0 has been released in July 2020, and I have updated it in
> core-updates in the
Hi Chris,
On Fri, 05 Mar 2021 at 10:34, Christopher Lemmer Webber
wrote:
> zimoun writes:
>> On Thu, 04 Mar 2021 at 16:05, Christopher Lemmer Webber
>> wrote:
>>
>>> I wonder if we should formalize it. What about adding a section to the
>>> "Contributing" section of the manual explaining
zimoun writes:
> Hi, Chris,
>
> On Thu, 04 Mar 2021 at 16:05, Christopher Lemmer Webber
> wrote:
>
>> I wonder if we should formalize it. What about adding a section to the
>> "Contributing" section of the manual explaining what the different
>> branches are, and when you have a patch that's
Hello,
Am Tue, Mar 02, 2021 at 03:03:50PM -0500 schrieb Leo Famulari:
> I think that timeline is too short for core-updates, although it depends
> on how many people choose to monitor the building and fix problems.
> Regarding the bug tracker, I don't think we've begun identifying
> core-updates
14 matches
Mail list logo
