[factory] [15.6] dracut requires wicked?!?!
# zypper rm wicked Reading installed packages... Resolving package dependencies... The following 2 packages are going to be REMOVED: dracut wicked 2 packages to remove. After the operation, 5.7 MiB will be freed. Continue? [y/n/v/...? shows all options] (y): n Why? Is this Leap dracut dependency on wicked real? TW doesn't have such need. This was a fresh minimalist NET installation this AM: # grep onlyR /etc/zypp/zypp.conf ## OEM=solver.onlyRequires = false solver.onlyRequires = true # inxi -Snz --vs inxi 3.3.32-00 (2024-01-30) System: Kernel: 6.4.0-150600.4-default arch: x86_64 bits: 64 Console: pty pts/0 Distro: openSUSE Leap 15.6 Alpha Network: Device-1: Intel Ethernet I219-V driver: e1000e IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac: <filter> # zypper se -si NetworkManager wicked wicked-service systemd-network | grep 86 i+ | systemd-network | package | 254.5-150600.2.8 | x86_64 | OSS i+ | wicked | package | 0.6.73-150500.3.10.1 | x86_64 | OSS i | wicked-service | package | 0.6.73-150500.3.10.1 | x86_64 | OSS # systemctl list-unit-files | egrep 'd-net|solv|wick' systemd-network-generator.service disabled disabled systemd-networkd-wait-online.service disabled disabled systemd-networkd-wait-online@.service disabled disabled systemd-networkd.service disabled disabled systemd-resolved.service masked disabled wicked.service disabled disabled wickedd-auto4.service disabled disabled wickedd-dhcp4.service disabled disabled wickedd-dhcp6.service disabled disabled wickedd-nanny.service disabled disabled wickedd-pppd@.service static - wickedd.service indirect disabled systemd-networkd.socket enabled disabled # Should I make a bug report? -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
The following requirement was already added for 15.5: ``` Requires: (iputils or arping2 or wicked) ``` But yes, maybe it does no make much sense for desktop-only use cases. On 02/02/2024 21.29, Felix Miata wrote:
# zypper rm wicked Reading installed packages... Resolving package dependencies...
The following 2 packages are going to be REMOVED: dracut wicked
2 packages to remove. After the operation, 5.7 MiB will be freed. Continue? [y/n/v/...? shows all options] (y): n
Why? Is this Leap dracut dependency on wicked real? TW doesn't have such need.
This was a fresh minimalist NET installation this AM: # grep onlyR /etc/zypp/zypp.conf ## OEM=solver.onlyRequires = false solver.onlyRequires = true # inxi -Snz --vs inxi 3.3.32-00 (2024-01-30) System: Kernel: 6.4.0-150600.4-default arch: x86_64 bits: 64 Console: pty pts/0 Distro: openSUSE Leap 15.6 Alpha Network: Device-1: Intel Ethernet I219-V driver: e1000e IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac: <filter> # zypper se -si NetworkManager wicked wicked-service systemd-network | grep 86 i+ | systemd-network | package | 254.5-150600.2.8 | x86_64 | OSS i+ | wicked | package | 0.6.73-150500.3.10.1 | x86_64 | OSS i | wicked-service | package | 0.6.73-150500.3.10.1 | x86_64 | OSS # systemctl list-unit-files | egrep 'd-net|solv|wick' systemd-network-generator.service disabled disabled systemd-networkd-wait-online.service disabled disabled systemd-networkd-wait-online@.service disabled disabled systemd-networkd.service disabled disabled systemd-resolved.service masked disabled wicked.service disabled disabled wickedd-auto4.service disabled disabled wickedd-dhcp4.service disabled disabled wickedd-dhcp6.service disabled disabled wickedd-nanny.service disabled disabled wickedd-pppd@.service static - wickedd.service indirect disabled systemd-networkd.socket enabled disabled #
Should I make a bug report?
-- Antonio Álvarez Feijoo System Boot and Init SUSE
On Mon, 2024-02-05 at 08:32 +0100, Antonio Feijoo via openSUSE Factory wrote:
The following requirement was already added for 15.5:
``` Requires: (iputils or arping2 or wicked) ```
But yes, maybe it does no make much sense for desktop-only use cases.
this would only trigger if someone had neither iputils nor arping2 nor wicked installed. It is important because network device bringup in the initrd may fail without it. We can't simply remove it. I guess we can add NetworkManager in the list (I am not sure what NM uses to check for duplicate address detection; but if NM is in use, I don't think we'll use the network-legacy dracut module, right?) We can consider modularizing the dracut package more, so that only the ifup-legacy subpackage depends on wicked. But that's about all we can do here. Regards Martin
On 05/02/2024 14.41, Martin Wilck wrote:
On Mon, 2024-02-05 at 08:32 +0100, Antonio Feijoo via openSUSE Factory wrote:
The following requirement was already added for 15.5:
``` Requires: (iputils or arping2 or wicked) ```
But yes, maybe it does no make much sense for desktop-only use cases.
this would only trigger if someone had neither iputils nor arping2 nor wicked installed. It is important because network device bringup in the initrd may fail without it. We can't simply remove it.
I guess we can add NetworkManager in the list (I am not sure what NM uses to check for duplicate address detection; but if NM is in use, I don't think we'll use the network-legacy dracut module, right?)
We can consider modularizing the dracut package more, so that only the ifup-legacy subpackage depends on wicked. But that's about all we can do here.
Yes, shipping a network subpackage seems the cleanest way, BTW adopted by Fedora/RH [1] since forever [2]. [1] https://src.fedoraproject.org/rpms/dracut/blob/rawhide/f/dracut.spec#_151 [2] https://github.com/dracutdevs/dracut/commit/ec74fa8789453a7949869947ba07e66b...
Regards Martin
-- Antonio Álvarez Feijoo System Boot and Init SUSE
Martin Wilck composed on 2024-02-05 14:41 (UTC+0100):
On Mon, 2024-02-05 at 08:32 +0100, Antonio Feijoo Factory wrote:
The following requirement was already added for 15.5:
``` Requires: (iputils or arping2 or wicked) ```
But yes, maybe it does no make much sense for desktop-only use cases.
this would only trigger if someone had neither iputils nor arping2 nor wicked installed. It is important because network device bringup in the initrd may fail without it. We can't simply remove it.
I guess we can add NetworkManager in the list (I am not sure what NM uses to check for duplicate address detection; but if NM is in use, I don't think we'll use the network-legacy dracut module, right?)
I can't see how that would help here. I thought I made it evident in OP that neither NM nor Wicked are installed, thus can't be responsible for network setup here. systemd-networkd.socket is all I have explicitly enabled to bring up networking.
We can consider modularizing the dracut package more, so that only the ifup-legacy subpackage depends on wicked. But that's about all we can do here. Antonio Feijoo composed on 2024-02-05 17:32 (UTC+0100):
Yes, shipping a network subpackage seems the cleanest way, BTW adopted by Fedora/RH [1] since forever [2].
[1] https://src.fedoraproject.org/rpms/dracut/blob/rawhide/f/dracut.spec#_151 [2] https://github.com/dracutdevs/dracut/commit/ec74fa8789453a7949869947ba07e66b...
I use only systemd-network on Fedora as well, on every systemd distro actually. Leap is my primary and very most used. Home. :) -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On Mon, 2024-02-05 at 15:17 -0500, Felix Miata wrote:
Martin Wilck composed on 2024-02-05 14:41 (UTC+0100):
On Mon, 2024-02-05 at 08:32 +0100, Antonio Feijoo Factory wrote:
The following requirement was already added for 15.5:
``` Requires: (iputils or arping2 or wicked) ```
But yes, maybe it does no make much sense for desktop-only use cases.
this would only trigger if someone had neither iputils nor arping2 nor wicked installed. It is important because network device bringup in the initrd may fail without it. We can't simply remove it.
I guess we can add NetworkManager in the list (I am not sure what NM uses to check for duplicate address detection; but if NM is in use, I don't think we'll use the network-legacy dracut module, right?)
I can't see how that would help here. I thought I made it evident in OP that neither NM nor Wicked are installed, thus can't be responsible for network setup here. systemd-networkd.socket is all I have explicitly enabled to bring up networking.
Yeah, that would be another exception. And connman, too ;-) The point is, you don't need networking for booting. But other people do, and their systems may fail to boot if no tool for DAD exists. IMO we'd better make sure such boot failures don't occur, even if this means that some people have to install iputils (size 550k, and generally a quite useful package) or arping2 (size 67k). As mentioned, we can split off a dracut-networking package which people who don't need network boot can uninstall together with its dependencies. But we will need to install that package by default, unless we figure out a reliable way to figure out *on the package management level* whether or not network boot capability is required. Regards Martin
participants (3)
-
Antonio Feijoo -
Felix Miata -
Martin Wilck