Bug#412387: [#412387] patch doesn't fix the real issue

2007-03-06 Thread Ben Hutchings
You wrote: Setting up apt-proxy (1.9.35-0.2) ... Disabling inetd's apt-proxy v1 line. invoke-rc.d: unknown initscript, /etc/init.d/inetd not found. dpkg: error processing apt-proxy (--configure): subprocess post-installation script returned error exit status 100 Errors were encountered

Bug#412387: [#412387] patch doesn't fix the real issue

2007-03-03 Thread Ben Hutchings
Why depend on anything to do with inetd when it's only ever needed on upgrades from very old versions? The stable version is 1.9.29, so there is no need to support upgrades from pre-1.9. I propose to remove this part of the upgrade logic altogether: diff -ur

Bug#412387: [#412387] patch doesn't fix the real issue

2007-03-03 Thread Damyan Ivanov
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - -=| Ben Hutchings, 3.03.2007 14:24 |=- Why depend on anything to do with inetd when it's only ever needed on upgrades from very old versions? The stable version is 1.9.29, so there is no need to support upgrades from pre-1.9. I propose to

Bug#412387: [#412387] patch doesn't fix the real issue

2007-03-02 Thread Damyan Ivanov
Hi, Looking at the .postinst, there is no need to restart inetd at all, since this will be done by update-inetd. Quoting from update-inetd(8): - After the /etc/inetd.conf file has been changed, update-inetd will send a SIGHUP signal to the inetd process to make sure that inetd will use