pe 4.4.2025 klo 4.25 Santiago Ruano Rincón (santiag...@riseup.net) kirjoitti: > El 31/03/25 a las 18:31, Daniel Gröber escribió: > > Hi Martin, Santiago, Jose, > > > > On Wed, Mar 26, 2025 at 05:32:36PM +0200, Martin-Éric Racine wrote: > > > We request assistance with maintaining the ifupdown package. > > > > I'd be happy to adopt ifupdown as sole Maintainer with a very collaborative > > mindset. > > Maintainer is currently > Debian Networking Team <team+network...@tracker.debian.org>. It is not > clear to me if you are proposing to change that. Could you clarify it > please? > And just in case, I would prefer to keep it like that, and adding you as > Uploader.
It was changed to team maintenance for a good reason. Let's not revert that. > May I ask what do you propose to build a strong team? I'd like to hear that too. > > I agree with Santiago, we should move towards ifupdown-ng, but I don't want > > to do that until we have a really good understanding of the problem space > > and whether ifupdown's model truly does solve enough of it to be useful in > > the modern world. > > OK dhcpcd can already do most of what ifupdown does. The only serious lacking it has is that it cannot handle hostap configs and it cannot create bridges or vlans. Once that has been implemented, it could replace ifupdown entirely. > > Frankly as soon as I'm empowered to just make the necessary changes I'm > > happy to do it. I have plenty of Debian events and time lined up before the > > Soft Freeze still, but I don't want to do it if I have to fight over every > > technical decision I make. > > As far as it concerns me, join the current team, and you would be > empowered to make the changes. TBH, many of the bugs that Daniel has filed against dhcpcd makes me seriously ponder whether I'd trust him to make any change at all. > > I'd just be happy for input on any particularly jucy/difficult bugs, maybe > > major overall problems you think need addressing and the like. > > I haven't had the time to look at that. I believe Martin-Éric has a > better idea of priority bugs. I have specific issues that have been left unattended to, some of which specifically concern dhcpcd integration for Trixie. At the very least, I'd like our CLI recipe to safeguard us against any upstream change of mind for the default config. Another point would have been to integrate bridge creation using 'ip' directly into 'ifupdown' and retire bridge-utils, and also better document the fact that 'ifupdown' can already create vlans without the old external package. Martin-Éric
