Bug#435991: [Pkg-emboss-devel] Bug#435991: emboss-explorer: crontest failure find: /var/www/emboss-explorer: No such file or directory
found 435991 2.2.0-3 reopen 435991 thanks On Wed, Sep 26, 2007 at 07:12:54PM +0200, David Paleino wrote: fixed 435991 2.2.0-4 thanks Hi, I've fixed this in our SVN repository. I'm afraid this isn't fixed, you should check if do_cleanup.sh is present itself, otherwise you just moved the problem :) Either move do_cleanup.sh inside the crontab (preferred?) or change the crontab to read: [ -e /usr/share/emboss-explorer/do_cleanup.sh ] /usr/share/emboss-explorer/do_cleanup.sh thanks, filippo -- Filippo Giunchedi - http://esaurito.net PGP key: 0x6B79D401 random quote follows: I find television very educating. Every time somebody turns on the set, I go into the other room and read a book. -- Groucho Marx signature.asc Description: Digital signature
Bug#435991: [Pkg-emboss-devel] Bug#435991: emboss-explorer: crontest failure find: /var/www/emboss-explorer: No such file or directory
fixed 435991 2.2.0-4 thanks Hi, I've fixed this in our SVN repository. Please, any DD following [EMAIL PROTECTED], consider uploading the new version of emboss-explorer. Kindly, David -- . ''`. Debian maintainer | http://snipurl.com/gofoxygo/ : :' : Linuxer #334216 | http://www.hanskalabs.net/ `. `'`GPG: 1392B174 | http://www.debianizzati.org/ `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#435991: [Pkg-emboss-devel] Bug#435991: emboss-explorer: crontest failure find: /var/www/emboss-explorer: No such file or directory
On Sun, Aug 05, 2007 at 12:13:56AM -0400, Justin Pryzby wrote: On Sun, Aug 05, 2007 at 12:56:01PM +0900, Charles Plessy wrote: Le Sat, Aug 04, 2007 at 04:05:47PM +0200, Filippo Giunchedi a écrit : it seems that emboss-explorer cron files are giving output when the package itself is removed (REMOVE) or its dependencies (AUTOREMOVE). Dear Filippo, I am affraid that I do not understand the problem. Can you give me a link to the relevant part of the policy documenting the interaction bewteen package removal and cron jobs? Actually (unfortunately) I don't think the policy specifically mentions this. It does, however, mention this case for initscripts I checked, it does in section 9.5, last sentence: The scripts or crontab entries in these directories should check if all necessary programs are installed before they try to execute them. Otherwise, problems will arise when a package was removed but not purged since configuration files are kept on the system in this situation. filippo -- Filippo Giunchedi - http://esaurito.net PGP key: 0x6B79D401 random quote follows: I always keep the Titanic in mind when I talk about security or safety, meaning that nothing is fully secure. -- Anonymous (?)
Bug#435991: [Pkg-emboss-devel] Bug#435991: emboss-explorer: crontest failure find: /var/www/emboss-explorer: No such file or directory
On Sun, Aug 05, 2007 at 12:13:56AM -0400, Justin Pryzby wrote: Crontabs have the same problem. They're in /etc, are often dpkg conffiles, and cause some program to be executed. But the existence of the program binary can't be guarnateed, so nonexistence should be handled cleanly and elegantly. Exactly, thanks Justin. Also, what is the AUTOREMOVE fuction you are talking about? Hmm this I can't answer.. I think maybe he means dpkg deconfigure action? It is the new apt feature of removing packages installed automatically but no longer in use (a-la aptitude). The test is for spotting cronjobs depending on one of their deps to be available (e.g. #436025). Sorry if that wasn't clear enough. HTH, filippo -- Filippo Giunchedi - http://esaurito.net PGP key: 0x6B79D401 random quote follows: UNIX was not designed to stop its users from doing stupid things, as that would also stop them from doing clever things. -- Doug Gwyn -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#435991: [Pkg-emboss-devel] Bug#435991: emboss-explorer: crontest failure find: /var/www/emboss-explorer: No such file or directory
Le Sat, Aug 04, 2007 at 04:05:47PM +0200, Filippo Giunchedi a écrit : it seems that emboss-explorer cron files are giving output when the package itself is removed (REMOVE) or its dependencies (AUTOREMOVE). Dear Filippo, I am affraid that I do not understand the problem. Can you give me a link to the relevant part of the policy documenting the interaction bewteen package removal and cron jobs? Also, what is the AUTOREMOVE fuction you are talking about? Have a nice day, -- Charles Plessy http://charles.plessy.org Wako, Saitama, Japan
Bug#435991: [Pkg-emboss-devel] Bug#435991: emboss-explorer: crontest failure find: /var/www/emboss-explorer: No such file or directory
On Sun, Aug 05, 2007 at 12:56:01PM +0900, Charles Plessy wrote: Le Sat, Aug 04, 2007 at 04:05:47PM +0200, Filippo Giunchedi a écrit : it seems that emboss-explorer cron files are giving output when the package itself is removed (REMOVE) or its dependencies (AUTOREMOVE). Dear Filippo, I am affraid that I do not understand the problem. Can you give me a link to the relevant part of the policy documenting the interaction bewteen package removal and cron jobs? Actually (unfortunately) I don't think the policy specifically mentions this. It does, however, mention this case for initscripts which have exactly the same problem. initscripts are in /etc, and are typically dpkg conffiles. But conffiles aren't removed when the package is removed (only when it's purged), so if an initscript of a removed (but not purged) package were to attempt starting a program from that package, it would fail. The recommended way to avoid this is to add to the top of the initscript: [ -x $DAEMON ] || exit 0 Crontabs have the same problem. They're in /etc, are often dpkg conffiles, and cause some program to be executed. But the existence of the program binary can't be guarnateed, so nonexistence should be handled cleanly and elegantly. Also, what is the AUTOREMOVE fuction you are talking about? Hmm this I can't answer.. I think maybe he means dpkg deconfigure action? Justin
