GNU bug report logs - #61475
Staging branch (was: Moving forward with teams and feature branches)

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#61475: closed (Staging branch (was: Moving forward with teams
 and feature branches))
Date: Wed, 10 May 2023 02:56:02 +0000

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

Your message dated Tue, 09 May 2023 22:55:50 -0400
with message-id <875y90sxmx.fsf_-_ <at> gmail.com>
and subject line Re: bug#61475: Staging branch (was: Moving forward with teams and feature branches)
has caused the debbugs.gnu.org bug report #61475,
regarding Staging branch (was: Moving forward with teams and feature branches)
to be marked as done.

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


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

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

From: Andreas Enge <andreas <at> enge.fr>
To: Josselin Poiret <dev <at> jpoiret.xyz>
Cc: bug-guix <at> gnu.org
Subject: Re: Staging branch (was: Moving forward with teams and feature
 branches)
Date: Mon, 13 Feb 2023 15:04:09 +0100

Am Sun, Feb 12, 2023 at 10:13:35PM +0100 schrieb Josselin Poiret:
> 4. staging merge happens, and the branch gets deleted.

I tried to build staging for my profile on x86_64, but it failed with
a dependency of ffmpeg, rust-rav1e-0.5.1. There is a newer version 0.6.3,
but I did not simply update it, since the package looks particularly
complicated, containing a phase:
         (add-after 'configure 'force-rust-edition-2018
           (lambda* (#:key vendor-dir #:allow-other-keys)
             ;; Force all the dependencies to not be higher than edition 2018.
             (with-fluids ((%default-port-encoding #f))
               (substitute* (find-files vendor-dir "Cargo.toml")
                 (("edition = \\\"2021\\\"") "edition = \"2018\"")))))
and many other changes.

If someone who knows rust could have a look and make a suggestion, that
would be great.

Andreas

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

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Andreas Enge <andreas <at> enge.fr>
Cc: Josselin Poiret <dev <at> jpoiret.xyz>, 61475-done <at> debbugs.gnu.org
Subject: Re: bug#61475: Staging branch (was: Moving forward with teams and
 feature branches)
Date: Tue, 09 May 2023 22:55:50 -0400

Hi,

Andreas Enge <andreas <at> enge.fr> writes:

> Am Sun, Feb 12, 2023 at 10:13:35PM +0100 schrieb Josselin Poiret:
>> 4. staging merge happens, and the branch gets deleted.
>
> I tried to build staging for my profile on x86_64, but it failed with
> a dependency of ffmpeg, rust-rav1e-0.5.1. There is a newer version 0.6.3,
> but I did not simply update it, since the package looks particularly
> complicated, containing a phase:
>          (add-after 'configure 'force-rust-edition-2018
>            (lambda* (#:key vendor-dir #:allow-other-keys)
>              ;; Force all the dependencies to not be higher than edition 2018.
>              (with-fluids ((%default-port-encoding #f))
>                (substitute* (find-files vendor-dir "Cargo.toml")
>                  (("edition = \\\"2021\\\"") "edition = \"2018\"")))))
> and many other changes.
>
> If someone who knows rust could have a look and make a suggestion, that
> would be great.

Closing, both staging and the rust branch having been merged.

-- 
Thanks,
Maxim

Previous Next

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