Bug#386679: Please clean discover1 init.d script
Package: discover Version: 2.1.0-1 Severity: normal Hi, I've installed Etch (d-i beta 3) and ended with discover1 package. I've upgraded to discover (2.1.0-1) and in the next reboot I've notice a lot of error during the boot. It seems that since discover stopped shiping the init.d script, /etc/init.d still has the init.d script from discover1. Since discover conflicts with discover1 that package is removed but not purged. The init.d script stay in the system till the purge. Please clean the discover1 init.d script. Thanks. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-amd64-generic Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages discover depends on: ii libdiscover2 2.1.0-1hardware identification library discover recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#386679: Please clean discover1 init.d script
reassign 386679 discover1 thanks [Lior Kaplan] I've installed Etch (d-i beta 3) and ended with discover1 package. I've upgraded to discover (2.1.0-1) and in the next reboot I've notice a lot of error during the boot. If the init.d script in discover1 can't run properly after the package is removed but before it is purged, then I believe that is a bug in the discover1 package, and it need to be fixed there. I am not sure if it make sense to let the discover package purge files for the discover1 package. Great to hear that you are testing discover v2. :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#386679: Please clean discover1 init.d script
Since etc/init.d/discover is a conffile for discover1 package, it should not be deleted when the package is removed, only when it is purged. So it's not a bug in disocver1, but normal behaviour. Since disocver conflicts with discover1 is it OK to removed their init.d file. discover1 does remove it's init.d script when purged. I'd wait for your response before reassgining it back to discover. Kaplan On Sat, September 9, 2006 3:03 pm, Petter Reinholdtsen wrote: reassign 386679 discover1 thanks [Lior Kaplan] I've installed Etch (d-i beta 3) and ended with discover1 package. I've upgraded to discover (2.1.0-1) and in the next reboot I've notice a lot of error during the boot. If the init.d script in discover1 can't run properly after the package is removed but before it is purged, then I believe that is a bug in the discover1 package, and it need to be fixed there. I am not sure if it make sense to let the discover package purge files for the discover1 package. Great to hear that you are testing discover v2. :) -- Lior Kaplan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#386679: Please clean discover1 init.d script
[Lior Kaplan] Since etc/init.d/discover is a conffile for discover1 package, it should not be deleted when the package is removed, only when it is purged. Exactly. And the presense of that init.d script after the package is removed and before it is purged should not lead to errors, so if you see errors in that case, those need to be fixed in the init.d script in discover1. Since disocver conflicts with discover1 is it OK to removed their init.d file. Nope, I do not believe this is OK. I suspect it is against policy too. And this is partly the reason why I assigned it to discover1 instead of discover. Friendly, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#386679: Please clean discover1 init.d script
On Sat, September 9, 2006 6:49 pm, Petter Reinholdtsen wrote: [Lior Kaplan] Since etc/init.d/discover is a conffile for discover1 package, it should not be deleted when the package is removed, only when it is purged. Exactly. And the presense of that init.d script after the package is removed and before it is purged should not lead to errors, so if you see errors in that case, those need to be fixed in the init.d script in discover1. Since discover provides the same binary as discover1 (/sbin/discover), the init.d script can't know the package isn't installed. The script *does* check for the binary existence, but not for it's source package. This is why I ask discover to fix this, and not discover1. Since disocver conflicts with discover1 is it OK to removed their init.d file. Nope, I do not believe this is OK. I suspect it is against policy too. And this is partly the reason why I assigned it to discover1 instead of discover. If you conflict with a package, it's the same as owning it's files, so you should take care of this problem in discover. This is OK, same way you provided the same init.d script in the past. -- Lior Kaplan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
