Bug#1003796: marked as done (ITP: ifupdown-ng -- network device manager compatible with ifupdown)
Your message dated Mon, 31 Jan 2022 17:00:09 +0000
with message-id <E1nEa2D-000F4G-C4@fasolo.debian.org>
and subject line Bug#1003796: fixed in ifupdown-ng 0.11.4~rc1-1
has caused the Debian Bug report #1003796,
regarding ITP: ifupdown-ng -- network device manager compatible with ifupdown
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
1003796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003796
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Daniel Gröber <dxld@darkboxed.org>
X-Debbugs-Cc: debian-devel@lists.debian.org, dxld@darkboxed.org
Hi,
* Package name : ifupdown-ng
Version : 0.11.3
Upstream Author : Ariadne Conill <ariadne@dereferenced.org>
Maximilian Wilhelm <max@sdn.clinic>
* 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
--- End Message ---
--- Begin Message ---
Source: ifupdown-ng
Source-Version: 0.11.4~rc1-1
Done: Maximilian Wilhelm <max@sdn.clinic>
We believe that the bug you reported is fixed in the latest version of
ifupdown-ng, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1003796@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Maximilian Wilhelm <max@sdn.clinic> (supplier of updated ifupdown-ng package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Sat, 16 Oct 2021 15:40:25 +0200
Source: ifupdown-ng
Binary: ifupdown-ng ifupdown-ng-dbgsym
Architecture: source amd64
Version: 0.11.4~rc1-1
Distribution: unstable
Urgency: medium
Maintainer: Ifupdown NG Maintainers <team+ifupdownng@tracker.debian.org>
Changed-By: Maximilian Wilhelm <max@sdn.clinic>
Description:
ifupdown-ng - Network Interface Management tool similar to ifupdown{,2}
Closes: 1003796
Changes:
ifupdown-ng (0.11.4~rc1-1) unstable; urgency=medium
.
* Initial release. (Closes: #1003796)
Checksums-Sha1:
05ce274709927e377ad82c796996755b105c561a 2117 ifupdown-ng_0.11.4~rc1-1.dsc
b80251f1fbb505cab7c62a706e740491ae21ccd3 69568 ifupdown-ng_0.11.4~rc1.orig.tar.xz
5cbe3218eadc8607562e5ef50f29ccf54449f19b 3136 ifupdown-ng_0.11.4~rc1-1.debian.tar.xz
e6873da4dcb99f8db706f9123e74e461b1ebfbb4 72216 ifupdown-ng-dbgsym_0.11.4~rc1-1_amd64.deb
67ad75c9d15fcd99c1c4fb7530970ccf88a95bdd 7404 ifupdown-ng_0.11.4~rc1-1_amd64.buildinfo
0a2ea05bc2ba23d59111ea39d26e22f23b0c1ab4 63572 ifupdown-ng_0.11.4~rc1-1_amd64.deb
Checksums-Sha256:
789ad82868c31030d5c32507034c2b7fdbcf8bc4a35d3455afb11627a18c0141 2117 ifupdown-ng_0.11.4~rc1-1.dsc
d3c3b563785f35e59dde4b93b0075e67cea65e1139045516aff5574bc1afc43e 69568 ifupdown-ng_0.11.4~rc1.orig.tar.xz
794f66c382b459f6833587ba5b637d3fa369605d0c0b29d33e582515a5af7c9a 3136 ifupdown-ng_0.11.4~rc1-1.debian.tar.xz
abcd0c54988f4906c4736a989b596d532a6c48b5f2c89134542cca17ecf25d39 72216 ifupdown-ng-dbgsym_0.11.4~rc1-1_amd64.deb
08f0322ca01efe48d14f8f0a015bf6fb6ec77486378114d4113d867635e3b279 7404 ifupdown-ng_0.11.4~rc1-1_amd64.buildinfo
f4d7904a5f2cffa2bdb95809745e66cf262b60e098b8b0f60c8d41d8a76cb786 63572 ifupdown-ng_0.11.4~rc1-1_amd64.deb
Files:
c54688c18d897702b761df53daa4e015 2117 admin optional ifupdown-ng_0.11.4~rc1-1.dsc
023817235b134aaa6120e33354387e54 69568 admin optional ifupdown-ng_0.11.4~rc1.orig.tar.xz
d204e07b166c65a41c35b0cc1c786164 3136 admin optional ifupdown-ng_0.11.4~rc1-1.debian.tar.xz
7f5d66acedf74c6f7cd8c7c78255bab9 72216 debug optional ifupdown-ng-dbgsym_0.11.4~rc1-1_amd64.deb
b0835d341d5c35c033167dd7491dc45e 7404 admin optional ifupdown-ng_0.11.4~rc1-1_amd64.buildinfo
4a63478659c4ab6e3a8b7f4ad55c006a 63572 admin optional ifupdown-ng_0.11.4~rc1-1_amd64.deb
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmH3q0IACgkQ1BatFaxr
Q/4G0Q//YmG35WeW2c2KHWjoZMmehMyZOeMBVna35YaV38S7Gem7l2zEZYuZQIVY
6HcGI3I3ZOVqA46BlFWXgSA9QqLxfZNVdpiZhEW8w0+mHaMXRbcd/mZ2DzKDyz7D
SSls3IANAa84ntEXaJpkosNS2yFOANCZgg0ttkuFJmvDkAJK/dJFl9hbk2/1qFBA
4X4s7giDI1+R6CJTWbpQ90MH211DDNChKym5CaWvL+B4MI6ajaK3UDQuM5wlsqb6
gpJTsekO4iGW9qStMspysjHdh10ugPYq55c5KrrrUyBRZXpuXVT5cukUA3gbIQnK
J7TQ2dfsQAslCUd4RaTefcX/ctKgY6z9R+r5giuQDw0ewyz+raUjN8e6ed4el8SH
OOTd1jTrSjp6oiLp9TbaUI5XiCeMuaVn5qC8LU8ooQFvU16sPK99io2tTkjpX9HA
v9fRwy2hq3GFhyIBga3NjgNf2kFPa2tJByuuFwMJzIqwvLmMrZs38LgyS9a0hjRs
TM9F6GaMqKHBA5TDVg5K3fyp/LJZ8olk+3E22PIAp22kzKDqG/ffwg0atvtfTm+c
9Hud4WY0ruLUFTkFPJYXUubWgWfA9nzI9iCvvYUH+/i0M8F0DzUrXRKQy1GHPpPp
/ha82HPY3k1aGCvTl5CCT9vYoSLi14AIMLhON1Cajv8PXwpmk6I=
=wxEF
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: