quoting Jakub Wilk:
> But next reconf-inetd run can happen a month later. (Or never.) In the mean
> time, nyancat server won't be running, will it? Or did I misunderstand
> something?
That's right. I take responsibility for that; I didn't realise that the
postinst script would run after the reconf-inetd trigger.
In any case, the solution is simple: invoke reconf-inetd right after
update-inetd in postinst.
On a different topic, nyancat/1.0+git20120519.5fe3de9-1 checks for only a
specific release:
if [ "$2" = "0.1+git20120401.5a88b86-1" ]; then
whereas ideally it'd take action on any release less than or equal to that.
(perhaps that's not relevant to nyancat, but it'd be nice to get it right,
because I suspect that other maintainers will copy from it)
thanks,
sez
--
Every great idea is worthless without someone to do the work. --Neil Williams
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120602112901.GA19589@mobee
