bug#49992: guix bug

I ran guix pull​ and got this ``` $ guix pull Updating channel 'guix' from Git repository at 'https://git.savannah.gnu.org/git/guix.git'... Authenticating channel 'guix', commits 9edb3f6 to 2730ed9 (4,844 new commits)... Building from this channel: guix https://git.savannah.gnu.org/git/gu

bug#49744: cuirass: Invalid RSS feed.

Fixed with b210fcc963865acd820078e705132cd2b5f339a7. Thanks, Mathieu

bug#49769: Cuirass returns 500 on typo in search

Hello Julien, > When searching for builds on the cuirass website, I made a typo, > looking for "maven sytem:x86_64-linux" (instead of system). The > website returns an empty error 500 page. That's fixed with e95e723f3c4fddc4a2fa7a9ac58230c262470c76. Thanks for reporting, Mathieu

bug#49985: bash-mesboot0: Inscrutable error in build phase

On +2021-08-11 02:38:54 +0200, Bengt Richter wrote: > On +2021-08-10 15:41:25 -0400, Carl Dong wrote: > > Hi all, > > > > While setting up Guix for a community member of mine, we encountered this > > somewhat inscrutable problem (I later learned this is not the first time > > Guix users have run

bug#49985: bash-mesboot0: Inscrutable error in build phase

On +2021-08-10 15:41:25 -0400, Carl Dong wrote: > Hi all, > > While setting up Guix for a community member of mine, we encountered this > somewhat inscrutable problem (I later learned this is not the first time Guix > users have run into this problem!). When building > /gnu/store/2nvaxgs0rdxfkr

bug#49979: Duplicity BackendException: No module named 'paramiko'

On Tue, Aug 10, 2021 at 12:15:44PM +0200, Cayetano Santos wrote: > > Context: > > Using guix as a package manager under a foreign up to date archlinux > distribution. > > The output of guix describe --format=channels is > > > https://gitlab.com/csantosb/wikidata/-/blob/master/guix-profiles-

bug#49990: [core-updates-frozen] Ant-bootstrap broken by classpath-bootstrap

Hi Guix! I've finally taken the time to investigate the build failure of ant-bootstrap. It is failing after reporting a file exists: ``` /tmp/guix-build-ant-bootstrap-1.8.4.drv-0/apache-ant-1.8.4/build.xml:558: Unable to create directory as a file already exists with that name: /tmp/guix-build-an

bug#49611: Despite wireless-regdb being installed in my operating-system, dmesg indicates it can't find `regulatory.db`

On 20/07/2021 04:21, Katherine Cox-Buday wrote: This is not part of the bug per-say, but a question around this space: despite all of this, I still cannot broadcast on US approved channels. I think this is because the EEPROM on the card is set as global. What am I missing? Do you know how Linux i

bug#49611: Despite wireless-regdb being installed in my operating-system, dmesg indicates it can't find `regulatory.db`

On 20/07/2021 04:21, Katherine Cox-Buday wrote: I think this is because the EEPROM on the card is set as global. What am I missing? Do you know how Linux intend for people to notify the stack that this is an OK thing to do? I know projects like OpenWRT carry patches to the driver, but I keep thin

bug#49979: Duplicity BackendException: No module named 'paramiko'

Context: Using guix as a package manager under a foreign up to date archlinux distribution. The output of guix describe --format=channels is https://gitlab.com/csantosb/wikidata/-/blob/master/guix-profiles-backup/guix-channels.scm Problem: When using duplicity to backup to a sftp ser

bug#49985: bash-mesboot0: Inscrutable error in build phase

Hi all, While setting up Guix for a community member of mine, we encountered this somewhat inscrutable problem (I later learned this is not the first time Guix users have run into this problem!). When building /gnu/store/2nvaxgs0rdxfkrwklh622ggaxg0wap6n-bash-mesboot0-2.05b.drv, we encountered

bug#49968: Fwd: issue website creates invalid comment expectations

Hi Maxime, I took a quick look, but I'm not seeing how the proposed fix works: there is already that line for defining mu-debug in the only file that uses mu-message-send...? (Perhaps this should be sent to that original issue, I can send it again there if that is helpful.) If there is not a r

bug#49439: grafts cause “guix environment” to get killed with OOM

Hello! Ludovic Courtès skribis: > I added counters and ‘pk’ calls in ‘map/accumulate-builds’ & co. to see > what happens. AFAICS, a cutoff as in the attached patch does the job. > It’s a basic heuristic to avoid unbounded growth, at the expense of > possibly reduced accumulation. For example,

bug#49968: Fwd: issue website creates invalid comment expectations

> [... mumi ‘send comment’ interface doesn't work ...] Some time ago, I received a copy of the logs and Ludovic and I found out what causes comments to be swallowed: . Ludovic has a suggestion on how to fix it. The source code is at

bug#49968: Fwd: issue website creates invalid comment expectations

(I think the bug title should be "comments sent via issues.guix.gnu.org disappear" as they seem to get swallowed by the server) I sent a comment just a few minutes ago via the webform, that got the message that was successful. I'll check back to see if it appears later, but have not had it work

bug#49977: Texlive importer is outdated?

On Tue, Aug 10 2021, Ricardo Wurmus wrote: > Xinglu Chen writes: > >> [Cc Ricardo since you wrote the texlive importer] > > In the future please use the X-Debbugs-Cc header instead of Cc, so > that Debbugs can put me on Cc *after* it has assigned a bug > number. Ah, I didn’t know about that.

bug#49977: Texlive importer is outdated?

Xinglu Chen writes: [Cc Ricardo since you wrote the texlive importer] In the future please use the X-Debbugs-Cc header instead of Cc, so that Debbugs can put me on Cc *after* it has assigned a bug number. In general, I have rarely been able to successfully import a CTAN package using t

bug#49977: Texlive importer is outdated?

[Cc Ricardo since you wrote the texlive importer] In section "9.5 Invoking ‘guix import’" in the manual, there are two examples of runnning the ‘texlive’ importer, but both of them result in incomplete package definitions. --8<---cut here---start->8--- ~/src/gu

bug#49781: Successful build on ci.guix not available as substitute

Hi, Mathieu Othacehe skribis: > I found out the reason of this failure, the .185 key was not authorized > on Berlin. This issue while really simple, took us a long time to > detect. I think we need to come out with a big warning somewhere when a > substitute is refused because the server is not