[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#719792: marked as done (RFA: reconf-inetd -- maintainer script for programmatic updates of inetd.conf)

Your message dated Sun, 16 Feb 2020 00:25:53 +0000
with message-id <E1j37kv-0006LE-Um@fasolo.debian.org>
and subject line Bug#951290: Removed package(s) from unstable
has caused the Debian Bug report #719792,
regarding RFA: reconf-inetd -- maintainer script for programmatic updates of inetd.conf
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.)


-- 
719792: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719792
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: wnpp
Severity: normal

I request an adopter for the reconf-inetd package.

The package description is:
 reconf-inetd is a dpkg-trigger script that updates the configuration of the
 internet superserver. It is a replacement for update-inetd, as per DEP9.
 .
 If the above does not mean anything to you, then you most certainly do not
 need this package.


I do not have the time to be the sole driver of DEP9, and its implementation,
reconf-inetd. reconf-inetd is pretty much complete, it works, and it comes
with dozens of system tests. Remaining work includes:

- port to python 3
- use of a Debian python helper to manage byte-compilation
- file bug reports to the reverse dependencies of update-inetd to migrate to
  reconf-inetd, as described in DEP9 (which also describes how to prepare
  patches)

The last item is a lot of work, and will require interacting with lots of
other maintainers via the BTS. The adopter must know python (reconf-inetd is a
native package), have packaging experience, and lots of motivation.

I'm not sure anymore whether DEP9 (ie. replacing update-inetd with
reconf-inetd) is worthwhile, because inetd (which is what update/reconf-inetd
configure) will eventually be deprecated by systemd and upstart. Having said
that, inetd is unlikely to vanish anytime now, and in the meantime
update-inetd is buggy and has 120k installations.

I'll be around to sponsor (if necessary) & answer questions, but will
otherwise not be actively involved.

Links:

- functional description of reconf-inetd & plan of migration away from
  update-inetd: http://dep.debian.net/deps/dep9/

- pts & git:
http://packages.qa.debian.org/r/reconf-inetd.html
http://git.debian.org/?p=collab-maint/reconf-inetd.git;a=summary

- vaguely related talk at fosdem (includes a description of the reconf-inetd
  system tests)
  http://video.fosdem.org/2012/crossdistro/How_to_replace_a_legacy_tool_with_100k_installations.webm

--- End Message ---
--- Begin Message --- 
Version: 1.120603+rm

Dear submitter,

as the package reconf-inetd has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/951290

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

--- End Message ---
Reply to: