> However, I don't see how we can argue that dropping FAN support is > *not* a regression, even if the kernel we ship does not support it.
I understand. I guess the situation is a bit particular here. If the official kernel doesn't support it -- something Ubuntu-specific, not upstreamed -- it means Ubuntu FAN cannot be used: there is no way to even validate that these patches work on Ubuntu 24.04. The regression would be more on the kernel side :) >> and dropping these patches would stop the diversion with Debian? > > That's not a goal of our SRU process. We can always realign with > Debian during the next devel cycle. Good point. I just wanted to suggest that dropping these patches could be seen as a "safer approach" as it is closer to the upstream version, what is on Debian and other distributions. > The package does seem to include this in its autopkgtests > (debian/tests/testsuite.sh), so I think we have that coverage. Oh, I missed that, thank you for having checked! Good news then! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/2051672 Title: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main) Status in iproute2 package in Ubuntu: Incomplete Bug description: iproute2 upstream produces releases coinciding with upstream kernel releases to support the latest kernel features. Noble's iproute2 is still back at v6.1 even though it will use the v6.8 kernel. This means we provide no userspace interface for newer features - some of which are noted by a networking hardware partner in bug 2060969. Ubuntu's iproute2 has diverged from Debian's to add support for Ubuntu FAN. Noble has dropped kernel support for Ubuntu FAN, so those are no longer needed, and we could now just do a merge. We could also port the FAN patches forward if we can identify a need (see the original description of this bug to a link to such a port), but I have not done any testing with that. I have built Debian's iproute2 in a noble ppa at ppa:dannf/test and smoke tested it on an amd64 virtual machine: ubuntu@cortez-vm-0:~$ sudo dpkg -i iproute2_6.8.0-1~24.04.1_amd64.deb (Reading database ... 83134 files and directories currently installed.) Preparing to unpack iproute2_6.8.0-1~24.04.1_amd64.deb ... Unpacking iproute2 (6.8.0-1~24.04.1) over (6.1.0-1ubuntu6) ... dpkg: warning: unable to delete old directory '/etc/iproute2/rt_tables.d': Directory not empty dpkg: warning: unable to delete old directory '/etc/iproute2/rt_protos.d': Directory not empty dpkg: warning: unable to delete old directory '/etc/iproute2': Directory not empty Setting up iproute2 (6.8.0-1~24.04.1) ... Removing obsolete conffile /etc/iproute2/group ... Removing obsolete conffile /etc/iproute2/rt_realms ... Removing obsolete conffile /etc/iproute2/rt_scopes ... Removing obsolete conffile /etc/iproute2/rt_tables ... Removing obsolete conffile /etc/iproute2/rt_tables.d/README ... Removing obsolete conffile /etc/iproute2/rt_protos.d/README ... Removing obsolete conffile /etc/iproute2/rt_protos ... Removing obsolete conffile /etc/iproute2/rt_dsfield ... Removing obsolete conffile /etc/iproute2/nl_protos ... Removing obsolete conffile /etc/iproute2/ematch_map ... Removing obsolete conffile /etc/iproute2/bpf_pinning ... Processing triggers for man-db (2.12.0-4build1) ... The system rebooted fine. The ip command seems to behave normally. Since the upstream test suite only appears to run at autopkgtest time, I triggered a run in my PPA, and it passed: https://autopkgtest.ubuntu.com/results/autopkgtest-noble-dannf-test/noble/amd64/i/iproute2/20240412_210819_97417@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
