Hi Jon, On Tue, Apr 01, 2014 at 11:51:09PM +0100, Jonathan McCrohan wrote: > Hi Serafeim, > > On 02/01/14 23:13, Serafeim Zanikolas wrote: > > Here's a list of instructions instead: > > > > - don't ship anything under /usr/share/reconf-inetd/ > > - replace dependency on reconf-inetd with one on update-inetd > > - revert postinst script to the one you had before, and put > > "reconf-inetd || true" before invoking "update-inetd --add ..." > > (the former will remove any entries added by reconf-inetd, for which > > there's > > no fragment under /usr/share/reconf-inetd) > > > > Let me know if you run into any issues. > > Have you tested this yourself? I have tried above and it doesn't work.
I haven't tested it, and in fact my suggestion shouldn't work (sorry). I didn't remember that reconf-inetd won't delete an inetd.conf entry that refers to an existing path (that's a feature; see table in http://dep.debian.net/deps/dep9/#index3h1). > How you do you propose you fix this? I see two alternatives. Either we leave nyancat on reconf-inetd (it does work and in fact it's the only way to have both ip4 & ipv6 entries, it's just that it doesn't make much sense to keep reconf-inetd for just one package). Alternatively, you can put in postinst "update-inetd --multi --pattern nyancat --remove telnet" on the condition that the nyancat server package is being upgraded from 1.2.2-1 (the latest version that uses reconf-inetd) *and* inetd.conf has telnet entries exactly as they were shipped by that version. That's more or less the example snippet at http://dep.debian.net/deps/dep9/#index5h1 but adding the new entries with update-inetd (instead of reconf-inetd). If you're okay with the latter idea, I'll send you a patch. -- Every great idea is worthless without someone to do the work. --Neil Williams -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
