Bug#1003796: ITP: ifupdown-ng -- network device manager compatible with ifupdown
On 1/23/22 21:03, d...@darkboxed.org wrote: Hi Thomas, I've been working on the ifupdown-ng packaging today. I had a look at your existing git repo and did incorporate most of the debian/ files from that but decided to start the repo from scratch. The main reason being that I don't feel the gbp-import-ref workflow is quite ready yet so while I would prefer basing Debian packaging on the upstream git repo as you've done it just causes more friction right now in my experience. Hi, I'm not using gbp-import-ref, but my own tooling from openstack-pkg-tools. To import a new tag, I just do: ./debian/rules fetch-upstream-remote git merge -X theirs dch -i # edit changelog to match the new tag name ./debian/rules gen-orig-xz Maybe gbp-import-ref does the same thing? I've used this workflow for all of the OpenStack packages [1] without any issue for YEARS. I'm also not sure what kind of "friction" you're referring to... Could you add me to the debian/ifupdown-ng repo so I can push my work there? In the meantime the repo is here: https://salsa.debian.org/dxld-guest/ifupdown-ng/ One significant thing I noticed is that you seem to have Depends specifically for kfreebsd and hurd which I haven't dealt with yet. Did you test this stuff on those systems? I am not sure why I wrote these dependencies, probably because it was like that upstream already. I haven't tested on these arch, however, it should be easy to do so with Virtualbox or Qemu. FYI, when I first uploaded openrc to Debian, I used Virtualbox with the help of an OpenRC upstream author, so we could check and fix the port. These aren't official arch these days, so it maters less. Ordinarily I would think we could just go and get access porterbox for these arches but since I need to play with networking stuff for testing the porterboxes are likely not going to be much help. Right, porterbox wont be of any help here. Anyway, I have merged all of your changes to the main Salsa repository, and gave you access to it. Since you've audited my work and the package looks like in good enough shape, I have uploaded the final result. It's now up for review on the FTP master NEW queue. Let's hope it clears the NEW queue quickly... :) When it does, I very much welcome you to take care of this package as much as possible yourself, as I'm a fairly busy DD maintaining many packages. I will happily sponsor any change you want to include. Cheers, Thomas Goirand (zigo) [1] https://qa.debian.org/developer.php?login=team%2Bopenstack%40tracker.debian.org
Bug#1003796: ITP: ifupdown-ng -- network device manager compatible with ifupdown
Hi Thomas, I've been working on the ifupdown-ng packaging today. I had a look at your existing git repo and did incorporate most of the debian/ files from that but decided to start the repo from scratch. The main reason being that I don't feel the gbp-import-ref workflow is quite ready yet so while I would prefer basing Debian packaging on the upstream git repo as you've done it just causes more friction right now in my experience. Could you add me to the debian/ifupdown-ng repo so I can push my work there? In the meantime the repo is here: https://salsa.debian.org/dxld-guest/ifupdown-ng/ One significant thing I noticed is that you seem to have Depends specifically for kfreebsd and hurd which I haven't dealt with yet. Did you test this stuff on those systems? Hurd still seems to be available as d-i/bootable images at[1] but I'm having trouble finding any way to even install a Debian/kFreeBSD system for bullseye. I suspect I should at least lightly test this stuff there if we're going to have (seemingly) explicit support for those systems. [1]: https://cdimage.debian.org/cdimage/ports/ Ordinarily I would think we could just go and get access porterbox for these arches but since I need to play with networking stuff for testing the porterboxes are likely not going to be much help. --Daniel signature.asc Description: PGP signature
Bug#1003796: ITP: ifupdown-ng -- network device manager compatible with ifupdown
Hi Thomas, On Sun, Jan 16, 2022 at 09:17:25PM +0100, Thomas Goirand wrote: > There's already some kind of packaging over here: > https://salsa.debian.org/debian/ifupdown-ng Uh, nice. I'll check it out. > I started it, and then stopped, seeing that others were about to do it, in > the hope to not get into the packaging of yet-another-thing. Understandable, haha. > However, I'd happily be co-maintainer. Sure thing :) --Daniel signature.asc Description: PGP signature
Bug#1003796: ITP: ifupdown-ng -- network device manager compatible with ifupdown
On 1/15/22 23:31, Daniel Gröber wrote: Package: wnpp Severity: wishlist Owner: Daniel Gröber X-Debbugs-Cc: debian-de...@lists.debian.org, d...@darkboxed.org Hi, * Package name: ifupdown-ng Version : 0.11.3 Upstream Author : Ariadne Conill Maximilian Wilhelm * URL : https://github.com/ifupdown-ng/ifupdown-ng * License : ISC Programming Lang: C, Shell Description : network device manager compatible with ifupdown ifupdown-ng is a network device manager which is backwards compatible with traditional ifup and ifdown as used on Debian and Alpine systems, while solving many design deficits with the original approach through robust error handling and the use of a dependency-solver to determine interface bring-up order. Unlike ifupdown2 (already in Debian) ifudown-ng's core is written in plain C with "executors" written in Shell talking to the kernel and system services, making it quite light yet easy to extend. See also Maximilian Wilhelm's Debconf21 talk: https://debconf21.debconf.org/talks/52-contemporary-networking-configuration-with-ifupdown-ng/ I plan on maintaining this package by myself, however I am looking for a sponsor. --Daniel Hi Daniel, There's already some kind of packaging over here: https://salsa.debian.org/debian/ifupdown-ng I started it, and then stopped, seeing that others were about to do it, in the hope to not get into the packaging of yet-another-thing. However, I'd happily be co-maintainer. Your thoughts? Cheers, Thomas Goirand (zigo)
Bug#1003796: ITP: ifupdown-ng -- network device manager compatible with ifupdown
Hi Andrej, On Sun, Jan 16, 2022 at 03:31:17PM +0100, Andrej Shadura wrote: > I would be happy to sponsort ifupdown-ng for you. Awesome! I'll let you know as soon as I have a package to review up on salsa. --Daniel
Bug#1003796: ITP: ifupdown-ng -- network device manager compatible with ifupdown
Hi Daniel, On Sat, 15 Jan 2022, at 23:31, Daniel Gröber wrote: > * Package name: ifupdown-ng > Version : 0.11.3 > Upstream Author : Ariadne Conill > Maximilian Wilhelm > * URL : https://github.com/ifupdown-ng/ifupdown-ng > * License : ISC > Programming Lang: C, Shell > Description : network device manager compatible with ifupdown > > ifupdown-ng is a network device manager which is backwards compatible with > traditional ifup and ifdown as used on Debian and Alpine systems, while > solving many design deficits with the original approach through robust > error handling and the use of a dependency-solver to determine interface > bring-up order. > > Unlike ifupdown2 (already in Debian) ifudown-ng's core is written in plain > C with "executors" written in Shell talking to the kernel and system > services, making it quite light yet easy to extend. > > See also Maximilian Wilhelm's Debconf21 talk: > > https://debconf21.debconf.org/talks/52-contemporary-networking-configuration-with-ifupdown-ng/ > > I plan on maintaining this package by myself, however I am looking for > a sponsor. I would be happy to sponsort ifupdown-ng for you. -- Cheers, Andrej
Bug#1003796: ITP: ifupdown-ng -- network device manager compatible with ifupdown
Package: wnpp Severity: wishlist Owner: Daniel Gröber X-Debbugs-Cc: debian-de...@lists.debian.org, d...@darkboxed.org Hi, * Package name: ifupdown-ng Version : 0.11.3 Upstream Author : Ariadne Conill Maximilian Wilhelm * URL : https://github.com/ifupdown-ng/ifupdown-ng * License : ISC Programming Lang: C, Shell Description : network device manager compatible with ifupdown ifupdown-ng is a network device manager which is backwards compatible with traditional ifup and ifdown as used on Debian and Alpine systems, while solving many design deficits with the original approach through robust error handling and the use of a dependency-solver to determine interface bring-up order. Unlike ifupdown2 (already in Debian) ifudown-ng's core is written in plain C with "executors" written in Shell talking to the kernel and system services, making it quite light yet easy to extend. See also Maximilian Wilhelm's Debconf21 talk: https://debconf21.debconf.org/talks/52-contemporary-networking-configuration-with-ifupdown-ng/ I plan on maintaining this package by myself, however I am looking for a sponsor. --Daniel
