Re: Welcome to Jorge Gomez (jgart) as a new Guix committer
Congratulations jgart! Glad to see you're plowing ahead :) "jgart" writes: >> I'd like to welcome Jorge as a new Guix committer! Jorge has been >> around for some time already, and is always very active around the Guix >> community; I'm sure they'll know to use their new privilege in a way >> that benefits the Guix community! > > Hi Maxim, > > Thanks for the warm welcome. It is much appreciated. I look forward to > continuing to push our efforts forward as a group. > > I also want to thank everyone who has reviewed and merged my patches > in the past and I look forward to now returning the help to others. > > all best, > > jgart > > ps > > I also made a statement about my commit access grant here: > > https://lists.gnu.org/archive/html/guix-devel/2023-05/msg00202.html
Re: Welcome to Jorge Gomez (jgart) as a new Guix committer
Thanks Blake and nice to hear from you. It's been a minute ;()
Re: Commit Access: jgart
"jgart" writes: > Hi Guixers, > > Thanks for granting me commit access. I'm looking forward to helping out with > patch review, with a > particular focus on moving patches along for the Python team. > > I also intend to continue contributing more packages, updates, and > improvements. > > Thanks again for granting me the privilege of commit access and I am looking > forward to continuing our collaborations. > > all best, Hi jgart, congrats and thank you for joining the party! Always a pleasure working with you :)
Re: Commit Access: jgart
Felicidades! --- Original Message --- On Tuesday, May 16th, 2023 at 2:28 AM, jgart wrote: > Hi Guixers, > > Thanks for granting me commit access. I'm looking forward to helping out with > patch review, with a > particular focus on moving patches along for the Python team. > > I also intend to continue contributing more packages, updates, and > improvements. > > Thanks again for granting me the privilege of commit access and I am looking > forward to continuing our collaborations. > > all best, > > jgart (Jorge Gomez)
Re: Guix CI "No space left on device"
Hi, On Tue, 09 May 2023 at 10:47, Greg Hogan wrote: > icedtea-3.19.0 fails to build with ... > http://ci.guix.gnu.org/build/1331007/details [...] > note: build failure may have been caused by lack of free disk space > builder for `/gnu/store/x4d9c7crnzn17pw8ahxjl5jc6jjdbyn4-icedtea-3.19.0.drv' > failed with exit code 1 Thanks for the notification. Now, all seems fixed, right? Cheers, simon
Re: Guix CI "No space left on device"
On Tue, May 16, 2023 at 11:06 AM Simon Tournier wrote: > > Hi, > > On Tue, 09 May 2023 at 10:47, Greg Hogan wrote: > > icedtea-3.19.0 fails to build with ... > > http://ci.guix.gnu.org/build/1331007/details > > [...] > > > note: build failure may have been caused by lack of free disk space > > builder for `/gnu/store/x4d9c7crnzn17pw8ahxjl5jc6jjdbyn4-icedtea-3.19.0.drv' > > failed with exit code 1 > > Thanks for the notification. Now, all seems fixed, right? Yes! I can download substitutes of dependent packages.
Order of manifest and overlapping binaries
I could not find documentation on this circumstance or how to resolve. Both 'parallel' and 'moreutils' produce a 'bin/parallel' and only one can go in the $GUIX_PROFILE. Creating a container, the latter package overshadows the former package, as below. Unclear if this is consistent. In my manifest the former package overshadows the latter (I'd prefer to have parallel's parallel, but by default I have sorted the listing alphabetically). Is there a better way to fix this? Greg --8<---cut here---start->8--- $ guix shell --container moreutils parallel which coreutils [env]$ readlink -f `which parallel` /gnu/store/xd9kbadmrrbpkjs9vl1v9rhgayfxwgbc-parallel-20230422/bin/parallel guix shell --container parallel moreutils which coreutils [env]$ readlink -f $(which parallel) /gnu/store/60zdm9zm0nqm5d97vs30sf4plb2ib5p9-moreutils-0.67/bin/parallel --8<---cut here---end--->8--- This is operating from a recent guix pull: --8<---cut here---start->8--- $ guix describe Generation 44 May 11 2023 17:02:53(current) guix d6f6b57 repository URL: https://git.savannah.gnu.org/git/guix.git branch: master commit: d6f6b57766e95d2fa8af63d4460a2b303ca4d867 --8<---cut here---end--->8---
Re: Order of manifest and overlapping binaries
Greg Hogan writes: > I could not find documentation on this circumstance or how to resolve. > Both 'parallel' and 'moreutils' produce a 'bin/parallel' and only one > can go in the $GUIX_PROFILE. > > Creating a container, the latter package overshadows the former > package, as below. Unclear if this is consistent. In my manifest the > former package overshadows the latter (I'd prefer to have parallel's > parallel, but by default I have sorted the listing alphabetically). Is > there a better way to fix this? > > Greg > > --8<---cut here---start->8--- > $ guix shell --container moreutils parallel which coreutils > [env]$ readlink -f `which parallel` > /gnu/store/xd9kbadmrrbpkjs9vl1v9rhgayfxwgbc-parallel-20230422/bin/parallel > > guix shell --container parallel moreutils which coreutils > [env]$ readlink -f $(which parallel) > /gnu/store/60zdm9zm0nqm5d97vs30sf4plb2ib5p9-moreutils-0.67/bin/parallel > --8<---cut here---end--->8--- > > > This is operating from a recent guix pull: > > --8<---cut here---start->8--- > $ guix describe > Generation 44 May 11 2023 17:02:53(current) > guix d6f6b57 > repository URL: https://git.savannah.gnu.org/git/guix.git > branch: master > commit: d6f6b57766e95d2fa8af63d4460a2b303ca4d867 > --8<---cut here---end--->8--- You could create a package that just copies the contents of moreutils to $output, but renames some files, then include the resulting package in your manifest. If moreutils is not propagated from any other package, then you don't even have to do an input rewrite.
Re: Order of manifest and overlapping binaries
> I could not find documentation on this circumstance or how to resolve. > Both 'parallel' and 'moreutils' produce a 'bin/parallel' and only one > can go in the $GUIX_PROFILE. i have proposed a solution for a special case of this problem: to do alphanumeric sorting, which together with semantic versioning picks the latest from the collisions of different versions of the same package. see: https://issues.guix.gnu.org/50878#12 the cleanup commits reached master by now, but the actual change of the semantics of the union has not. it needs to be revived/rebased. in its current form it wouldn't help in your case, but it points to the relevant part of the codebase. HTH, -- • attila lendvai • PGP: 963F 5D5F 45C7 DFCD 0A39 -- “In a country where the sole employer is the State, opposition means death by slow starvation. The old principle: who does not work does not eat, has been replaced by a new one: who does not obey shall not eat.” — Leon Trotsky
Re: Setuid handling?
Hi everyone, On Tue, Apr 25, 2023 at 10:04 AM Saku Laesvuori wrote: > > Maybe you could remove the packages with setuid-programs from your home > configuration, but really this seems like a bug in guix home to me. Maybe so, but it did not help that we ship an 'su' implementation that, according to the Heindal maintainers, has been obsolete for five years. Their releases are based on a stable branch which means they rely on distributions to drop the executables. (Debian renames them [1] but they are useless without setuid root and may not meet the PAM policy of the local administrator.) Here is a patch that removes the obsolete executables from Guix. [2] Perhaps someone with newly granted committer rights would like to have a look at it. Congratulations, also! I switched to building Heimdal from Git since I was not sure if or when [3] our gnu-build-system runs autogen.sh or any invocation of autoreconf when a ./configure script is already present (in the tarball). Kind regards Felix [1] https://sources.debian.org/src/heimdal/7.8.git20221117.28daf24%2Bdfsg-2/debian/rules/#L116 [2] https://issues.guix.gnu.org/63545 [3] https://github.com/guix-mirror/guix/blob/c8e599b9391f789a8a3e2183fc8f0c2a5061ceb0/gnu/packages/networking.scm#L3250-L3255
