Hi, Sure, you can go ahead and prepare/handle the upload, i'd appreciate that! I don't have much time at the moment for upstream unfortunately. I plan to upstream more code to our github repo soon-ish. But we could make a new upload whenever that happens.
Let me know what you need from me. Julien ________________________________ From: Fabian Grünbichler <[email protected]> Sent: Thursday, October 9, 2025 12:01 PM To: [email protected] <[email protected]>; Michael Prokop <[email protected]> Cc: Julien Fortin <[email protected]> Subject: Re: Bug#1100102: please package new upstream version 3.9.0 [You don't often get email from [email protected]. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] External email: Use caution opening links or attachments On October 8, 2025 3:11 pm, Michael Prokop wrote: > * Fabian Grünbichler [Fri Aug 01, 2025 at 09:57:07AM +0200]: >> On July 31, 2025 10:40 pm, Bernhard Schmidt wrote: >> > On 27/03/25 02:14 PM, Fabian Grünbichler wrote: > >> >> would it be okay for you if I imported the current version in the >> >> archive to salsa (in a namespace of your choice?) and prepare an upload >> >> with the update to 3.9.0 (and maybe do a bit of housekeeping)? If so, >> >> would you like to review it before I go ahead? >> >> >> >> I'm a DD so I can take care of uploading and any follow-up work needed. >> > >> > I think this would be a good fit for the Package Salvaging process. >> > >> > https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.debian.org%2Fdoc%2Fmanuals%2Fdevelopers-reference%2Fpkgs.en.html%23package-salvaging&data=05%7C02%7Cjfortin%40nvidia.com%7C4fbbf09c69d24e9bea1808de071ae0ac%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C638956009192068410%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=JjZX5I2m0jrztmeN5yEoXgvk35k%2FsJyGB5g%2FJmno11Y%3D&reserved=0<https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging> >> >> I am not sure that is necessary (yet) - I mainly did not follow-up on >> this because of the incoming freeze. >> >> @Julien my offer above still stands, if you want me to co-maintain or >> takeover maintainership on the Debian side just say so :) > > Friendly ping, given that I just had a Debian/trixie system where I > wanted to replace ifupdown with ifupdown2 (in preparation for > deploying Proxmox VE), but it even complained about: > > | Unpacking ifupdown2 (3.0.0-1.3) ... > | Setting up ifupdown2 (3.0.0-1.3) ... > | Installing new version of config file /etc/default/networking ... > | find: ‘/var/lib/dhcp/’: No such file or directory > | /usr/share/ifupdown2/addons/bridge.py:3641: SyntaxWarning: invalid escape > sequence '\s' > | for protocol in re.split(',|\s*', user_config_l2protocol_tunnel): > | /usr/share/ifupdown2/ifupdown/ifupdownmain.py:1569: SyntaxWarning: invalid > escape sequence '\d' > | vlan_match = re.match("^([\d]+)-([\d]+)", ifacename) > | /usr/share/ifupdown2/ifupdown/utils.py:233: SyntaxWarning: invalid escape > sequence '\w' > | range_match = re.match("^([\w]+)\[([\d]+)-([\d]+)\]([\.\w]+)", name) > | /usr/share/ifupdown2/ifupdown/utils.py:243: SyntaxWarning: invalid escape > sequence '\w' > | range_match = re.match("^([\w\.]+)\[([\d]+)-([\d]+)\]", name) > | /usr/share/ifupdown2/lib/iproute2.py:65: SyntaxWarning: invalid escape > sequence '\s' > | VXLAN_PEER_REGEX_PATTERN = re.compile("\s+dst\s+(\d+.\d+.\d+.\d+)\s+") these are https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.debian.org%2Fcgi-bin%2Fbugreport.cgi%3Fbug%3D1085641&data=05%7C02%7Cjfortin%40nvidia.com%7C4fbbf09c69d24e9bea1808de071ae0ac%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C638956009192108224%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=qOFueSWKLUv2RFk4bFODBXD%2FSxssnIdU5ID1C5bLqR0%3D&reserved=0<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085641> > And the resulting system didn't manage to come up with networking. could you share your /etc/network/interfaces[.d/*] contents? feel free to anonymize/censor (if you do it consistently ;)). note that if you are using DHCP, you need to install the (deprecated) isc-dhcp-client if using ifupdown2, since that is the only client implementation currently supported by it. it's currently only Suggested by ifupdown2, so this is easily missed and "stock" trixie doesn't come with it pre-installed (anymore). I will see about preparing an NMU or starting ITS for updating and fixing related packaging issues, and then see what we can do to improve the dhcp client situation upstream as well.
