bug#61379: Guix creates 1M+ symlinks for papirus-icon-theme

2023-02-21 Thread Maxim Cournoyer
Hi, SkeletonAdventure writes: > After installing papirus-icon-theme my profile build became much > slower, and after a few more generations I ran out of Inodes. After > probing around with du I found that each profile had nearly 1.5M > Inodes. > > From 'du --inodes -d 1 /gnu/store | sort -n' > >

bug#48214: inetutils-1.9.4 build fails

2023-02-21 Thread 宋文武 via Bug reports for GNU Guix
Bone Baboon writes: > I have reopened bug#48214 because while inetutils-1.9.4 can be built on > x86_64 with IPv6 disabled this command fails on x86_64 with IPv6 > disabled `guix build --no-substitutes --system=i686-linux` inetutils`. > This command has the same failing test. Attached is the fail

bug#61676: package transformations not honored working from a manifest

2023-02-21 Thread Maxim Cournoyer
Hi Ludo! Ludovic Courtès writes: [...] >> But noticed that --with-source and --with-patch were not effective for >> the jami-with-certs customized package provided by the >> guix-pack-manifest.scm manifest. > > Indeed, that’s expected. > >> It seems to me that the rewriting options should be ho

bug#61676: package transformations not honored working from a manifest

2023-02-21 Thread Ludovic Courtès
Hi, Maxim Cournoyer skribis: > I was trying to simplify the Jami packaging tooling using the latest > recursive '--with-source' transformation, like so (in a Makefile): > > define guix-pack-command > guix pack -C xz -f deb -f > extras/packaging/gnu-linux/guix/guix-pack-manifest.scm -v3 \ > --

bug#61690: Failure to mount /sys in nested ‘guix shell’ container

2023-02-21 Thread Ludovic Courtès
Hi! As reported by Konrad¹, nested ‘guix shell -C’ fails: --8<---cut here---start->8--- $ guix shell -CN guix \ --expose=/var/guix/daemon-socket/socket \ --expose=/gnu/store \ -- guix shell -C coreutils -- ls / guix shell: error: mount: mount

bug#61684: can't compose 'with-patch' with 'with-source'

2023-02-21 Thread Simon Tournier
Hi Maxim, On Tue, 21 Feb 2023 at 13:08, Maxim Cournoyer wrote: > Given 'with-source' discards any patch from the original source, I thought > I could at least add them back via 'with-patch', but it appears this > does not work: I remember some headaches with this thread [1]. :-) 1:

bug#61684: can't compose 'with-patch' with 'with-source'

2023-02-21 Thread Maxim Cournoyer
Hi, Given 'with-source' discards any patch from the original source, I thought I could at least add them back via 'with-patch', but it appears this does not work: --8<---cut here---start->8--- scheme@(gnu packages jami)> (options->transformation

bug#61573: Arbitrary memory write vulnerability in NSS CVE-2023-0767

2023-02-21 Thread Maxim Cournoyer
Hi Leo, Leo Famulari writes: > There's a serious vulnerability in NSS: > > "An attacker could construct a PKCS 12 cert bundle in such a way that > could allow for arbitrary memory writes via PKCS 12 Safe Bag attributes > being mishandled." > > https://www.mozilla.org/en-US/security/advisories/mf

bug#61676: package transformations not honored working from a manifest

2023-02-21 Thread Maxim Cournoyer
Hi Guix, I was trying to simplify the Jami packaging tooling using the latest recursive '--with-source' transformation, like so (in a Makefile): --8<---cut here---start->8--- define guix-pack-command guix pack -C xz -f deb -f extras/packaging/gnu-linux/guix/gu

bug#42155: --with-source=PACKAGE=REPLACEMENT-SOURCE doesn't work recursively

2023-02-21 Thread Maxim Cournoyer
Hi, Ludovic Courtès writes: > pkill9 skribis: > >>> I think what you're looking for is more of: >>> >>> guix build --no-grafts mpv --with-input=youtube-dl=$(guix build >>> --no-grafts youtube-dl >>> --with-source=https://github.com/ytdl-org/youtube-dl/releases/download/2020.06.16/youtube-dl-20

bug#61513: [PATCH 1/2] gnu: Add emacs-next-tree-sitter.

2023-02-21 Thread Simon Tournier
Hi, On Mon, 20 Feb 2023 at 20:21, Liliana Marie Prikler wrote: >> Naive question: why not squash the 2 patches?  Adding the new >> variable and fix the version of emacs-next. > > Because the next patch "upgrades" emacs-next to the then HEAD of the > emacs-29 branch, which wasn't hitherto packag