Re: piuparts unprocessed failed logs page
pe, 2006-08-11 kello 14:42 +1000, Brian May kirjoitti: Can the argument be made that these aren't packaging bugs but rather the fact the hostname hasn't been configured correctly? Not only can that argument be made, but I would like to make it myself. I'll fix the chroot piuparts uses so that hostname works within it. -- One does not see anything until one sees its beauty. -- Oscar Wilde -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: piuparts unprocessed failed logs page
ke, 2006-08-09 kello 10:21 +0300, Lars Wirzenius kirjoitti: While I wait to have time to do something better and more easily usable, the following page lists the logs of failed piuparts files that have not yet been processed: http://piuparts.cs.helsinki.fi/fail/ I made some more logs available, in the hope that they're useful: http://piuparts.cs.helsinki.fi/bugged/ http://piuparts.cs.helsinki.fi/fixed/ http://piuparts.cs.helsinki.fi/untestable/ The meaning is this: * fail is UNPROCESSED log files for failed piuparts tests. The problems may or may not be in the package, and they may be temporary (e.g., mirror problems). * bugged is failures for which a bug has been reported; the log file is moved there from the fail directory manually. The goal is to have the bug number at the top of the file. Sometimes the bug hasn't been reported and there's some other explanation. Sometimes there's no good reason for the log to be there anymore (or in the first place); my fingers sometimes fumble, and my brain, too. * fixed is where a log moves from bugged after a bug has been fixed. * untestable is where logs for packages are stored that can't be tested with piuparts, for whatever reason (sometimes because piuparts is not smart enough). The only category of log files not visible via http is the pass ones, i.e., logs for piuparts runs that failed to find any problems in the package. These are not public because the directory is huge. -- Every time I say /quit I die a little. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: piuparts unprocessed failed logs page
ke, 2006-08-09 kello 11:45 -0700, Kevin B. McCarty kirjoitti: I was looking through these, and at least the following errors appear to be false positives for the given packages, caused only by some combination of x11-common, xcursor-themes, xutils (which leaves behind junk in /etc/X11/rstart), xlibs-data (which leaves things in /usr/X11R6/lib/X11/icons, looks like #362109 was already filed about this) and/or ttf-bitstream-vera. Yeah, that happens a lot. piuparts can't know (or at least doesn't try; anyone wanting to send an AI patch is welcome) which package it is that actually fails, so if there's a package that lots of others depend on (like xutils or the others), and that fails (and sometimes they fail only when tested with packages that depend on them), there's a lot of false positives. That's why logs are processed manually before bugs are reported. Hope this is helpful. Sure, thanks. -- Programming should be fun, otherwise you're doing something wrong. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: piuparts unprocessed failed logs page
Lars == Lars Wirzenius [EMAIL PROTECTED] writes: Lars While I wait to have time to do something better and more Lars easily usable, the following page lists the logs of failed Lars piuparts files that have not yet been processed: Lars http://piuparts.cs.helsinki.fi/fail/ http://piuparts.cs.helsinki.fi/fail/heimdal-kdc_0.7.2.dfsg.1-3.log: ... Setting up krb5-config (1.10) ... dnsdomainname: Unknown host ... Setting up heimdal-kdc (0.7.2.dfsg.1-3) ... hostname: Unknown host kstash: writing key to `/var/lib/heimdal-kdc/m-key' kstash: writing master key file: unable to find realm of host piatti dpkg: error processing heimdal-kdc (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: heimdal-kdc E: Sub-process /usr/bin/dpkg returned an error code (1) ... Can the argument be made that these aren't packaging bugs but rather the fact the hostname hasn't been configured correctly? Or... Is it expected Debian packages should be able to cope regardless? In the case of heimdal-kdc, it makes no sense to install heimdal-kdc without the realm, and if the realm cannot be guessed by looking up the hostname domain, and if it cannot be found by debconf question, it makes no sense to continue. -- Brian May [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: piuparts unprocessed failed logs page
Hi Lars, I was looking through these, and at least the following errors appear to be false positives for the given packages, caused only by some combination of x11-common, xcursor-themes, xutils (which leaves behind junk in /etc/X11/rstart), xlibs-data (which leaves things in /usr/X11R6/lib/X11/icons, looks like #362109 was already filed about this) and/or ttf-bitstream-vera. amphetamine-data_0.8.7-12 artwiz-cursor_1:1.3-5 big-cursor_3.6 culmus_0.101-6 curator_2.1-5 extract_0.5.14-2 fgfs-base_0.9.10-1 fsviewer-icons_1.0-4 genesis-data_2.2.1-8 gftp-common_2.0.18-15 gvr-lessons_0.5-2 holotz-castle-data_1.3.8-1.1 jikes-kaffe_2:1.1.7-3 ketm-data_0.0.6-19 kq-data_0.99.cvs20060528-3 libgcompris-1-dev_7.4-3+b1 libgtk2.0-common_2.8.18-7 libsdl1.2debian-alsa_1.2.11-2 libsdl1.2debian-arts_1.2.11-2 libsdl1.2debian-esd_1.2.11-2 libsdl1.2debian-nas_1.2.11-2 libsdl1.2debian-oss_1.2.11-2 libx11-6_2:1.0.0-8 mesa-common-dev_6.4.2-1 paw-common_2005.05.09.dfsg-9 powermanga-data_0.80-3 python-openal_0.1.6-2 python-sip4-dev_4.4.5-2 rafkill-data_1.2.1-3 sunclock-maps_3.56-1 sylpheed-claws-themes_20060615-1 wesnoth-data_1.1.8-1 wing-data_0.7-27 xfonts-100dpi-transcoded_1:1.0.0-2 xfonts-75dpi-transcoded_1:1.0.0-2 The piuparts error usually looks something like this: 3m0.4s ERROR: Package purging left files on system: /etc/X11 owned by: x11-common, xcursor-themes /usr/X11R6 owned by: x11-common /usr/X11R6/lib owned by: x11-common /usr/X11R6/lib/X11 owned by: x11-common /usr/X11R6/lib/X11/icons /usr/X11R6/lib/X11/icons/default /usr/share/fonts owned by: ttf-bitstream-vera or if xutils is involved, like this: 2m18.8s ERROR: Package purging left files on system: /etc/X11 owned by: x11-common, culmus /etc/X11/rstart /etc/X11/rstart/commands /etc/X11/rstart/commands/@List /etc/X11/rstart/commands/ListContexts /etc/X11/rstart/commands/ListGenericCommands /etc/X11/rstart/commands/x11r6 /etc/X11/rstart/commands/x11r6/@List /etc/X11/rstart/commands/x11r6/LoadMonitor /etc/X11/rstart/commands/x11r6/Terminal /etc/X11/rstart/config /etc/X11/rstart/contexts /etc/X11/rstart/contexts/@List /etc/X11/rstart/contexts/default /etc/X11/rstart/contexts/x11r6 Other common packages that left junk on the system included libcupsys2, cupsys, gs-esp, libcupsys2-gnutls10, gsfonts, defoma, gs-common. Hope this is helpful. -- Kevin B. McCarty [EMAIL PROTECTED] Physics Department WWW: http://www.princeton.edu/~kmccarty/Princeton University GPG: public key ID 4F83C751 Princeton, NJ 08544 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
