Processed: Bug#493702: bot fixed in tla 1.3.5+dfsg-13
Processing commands for [EMAIL PROTECTED]: found 493702 1.3.5+dfsg-13 Bug#493702: tla(GNU/k*BSD): FTBFS: out of date libtool scripts Bug marked as found in version 1.3.5+dfsg-13 and reopened. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Bug#404248: not fixed in apollon 1.0.2.1-3
Processing commands for [EMAIL PROTECTED]: found 404248 1.0.2.1-3 Bug#404248: apollon(GNU/k*BSD): FTBFS: out of date libtool scripts Bug marked as found in version 1.0.2.1-3 and reopened. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493702: bot fixed in tla 1.3.5+dfsg-13
found 493702 1.3.5+dfsg-13 thanks Hello (Aurelien), unfortunately #493702 is not fixed, The 06-relibtoolize.dpatch is not included in debian/patches/00list, therefore it is not applied during build. Petr tla (1.3.5+dfsg-13) unstable; urgency=low . * QA upload. * debian/patches/06-relibtoolize.dpatch: relibtoolize (closes: #493702). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#404248: not fixed in apollon 1.0.2.1-3
found 404248 1.0.2.1-3 thanks Hi (Aurelien), the admin/libtool.m4.in have not been updated, libtool still does not support GNU/kFreeBSD. Petr http://buildd.debian-ports.org/fetch.php?pkg=apollonarch=kfreebsd-i386ver=1.0.2.1-3stamp=1218760637file=logas=raw checking how to recognise dependent libraries... unknown checking if libtool supports shared libraries... no -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
fonty REMOVED from testing
FYI: The status of the fonty source package in Debian's testing distribution has changed. Previous version: 1.0-23.7 Current version: (not in testing) Hint: Package not in unstable The script that generates this mail tries to extract removal reasons from comments in the britney hint files. Those comments were not originally meant to be machine readable, so if the reason for removing your package seems to be nonsense, it is probably the reporting script that got confused. Please check the actual hints file before you complain about meaningless removals. -- This email is automatically generated; the Debian Release Team [EMAIL PROTECTED] is responsible. See http://release.debian.org/testing-watch/ for more information. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#404248: marked as done (apollon(GNU/k*BSD): FTBFS: out of date libtool scripts)
Your message dated Fri, 15 Aug 2008 19:02:04 + with message-id [EMAIL PROTECTED] and subject line Bug#404248: fixed in apollon 1.0.2.1-4 has caused the Debian Bug report #404248, regarding apollon(GNU/k*BSD): FTBFS: out of date libtool scripts to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 404248: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=404248 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: apollon Version: 1.0.2.1-1.1 Severity: important Hi, the current version of fails to build on GNU/kFreeBSD due to outdated libtool. The version of libtool in apollon is too old to correctly support Debian GNU/k*BSD. Here is how to update the libtool in your package: cp -f /usr/share/libtool/libtool.m4 admin/libtool.m4.in cp -f /usr/share/libtool/ltmain.sh admin/ltmain.sh cp -f /usr/share/misc/config.guess admin/config.guess cp -f /usr/share/misc/config.sub admin/config.sub (alternatively you can update the admin/ directory from the latest KDE SVN [1] instead). make -f admin/Makefile.common You might find usefull also patch bellow for current autoconf. Note that using libtool.m4 from the Debian package is prefered, because it prunes the package dependencies, as explain by Steve Langasek [2]. Thanks for your cooperation Petr [1] http://websvn.kde.org/branches/KDE/3.5/kde-common/admin/ [2] http://lists.debian.org/debian-devel-announce/2005/11/msg00016.html --- admin/cvs.sh~ 2006-12-22 21:18:31.0 +0100 +++ admin/cvs.sh2006-12-22 21:18:31.0 +0100 @@ -30,7 +30,7 @@ required_autoconf_version=2.53 or newer AUTOCONF_VERSION=`$AUTOCONF --version | head -n 1` case $AUTOCONF_VERSION in - Autoconf*2.5* | autoconf*2.5* ) : ;; + Autoconf*2.5* | autoconf*2.5* | autoconf*2.6* ) : ;; ) echo *** AUTOCONF NOT FOUND!. echo *** KDE requires autoconf $required_autoconf_version @@ -45,7 +45,7 @@ AUTOHEADER_VERSION=`$AUTOHEADER --version | head -n 1` case $AUTOHEADER_VERSION in - Autoconf*2.5* | autoheader*2.5* ) : ;; + Autoconf*2.5* | autoheader*2.5* | autoheader*2.6* ) : ;; ) echo *** AUTOHEADER NOT FOUND!. echo *** KDE requires autoheader $required_autoconf_version ---End Message--- ---BeginMessage--- Source: apollon Source-Version: 1.0.2.1-4 We believe that the bug you reported is fixed in the latest version of apollon, which is due to be installed in the Debian FTP archive: apollon_1.0.2.1-4.diff.gz to pool/main/a/apollon/apollon_1.0.2.1-4.diff.gz apollon_1.0.2.1-4.dsc to pool/main/a/apollon/apollon_1.0.2.1-4.dsc apollon_1.0.2.1-4_amd64.deb to pool/main/a/apollon/apollon_1.0.2.1-4_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Aurelien Jarno [EMAIL PROTECTED] (supplier of updated apollon package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 15 Aug 2008 20:26:41 +0200 Source: apollon Binary: apollon Architecture: source amd64 Version: 1.0.2.1-4 Distribution: unstable Urgency: low Maintainer: Aurelien Jarno [EMAIL PROTECTED] Changed-By: Aurelien Jarno [EMAIL PROTECTED] Description: apollon- KDE-based interface to the giFT file-sharing system Closes: 404248 Changes: apollon (1.0.2.1-4) unstable; urgency=low . * QA upload. * Relibtoolize properly (Closes: #404248). Checksums-Sha1: 9c7f9b847ba6cfbd94bbc7537037f6c1f53a8603 1071 apollon_1.0.2.1-4.dsc c09e75914c45cefc2c134174339cce364bcb81b8 450922 apollon_1.0.2.1-4.diff.gz 076d4a92879477c127fdb1cff8a0c4f4181ffe3c 488656 apollon_1.0.2.1-4_amd64.deb Checksums-Sha256: 9dfb25059e83b9d7543e0a200d117399b41e9d1cad1603fcf02579c6cb2762a5 1071 apollon_1.0.2.1-4.dsc b84b6d24a3191332bb628835f00114b410061a0f7bfbcf41981917727f0aee4a 450922 apollon_1.0.2.1-4.diff.gz 63f34d057624f9f89fda7a2f7ccbad8b1af919fccc2c33ea1745239bcd4a0a04 488656 apollon_1.0.2.1-4_amd64.deb Files: c087d962f42fed1686ff7a2daab37871 1071 net optional apollon_1.0.2.1-4.dsc a388f7f1f1adb82cfe3f44c406129449 450922 net optional apollon_1.0.2.1-4.diff.gz 05afcd2e1ff21a0a722af5d87136 488656 net optional apollon_1.0.2.1-4_amd64.deb -BEGIN PGP
Processed: RC Bugs that don't affect etch
Processing commands for [EMAIL PROTECTED]: # # According to the version information these bugs # affect the stable release, but for one reason or # another that is not actually true. # # Mark them as lenny,sid as discussed on debian-release # See http://lists.debian.org/debian-release/2008/08/msg00761.html # and the following thread # # If you find any error, please feel to correct it yourself # (a short comment in your control command would be appreciated) # tested, build fine in etch tag 486973 + lenny sid Bug#486973: 9menu: FTBFS: ld: cannot find -lXext There were no tags set. Tags added: lenny, sid tag 479936 + lenny sid Bug#479936: adabrowse: FTBFS: gnatmake: debian/adabrowse.gpr processing failed There were no tags set. Tags added: lenny, sid tag 465638 + lenny sid Bug#465638: blacs-mpi: FTBFS: btprim_MPI.f:(.text+0x56): undefined reference to `mpi_type_size__' There were no tags set. Tags added: lenny, sid tag 470336 + lenny sid Bug#470336: bristol: Please provide bristol-0.20.5 There were no tags set. Tags added: lenny, sid tag 482205 + lenny sid Bug#482205: brltty: FTBFS: Empty declarator Tags were: patch Tags added: lenny, sid tag 477006 + lenny sid Bug#477006: bookmarkbridge: FTBFS: checking for QT... configure: error: The pkg-config script could not be found or is too old. Tags were: patch Tags added: lenny, sid tag 441227 + lenny sid Bug#441227: FTBFS: can't configure Java There were no tags set. Tags added: lenny, sid tag 479890 + lenny sid Bug#479890: compartment: FTBFS: compartment.c:48: error: 'CAP_FS_MASK' undeclared here (not in a function) Tags were: patch Tags added: lenny, sid tag 483318 + lenny sid Bug#483318: crip: FTBFS: applying patch 30dont_overwrite_files to ./ ... failed. Tags were: patch Tags added: lenny, sid tag 459799 + lenny sid Bug#459799: driftnet: doesn't build any more Tags were: help Tags added: lenny, sid tag 476046 + lenny sid Bug#476046: gcal: FTBFS: configure: error: installation or configuration problem: C compiler cannot create executables. There were no tags set. Tags added: lenny, sid # gcc 4.3 tag 417104 + lenny sid Bug#417104: FTBFS with GCC 4.3: missing #includes Tags were: patch Tags added: lenny, sid tag 417083 + lenny sid Bug#417083: FTBFS with GCC 4.3: missing #includes Tags were: patch Tags added: lenny, sid tag 472529 + lenny sid Bug#472529: asis: FTBFS with gnat-4.3: Name_Id is not visible There were no tags set. Tags added: lenny, sid tag 417489 + lenny sid Bug#417489: FTBFS with GCC 4.3: missing #includes Tags were: patch Tags added: lenny, sid tag 470975 + lenny sid Bug#470975: bakery2.4: FTBFS with g++-4.3: Missing includes Tags were: patch Tags added: lenny, sid tag 417133 + lenny sid Bug#417133: FTBFS with GCC 4.3: missing #includes Tags were: patch Tags added: lenny, sid tag 417161 + lenny sid Bug#417161: FTBFS with GCC 4.3: missing #includes Tags were: patch Tags added: lenny, sid tag 467474 + lenny sid Bug#467474: gcl: Builds broken package with gcc-4.3 There were no tags set. Tags added: lenny, sid tag 474806 + lenny sid Bug#474806: gforth: FTBFS: cc1: error: unrecognized command line option -m486 There were no tags set. Tags added: lenny, sid tag 456105 + lenny sid Bug#456105: FTBFS with GCC 4.3: declaration of... changes meaning of... Tags were: patch Tags added: lenny, sid tag 417209 + lenny sid Bug#417209: FTBFS with GCC 4.3: missing #includes Tags were: fixed-upstream Tags added: lenny, sid # new dpkg-dev tag 476012 + lenny sid Bug#476012: bitcollider: configure: warning: CFLAGS=-g -O2: invalid host type There were no tags set. Tags added: lenny, sid tag 464269 + lenny sid Bug#464269: freedroid: FTBFS: parsechangelog/debian: warning: debian/changelog(l11): found change data where expected next heading or eof There were no tags set. Tags added: lenny, sid # outdated build-depends, fine for etch tag 479188 + lenny sid Bug#479188: please build depend on libxerces-c2-dev There were no tags set. Tags added: lenny, sid tag 479189 + lenny sid Bug#479189: please build depend on libxerces-c2-dev There were no tags set. Tags added: lenny, sid tag 479190 + lenny sid Bug#479190: please build depend on libxerces-c2-dev There were no tags set. Tags added: lenny, sid tag 482510 + lenny sid Bug#482510: cvm: FTBFS: Unmet build dependencies: bglibs-dev ( 1.020-0) There were no tags set. Tags added: lenny, sid tag 466373 + lenny sid Bug#466373: dact: switch to liblzo2 Tags were: patch Tags added: lenny, sid tag 419023 + lenny sid Bug#419023: enlightenment: build-depends on transitional package xlibs-data Tags were: pending Tags added: lenny, sid tag 421559 + lenny sid Bug#421559: enlightenment: build-depends on obsolete package xlibs-static-dev There were no tags set. Tags added: lenny, sid tag 472563 + lenny sid Bug#472563: gfccore: FTBFS with g++-4.3: Missing includes There were no tags set. Tags added: lenny, sid tag 421563 + lenny sid Bug#421563: gl-117:
Processed: found 441913 in 6.revised-3.1, found 441914 in 20001107-a-3.1, found 441915 in 1.0.0-5.1 ...
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.35 # add version numbers so they dont get falsely assigned to etch found 441913 6.revised-3.1 Bug#441913: buggy dict-* invoke-rc.d fixes Bug marked as found in version 6.revised-3.1. found 441914 20001107-a-3.1 Bug#441914: buggy dict-* invoke-rc.d fixes Bug marked as found in version 20001107-a-3.1. found 441915 1.0.0-5.1 Bug#441915: buggy dict-* invoke-rc.d fixes Bug marked as found in version 1.0.0-5.1. found 441916 0.48-4.4 Bug#441916: buggy dict-* invoke-rc.d fixes Bug marked as found in version 0.48-4.4. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#441914: found 441913 in 6.revised-3.1, found 441914 in 20001107-a-3.1, found 441915 in 1.0.0-5.1 ...
# Automatically generated email from bts, devscripts version 2.10.35 # add version numbers so they dont get falsely assigned to etch found 441913 6.revised-3.1 found 441914 20001107-a-3.1 found 441915 1.0.0-5.1 found 441916 0.48-4.4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: RC bugs that don't affect etch (2)
Processing commands for [EMAIL PROTECTED]: # # According to the version information these bugs # affect the stable release, but for one reason or # another that is not actually true. # # Mark them as lenny,sid as discussed on debian-release # See http://lists.debian.org/debian-release/2008/08/msg00761.html # and the following thread # # If you find any error, please feel to correct it yourself # (a short comment in your control command would be appreciated) # invoke-rc.d only became serious after etch tag 367737 + lenny sid Bug#367737: dict-bouvier: must use invoke-rc.d There were no tags set. Tags added: lenny, sid tag 348259 + lenny sid Bug#348259: dict-elements: use invoke-rc.d There were no tags set. Tags added: lenny, sid tag 367740 + lenny sid Bug#367740: dict-gazetteer2k-zips: must use invoke-rc.d There were no tags set. Tags added: lenny, sid tag 341415 + lenny sid Bug#341415: dict-gcide: should use invoke-rc.d There were no tags set. Tags added: lenny, sid tag 348263 + lenny sid Bug#348263: dict-jargon: use invoke-rc.d Tags were: patch Tags added: lenny, sid tag 367733 + lenny sid Bug#367733: dict-moby-thesaurus: must use invoke-rc.d There were no tags set. Tags added: lenny, sid tag 367731 + lenny sid Bug#367731: iptotal: must use invoke-rc.d Tags were: patch Tags added: lenny, sid tag 367725 + lenny sid Bug#367725: net-acct: must use invoke-rc.d There were no tags set. Tags added: lenny, sid tag 367729 + lenny sid Bug#367729: rbootd: must use invoke-rc.d There were no tags set. Tags added: lenny, sid tag 367755 + lenny sid Bug#367755: tama: must use invoke-rc.d There were no tags set. Tags added: lenny, sid tag 367754 + lenny sid Bug#367754: wdm: must use invoke-rc.d Tags were: patch Tags added: lenny, sid tag 427892 + lenny sid Bug#427892: circumvents invoke-rc.d (and thus policy-rc.d) in postinst There were no tags set. Tags added: lenny, sid # FTBFS not reproducible on etch tag 476055 + lenny sid Bug#476055: epic4: checking whether the C compiler (gcc -O1 -pedantic ) works... no Tags were: patch Tags added: lenny, sid tag 450459 + lenny sid Bug#450459: gtkglarea: FTBFS: configure.in:29: required file `./ltmain.sh' not found Tags were: patch Tags added: lenny, sid tag 494325 + lenny sid Bug#494325: kaya: FTBFS in lenny: Heap.cc:177: error: 'strchr' was not declared in this scope There were no tags set. Tags added: lenny, sid tag 458635 + lenny sid Bug#458635: krecord: FTBFS: sound.h:45: error: expected `)' before '*' token There were no tags set. Tags added: lenny, sid tag 474891 + lenny sid Bug#474891: please rebuild libsdl-sound1.2 against new libspeex There were no tags set. Tags added: lenny, sid tag 474895 + lenny sid Bug#474895: gst-plugins-good0.10: FTBFS: libtool: link: `/usr/lib/libspeex.la' is not a valid libtool archive There were no tags set. Tags added: lenny, sid # GCC 4.3 tag 441537 + lenny sid Bug#441537: ftbfs with g++-4.3/gcc-snapshot Tags were: pending patch Bug#446333: When gcc-default (4:4.3-20070902-0) is installed, the repackaging cannot be done. Bug#456971: libsigc++-2.0-dev: causes FTBFS: declaration changes meaning Bug#466945: libsigc++-2.0: FTBFS with g++-4.3: declaration of ... changes meaning of ... Tags added: lenny, sid tag 417363 + lenny sid Bug#417363: FTBFS with GCC 4.3: missing #includes Tags were: patch Tags added: lenny, sid tag 461706 + lenny sid Bug#461706: FTBFS with GCC 4.3: uses (removed) pre-iso c++ headers Tags were: patch Tags added: lenny, sid tag 417437 + lenny sid Bug#417437: FTBFS with GCC 4.3: missing #includes Tags were: patch Tags added: lenny, sid tag 455285 + lenny sid Bug#455285: FTBFS with GCC 4.3: missing #includes Tags were: patch Tags added: lenny, sid tag 425544 + lenny sid Bug#425544: FTBFS with GCC 4.3: inf loop checking for mktime Tags were: patch Tags added: lenny, sid tag 454879 + lenny sid Bug#454879: FTBFS with GCC 4.3: duplicate function parameters Tags were: patch Tags added: lenny, sid tag 455174 + lenny sid Bug#455174: FTBFS with GCC 4.3: missing #includes There were no tags set. Tags added: lenny, sid tag 477283 + lenny sid Bug#477283: FTBFS with gcc-4.3 Tags were: patch Tags added: lenny, sid tag 417713 + lenny sid Bug#417713: FTBFS with GCC 4.3: missing #includes Tags were: patch Tags added: lenny, sid # FTBFS due to changed x.org dependencies tag 486983 + lenny sid Bug#486983: libforms1: FTBFS: ld: cannot find -lXext There were no tags set. Tags added: lenny, sid tag 486960 + lenny sid Bug#486960: libforms1: FTBFS: ld: cannot find -lXext There were no tags set. Tags added: lenny, sid tag 486985 + lenny sid Bug#486985: drawtiming: FTBFS: ld: cannot find -lXext Tags were: patch Tags added: lenny, sid tag 486972 + lenny sid Bug#486972: xfishtank: FTBFS: ld: cannot find -lXext Tags were: patch Tags added: lenny, sid tag 486976 + lenny sid Bug#486976: xhangglider: FTBFS: ld: cannot find -lXext There were no tags set. Tags added: lenny,
Bug#495308: bfr: man page contains POD errors
Package: bfr Version: 1.6-2 Severity: normal bfr(1) ends with POD ERRORS. POD ERRORS Hey! The above document had some coding errors, which are explained below: Around line 179: You forgot a '=back' before '=head2' Around line 181: '=item' outside of any '=over' Around line 229: You forgot a '=back' before '=head2' Around line 231: '=item' outside of any '=over' bfr documentation2004-03-03 BFR(1) -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.25-2-686 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages bfr depends on: ii libc6 2.7-13 GNU C Library: Shared libraries bfr recommends no packages. bfr suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Report from Debconf's QA BOF
* Lucas Nussbaum [EMAIL PROTECTED] [2008-08-14 18:16]: The idea of having a script inside devscripts that lists the RC-buggy and orphaned packages that are locally installed was proposed. I filed a bug about that. See #495152 These are included already: wnpp-alert - check for installed packages up for adoption or orphaned rc-alert - check for installed packages with release-critical bugs Ah, according to #495152 you want cronjobs around those scripts, I see. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RFS: gimageview (updated package, QA Upload)
Dear mentors/QA group, I am looking for a sponsor for the new version 0.2.27-2 of package gimageview (QA upload). It builds these binary packages: gimageview - image viewer using GTK+ The package appears to be lintian clean. The upload would fix these bugs: 243583, 243584, 389071, 397075, 440648, 459288, 494304 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/g/gimageview - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/g/gimageview/gimageview_0.2.27-2.dsc I would be glad if someone uploaded this package for me. Kind regards Sandro Tosi -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: suite tags (Re: Doing some stable QA work)
Le August 15, 2008 01:39:23 am Steve Langasek, vous avez écrit : On Thu, Aug 14, 2008 at 11:35:39PM -0400, Filipus Klutiero wrote: Le August 14, 2008 11:08:10 pm Steve Langasek, vous avez écrit : On Thu, Aug 14, 2008 at 11:01:46PM -0400, Filipus Klutiero wrote: Tagging lenny and sid does not imply that other suites are free from the bug, Yes, it does. Why would it? Because it always has. Ehm, AFAIK Debian only exists since 15 years, so it should be possible to get a more convincing reference if it's true. AFAIK, it never did, but for sure it doesn't since 2005. It's granted that before the meaning change, the implication could appear true in many bug reports. so this unfortunately wouldn't help the graph. Moreover, suite x doesn't mean anymore that the bug is found in suite x, but This bug should not be archived until it is fixed in suite x. Not unless there's been a regression since the last time I talked to Don about this. For current suites, the meaning was changed (see http://www.debian.org/Bugs/Developer#tags ). Assuming that the tags whose meaning changed were cleared when the change happened, this isn't a regression, except that people who missed the announcement may of course use the tag in error. No, I spoke with Don after that documentation was changed and explained why it was necessary to retain tags with the original meanings separate from the suite-ignore tags. I don't understand what you mean by retain tags with the original meanings separate from the suite-ignore tags. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Report from Debconf's QA BOF
On 15/08/08 at 09:21 +0300, Martin Michlmayr wrote: * Lucas Nussbaum [EMAIL PROTECTED] [2008-08-14 18:16]: The idea of having a script inside devscripts that lists the RC-buggy and orphaned packages that are locally installed was proposed. I filed a bug about that. See #495152 These are included already: wnpp-alert - check for installed packages up for adoption or orphaned rc-alert - check for installed packages with release-critical bugs Ah, according to #495152 you want cronjobs around those scripts, I see. Yeah, sorry, I was probably too tired when I wrote the report. :-) -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Report from Debconf's QA BOF
On 15/08/08 at 05:49 +0200, Luk Claes wrote: Steve Langasek wrote: On Fri, Aug 15, 2008 at 12:01:26AM -0300, Lucas Nussbaum wrote: - O: bugs are now RC, so packages are removed from testing using the release team's existing policies. Which means that some O: packages might stay in testing for a longer time because they are dependencies of other packages. Were members of the release team represented in this BoF? Sure, Luk was here, and didn't express any disagreement. Actually, I tried hard to give several opportunities to raise concerns, but everybody apparently really agreed with the proposal. Hrm, ok... well, I still disagree, but I seem to be overruled :) The orphanage bug being RC does only mean that it needs to be adopted, removed (from unstable and/or testing) or downgraded before the next release IMHO. The three options should still be possible, but at least they are actively being watched as having non-maintained packages in the release should be avoided if possible IMHO. Could you give an example case where you would want to downgrade an orphaned package's bug? L. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#495227: PTS: please adjust BTS acronym
Package: qa.debian.org Severity: minor Hi, please adjust Debian BTS acronym on PTS page footer. There are too many spaces between 'Bug' and 'Tracking' words, in fact this is how it is actually displayed: acronym title=Bug Tracking SystemBTS/acronym/a. I guess this is due to the following line break in pts.xsl code: p ema href=http://www.debian.org;Debian/a Package Tracking System/em - Copyright 2002-2008 Raphaël Hertzog and others.br/ Report problems to the a href=http://bugs.debian.org/qa.debian.org;ttqa.debian.org/tt pseudopackage/a in the a href=http://bugs.debian.org;Debian acronym title=Bug Tracking SystemBTS/acronym/a.br/ Last modified: xsl:value-of select=$date/. /p Thanks, Cristian -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash signature.asc Description: Digital signature
Re: suite tags (Re: Doing some stable QA work)
On Fri, 15 Aug 2008, Frank Lichtenheld wrote: On Thu, Aug 14, 2008 at 08:08:10PM -0700, Steve Langasek wrote: On Thu, Aug 14, 2008 at 11:01:46PM -0400, Filipus Klutiero wrote: Tagging lenny and sid does not imply that other suites are free from the bug, Yes, it does. It only implies that for britney; the BTS itself ignores it save for archiving. It's quite likely that we should change this, but it's not the way it works currently. [1] How to interpret those tags has always been problematic in my mind, but I suppose the following interpretation would resolve what the release managers are looking for, and would also work for the bts. *** proposal *** For the purposes of determining buginess, setting a distribution tag limits the bugginess of a package in distribtions to the intersection of the distributions and the version-based bugginness of a package. This means that a bug that would normally be buggy in etch and lenny (but fixed in sid) due to the versions present of that package would only be present in lenny if tagged lenny and tagged sid. For the purposes of archival, we just use the buginess state above instead, defaulting to (testing distribution), sid. *** end proposal *** Does that meet the needs of the RMs et al? Are there any objections? Don Armstrong 1: It's quite likely that we talked about the way it should work, and I totally forgot about what we decided that it should do after promising that I'd change it. My brain is at its base, a sieve. -- Miracles had become relative common-places since the advent of entheogens; it now took very unusual circumstances to attract public attention to sightings of supernatural entities. The latest miracle had raised the ante on the supernatural: the Virgin Mary had manifested herself to two children, a dog, and a Public Telepresence Point. -- Bruce Sterling, _Holy Fire_ p228 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Report from Debconf's QA BOF
On Fri, Aug 15, 2008 at 09:21:30AM +0300, Martin Michlmayr wrote: These are included already: wnpp-alert - check for installed packages up for adoption or orphaned rc-alert - check for installed packages with release-critical bugs Ah, according to #495152 you want cronjobs around those scripts, I see. Yep. Additionally, we also discussed the idea of having a single script instead of multiple ones, with a single configuration entry and possibly sane defaults. Cc-ing the bugreport to store this wish. Cheers. -- Stefano Zacchiroli -*- PhD in Computer Science \ PostDoc @ Univ. Paris 7 [EMAIL PROTECTED],pps.jussieu.fr,debian.org} -- http://upsilon.cc/zack/ I'm still an SGML person,this newfangled /\ All one has to do is hit the XML stuff is so ... simplistic -- Manoj \/ right keys at the right time signature.asc Description: Digital signature
Re: Report from Debconf's QA BOF
On Friday 15 August 2008 15:52:55 Stefano Zacchiroli wrote: On Fri, Aug 15, 2008 at 09:21:30AM +0300, Martin Michlmayr wrote: These are included already: wnpp-alert - check for installed packages up for adoption or orphaned rc-alert - check for installed packages with release-critical bugs Ah, according to #495152 you want cronjobs around those scripts, I see. Yep. Additionally, we also discussed the idea of having a single script instead of multiple ones, with a single configuration entry and possibly sane defaults. Cc-ing the bugreport to store this wish. I think it would also be nice if wnpp-alert could sort packages by popcon score so that developers know which packages are more worth adopting. Cheers, Frank -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: suite tags (Re: Doing some stable QA work)
Don Armstrong wrote: On Fri, 15 Aug 2008, Frank Lichtenheld wrote: On Thu, Aug 14, 2008 at 08:08:10PM -0700, Steve Langasek wrote: On Thu, Aug 14, 2008 at 11:01:46PM -0400, Filipus Klutiero wrote: Tagging lenny and sid does not imply that other suites are free from the bug, Yes, it does. It only implies that for britney; the BTS itself ignores it save for archiving. Thanks for the clarification. It's quite likely that we should change this, but it's not the way it works currently. [1] How to interpret those tags has always been problematic in my mind, but I suppose the following interpretation would resolve what the release managers are looking for, and would also work for the bts. *** proposal *** For the purposes of determining buginess, setting a distribution tag limits the bugginess of a package in distribtions to the intersection of the distributions and the version-based bugginness of a package. This means that a bug that would normally be buggy in etch and lenny (but fixed in sid) due to the versions present of that package would only be present in lenny if tagged lenny and tagged sid. Does this also mean that the bug would not be present anywere when the intersection would be empty (tagged lenny with a version higher than the one in testing for instance)? We should probably look at all the possibilities and think about good defaults for them? For the purposes of archival, we just use the buginess state above instead, defaulting to (testing distribution), sid. *** end proposal *** Does that meet the needs of the RMs et al? Are there any objections? I think it's a bit more complex than what you propose, but it seems to be a good starting point. Cheers Luk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Report from Debconf's QA BOF
On Fri, 2008-08-15 at 17:45 +0200, Frank S. Thomas wrote: [...] I think it would also be nice if wnpp-alert could sort packages by popcon score so that developers know which packages are more worth adopting. That would be #478835. Adam (who really should be packing and not reading mail :-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: suite tags (Re: Doing some stable QA work)
On Fri, 15 Aug 2008, Luk Claes wrote: Don Armstrong wrote: *** proposal *** For the purposes of determining buginess, setting a distribution tag limits the bugginess of a package in distribtions to the intersection of the distributions and the version-based bugginness of a package. This means that a bug that would normally be buggy in etch and lenny (but fixed in sid) due to the versions present of that package would only be present in lenny if tagged lenny and tagged sid. Does this also mean that the bug would not be present anywere when the intersection would be empty (tagged lenny with a version higher than the one in testing for instance)? Right. [I submit that in such a case, the lenny tag should be removed if it actually affects unstable; possibly it shouldn't have been applied in the first case.] We should probably look at all the possibilities and think about good defaults for them? We should think about them, but whatever decision we make needs to apply to all of the possible distribution tags in a similar manner. [That is, I really don't want to special case every single tag, because that's not maintainable.] Don Armstrong -- If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money it values more, it will lose that, too. -- W. Somerset Maugham http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: suite tags (Re: Doing some stable QA work)
Don Armstrong [EMAIL PROTECTED] writes: *** proposal *** For the purposes of determining buginess, setting a distribution tag limits the bugginess of a package in distribtions to the intersection of the distributions and the version-based bugginness of a package. This means that a bug that would normally be buggy in etch and lenny (but fixed in sid) due to the versions present of that package would only be present in lenny if tagged lenny and tagged sid. For the purposes of archival, we just use the buginess state above instead, defaulting to (testing distribution), sid. *** end proposal *** Does that meet the needs of the RMs et al? Yes. Marc -- Fachbegriffe der Informatik - Einfach erklärt 117: Las Vegas Mekka fuer experimentelle Statistik. (Jens Hoffmann) pgpEPqt8zrM0v.pgp Description: PGP signature
Re: Doing some stable QA work
On Fri, Aug 15, 2008 at 01:41:26AM +0200, Frank Lichtenheld wrote: Hi. I had the idea to go through the list of RC bugs currently believed by the BTS to affect stable and do some cleanup work: * Fix version information * Mark by etch-ignore bus that are not affected in stable for reason independent from their version (e.g. GCC 4.3 FTBFS) * Compile a list for the maintainers and the SRM for packages that could need a stable upload. Feel free to contact me if you would like to help or if you spot any problems with my work. I have been tagging them with lenny + sid before. I've also tagged those that _do_ effect stable with the debian-qa@lists.debian.org user and etch tag. I have a hacked up script that lists the bugs that are RC in stable and are not tagged etch. But I would like to rewrite that to use the SOAP interface. I think some things weren't supported at that time. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Report from Debconf's QA BOF
Lucas Nussbaum wrote: Sure, Luk was here, and didn't express any disagreement. Actually, I tried hard to give several opportunities to raise concerns, but everybody apparently really agreed with the proposal. (you might want to check the video when it will be available) That wasn't really my impression watching the video. I seem to recall Bdale arguing persuasively that this would be a bad idea, for one. (IMHO: Horrible idea, will tend to result in maintainers not orphaning packages and instead letting them rot unmaintained.) -- see shy jo signature.asc Description: Digital signature
Re: Report from Debconf's QA BOF
On 15/08/08 at 12:30 -0400, Joey Hess wrote: Lucas Nussbaum wrote: Sure, Luk was here, and didn't express any disagreement. Actually, I tried hard to give several opportunities to raise concerns, but everybody apparently really agreed with the proposal. (you might want to check the video when it will be available) That wasn't really my impression watching the video. I seem to recall Bdale arguing persuasively that this would be a bad idea, for one. I think that Bdale's point was about removals from unstable (the bapase stuff), for which, indeed, I agree that we need to be extremely careful, and that we must always try to contact the maintainer. I don't think that he opposed what was discussed about the handling of orphaned packages. If I remember correctly, the discussion about orphaned packages went quite well, then we switched to removals from unstable, Ganneff talked, and then Bdale. Please correct me if I'm wrong. FWIW, my motivation for that is not to reduce archive size by removing tons of packages, but to increase the visibility of orphaned packages, so those which are useful to someone find an adopter. Each time I run wnpp-alert, I'm amazed by what I read, and I can't adopt everything I use, unfortunately. (IMHO: Horrible idea, will tend to result in maintainers not orphaning packages and instead letting them rot unmaintained.) Isn't it already the case? Do you have something better to propose? Or do you think that we can continue to ignore that 5% of our archive doesn't have a maintainer? -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#495227: marked as done (PTS: please adjust BTS acronym)
Your message dated Fri, 15 Aug 2008 21:29:53 + with message-id [EMAIL PROTECTED] and subject line qa.debian.org bug fixed in revision 1977 has caused the Debian Bug report #495227, regarding PTS: please adjust BTS acronym to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 495227: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495227 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: qa.debian.org Severity: minor Hi, please adjust Debian BTS acronym on PTS page footer. There are too many spaces between 'Bug' and 'Tracking' words, in fact this is how it is actually displayed: acronym title=Bug Tracking SystemBTS/acronym/a. I guess this is due to the following line break in pts.xsl code: p ema href=http://www.debian.org;Debian/a Package Tracking System/em - Copyright 2002-2008 Raphaël Hertzog and others.br/ Report problems to the a href=http://bugs.debian.org/qa.debian.org;ttqa.debian.org/tt pseudopackage/a in the a href=http://bugs.debian.org;Debian acronym title=Bug Tracking SystemBTS/acronym/a.br/ Last modified: xsl:value-of select=$date/. /p Thanks, Cristian -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Version: 1977 This bug was closed by Stefano Zacchiroli (zack) in SVN revision 1977. Note that it might take some time until the qa.debian.org code has been updated and cronjobs have picked up changed data. Commit message: fix unfortunate line-wrapping in BTS acronym expansion (Closes: #495227) ---End Message---
Re: suite tags (Re: Doing some stable QA work)
On Fri, Aug 15, 2008 at 05:48:56PM +0200, Luk Claes wrote: Don Armstrong wrote: This means that a bug that would normally be buggy in etch and lenny (but fixed in sid) due to the versions present of that package would only be present in lenny if tagged lenny and tagged sid. Does this also mean that the bug would not be present anywere when the intersection would be empty (tagged lenny with a version higher than the one in testing for instance)? We should probably look at all the possibilities and think about good defaults for them? Note that for most bugs I will tag they will indeed be not present anymore in any suite afterwards, since they usually are only present in etch according to the version information, but will be tagged lenny, sid. Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: suite tags (Re: Doing some stable QA work)
Le August 15, 2008 10:29:45 am Don Armstrong, vous avez écrit : On Fri, 15 Aug 2008, Frank Lichtenheld wrote: On Thu, Aug 14, 2008 at 08:08:10PM -0700, Steve Langasek wrote: On Thu, Aug 14, 2008 at 11:01:46PM -0400, Filipus Klutiero wrote: Tagging lenny and sid does not imply that other suites are free from the bug, Yes, it does. [...] *** end proposal *** Does that meet the needs of the RMs et al? Are there any objections? Supposing your proposal is accepted, would the debbugs teams copy the state of the stable tag when creating a new testing tag? For example, would a bug tagged lenny get the tag for Debian 6 when adding that tag? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: suite tags (Re: Doing some stable QA work)
On Fri, 15 Aug 2008, Filipus Klutiero wrote: Supposing your proposal is accepted, would the debbugs teams copy the state of the stable tag when creating a new testing tag? For example, would a bug tagged lenny get the tag for Debian 6 when adding that tag? Not automatically, but it's not like doing this manually in a single shot is hard. Don Armstrong -- Only one creature could have duplicated the expressions on their faces, and that would be a pigeon who has heard not only that Lord Nelson has got down off his column but has also been seen buying a 12-bore repeater and a box of cartridges. -- Terry Pratchet _Mort_ http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
