Re: new test on archive packages: cron files
hello Michael, On Thu, Aug 02, 2007 at 11:11:47AM +0200, Michael Ablassmeier wrote: > great stuff! The Format looks right to me, even tho some of those entries > appear twice? The usual way would be to commit this logfile into the collab-qa > repository and write a small Notes file which explains what those marks like > CMD_NOT_FOUND mean. (collab-qa/crontest/{Notes,/crontest-/logfile.txt}) I fixed the duplicate lines and commited crontest/ directory to collab-qa with the latest run results as well. I'm writing Notes file. > > Then go ahead and file bugs for the packages. You can usertag the bugs with a > usertag like 'qa-cron-' and the user set to the QA groups mail address. > You can then mark the packages you have filed bugs for with NNN: and use the > bts2pkglist.pl from tools/ to fetch all the filed bugs and replace the NNN: in > your list with the real bug ID (so you dont have to wait for the BTS to come > up > with a bugnumber while processing ..) great :) > > Lucas does some magic with his ruby scripts to merge old logs with new ones > and > does so mark new failures with NEWFAIL etc.. im not sure if they would work > with > your list, .. if you want to run this check on a regular basis this is > something > we should look into. Sure I can run periodically, once in two weeks sounds ok? I'll investigate NEWFAIL stuff as well. thanks, 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]
Re: [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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]