bug#62294: gnupg is pinned at 2.2.32 for bug that is fixed upstream

2023-04-04 Thread Leo Famulari
On Tue, Apr 04, 2023 at 07:31:47PM +0200, Simon Tournier wrote: > Maybe I am doing something wrong, I get: > > --8<---cut here---start->8--- > $ guix refresh -l gnupg | cut -f1 -d':' > Building the following 1491 packages would ensure 2880 dependent packages are

bug#62672: Unexpected interaction between gobject-introspection and grafts

2023-04-04 Thread Collin J. Doering
Hi team Guix! I was working on packaging taffybar (https://github.com/taffybar/taffybar), which depends on haskell-gi (https://github.com/haskell-gi/haskell-gi) - haskell bindings for goject-introspection capable libraries. While packaging gi-gdk, I hit this error: --8<---cut here-

bug#62668: ddcci-driver-linux 0.4.2 build failure

2023-04-04 Thread calcium via Bug reports for GNU Guix
Building ddcci-driver-linuxf 0.4.2 no longer works which means I can't update my system :(. The build status also shows that since January 8, (ID:325553 8 Jan 04:21) ddcci-driver-linux no longer builds. https://ci.guix.gnu.org/search?query=ddcci-driver-linux%200.4.2%20spec:master&border-high-i

bug#62294: gnupg is pinned at 2.2.32 for bug that is fixed upstream

2023-04-04 Thread Simon Tournier
Hi Leo, On Tue, 04 Apr 2023 at 12:23, Leo Famulari wrote: >> Well, graft does not seem recommended because it would update to two >> versions. And update the package would be a core-updates. >> >> Well, maybe it could be of the current core-updates dance. Could you >> send a patch for core-up

bug#62294: gnupg is pinned at 2.2.32 for bug that is fixed upstream

2023-04-04 Thread Leo Famulari
On Mon, Mar 20, 2023 at 09:01:33AM -0400, Ethan Blanton via Bug reports for GNU Guix wrote: > However, the bug referenced here is fixed in upstream commit > 4cc724639c012215f59648cbb4b7631b9d352e36, which shipped in gnupg > 2.2.34. Meanwhile, all gnupg releases older than 2.2.35 suffer from > an

bug#62294: gnupg is pinned at 2.2.32 for bug that is fixed upstream

2023-04-04 Thread Leo Famulari
On Tue, Apr 04, 2023 at 11:48:31AM +0200, Simon Tournier wrote: > On Mon, 20 Mar 2023 at 09:01, Ethan Blanton via Bug reports for GNU Guix > wrote: > > I believe the pin on 2.2.32 can be lifted, but as gnupg is important > > infrastructure I am unsure about directly submitting a patch to update >

bug#62064: Why is only rust-1.60 exported when 1.65 is defined?

2023-04-04 Thread Jonas Møller via Bug reports for GNU Guix
Yes, rust-next works, but I was imagining renaming the current rust to something like default-rust-build, then defining a new ‘rust’ which will be continuously updated to the latest version of rust. I think a user centric design would name the latest rust as just ‘rust’, while letting the packa

bug#62064: Why is only rust-1.60 exported when 1.65 is defined?

2023-04-04 Thread Simon Tournier
Hi, On Mon, 13 Mar 2023 at 21:11, paren--- via Bug reports for GNU Guix wrote: > There's another important reason: > > rust != rust-1.60 Well, as discussed in [1] [bug#62643] [PATCH] gnu: rust-1.65: Rename package to rust-next. this report #62064 is not a bug but instead a wish list: u

bug#62656: broken guix time-machine + software-heritage

2023-04-04 Thread Simon Tournier
Hi, Cool you did this test! :-) On Mon, 03 Apr 2023 at 23:39, Nicolas Graves via Bug reports for GNU Guix wrote: > Here is the content + backtrace of the time-machine call, after the ~10 > hours long object processing on Software Heritage side: Last time I checked that, I never got the object

bug#62071: openjdk@9/10 sources not reproducible

2023-04-04 Thread Simon Tournier
Hi, On Mon, 20 Mar 2023 at 10:08, Ludovic Courtès wrote: >> I was thinking a second time about it and found that not only the newer >> development of OpenJDK is on GitHub, but also the older versions are >> available. So I could add another patch like this: >> >> + (method git-fetc

bug#62294: gnupg is pinned at 2.2.32 for bug that is fixed upstream

2023-04-04 Thread Simon Tournier
Hi, On Mon, 20 Mar 2023 at 09:01, Ethan Blanton via Bug reports for GNU Guix wrote: > I believe the pin on 2.2.32 can be lifted, but as gnupg is important > infrastructure I am unsure about directly submitting a patch to update > to a newer version. Well, graft does not seem recommended because