Re: proposal: Hybrid network stack for Trixie

2024-09-23 Thread Holger Levsen
On Mon, Sep 23, 2024 at 11:04:06AM +0200, Marco d'Itri wrote: > > ifupdown2 is like ifupdown, just rewritten in python. > Yes, that's the problem: there was a consensus that it is not an > appropriate dependency for the base system. ah! thanks for pointing this out. > ifupdown2 will still be aro

Re: proposal: Hybrid network stack for Trixie

2024-09-23 Thread Lukas Märdian
Hi! On 22.09.24 15:58, Ansgar 🙀 wrote: On Fri, 2024-09-20 at 13:12 +0200, Lukas Märdian wrote: I've repeated the reasons why I think a hybrid stack using Netplan is a feasible solution many times in previous threads, therefore I'd like to refer to a list of frequently asked questions, instead o

Re: proposal: Hybrid network stack for Trixie

2024-09-23 Thread Chris Hofstaedtler
* Holger Levsen [240923 12:05]: > > ifupdown2 will still be around for anybody who wants to install it. > > sure. Except that right now it has an open r-c bug since June 25, and is missing from testing since August 6th. If people want to continue having it, somebody who wants to work on it need

Re: proposal: Hybrid network stack for Trixie

2024-09-23 Thread Chris Hofstaedtler
* Pierre-Elliott Bécue [240923 11:34]: > Lukas Märdian wrote on 20/09/2024 at 13:12:36+0200: > > # Why > > The ifupdown package is a Debian only solution that is becoming a > > maintenance > > burden. We've had plenty of discussions over the years and consensus is > > that we > > want to get ri

Re: proposal: Hybrid network stack for Trixie

2024-09-23 Thread Lukas Märdian
On 22.09.24 23:59, Josh Triplett wrote: On Sun, Sep 22, 2024 at 10:30:12PM +0200, Andrea Pappacoda wrote: On Sun Sep 22, 2024 at 8:06 PM CEST, Josh Triplett wrote: There's one other desirable feature that would make this a robust solution: having NetworkManager do something to handle or ignore

Re: proposal: Hybrid network stack for Trixie

2024-09-23 Thread Chris Hofstaedtler
* Holger Levsen [240923 10:06]: > I miss ifupdown2 in this discussion. In the older thread, it was pointed out that ifupdown2 might be currently in a bad place maintenance-wise; https://github.com/CumulusNetworks/ifupdown2/pulse/monthly and https://github.com/CumulusNetworks/ifupdown2/graphs/cont

Re: proposal: Hybrid network stack for Trixie

2024-09-23 Thread Holger Levsen
On Mon, Sep 23, 2024 at 10:14:39AM +0200, Chris Hofstaedtler wrote: > * Holger Levsen [240923 10:06]: > > I miss ifupdown2 in this discussion. > In the older thread, it was pointed out that ifupdown2 might be > currently in a bad place maintenance-wise; > https://github.com/CumulusNetworks/ifupdow

ifupdown-ng source stanza (Was: proposal: Hybrid network stack for Trixie)

2024-09-23 Thread Daniel Gröber
Hi Sirius, Thanks for taking ifupdown-ng for a spin. On Mon, Sep 23, 2024 at 08:22:51AM +0200, Sirius wrote: > > If you want no belss or whistles, then install neither of ifupdown, > > network-manager nor systemd-networkd, and operate your network using ip > > and (unless you also consider that a

Re: proposal: Hybrid network stack for Trixie

2024-09-23 Thread Lukas Märdian
On 23.09.24 11:04, Marco d'Itri wrote: On Sep 23, Holger Levsen wrote: ifupdown2 is like ifupdown, just rewritten in python. Yes, that's the problem: there was a consensus that it is not an appropriate dependency for the base system. ifupdown2 will still be around for anybody who wants to ins

Re: proposal: Hybrid network stack for Trixie

2024-09-23 Thread Richard Lewis
Lukas Märdian writes: > On 23.09.24 12:27, Ansgar 🙀 wrote: >> On Mon, 2024-09-23 at 12:22 +0200, Lukas Märdian wrote: >>> On 22.09.24 15:58, Ansgar 🙀 wrote: On Fri, 2024-09-20 at 13:12 +0200, Lukas Märdian wrote: >>> The benefit that Netplan would provide in such cases is that >>> debian-in

ifupdown behaviour with IPv6 DAD failure (Was: proposal: Hybrid network stack for Trixie)

2024-09-23 Thread Daniel Gröber
On Mon, Sep 23, 2024 at 12:25:15PM +0200, Chris Hofstaedtler wrote: > * Pierre-Elliott Bécue [240923 11:34]: > > I like ifupdown. It's simple and just works. > > I find this quite funny, given a recent discussion about IPv6 dad > issues with ifupdown on #debian-admin. The "discussion" was about

Re: proposal: Hybrid network stack for Trixie

2024-09-23 Thread Bjørn Mork
Lukas Märdian writes: > On 23.09.24 12:27, Ansgar 🙀 wrote: > >> So on desktop installations including NetworkManager, netplan will >> be >> configured to do nothing? Why install netplan at all on desktop systems >> then? > > Because it allows to add configuration in a way that is common with serve

Re: proposal: Hybrid network stack for Trixie

2024-09-23 Thread Didier 'OdyX' Raboud
Le lundi, 23 septembre 2024, 13.04:41 h CEST Lukas Märdian a écrit : > On 22.09.24 12:22, Chris Hofstaedtler wrote: > > * Lukas Märdian [240920 13:13]: > >> I've repeated the reasons why I think a hybrid stack using Netplan is a > >> feasible solution many times in previous threads, therefore I'd

Re: proposal: Hybrid network stack for Trixie

2024-09-23 Thread Marco d'Itri
On Sep 23, Holger Levsen wrote: > ifupdown2 is like ifupdown, just rewritten in python. Yes, that's the problem: there was a consensus that it is not an appropriate dependency for the base system. ifupdown2 will still be around for anybody who wants to install it. -- ciao, Marco signature.as

Re: proposal: Hybrid network stack for Trixie

2024-09-23 Thread Ansgar 🙀
Hi, On Mon, 2024-09-23 at 12:22 +0200, Lukas Märdian wrote: > On 22.09.24 15:58, Ansgar 🙀 wrote: > > On Fri, 2024-09-20 at 13:12 +0200, Lukas Märdian wrote: > > > I've repeated the reasons why I think a hybrid stack using Netplan is a > > > feasible solution many times in previous threads, therefo

Re: proposal: Hybrid network stack for Trixie

2024-09-23 Thread Lukas Märdian
On 22.09.24 12:22, Chris Hofstaedtler wrote: * Lukas Märdian [240920 13:13]: I've repeated the reasons why I think a hybrid stack using Netplan is a feasible solution many times in previous threads, therefore I'd like to refer to a list of frequently asked questions, instead of spreading more r

Bug#1082623: ITP: ocaml-cinaps -- trivial metaprogramming tool

2024-09-23 Thread Stéphane Glondu
Package: wnpp Severity: wishlist Owner: Stéphane Glondu X-Debbugs-Cc: debian-devel@lists.debian.org, debian-ocaml-ma...@lists.debian.org * Package name: ocaml-cinaps Version : 0.15.1 Upstream Contact: Jane Street developers * URL : https://github.com/ocaml-ppx/cinaps *

Re: ifupdown behaviour with IPv6 DAD failure (Was: proposal: Hybrid network stack for Trixie)

2024-09-23 Thread Philipp Kern
On 23.09.24 13:39, Daniel Gröber wrote: On Mon, Sep 23, 2024 at 12:25:15PM +0200, Chris Hofstaedtler wrote: * Pierre-Elliott Bécue [240923 11:34]: I like ifupdown. It's simple and just works. I find this quite funny, given a recent discussion about IPv6 dad issues with ifupdown on #debian-ad

Re: Replacing isc-dhcp-client with dhcpcd-base (Was: ifupdown maintenance)

2024-09-23 Thread Daniel Gröber
Hi Martin, On Sat, Sep 14, 2024 at 06:28:36PM +0300, Martin-Éric Racine wrote: > la 14. syysk. 2024 klo 15.30 Daniel Gröber (d...@darkboxed.org) kirjoitti: > > 2) I'm worried about the behavioural change regarding inet/inet6 stanzas > > outlined in #1065085 with a patch by ktetzlaff pending.

Re: proposal: Hybrid network stack for Trixie

2024-09-23 Thread Hakan Bayındır
Hi, On 23.09.2024 ÖS 2:09, Lukas Märdian wrote: But about working towards unified network configuration. -- Lukas So, is it "Let's include it in a dormant state for desktop systems today, so we can go netplan-only in Trixie+1"? I personally can't fathom why there's a great push about netpl

Re: proposal: Hybrid network stack for Trixie

2024-09-23 Thread Marco d'Itri
On Sep 23, Lukas Märdian wrote: > As described in the "Proposal" section and first answer of the FAQ, it's all > about consistency. > > There seems to be a tendency for moving towards a hybrid stack, using > sd-networkd and NetworkManager in different contexts/use-cases. But having > fragmented

Re: proposal: Hybrid network stack for Trixie

2024-09-23 Thread Marvin Renich
* Lukas Märdian [240923 07:05]: > As described in the "Proposal" section and first answer of the FAQ, it's all > about consistency. > > There seems to be a tendency for moving towards a hybrid stack, using > sd-networkd and NetworkManager in different contexts/use-cases. But having > fragmented w

Re: proposal: Hybrid network stack for Trixie

2024-09-23 Thread Holger Levsen
hi, I miss ifupdown2 in this discussion. -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ Change is coming whether you like it or not. signature.asc Description: PGP signature

Re: proposal: Hybrid network stack for Trixie

2024-09-23 Thread Pierre-Elliott Bécue
Lukas Märdian wrote on 20/09/2024 at 13:12:36+0200: > # Why > The ifupdown package is a Debian only solution that is becoming a maintenance > burden. We've had plenty of discussions over the years and consensus is that > we > want to get rid of it. I like ifupdown. It's simple and just works. I

Re: proposal: Hybrid network stack for Trixie

2024-09-23 Thread Lukas Märdian
On 23.09.24 12:27, Ansgar 🙀 wrote: On Mon, 2024-09-23 at 12:22 +0200, Lukas Märdian wrote: On 22.09.24 15:58, Ansgar 🙀 wrote: On Fri, 2024-09-20 at 13:12 +0200, Lukas Märdian wrote: I've repeated the reasons why I think a hybrid stack using Netplan is a feasible solution many times in previous

Re: ifupdown behaviour with IPv6 DAD failure (Was: proposal: Hybrid network stack for Trixie)

2024-09-23 Thread Noah Meyerhans
On Mon, Sep 23, 2024 at 05:48:53PM +0200, Philipp Kern wrote: > > > > I like ifupdown. It's simple and just works. > > > > > > I find this quite funny, given a recent discussion about IPv6 dad > > > issues with ifupdown on #debian-admin. > > > > The "discussion" was about ifup@eth0 being in a fai

Re: proposal: Hybrid network stack for Trixie

2024-09-23 Thread Daniel Baumann
On 9/23/24 13:04, Lukas Märdian wrote: > It's sad to see that fellow DDs do not seem to care It's sad to see that in this and the other thread before, the same weak arguments in favour of netplan are repeated by you without neither adressing the valid points raised against it, nor providing an act

Bug#1082654: ITP: ocaml-optint -- efficient integer types on 64-bit architectures

2024-09-23 Thread Stéphane Glondu
Package: wnpp Severity: wishlist Owner: Stéphane Glondu X-Debbugs-Cc: debian-devel@lists.debian.org, debian-ocaml-ma...@lists.debian.org * Package name: ocaml-optint Version : 0.3.0 Upstream Contact: Romain Calascibetta * URL : https://github.com/mirage/optint * Licens