Re: Defaulting to MAC-based names for network interfaces
Hi Efraim, On Mon, May 15, 2023 at 7:47 AM Efraim Flashner wrote: > > > the standard command to test udev setups: [2] > > > > $ udevadm --debug test /sys/class/net/* > > > > did not find the script installed via the 'udev-service-type'. > > I was curious about this, since I've been using a udev rule for quite a > while to setup zram swap. I definitely have my zram swap enabled and > working, but 'udevadm --debug test /dev/zram0' didn't find any rule for > zram. Your zram probably works because your udev rule does not need a working udevadm. I believe that network interfaces actually use udevadm to determine their name. Either way, my latest amendments to Bug#63508 (v2) will fix your udevadm. [1] In a concession to Liliana's opposition, I retitled the bug to sidestep the question of the MAC-based names as a default setting. My position has not changed but that should probably be a separate discussion. Personally, I hope to win everyone's hearts with this: My fix allows folks to experiment with MAC-based names so everyone can see their great utility. Anyone interested, please put this in your system services: (udev-rules-service 'net-name-mac (udev-rule "79-net-name-mac.rules" " SUBSYSTEM==\"net\", ACTION==\"add\", NAME=\"$env{ID_NET_NAME_MAC}\" "))) Sorry I cannot offer substitutes. The change rebuilds more than it should. As a side note, I looked into upgrading to eudev 3.2.12, which was tagged yesterday, but that will bring more pain because upstream hardcoded the path to the hwdb. [2] I have a partial fix, although some consuming packages like upower aren't working yet. Kind regards Felix [1] https://issues.guix.gnu.org/63508#12 [2] https://github.com/eudev-project/eudev/blob/2703baf55615b7554fb67c4f1c241f057f8c0a79/src/udev/udevadm-hwdb.c#L588
Re: nudging patches
Hello Remco, sorry for cross posting to guix-devel but I think this is more a devel (committers needing help) discussion than a user (needing help) one :-) Remco van 't Veer writes: > Hi, > > What's the preferred / politest way to draw attention to patches (and / > or bugs) which seem to have been overlooked? AFAIU send an email ping to the patch/bug, possibly Cc-ing the related team [1] > And while I have your attention and you're wondering which patches I'd > like to promote.. 😉 > > - #62557 [guix-patches] > [PATCH] gnu: ruby-2.7-fixed: Upgrade to 2.7.8 [fixes CVE-2023-{28755, > 28756}] > - #62558 [guix-patches] > [PATCH] gnu: ruby-3.0: Upgrade to 3.0.6 [fixes CVE-2023-{28755, 28756}]. > - #62559 [guix-patches] > [PATCH] gnu: ruby-3.1: Upgrade to 3.1.4 [fixes CVE-2023-{28755, 28756}]. > - #62561 [guix-patches] > [PATCH] gnu: ruby-3.2: Upgrade to 3.2.2 [fixes CVE-2023-{28755, 28756}]. > > They still apply cleanly on master. This is the current Ruby team: id: ruby name: Ruby team description: scope: "gnu/packages/ruby.scm" "guix/build/ruby-build-system.scm" "guix/build-system/ruby.scm" "guix/import/gem.scm" "guix/scripts/import/gem.scm" "tests/gem.scm" members: + Christopher Baines > But seriously, what is the preferred way to do this? HTH! Gio' [1] https://guix.gnu.org/en/manual/devel/en/html_node/Teams.html#Teams -- Giovanni Biscuolo Xelera IT Infrastructures signature.asc Description: PGP signature
Re: bug#20255: 'search-paths' should respect both user and system profile.
Maxim Cournoyer writes: > Hi, > > 宋文武 writes: > >> Hello, commit 40310efde9b4a4f2cf98081d6cd10f843685ebb6 fix this by merge >> search-paths from multiple profiles by `guix package --search-paths`, in >> ~/.bashrc and ~/.zprofile (skeletons, so existed systems need manual >> update). >> >> >> Close now! Well, I reopen this since the changes is not totaly (duplicates in /etc/profile, guix home changes) done, sorry... > > Cool, thanks for the update. Perhaps a NEWS entry would be useful to > keep Guix System existing users in the loop? Until we have a better > mechanism/approach to these stateful files that don't change past the > original installation. Now, I send more patches with NEWS entry. Add guix-devel to CC for more reviews, TIA!
Re: Contributing Guix Home services
Hi Ludo’, Sorry, busy week! 😅 … euh… busy 2 weeks! 😱 Quoting Ludovic Courtès (2023-05-03 22:42:27) > Tanguy LE CARROUR skribis: > > > Quoting Ludovic Courtès (2023-04-17 15:39:02) > >> Tanguy LE CARROUR skribis: > >> > It's been quite a journey on my side! Ups. Downs. Mostly downs, though! 😅 > >> > Thanks to Simon's unconditional technical and moral support, a **LOT** > >> > has changed since I sent this message. Hopefully for the better! 🤞 > >> > >> Heh. :-) While it’s fresh on your mind, it would be nice to list the > >> problems you ran into on your journey and see what we can do about it. > > > > Mostly figuring out how to test it! > > > > On my machine at home, `guix home reconfigure` can take minutes. > > Did you test with ‘guix home container’ first? That’s what I do and I > added this command precisely so one can test without any risk of > breaking things. > > It’s still too slow though, that’s right. Yes, when I use my actual home config, it also takes minutes to build the container, but, if I use a fake home config, limited to the service I want to test, it's way faster! Still slower than the following… Append this test code at the end of the service file: ```scheme (define configuration (home-service-configuration ; […] ) (mixed-text-file "test" (serialize-configuration configuration home-service-configuration-fields)) ``` Then, from the command line: ```console $ cat (guix build -f path/to/home/service.scm) # … the content of the generated file ``` > > I can only test file generation, though. > > The msmtp service does nothing but file generation though, right? > > > Then I painfully discovered that replacing in a string is not as easy as > > it sounds, or, more precisely, that "python replace in string" yields > > better results than "scheme replace in string" in DuckDuckGo! > > True! Perhaps something to add to the Cookbook’s Scheme intro. > > (Fun fact: I’ve never used that (ice-9 string-fun) module that keeps > popping up in new code. :-)) Wht?! 🤯 How one would you do without it? 😅 -- Tanguy