GNU bug report logs - #51428
core-updates-frozen-batched-changes built and ready to merge

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#51428: closed (core-updates-frozen-batched-changes built and
 ready to merge)
Date: Fri, 12 Nov 2021 05:31:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Fri, 12 Nov 2021 00:29:54 -0500
with message-id <87k0heq6ul.fsf <at> gmail.com>
and subject line Re: [bug#51428] core-updates-frozen-batched-changes built and ready to merge
has caused the debbugs.gnu.org bug report #51428,
regarding core-updates-frozen-batched-changes built and ready to merge
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
51428: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=51428
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: guix-patches <guix-patches <at> gnu.org>
Subject: core-updates-frozen-batched-changes built and ready to merge
Date: Wed, 27 Oct 2021 00:04:01 -0400

Hello,

I've experimented quite a bit with core-updates-frozen-batched-changes
in the last weeks, and it seems to be in a decent shape, good enough to
merge into core-updates-frozen, I think.

I'd like to bring attention to some non-trivial changes that I included
in the branch:

1. merging of the staging branch -- quite a few conflicts had to be
resolved.

2. Replacement of inkscape <at> 0.92 by inkscape <at> 1.1, which required solving
some dependency cycles.

3. Fix for https://issues.guix.gnu.org/50957 via a new search path
specification on gdk-pixbuf and accompanying build phase and profile
hook.

I'll send the corresponding patches for review, which can also be
consulted directly on the core-updates-frozen-batched-changes branch,
which I've manually built on Berlin for things such as Rust and
ungoogled-chromium.

I'd like to merge it into core-updates-frozen by the beginning of
November, unless there are problems you can spot :-).

Thank you,

Maxim

[Message part 3 (message/rfc822, inline)]

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Thiago Jung Bauermann <bauermann <at> kolabnow.com>
Cc: 51428-done <at> debbugs.gnu.org
Subject: Re: [bug#51428] core-updates-frozen-batched-changes built and ready
 to merge
Date: Fri, 12 Nov 2021 00:29:54 -0500

Hi Thiago,

Thiago Jung Bauermann <bauermann <at> kolabnow.com> writes:

> Hello Maxim,
>
> Em sexta-feira, 5 de novembro de 2021, às 02:06:04 -03, Maxim Cournoyer 
> escreveu:
>> It's curious that it would occur though, because I thought that when
>> gdk-pixbuf was found with `manifest-lookup-package', it meant it'd also
>> be part of the manifest inputs?  Apparently it isn't the case.  Weird!
>
> I’m glad you found out what the problem was. I didn’t know where to start 
> investigating it!
>
>> Thanks for the report!
>
> Thank you for looking into it. Should I open a bug report about it?

No, the commit 20e3dd052d7e4f59273e3646d3533d43c87c30b0 contains a
workaround guarding against such situation.

Thanks :-).

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.