Processed: Re: [Pkg-samba-maint] Bug#446410: samba fails in post-installation
Processing commands for [EMAIL PROTECTED]: severity 446410 normal Bug#446410: samba fails in post-installation Severity set to `normal' from `grave' 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: [patch] libwww-mechanize-perl - FTBFS: Failed test 'Got http://en.wikipedia.org/'
Processing commands for [EMAIL PROTECTED]: tags 432485 + patch Bug#432485: libwww-mechanize-perl - FTBFS: Failed test 'Got http://en.wikipedia.org/' There were no tags set. Tags added: patch 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#432485: [patch] libwww-mechanize-perl - FTBFS: Failed test 'Got http://en.wikipedia.org/'
tags 432485 + patch
thanks
Hi Jay,
I saw the bug report at it seens that you are working on this.
Anyway, I've attach a patch to skip the test that requiere
for internet access if you set a env var at debian/rules
Cheers
--
Rene Mauricio Mayorga | GPG: A209C305
http://rmayorga.org |
--
08B6 58AB A691 DD56 C30B 8D37 8040 19FA A209 C305
diff -ruN libwww-mechanize-perl-1.30.old/debian/rules libwww-mechanize-perl-1.30/debian/rules
--- libwww-mechanize-perl-1.30.old/debian/rules 2007-10-13 00:27:35.0 -0600
+++ libwww-mechanize-perl-1.30/debian/rules 2007-10-13 00:31:55.0 -0600
@@ -30,7 +30,7 @@
dh_clean -k
dh_installdirs
- $(MAKE) PREFIX=$(CURDIR)/debian/$(PACKAGE)/usr OPTIMIZE=-O2 -g -Wall test install
+ NOINTERNET=1 $(MAKE) PREFIX=$(CURDIR)/debian/$(PACKAGE)/usr OPTIMIZE=-O2 -g -Wall test install
install -d $(ETCROOT)
install -m 644 $(CURDIR)/etc/* $(ETCROOT)
-find $(CURDIR)/debian -type d | xargs rmdir -p --ignore-fail-on-non-empty
diff -ruN libwww-mechanize-perl-1.30.old/t/live/computers4sure.t libwww-mechanize-perl-1.30/t/live/computers4sure.t
--- libwww-mechanize-perl-1.30.old/t/live/computers4sure.t 2007-05-24 20:34:37.0 -0600
+++ libwww-mechanize-perl-1.30/t/live/computers4sure.t 2007-10-13 00:31:21.0 -0600
@@ -3,6 +3,9 @@
use warnings;
use strict;
+if ( $ENV{NOINTERNET} ) {
+ use Test::More skip_all = We don't have internet here;
+}
use Test::More skip_all = Still need to get the error-handling on here working;
use Test::More tests = 9;
@@ -38,7 +41,7 @@
SKIP: {
eval use Test::Memory::Cycle;
skip Test::Memory::Cycle not installed, 1 if $@;
-
+
memory_cycle_ok( $mech, No memory cycles found );
}
diff -ruN libwww-mechanize-perl-1.30.old/t/live/wikipedia.t libwww-mechanize-perl-1.30/t/live/wikipedia.t
--- libwww-mechanize-perl-1.30.old/t/live/wikipedia.t 2007-05-24 20:30:50.0 -0600
+++ libwww-mechanize-perl-1.30/t/live/wikipedia.t 2007-10-13 00:31:21.0 -0600
@@ -3,6 +3,9 @@
use warnings;
use strict;
+if ( $ENV{NOINTERNET} ) {
+ use Test::More skip_all = We don't have internet here;
+}
use constant LANGUAGES = qw( en it ja es nl pl );
use Test::More tests = 3 + (2 * scalar LANGUAGES);
signature.asc
Description: Esta parte del mensaje está firmada digitalmente
Bug#446410: [Pkg-samba-maint] Bug#446410: samba fails in post-installation
severity 446410 normal thanks Quoting Claudio Saavedra ([EMAIL PROTECTED]): Package: samba Version: 3.0.26a-1 Severity: grave Justification: renders package unusable Samba fails during the post-installation scripts execution. Here is the output: dijkstra:/home/claudio# apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded. 1 not fully installed or removed. Need to get 0B of archives. After unpacking 0B of additional disk space will be used. Setting up samba (3.0.26a-1) ... update-rc.d: warning: /etc/rc2.d/K09samba is not a link to ../init.d/samba or /etc/init.d/samba update-rc.d: warning: /etc/rc3.d/K09samba is not a link to ../init.d/samba or /etc/init.d/samba invoke-rc.d: dangling symlink: /etc/rc2.d/K09samba dpkg: error processing samba (--configure): subprocess post-installation script returned error exit status 102 Errors were encountered while processing: Why were you running apt-get -f install ? This is usually an indication of a previously failed apt-get run. What are the /etc/rc2.d/K09samba pointing to? These links are not installed by the samba default install. I highly suspect that you installed the samba package on a not so sane system, hence downgrading this bug reportuntil we get enough details to decide that this is a local issue and therefore close it. I suggest you remove those K09samba links in /etc/rc2.d and /etc/rc3.d signature.asc Description: Digital signature
Processed: setting package to exim4 exim4-base exim4-config exim4-daemon-custom exim4-daemon-custom-dbg exim4-daemon-heavy exim4-daemon-heavy-dbg exim4-daemon-light exim4-daemon-light-dbg exim4-dbg ex
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 package exim4 exim4-base exim4-config exim4-daemon-custom exim4-daemon-custom-dbg exim4-daemon-heavy exim4-daemon-heavy-dbg exim4-daemon-light exim4-daemon-light-dbg exim4-dbg exim4-dev eximon4 Ignoring bugs not assigned to: exim4-daemon-heavy exim4-daemon-light-dbg exim4-dev exim4-base exim4 exim4-daemon-heavy-dbg exim4-daemon-custom-dbg exim4-daemon-light exim4-dbg eximon4 exim4-daemon-custom exim4-config tags 440217 + pending Bug#440217: exim4-config: lowuid router is misplaced in order and breaks common setups Tags were: confirmed Tags added: pending tags 446346 + pending Bug#446346: exim4-config: incorrect condition in new configuration files causing bounced email There were no tags set. Tags added: pending 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#445932: maxima: FTBFS on hppa (test failure)
A new upstream release 5.13 is available. Please update unstable, than we might forward this bug to the maxima devel mailing list. Detlef -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#443032: Patch to enable the pixman package
Upstream already has a patch pending that I believe addresses this, but this one might be a bit cleaner if it really covers all the angles so I've forwarded it for their consideration. We're expecting an 0.7.9 release with all the necessary patches for preliminary xorg7.3 support RSN, though there is at least one outstanding issue that is also waiting on a patch to upstream xorg to be made before it can be properly fixed -- until that happens changes to the screen resolution cannot be properly handled by the tablet. My present understanding is that you will need more than just this patch for the tablet to work as an extended input device (as opposed to a mouse-like device) with the changes that xorg7.3 has introduced. There will be a new package uploaded as soon as upstream is happy enough with the level of xorg7.3 support to make the new release. This migration seems to have caught a few people (myself included) by surprise, so we are lagging a little on support for it. Hopefully not for too much longer though. Cheers, Ron On Fri, Oct 12, 2007 at 02:54:02PM -0700, Synx wrote: Julien Cristau wrote: That patch is (mostly) wrong. wacom should indeed use pkg-config to get the necessary cflags, but it doesn't have to care about pixman. ... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 446462 is serious
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.9 # raising severity to RC, since this bug leave people with vim/gvim commands returning command not found severity 446462 serious Bug#446462: /usr/bin/vim is left broken when alternative is manual and points to vim-full Severity set to `serious' from `important' 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#446465: CVE-2007-5378 buffer overflow in tkImgGif.c via crafted gif image
Package: tk8.3 Severity: grave Tags: security Hi, the following CVE (Common Vulnerabilities Exposures) id was published for tk8.3. CVE-2007-5378[0]: | Buffer overflow in the FileReadGIF function in tkImgGIF.c for Tk | Toolkit 8.4.12 and earlier, and 8.3.5 and earlier, allows | user-assisted attackers to cause a denial of service (segmentation | fault) via an animated GIF in which the first subimage is smaller than | a subsequent subimage, which triggers the overflow in the ReadImage | function, a different vulnerability than CVE-2007-5137. If you fix this vulnerability please also include the CVE id in your changelog entry. This bug is fixed in the 8.4 package in unstable and testing but not in etch. For further information: [0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-5378 Kind regards Nico -- Nico Golde - http://ngolde.de - [EMAIL PROTECTED] - GPG: 0x73647CFF For security reasons, all text in this mail is double-rot13 encrypted. pgprLoowfEHQT.pgp Description: PGP signature
Processed: also in older versions
Processing commands for [EMAIL PROTECTED]: found 441195 2.10.13-1 Bug#441195: gtk+2.0_2.11.6-1(sparc/experimental): FTBFS: error: dereferencing pointer to incomplete type Bug marked as found in version 2.10.13-1. -- 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#441195: gtk+2.0_2.11.6-1(sparc/experimental): FTBFS: error: dereferencing pointer to incomplete type)
From: Loïc Minier [EMAIL PROTECTED] Ok; I wasn't sure whether the experimental buildd are online 100% of the time. Sjoerd confirmed buildability under sparc, so I've pushed gtk to unstable and am closing this bug. This bug has nothing to do with SPARC, really. It's just that gtk+2.0 2.10 and 2.11 are incompatible with CUPS 1.3. I just ran into this on amd64 because testing has CUPS 1.3 but only gtk 2.10. Below is a patch for other people trying to compile testing. Index: debian/patches/080_cups_build_fix.patch === --- debian/patches/080_cups_build_fix.patch (revision 0) +++ debian/patches/080_cups_build_fix.patch (revision 0) @@ -0,0 +1,13 @@ +--- gtk+2.0-2.10.13/modules/printbackends/cups/gtkcupsutils.c~ 2007-10-13 09:10:08.0 + gtk+2.0-2.10.13/modules/printbackends/cups/gtkcupsutils.c 2007-10-13 09:10:13.0 + +@@ -30,10 +30,6 @@ + #include stdlib.h + #include time.h + +-#if CUPS_VERSION_MAJOR 1 || (CUPS_VERSION_MAJOR == 1 CUPS_VERSION_MINOR 1) || (CUPS_VERSION_MAJOR == 1 CUPS_VERSION_MINOR == 1 CUPS_VERSION_PATCH = 20) +-#define HAVE_HTTP_AUTHSTRING 1 +-#endif +- + typedef void (*GtkCupsRequestStateFunc) (GtkCupsRequest *request); + + static void _connect(GtkCupsRequest *request); Index: debian/patches/series === --- debian/patches/series (revision 631) +++ debian/patches/series (working copy) @@ -14,3 +14,4 @@ 040_filechooser_single-click.patch 041_ia32-libs.patch 070_mandatory-relibtoolize.patch +080_cups_build_fix.patch Index: debian/changelog === --- debian/changelog(revision 631) +++ debian/changelog(working copy) @@ -1,3 +1,10 @@ +gtk+2.0 (2.10.13-1olmec1) unstable; urgency=low + + * Backport a build fix from 2.12 that's needed when CUPS 1.3.2 is +used (see Debian bug #441195). + + -- Martin Michlmayr [EMAIL PROTECTED] Sat, 13 Oct 2007 11:13:00 +0200 + gtk+2.0 (2.10.13-1) unstable; urgency=low * Bump Conflicts to iiimf-client-gtk 12.3.91-4. -- Martin Michlmayr http://www.cyrius.com/
Bug#446468: gthumb: the message *** glibc detected *** double free or corruption appears
Package: gthumb Severity: grave Justification: causes non-serious data loss Starting gthumb 2.6.9 from xterm and navigating through different directories causes at some point that the following message appears in xterm window and gthumb does not react any more: *** glibc detected *** double free or corruption (out): 0x084498c0 *** It is not clear for me when the problem exactly happens but it happens often. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18 Locale: LANG=hu_HU, LC_CTYPE=hu_HU (charmap=ISO-8859-2) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#446465: CVE-2007-5378 buffer overflow in tkImgGif.c via crafted gif image
Hi,
I have an updated package ready to fix this.
The patch for it is attached.
It will be also archived on:
http://people.debian.org/~nion/nmu-diff/tk8.3-8.3.5-9_8.3.5-9.1.patch
I wait a few days before uploading this as NMU feel free to update
yourself with CVE-2007-5378.diff.
Kind regards
Nico
--
Nico Golde - http://ngolde.de - [EMAIL PROTECTED] - GPG: 0x73647CFF
For security reasons, all text in this mail is double-rot13 encrypted.
diff -u tk8.3-8.3.5/debian/changelog tk8.3-8.3.5/debian/changelog
--- tk8.3-8.3.5/debian/changelog
+++ tk8.3-8.3.5/debian/changelog
@@ -1,3 +1,11 @@
+tk8.3 (8.3.5-9.1) unstable; urgency=high
+
+ * Non-maintainer upload by testing security team.
+ * Included CVE-2007-5378.diff to fix overflow triggered
+by crafted gif file (CVE-2007-5378) (Closes: #446465).
+
+ -- Nico Golde [EMAIL PROTECTED] Sat, 13 Oct 2007 11:40:22 +0200
+
tk8.3 (8.3.5-9) unstable; urgency=high
* Applied patch by Nico Golde which fixes security vulnerability
diff -u tk8.3-8.3.5/debian/patches/series tk8.3-8.3.5/debian/patches/series
--- tk8.3-8.3.5/debian/patches/series
+++ tk8.3-8.3.5/debian/patches/series
@@ -1,4 +1,5 @@
gif.diff
+CVE-2007-5378.diff
fonts.diff
scalable-fonts.diff
canvpoly.diff
only in patch2:
unchanged:
--- tk8.3-8.3.5.orig/debian/patches/CVE-2007-5378.diff
+++ tk8.3-8.3.5/debian/patches/CVE-2007-5378.diff
@@ -0,0 +1,72 @@
+--- tk8.3-8.3.5~/generic/tkImgGIF.c 2007-10-13 11:54:19.0 +0200
tk8.3-8.3.5/generic/tkImgGIF.c 2007-10-13 11:59:30.0 +0200
+@@ -240,7 +240,7 @@
+ int srcX, srcY; /* Coordinates of top-left pixel to be used
+ * in image being read. */
+ {
+-int fileWidth, fileHeight;
++int fileWidth, fileHeight, imageWidth, imageHeight;
+ int nBytes, index = 0, argc = 0, i;
+ Tcl_Obj **objv;
+ Tk_PhotoImageBlock block;
+@@ -372,8 +372,8 @@
+ goto error;
+ }
+
+- fileWidth = LM_to_uint(buf[4],buf[5]);
+- fileHeight = LM_to_uint(buf[6],buf[7]);
++ imageWidth = LM_to_uint(buf[4],buf[5]);
++ imageHeight = LM_to_uint(buf[6],buf[7]);
+
+ bitPixel = 1((buf[8]0x07)+1);
+
+@@ -409,8 +409,8 @@
+ * marginally improve the speed of the less frequent case, I chose
+ * to maintain high performance for the common case.
+ */
+- if (ReadImage(interp, (char *) trashBuffer, chan, fileWidth,
+- fileHeight, colorMap, 0, 0, 0, 0, 0, -1) != TCL_OK) {
++ if (ReadImage(interp, (char *) trashBuffer, chan, imageWidth,
++ imageHeight, colorMap, 0, 0, 0, 0, 0, -1) != TCL_OK) {
+ goto error;
+ }
+ continue;
+@@ -436,8 +436,8 @@
+ srcX = 0;
+ }
+
+- if (width fileWidth) {
+- width = fileWidth;
++ if (width imageWidth) {
++ width = imageWidth;
+ }
+
+ index = LM_to_uint(buf[2],buf[3]);
+@@ -446,8 +446,8 @@
+ destY -= srcY; height += srcY;
+ srcY = 0;
+ }
+- if (height fileHeight) {
+- height = fileHeight;
++ if (height imageHeight) {
++ height = imageHeight;
+ }
+
+ if ((width = 0) || (height = 0)) {
+@@ -459,12 +459,12 @@
+ block.height = height;
+ block.pixelSize = (transparent=0) ? 4 : 3;
+ block.offset[3] = (transparent=0) ? 3 : 0;
+- block.pitch = block.pixelSize * width;
+- nBytes = block.pitch * height;
++ block.pitch = block.pixelSize * imageWidth;
++ nBytes = block.pitch * imageHeight;
+ block.pixelPtr = (unsigned char *) ckalloc((unsigned) nBytes);
+
+- if (ReadImage(interp, (char *) block.pixelPtr, chan, width,
+- height, colorMap, fileWidth, fileHeight, srcX, srcY,
++ if (ReadImage(interp, (char *) block.pixelPtr, chan, imageWidth,
++ imageHeight, colorMap, fileWidth, fileHeight, srcX, srcY,
+ BitSet(buf[8], INTERLACE), transparent) != TCL_OK) {
+ goto error;
+ }
Processed: tagging 446465
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.9 tags 446465 + patch Bug#446465: CVE-2007-5378 buffer overflow in tkImgGif.c via crafted gif image Tags were: security Tags added: patch 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#424820: what about etch?
It would be great if the dependency of php-file on PHP4 would be removed in etch too: $ apt-cache show php-file Package: php-file Priority: optional Section: web Installed-Size: 96 Maintainer: Chris Anderson [EMAIL PROTECTED] Architecture: all Version: 1.0.3-1 Depends: php4-pear ( 4:4.3.3) Filename: pool/main/p/php-file/php-file_1.0.3-1_all.deb Size: 10632 MD5sum: afe7211779523c84855355ac6d2ac9da SHA1: 7b7ec7147cdde5a89e0b480c5880537d58b9f10b SHA256: e06551955190d2174343d7765291206d52012907dc0be85a31b0d961a75c9a28 Description: PHP Pear modules for common file and directory routines Provides easy access to read/write to files along with some common routines to deal with paths. Also provides interface for handling CSV files. Tag: devel::lang:php, devel::library, implemented-in::php, works-with::file -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#443637: #443637 php5: FTBFS: recode extension can not be configured together with: imap mysql
Hi, List night debugging of this, with the help of Atomo64, seanius and vorlon, led to the conclusion that the build system is broken due to the suhosin.patch others changing files in incorrect order. Thing is, that configure needs to be re-generated in order to avoid the recode extension can not be configured together with: imap mysql error and replace it with just a warning. On amd64, due to its hi-res stamps, configure is not re-generated and so we have the error. OTOH, re-generating configure (and main/php_config.h.in) overwrites the patches applied to them so it can't be left for build-time. vorlon promised to take a look. I'd very much like to see this fixed properly, which will have educational effect too :) My ideas for the fix include yet another patch, that is applied before most of the rest, that applies the changes to configure and main/php_config.h.in so there won't be a need to re-generate them in non-controlled environment (a.k.a. buildd). This would require reordering of the patches, all patches that modify configure pre-requisites should be applied before the configure patch for example. As a nice side effect, auto* may be dropped from build-dependencies. -- damJabberID: [EMAIL PROTECTED] signature.asc Description: Digital signature
Bug#446472: CVE-2007-5246 stack-based buffer overflow
Package: firebird1.5 Severity: grave Tags: security patch Hi, the following CVE (Common Vulnerabilities Exposures) id was published for firebird1.5. CVE-2007-5246[0]: | Multiple stack-based buffer overflows in Firebird LI 2.0.0.12748 and | 2.0.1.12855, and WI 2.0.0.12748 and 2.0.1.12855, allow remote | attackers to execute arbitrary code via (1) a long attach request on | TCP port 3050 to the isc_attach_database function or (2) a long create | request on TCP port 3050 to the isc_create_database function. If you fix this vulnerability please also include the CVE id in your changelog entry. This bug is fixed in the 2.0 version of firebird. You can find a patch on: http://firebird.cvs.sourceforge.net/firebird/firebird2/src/jrd/why.cpp?r1=1.100.4.2r2=1.100.4.3 For further information: [0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-5246 Kind regards Nico -- Nico Golde - http://ngolde.de - [EMAIL PROTECTED] - GPG: 0x73647CFF For security reasons, all text in this mail is double-rot13 encrypted. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Tagging #445772 as sid-only
Processing commands for [EMAIL PROTECTED]: tags 445772 sid Bug#445772: gnat-gps: FTBFS: unsat b-deps: libgnatprj-dev: Depends: gnat-4.2 (= 4.2.1-7) but it is not going to be installed There were no tags set. Tags added: sid 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: tagging 440414
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.8 tags 440414 + lenny sid Bug#440414: libgnome-dev switched to db-4.6 but libgnomemm-dev and libglade-gnome0-dev are still refering to `/usr/lib/libdb-4.5.la' in the la file. There were no tags set. Tags added: lenny, sid 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#446475: CVE-2007-5245 multiple buffer overflows
Package: firebird1.5 Severity: grave Tags: security patch Hi, the following CVE (Common Vulnerabilities Exposures) id was published for firebird1.5. CVE-2007-5245[0]: | Multiple stack-based buffer overflows in Firebird LI 1.5.3.4870 and | 1.5.4.4910, and WI 1.5.3.4870 and 1.5.4.4910, allow remote attackers | to execute arbitrary code via (1) a long service attach request on TCP | port 3050 to the SVC_attach function or (2) unspecified vectors | involving the INET_connect function. If you fix this vulnerability please also include the CVE id in your changelog entry. This is fixed in the 2.0 package in unstable. As far as I can see the fixes for these issues are: http://firebird.cvs.sourceforge.net/firebird/firebird2/src/remote/inet.cpp?r1=1.122r2=1.123 and http://firebird.cvs.sourceforge.net/firebird/firebird2/src/jrd/svc.cpp?r1=1.97r2=1.98 but please check back with upstream, I might have missed something. For further information: [0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-5245 Kind regards Nico -- Nico Golde - http://ngolde.de - [EMAIL PROTECTED] - GPG: 0x73647CFF For security reasons, all text in this mail is double-rot13 encrypted. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#433736: Bug#446373: #446373: firebird1.5: CVE-2007-4992 stack based buffer overflow
Hi Damyan, * Damyan Ivanov [EMAIL PROTECTED] [2007-10-12 21:20]: block 446373 438862 thanks firebird1.5 is pending removal from the archive (#438862, #438855). Ok thanks for this information. Currently the only obstacle in the way is that php5 still build-depends on firebird1.5-dev. (#433736) I am preparing an NMU for the later, as it is pending for two weeks now and the patch is in BTS anyway. Ok. I just reported two other CVEs with patches, please also include them. firebird1.5 must go away ASAP, if nothing else, to stop wasting security team time :) Hehe yes :) Kind regards Nico -- Nico Golde - http://ngolde.de - [EMAIL PROTECTED] - GPG: 0x73647CFF For security reasons, all text in this mail is double-rot13 encrypted. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#445582: ldapscripts shows passwords in the clear on the command line
On Thu, 11 Oct 2007 08:32:52 +0200 (CEST), Ganael LAPLANCHE wrote Hi everybody, ldapscripts v1.7.1 are now available and fix these issues. Here is the CHANGELOG : 2007/10/13 : ldapscripts 1.7.1 - Fixes for CVE-2007-5373 see http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-5373 and http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=445582 1) Up to now, each ldap* command was called with the -w parameter, which allows to specify the bind password on the command line. Unfortunately, this could make the password appear to anybody performing a `ps` during the call. This is now avoided by using the -y parameter and a password file. - A new BINDPWDFILE option has been added : it specifies the path to the bind password file. This file can be created by something like : 'echo -n 'password' $BINDPWDFILE' and you can now safely remove (or comment) the BINDPWD parameter from your configuration file. 2) Changing a user password could also reveal the new password on the command line, because of the use of ldappasswd's -s option. This has been fixed by using a temporary file containing the new password (and ldappassword's -T option). - [internals] New mktempf() and reltempf() functions have been added [For older versions of OpenLDAP, -y and -T parameters may not be available. It is still possible to use the old BINDPWD parameter. Just uncomment it from the configuration file and comment the BINDPWDFILE parameter (which takes precedence over BINDPWD). The ldapscripts will just behave as previously and use inline -w and -s parameters, warning you this is not secure way of running them.] 3) A similar problem related to sed expressions has been found : it may also lead to reveal a user's password to `ps` users. This is now fixed by using temporary files containing sed expressions (and sed's -f option). 4) A new test has been added to check if 'echo' and '[' are built-in or not. If not, you'll be warned that the ldapscripts may not be safe to use (because these commands manipulate passwords when creating temporary files). - [internals] New is_builtin() function Note that these flaws depend largely on your kernel configuration : hardened kernels should not be impacted (e.g. if you use security.bsd.see_other_[u|g]ids sysctls on FreeBSD). It may also depend on the version of OpenLDAP client commands you run. Thanks a lot to Don and Madcoder for their help ! - Few fixes to avoid using non-standard 'if ! command's... Thanks a lot for your help in finding these issues ! (and don't hesitate to come back to me again if you find other problems related to the scripts) Best regards, Ganaël LAPLANCHE [EMAIL PROTECTED] http://www.martymac.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#445582: ldapscripts shows passwords in the clear on the command line
On Sat, 13 Oct 2007 13:37:25 +0200 (CEST), Ganael LAPLANCHE wrote On Thu, 11 Oct 2007 08:32:52 +0200 (CEST), Ganael LAPLANCHE wrote Hi everybody, ldapscripts v1.7.1 are now available and fix these issues. Woops, sorry I forgot to tell where the update is available : http://contribs.martymac.com/ldapscripts/ldapscripts-1.7.1.tgz http://www.sourceforge.net/projects/ldapscripts Best regards, Ganaël LAPLANCHE [EMAIL PROTECTED] http://www.martymac.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#446492: irm: should this package be removed?
Package: irm Version: 1.5.3.1-1.1 Severity: serious User: [EMAIL PROTECTED] Usertags: proposed-removal Hi, Your package came up as a package that should maybe be removed from Debian, because: * Low popcon (10 insts) * RC buggy (doesn't work with php5) * New upstream version available (1.5.7, since 2006-02-16) * GLPI is a fork of irm, seems like a suitable replacement, is maintained properly in Debian, and has an higher popcon * some irm bugs have been open for a long time with no answer from the maintainer. If you think that it should be orphaned instead of being removed from Debian, please reply to this bug and tell so. If you agree, sending the following commands to [EMAIL PROTECTED] should do it (after replacing nn with this bug's number): severity nn normal reassign nn ftp.debian.org retitle nn RM: irm -- RoM; RC-buggy, low popcon, better replacement in Debian thanks For more information, see http://wiki.debian.org/ftpmaster_Removals http://ftp-master.debian.org/removals.txt If you disagree and want to continue to maintain this package, please just close this bug, preferably in an upload also fixing the other issues. Thank you, -- | 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#446465: marked as done (CVE-2007-5378 buffer overflow in tkImgGif.c via crafted gif image)
Your message dated Sat, 13 Oct 2007 13:17:03 + with message-id [EMAIL PROTECTED] and subject line Bug#446465: fixed in tk8.3 8.3.5-10 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: tk8.3 Severity: grave Tags: security Hi, the following CVE (Common Vulnerabilities Exposures) id was published for tk8.3. CVE-2007-5378[0]: | Buffer overflow in the FileReadGIF function in tkImgGIF.c for Tk | Toolkit 8.4.12 and earlier, and 8.3.5 and earlier, allows | user-assisted attackers to cause a denial of service (segmentation | fault) via an animated GIF in which the first subimage is smaller than | a subsequent subimage, which triggers the overflow in the ReadImage | function, a different vulnerability than CVE-2007-5137. If you fix this vulnerability please also include the CVE id in your changelog entry. This bug is fixed in the 8.4 package in unstable and testing but not in etch. For further information: [0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-5378 Kind regards Nico -- Nico Golde - http://ngolde.de - [EMAIL PROTECTED] - GPG: 0x73647CFF For security reasons, all text in this mail is double-rot13 encrypted. pgpKwFfc6BIFQ.pgp Description: PGP signature ---End Message--- ---BeginMessage--- Source: tk8.3 Source-Version: 8.3.5-10 We believe that the bug you reported is fixed in the latest version of tk8.3, which is due to be installed in the Debian FTP archive: tk8.3-dev_8.3.5-10_i386.deb to pool/main/t/tk8.3/tk8.3-dev_8.3.5-10_i386.deb tk8.3-doc_8.3.5-10_all.deb to pool/main/t/tk8.3/tk8.3-doc_8.3.5-10_all.deb tk8.3_8.3.5-10.diff.gz to pool/main/t/tk8.3/tk8.3_8.3.5-10.diff.gz tk8.3_8.3.5-10.dsc to pool/main/t/tk8.3/tk8.3_8.3.5-10.dsc tk8.3_8.3.5-10_i386.deb to pool/main/t/tk8.3/tk8.3_8.3.5-10_i386.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. Sergei Golovan [EMAIL PROTECTED] (supplier of updated tk8.3 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.7 Date: Sat, 13 Oct 2007 16:38:49 +0400 Source: tk8.3 Binary: tk8.3-doc tk8.3-dev tk8.3 Architecture: source i386 all Version: 8.3.5-10 Distribution: unstable Urgency: high Maintainer: Tcl/Tk Debian Packagers [EMAIL PROTECTED] Changed-By: Sergei Golovan [EMAIL PROTECTED] Description: tk8.3 - Tk toolkit for Tcl and X11, v8.3 - run-time files tk8.3-dev - Tk toolkit for Tcl and X11, v8.3 - development files tk8.3-doc - Tk toolkit for Tcl and X11, v8.3 - manual pages Closes: 446465 Changes: tk8.3 (8.3.5-10) unstable; urgency=high . * Applied patch by Nico Golde which fixes security vulnerability CVE-2007-5378 overflow triggered by crafted GIF file (closes: #446465). Files: 5b06792280f7bf00f8dd9f268cb8b098 809 libs optional tk8.3_8.3.5-10.dsc 0f02d31ba5001d4d5b4373bc90b9465c 31880 libs optional tk8.3_8.3.5-10.diff.gz b77070c5ecd61ff0289cf626a738b85a 659370 doc optional tk8.3-doc_8.3.5-10_all.deb 9f7251beec54de2b00542180dbb2d61a 813618 libs optional tk8.3_8.3.5-10_i386.deb d72f7f2027035877d9ef982ee7439bfb 663082 devel optional tk8.3-dev_8.3.5-10_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHEMCWIcdH02pGEFIRAir3AJ4i4RZUgdwcTvsITwe7IOMrTT/hmQCePg1r dw1cGAvF/RzUGodNdDaRNSQ= =fC7G -END PGP SIGNATURE- ---End Message---
Bug#442208: request to remove dosemu-freedos from stable
On Fri, 2007-09-14 at 08:24 +0200, Mike Hommey wrote: On Fri, Sep 14, 2007 at 08:11:07AM +0200, Bart Martens [EMAIL PROTECTED] wrote: Please remove dosemu-freedos version 1:0.0.b9r5a-3 from Stable. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=442208 Isn't it simply possible to remove the rerror source and binary ? Or move the package in Stable from contrib to non-free ? Regards, Bart Martens -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#423240: comedi: should this package be orphaned?
Processing commands for [EMAIL PROTECTED]: severity 423240 normal Bug#423240: comedi: should this package be orphaned? Severity set to `normal' from `serious' reassign 423240 wnpp Bug#423240: comedi: should this package be orphaned? Bug reassigned from package `comedi' to `wnpp'. retitle 423240 O: comedi -- Comedi kernel module source Bug#423240: comedi: should this package be orphaned? Changed Bug title to `O: comedi -- Comedi kernel module source' from `comedi: should this package be orphaned?'. 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#423240: comedi: should this package be orphaned?
severity 423240 normal reassign 423240 wnpp retitle 423240 O: comedi -- Comedi kernel module source thanks Hi, Since this request was not answered by the maintainer for more than 150 days, and the situation of comedi hasn't improved in the mean time, I'm orphaning this as originally suggested. Thank you, -- | 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]
Processed (with 2 errors): Re: Bug#423292: lessdisks: should this package be orphaned?
Processing commands for [EMAIL PROTECTED]: retitle 423292 lessdisks: should this package be removed? Bug#423292: lessdisks: looks orphaned but just vry slow progress Changed Bug title to `lessdisks: should this package be removed?' from `lessdisks: looks orphaned but just vry slow progress'. severity 423292 serious Bug#423292: lessdisks: should this package be removed? Bug#389498: remove lessdisks from debian Severity set to `serious' from `normal' user [EMAIL PROTECTED] Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]). usertags - proposed-orphan Unknown command or malformed arguments to command. usertags + proposed-removal Unknown command or malformed arguments to command. 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#423241: marked as done (egnome: should this package be orphaned?)
Your message dated Sat, 13 Oct 2007 15:33:41 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#423241: egnome: should this package be orphaned? has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: egnome Version: 0.cvs20020302-4 Severity: serious User: [EMAIL PROTECTED] Usertags: proposed-orphan Hi, While reviewing packages that were not included in Etch, your package came up as a package that should maybe be orphaned by its maintainer, because: * RC bug open for more than 170 days without answer from the maintainer. If you think that it should be removed from Debian instead of being orphaned, please reply to this bug and tell so. If you agree that it should be orphaned, sending the following commands to [EMAIL PROTECTED] should do it (after replacing nn with this bug's number): severity nn normal reassign nn wnpp retitle nn O: egnome -- Eiffel wrapper for the Gnome library thanks For more information, see http://www.debian.org/doc/developers-reference/ch-pkgs.en.html#s-archive-manip http://www.debian.org/devel/wnpp/ If you disagree and want to continue to maintain this package, please close this bug, preferably in an upload also fixing the other issues. Thank you, -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | ---End Message--- ---BeginMessage--- egnome was already removed from Debian, closing bugs. Lucas ---End Message---
Processed: fixed in 1:3.8.1-1etch1 in proposed-updates
Processing commands for [EMAIL PROTECTED]: fixed 430836 1:3.8.1-1etch1 Bug#430836: python-pygresql: Missing dependency on libpq4 Bug marked as fixed in version 1:3.8.1-1etch1. 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]
Processed: Re: Bug#423287: harbour: should this package be orphaned?
Processing commands for [EMAIL PROTECTED]: severity 423287 normal Bug#423287: harbour: should this package be orphaned? Severity set to `normal' from `serious' reassign 423287 wnpp Bug#423287: harbour: should this package be orphaned? Bug reassigned from package `harbour' to `wnpp'. retitle 423287 O: harbour -- Compiler for the xBase superset language often referred to as Clipper Bug#423287: harbour: should this package be orphaned? Changed Bug title to `O: harbour -- Compiler for the xBase superset language often referred to as Clipper' from `harbour: should this package be orphaned?'. 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#446437: latest update has fixed this problem
update libcommons-collections-java to latest(2.1.1-8) this problem has been solved. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#423290: marked as done (hwtools: should this package be orphaned?)
Your message dated Sat, 13 Oct 2007 15:46:41 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#423290: hwtools: should this package be orphaned? has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: hwtools Version: 0.8-6.1 Severity: serious User: [EMAIL PROTECTED] Usertags: proposed-orphan Hi, While reviewing packages that were not included in Etch, your package came up as a package that should maybe be orphaned by its maintainer, because: * Release Critical Bugs for open more than 200 Days If you think that it should be removed from Debian instead of being orphaned, please reply to this bug and tell so. If you agree that it should be orphaned, sending the following commands to [EMAIL PROTECTED] should do it (after replacing nn with this bug's number): severity nn normal reassign nn wnpp retitle nn O: hwtools -- short package description thanks For more information, see http://www.debian.org/doc/developers-reference/ch-pkgs.en.html#s-archive-manip http://www.debian.org/devel/wnpp/ If you disagree and want to continue to maintain this package, please close this bug, preferably in an upload also fixing the other issues. Thank you, - michael ---End Message--- ---BeginMessage--- On 11/05/07 at 00:44 -0600, Michael Ablassmeier wrote: While reviewing packages that were not included in Etch, your package came up as a package that should maybe be orphaned by its maintainer, because: Actually it was already orphaned a long time ago. Closing. Lucas ---End Message---
Processed: Re: Bug#423285: fwatch: should this package be orphaned?
Processing commands for [EMAIL PROTECTED]: severity 423285 normal Bug#423285: fwatch: should this package be orphaned? Severity set to `normal' from `serious' reassign 423285 wnpp Bug#423285: fwatch: should this package be orphaned? Bug reassigned from package `fwatch' to `wnpp'. retitle 423285 O: fwatch -- Kernel level file activity monitoring Bug#423285: fwatch: should this package be orphaned? Changed Bug title to `O: fwatch -- Kernel level file activity monitoring' from `fwatch: should this package be orphaned?'. 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#423287: harbour: should this package be orphaned?
severity 423287 normal reassign 423287 wnpp retitle 423287 O: harbour -- Compiler for the xBase superset language often referred to as Clipper thanks On 11/05/07 at 00:38 -0600, Michael Ablassmeier wrote: Hi, While reviewing packages that were not included in Etch, your package came up as a package that should maybe be orphaned by its maintainer, because: * Release Critical Bugs for open 2 Years * Low Popcon Stats Hi, Since the situation didn't improve, and the maintainer never answered this bug report, I'm now orphaning the package, as originally suggested. Thank you, -- | 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#423285: fwatch: should this package be orphaned?
severity 423285 normal reassign 423285 wnpp retitle 423285 O: fwatch -- Kernel level file activity monitoring thanks On 11/05/07 at 00:36 -0600, Michael Ablassmeier wrote: Package: fwatch Version: 0.1-alpha-3 Severity: serious User: [EMAIL PROTECTED] Usertags: proposed-orphan Hi, While reviewing packages that were not included in Etch, your package came up as a package that should maybe be orphaned by its maintainer, because: * Long standing Release Critical Bugs * No Upload since 2004 * Low Popcon Stats Hi, Since the situation of fwatch hasn't changed at all, and the maintainer didn't answer, I'm now orphaning this package. Thank you, -- | 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#444196: These two bugs are related
Hi, these bugs #444196 and #444824 are probably related... Greetings, Joachim -- Joachim nomeata Breitner Debian Developer [EMAIL PROTECTED] | ICQ# 74513189 | GPG-Keyid: 4743206C JID: [EMAIL PROTECTED] | http://people.debian.org/~nomeata -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#423200: quake2: should this package be orphaned?
On 09/10/07 at 14:52 +0530, Kartik Mistry wrote: On 10/9/07, Lucas Nussbaum [EMAIL PROTECTED] wrote: This should probably be replaced by http://jdolan.dyndns.org/trac/wiki/Quetoo This word, I do not think it means what you think it means. Hi Jamie, I'm not sure I understand what you mean. Can you please rephrase? I think he want to say that 'Quetoo' is replacement of this 'Quake2' package, as I guess from given link :) So Jamie, can you confirm that quake2 should be removed from debian, and that Quetoo should be packaged instead? -- | 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]
Processed: Duplicate..
Processing commands for [EMAIL PROTECTED]: severity 444531 normal Bug#444531: galculator: FTBFS: error: conflicting types for 'gdk_color_to_string' Severity set to `normal' from `serious' merge 440844 440845 444531 Bug#440844: patch to fix FTBFS with newer GTK versions Bug#440845: Patch for galculator to fix gdk_color_to_string FTBFS Bug#444531: galculator: FTBFS: error: conflicting types for 'gdk_color_to_string' Merged 440844 440845 444531. 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#423292: lessdisks: should this package be orphaned?
severity 423292 normal reassign 423292 ftp.debian.org retitle 423292 RM: lessdisks -- RoM; RC-buggy, useless thanks Oh, well... - Jonas -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ - Enden er nær: http://www.shibumi.org/eoti.htm signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#423292: lessdisks: should this package be orphaned?
Processing commands for [EMAIL PROTECTED]: severity 423292 normal Bug#423292: lessdisks: should this package be removed? Bug#389498: remove lessdisks from debian Severity set to `normal' from `serious' reassign 423292 ftp.debian.org Bug#423292: lessdisks: should this package be removed? Bug#389498: remove lessdisks from debian Bug reassigned from package `lessdisks' to `ftp.debian.org'. retitle 423292 RM: lessdisks -- RoM; RC-buggy, useless Bug#423292: lessdisks: should this package be removed? Changed Bug title to `RM: lessdisks -- RoM; RC-buggy, useless' from `lessdisks: should this package be removed?'. 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#423311: pnet: should this package be orphaned?
severity 423311 normal reassign 423311 wnpp retitle 423311 O: pnet -- DotGNU C# compiler, runtime, (dis)assembler severity 423312 normal reassign 423312 wnpp retitle 423312 O: pnet-assemblies -- DotGNU C# class libraries thanks On 11/05/07 at 01:08 -0600, Michael Ablassmeier wrote: Hi, While reviewing packages that were not included in Etch, your package came up as a package that should maybe be orphaned by its maintainer, because: * Long Standing Release Critical Bugs Hi, Since the situation didn't improve, and the maintainer never answered this bug report, I'm now orphaning the package, as originally suggested. Thank you, -- | 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#423295: marked as done (libooc-vo: should this package be orphaned?)
Your message dated Sat, 13 Oct 2007 16:07:02 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#423295: libooc-vo: should this package be orphaned? has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: libooc-vo Version: 20020310-3 Severity: serious User: [EMAIL PROTECTED] Usertags: proposed-orphan Hi, While reviewing packages that were not included in Etch, your package came up as a package that should maybe be orphaned by its maintainer, because: * Release Critical Bugs * Outdated * #418508: libooc-vo: Please remove this package from unstable If you think that it should be removed from Debian instead of being orphaned, please reply to this bug and tell so. If you agree that it should be orphaned, sending the following commands to [EMAIL PROTECTED] should do it (after replacing nn with this bug's number): severity nn normal reassign nn wnpp retitle nn O: libooc-vo -- short package description thanks For more information, see http://www.debian.org/doc/developers-reference/ch-pkgs.en.html#s-archive-manip http://www.debian.org/devel/wnpp/ If you disagree and want to continue to maintain this package, please close this bug, preferably in an upload also fixing the other issues. Thank you, - michael ---End Message--- ---BeginMessage--- Package was removed from debian, closing. Lucas ---End Message---
Processed: Re: Bug#423308: oskit: should this package be orphaned?
Processing commands for [EMAIL PROTECTED]: severity 423308 normal Bug#423308: oskit: should this package be orphaned? Severity set to `normal' from `serious' reassign 423308 wnpp Bug#423308: oskit: should this package be orphaned? Bug reassigned from package `oskit' to `wnpp'. retitle 423308 O: oskit -- The Flux Operating System Toolkit, a framework for OS design Bug#423308: oskit: should this package be orphaned? Changed Bug title to `O: oskit -- The Flux Operating System Toolkit, a framework for OS design' from `oskit: should this package be orphaned?'. 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#423293: libapache2-mod-xmlrpc2: should this package be orphaned?
severity 423293 normal reassign 423293 wnpp retitle 423293 O: libapache2-mod-xmlrpc2 -- XMLRPC Server module for Apache2 web server thanks On 11/05/07 at 00:49 -0600, Michael Ablassmeier wrote: Hi, While reviewing packages that were not included in Etch, your package came up as a package that should maybe be orphaned by its maintainer, because: * Several Release Critical Bugs open for more than 200 days * Low popcon stats Hi, Since the situation didn't improve, and the maintainer never answered this bug report, I'm now orphaning the package, as originally suggested. Thank you, -- | 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#446500: roundcube: Needs versioned dependency on dbconfig-common
Package: roundcube Version: 0.1~rc1-2 Severity: serious Justification: Policy 3.5 Installing this package on an Etch system fullfills all dependencies, but fails to initialize a database. Backporting a newer version of dbconfig-common makes the installation succeed. this leads me to assume, that this package rely on dbconfig-common functionality only available in later releases, which means the package must declare a versioned dependency on dbconfig-common. - Jonas -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22-1jones1-amd64-desktop (SMP w/2 CPU cores; PREEMPT) Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#423297: marked as done (mc-foo: should this package be orphaned?)
Your message dated Sat, 13 Oct 2007 16:07:58 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#423297: mc-foo: should this package be orphaned? has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: mc-foo Version: 0.0.13 Severity: serious User: [EMAIL PROTECTED] Usertags: proposed-orphan Hi, While reviewing packages that were not included in Etch, your package came up as a package that should maybe be orphaned by its maintainer, because: * Several Release Critical Bugs * No python Transition happened yet * Last Upload back in 2003 If you think that it should be removed from Debian instead of being orphaned, please reply to this bug and tell so. If you agree that it should be orphaned, sending the following commands to [EMAIL PROTECTED] should do it (after replacing nn with this bug's number): severity nn normal reassign nn wnpp retitle nn O: mc-foo -- short package description thanks For more information, see http://www.debian.org/doc/developers-reference/ch-pkgs.en.html#s-archive-manip http://www.debian.org/devel/wnpp/ If you disagree and want to continue to maintain this package, please close this bug, preferably in an upload also fixing the other issues. Thank you, - michael ---End Message--- ---BeginMessage--- package was removed from debian, closing. Lucas ---End Message---
Processed: Re: Bug#423293: libapache2-mod-xmlrpc2: should this package be orphaned?
Processing commands for [EMAIL PROTECTED]: severity 423293 normal Bug#423293: libapache2-mod-xmlrpc2: should this package be orphaned? Severity set to `normal' from `serious' reassign 423293 wnpp Bug#423293: libapache2-mod-xmlrpc2: should this package be orphaned? Bug reassigned from package `libapache2-mod-xmlrpc2' to `wnpp'. retitle 423293 O: libapache2-mod-xmlrpc2 -- XMLRPC Server module for Apache2 web server Bug#423293: libapache2-mod-xmlrpc2: should this package be orphaned? Changed Bug title to `O: libapache2-mod-xmlrpc2 -- XMLRPC Server module for Apache2 web server' from `libapache2-mod-xmlrpc2: should this package be orphaned?'. 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#423299: metalog: should this package be orphaned?
severity 423299 normal reassign 423299 wnpp retitle 423299 O: metalog -- Modern logging daemon with regexp support thanks On 11/05/07 at 01:00 -0600, Michael Ablassmeier wrote: Hi, While reviewing packages that were not included in Etch, your package came up as a package that should maybe be orphaned by its maintainer, because: * release critical bugs open for more than 1 Year Hi, Since the situation didn't improve, and the maintainer never answered this bug report, I'm now orphaning the package, as originally suggested. Thank you, -- | 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#423308: oskit: should this package be orphaned?
severity 423308 normal reassign 423308 wnpp retitle 423308 O: oskit -- The Flux Operating System Toolkit, a framework for OS design thanks While reviewing packages that were not included in Etch, your package came up as a package that should maybe be orphaned by its maintainer, because: * Open Release Critical Bugs for Years Hi, Since the situation didn't improve, and the maintainer never answered this bug report, I'm now orphaning the package, as originally suggested. Thank you, -- | 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#423294: Bug#423327: liblinux-aio-perl: should this package be removed?
severity 423294 normal reassign 423294 wnpp retitle 423294 O: liblinux-aio-perl -- linux-specific perl aio implemented using clone thanks On 11/05/07 at 01:40 -0600, Michael Ablassmeier wrote: Hi, While reviewing packages that were not included in Etch, your package came up as a possible candidate for removal from Debian, because: * Long standing Release Critical Bugs * Low Popcon Stats Hi, Since the situation didn't improve, and the maintainer never answered this bug report, I'm now orphaning the package, as originally suggested. Thank you, -- | 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#423298: mercury: should this package be orphaned?
severity 423298 normal reassign 423298 wnpp retitle 423298 O: mercury -- A new logic/functional programming language thanks On 01/06/07 at 22:02 +1200, Roy Ward wrote: I'd like to adopt the mercury (and mercury-docs) packages, unless someone more qualified wishes to do it. Hi Roy, I've just orphaned mercury, since the previous maintainer never answered this bug. Feel free to adopt it if you are still interested. Thank you, -- | 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]
Processed: Re: Bug#423298: mercury: should this package be orphaned?
Processing commands for [EMAIL PROTECTED]: severity 423298 normal Bug#423298: mercury: should this package be orphaned? Severity set to `normal' from `serious' reassign 423298 wnpp Bug#423298: mercury: should this package be orphaned? Bug reassigned from package `mercury' to `wnpp'. retitle 423298 O: mercury -- A new logic/functional programming language Bug#423298: mercury: should this package be orphaned? Changed Bug title to `O: mercury -- A new logic/functional programming language' from `mercury: should this package be orphaned?'. 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: Re: Bug#423327: liblinux-aio-perl: should this package be removed?
Processing commands for [EMAIL PROTECTED]: severity 423294 normal Bug#423294: liblinux-aio-perl: should this package be orphaned? Severity set to `normal' from `serious' reassign 423294 wnpp Bug#423294: liblinux-aio-perl: should this package be orphaned? Bug reassigned from package `liblinux-aio-perl' to `wnpp'. retitle 423294 O: liblinux-aio-perl -- linux-specific perl aio implemented using clone Bug#423294: liblinux-aio-perl: should this package be orphaned? Changed Bug title to `O: liblinux-aio-perl -- linux-specific perl aio implemented using clone' from `liblinux-aio-perl: should this package be orphaned?'. 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: Re: Bug#423299: metalog: should this package be orphaned?
Processing commands for [EMAIL PROTECTED]: severity 423299 normal Bug#423299: metalog: should this package be orphaned? Severity set to `normal' from `serious' reassign 423299 wnpp Bug#423299: metalog: should this package be orphaned? Bug reassigned from package `metalog' to `wnpp'. retitle 423299 O: metalog -- Modern logging daemon with regexp support Bug#423299: metalog: should this package be orphaned? Changed Bug title to `O: metalog -- Modern logging daemon with regexp support' from `metalog: should this package be orphaned?'. 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#423305: marked as done (oo2c: should this package be orphaned?)
Your message dated Sat, 13 Oct 2007 16:17:25 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#423305: oo2c: should this package be orphaned? has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: oo2c Version: 2.1.11-2 Severity: serious User: [EMAIL PROTECTED] Usertags: proposed-orphan Hi, While reviewing packages that were not included in Etch, your package came up as a package that should maybe be orphaned by its maintainer, because: * Release Critical Bugs open for more than 100 Days If you think that it should be removed from Debian instead of being orphaned, please reply to this bug and tell so. If you agree that it should be orphaned, sending the following commands to [EMAIL PROTECTED] should do it (after replacing nn with this bug's number): severity nn normal reassign nn wnpp retitle nn O: oo2c -- short package description thanks For more information, see http://www.debian.org/doc/developers-reference/ch-pkgs.en.html#s-archive-manip http://www.debian.org/devel/wnpp/ If you disagree and want to continue to maintain this package, please close this bug, preferably in an upload also fixing the other issues. Thank you, - michael ---End Message--- ---BeginMessage--- package was already orphaned. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | ---End Message---
Processed: Re: Bug#423311: pnet: should this package be orphaned?
Processing commands for [EMAIL PROTECTED]: severity 423311 normal Bug#423311: pnet: should this package be orphaned? Severity set to `normal' from `serious' reassign 423311 wnpp Bug#423311: pnet: should this package be orphaned? Bug reassigned from package `pnet' to `wnpp'. retitle 423311 O: pnet -- DotGNU C# compiler, runtime, (dis)assembler Bug#423311: pnet: should this package be orphaned? Changed Bug title to `O: pnet -- DotGNU C# compiler, runtime, (dis)assembler' from `pnet: should this package be orphaned?'. severity 423312 normal Bug#423312: pnet-assemblies: should this package be orphaned? Severity set to `normal' from `serious' reassign 423312 wnpp Bug#423312: pnet-assemblies: should this package be orphaned? Bug reassigned from package `pnet-assemblies' to `wnpp'. retitle 423312 O: pnet-assemblies -- DotGNU C# class libraries Bug#423312: pnet-assemblies: should this package be orphaned? Changed Bug title to `O: pnet-assemblies -- DotGNU C# class libraries' from `pnet-assemblies: should this package be orphaned?'. 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#423302: marked as done (murasaki: should this package be orphaned?)
Your message dated Sat, 13 Oct 2007 16:15:15 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#423302: murasaki: should this package be orphaned? has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: murasaki Version: 0.8.11-3 Severity: serious User: [EMAIL PROTECTED] Usertags: proposed-orphan Hi, While reviewing packages that were not included in Etch, your package came up as a package that should maybe be orphaned by its maintainer, because: * Long standing Release Critical Bugs * Last Maintainer Action back in 2005 If you think that it should be removed from Debian instead of being orphaned, please reply to this bug and tell so. If you agree that it should be orphaned, sending the following commands to [EMAIL PROTECTED] should do it (after replacing nn with this bug's number): severity nn normal reassign nn wnpp retitle nn O: murasaki -- short package description thanks For more information, see http://www.debian.org/doc/developers-reference/ch-pkgs.en.html#s-archive-manip http://www.debian.org/devel/wnpp/ If you disagree and want to continue to maintain this package, please close this bug, preferably in an upload also fixing the other issues. Thank you, - michael ---End Message--- ---BeginMessage--- package was already removed from debian. Lucas ---End Message---
Bug#446502: roundcube: Config template must not be stored below /usr/share/doc
Package: roundcube Version: 0.1~rc1-2 Severity: serious Justification: Policy 12.3 Postinst creates the man config file from a file below /usr/share/doc. Debian Policy demands that packages must not rely on /usr/share/doc - instead, symlinks from /usr/share/doc to its location below /usr/share/package or /usr/lib/package should be made, as described in details in Debian Policy scetion 10.7.3. - Jonas -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22-1jones1-amd64-desktop (SMP w/2 CPU cores; PREEMPT) Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#423322: Maintainership of SWI-Prolog
Hi Chris, Janusz, On 09/07/07 at 10:27 +0200, Janusz S. =?UTF-8?Q?Bie=C5=84 wrote: On Thu, 21 Jun 2007 Chris Lamb [EMAIL PROTECTED] wrote: Dear all, I have contacted Gerardo Curiel and he has agreed to let me become a co-maintainer of the SWI-Prolog package. I am a regular user of this package and would dearly like to see a well-maintained package inside Debian. Great! I am in the latter stages of preparing an upload of the latest upstream version, which should close at least 5 (yes :-/) outstanding bugs. Any estimation when the package may be available? Please note my wish list about Prolog Unit Tests: http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=20;bug=425580 Here's hoping to a better future of this package. I will be very much grateful for its up-to-date and complete version. Best regards Chris, could you give us an update on that? Janusz P.S. What about merging 423322 and 425580? IMHO that's not a good idea: even if a new upstream release is uploaded, it doesn't mean that all issues are fixed. -- | 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#423317: ppscsi: should this package be orphaned?
On 11/05/07 at 22:35 +0200, Eduard Bloch wrote: #include hallo.h * Michael Ablassmeier [Fri, May 11 2007, 01:15:59AM]: Package: ppscsi Version: 0.3 Severity: serious User: [EMAIL PROTECTED] Usertags: proposed-orphan Hi, While reviewing packages that were not included in Etch, your package came up as a package that should maybe be orphaned by its maintainer, because: * Several Release Critical Bugs * Last upload back in 2004 * Seems to break with recent Kernels If you think that it should be removed from Debian instead of being orphaned, please reply to this bug and tell so. If you agree that it should be orphaned, sending the following commands to I disagree. There is an update available on the net but it does weird things with my scanner and the current SANE. I consider doing more work on it as soon as I get more spare time. Hi Eduard, Any news on this? If you are so low on spare time, have you considered seeking co-maintainers? -- | 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]
Processed: Re: Bug#429794: jmagick: should this package be orphaned?
Processing commands for [EMAIL PROTECTED]: severity 429794 normal Bug#429794: jmagick: should this package be orphaned? Severity set to `normal' from `serious' reassign 429794 wnpp Bug#429794: jmagick: should this package be orphaned? Bug reassigned from package `jmagick' to `wnpp'. retitle 429794 O: jmagick -- A java interface to ImageMagick - java classes Bug#429794: jmagick: should this package be orphaned? Changed Bug title to `O: jmagick -- A java interface to ImageMagick - java classes' from `jmagick: should this package be orphaned?'. 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: Re: Bug#385285: scsi-idle: obsolete kernel, dummy bug
Processing commands for [EMAIL PROTECTED]: forcemerge 385285 423321 Bug#385285: scsi-idle: obsolete kernel, dummy bug Bug#423321: scsi-idle: should this package be orphaned? Forcibly Merged 385285 423321. severity 385285 normal Bug#385285: scsi-idle: obsolete kernel, dummy bug Bug#423321: scsi-idle: should this package be orphaned? Severity set to `normal' from `serious' reassign 385285 ftp.debian.org Bug#385285: scsi-idle: obsolete kernel, dummy bug Bug#423321: scsi-idle: should this package be orphaned? Bug reassigned from package `scsi-idle' to `ftp.debian.org'. retitle 385285 RM: scsi-idle -- RoQA; RC-buggy, useless Bug#385285: scsi-idle: obsolete kernel, dummy bug Changed Bug title to `RM: scsi-idle -- RoQA; RC-buggy, useless' from `scsi-idle: obsolete kernel, dummy bug'. 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#423321: Bug#385285: scsi-idle: obsolete kernel, dummy bug
forcemerge 385285 423321 severity 385285 normal reassign 385285 ftp.debian.org retitle 385285 RM: scsi-idle -- RoQA; RC-buggy, useless thanks On 17/04/07 at 13:31 +0200, Lucas Nussbaum wrote: On 18/12/06 at 10:51 +0100, Marcus Better wrote: Suggest removing the package from Debian altogether. Agreed. Eduard, can you request the removal of scsi-idle, if you agree as well ? With no answer from Eduard for nearly 6 months, I file the removal request myself. Thank you, -- | 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#429794: jmagick: should this package be orphaned?
severity 429794 normal reassign 429794 wnpp retitle 429794 O: jmagick -- A java interface to ImageMagick - java classes thanks On 20/06/07 at 08:47 +0200, Lucas Nussbaum wrote: While reviewing packages that were not included in Etch, your package came up as a package that should maybe be orphaned by its maintainer, because: * RC bugs open for a very long time Hi, Since the situation didn't improve, and the maintainer never answered this bug report, I'm now orphaning the package, as originally suggested. I'm Ccing debian-java@ since they might be interested in taking over maintenance. Thank you, -- | 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]
Processed: Re: Bug#423316: pnetc: should this package be orphaned?
Processing commands for [EMAIL PROTECTED]: severity 423316 normal Bug#423316: pnetc: should this package be orphaned? Severity set to `normal' from `serious' reassign 423316 wnpp Bug#423316: pnetc: should this package be orphaned? Bug reassigned from package `pnetc' to `wnpp'. retitle 423316 O: pnetc -- DotGNU C runtime libraries Bug#423316: pnetc: should this package be orphaned? Changed Bug title to `O: pnetc -- DotGNU C runtime libraries' from `pnetc: should this package be orphaned?'. 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#423313: marked as done (php-image-canvas: should this package be orphaned?#)
Your message dated Sat, 13 Oct 2007 16:57:17 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#423313: php-image-canvas: should this package be orphaned?# has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: php-image-canvas Version: 0.2.2-1 Severity: serious User: [EMAIL PROTECTED] Usertags: proposed-orphan Hi, While reviewing packages that were not included in Etch, your package came up as a package that should maybe be orphaned by its maintainer, because: * Several Release Critical Bugs open for more than Years * Last upload in 2005 If you think that it should be removed from Debian instead of being orphaned, please reply to this bug and tell so. If you agree that it should be orphaned, sending the following commands to [EMAIL PROTECTED] should do it (after replacing nn with this bug's number): severity nn normal reassign nn wnpp retitle nn O: php-image-canvas -- short package description thanks For more information, see http://www.debian.org/doc/developers-reference/ch-pkgs.en.html#s-archive-manip http://www.debian.org/devel/wnpp/ If you disagree and want to continue to maintain this package, please close this bug, preferably in an upload also fixing the other issues. Thank you, - michael ---End Message--- ---BeginMessage--- Closing this bug as #423310 is exactly the same. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | signature.asc Description: Digital signature ---End Message---
Bug#442208: request to remove dosemu-freedos from stable
On Sat, Oct 13, 2007 at 03:21:36PM +0200, Bart Martens wrote: On Fri, 2007-09-14 at 08:24 +0200, Mike Hommey wrote: On Fri, Sep 14, 2007 at 08:11:07AM +0200, Bart Martens [EMAIL PROTECTED] wrote: Please remove dosemu-freedos version 1:0.0.b9r5a-3 from Stable. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=442208 Isn't it simply possible to remove the rerror source and binary ? If the maintainer wants to upload it to proposed-updates, that would be fine from a release point of view. I don't know in how far the package would still be usable though? Or move the package in Stable from contrib to non-free ? This as well as removal from the archive can normally only happen by a ftp-master during a point release on request of a release team member. If possible removing only the source file and binary file is preferred. Cheers Luk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#423316: pnetc: should this package be orphaned?
severity 423316 normal reassign 423316 wnpp retitle 423316 O: pnetc -- DotGNU C runtime libraries thanks On 11/05/07 at 01:15 -0600, Michael Ablassmeier wrote: While reviewing packages that were not included in Etch, your package came up as a package that should maybe be orphaned by its maintainer, because: * Depends on broken Pacakge pnet-assemblies not fixed since long. Hi, Since the situation didn't improve, and the maintainer never answered this bug report, I'm now orphaning the package, as originally suggested. Thank you, -- | 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#446505: wesnoth: not meant for unstable
Package: wesnoth Version: 1.3.9-2 Severity: serious Hi! The upload of 1.3.9 to unstable instead of experimental was an error - this will get addressed with a reupload of an epoched version of 1.2.7. 1.3.9 is the development branch and too much changing in between releases to properly being able to support it, and the next stable upstream release is targeted for next year only. So long, Rhonda -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#445840: irssi: prepared NMU to fix some pending issues
Package: irssi Followup-For: Bug #445840 Hi! I've prepared an NMU which I plan to upload on monday, with the following changelog: #v+ irssi (0.8.12-0.1) unstable; urgency=low * NMU: New upstream release (closes: #445840, 421053) - patch 05upgrade-check-binary.dpatch applied upstream. - patch 08doublefree applied upstream. - C1 control characters aren't passed through anymore (closes: #435315) - return random host on DNS round robin (closes: #374715) * Updated menu file to new menu policy section, added longtitle. -- Gerfried Fuchs [EMAIL PROTECTED] Sat, 13 Oct 2007 16:58:01 +0200 #v- It closes 4 bugs right ahead. I've noticed two more bugreports that propably are able to get closed right ahead (want to take a look at version history and maybe close them with proper version header). I haven't gone through all the other pending issues (yet) about if they might still be an issue with this update or not, even though I did a quick read through them all with which I was able to find the two closes for the changelog above. You can find the package at my site in http://alfie.ist.org/debian/irssi together with a powerpc build and an interdiff between the last version and my NMU preparation, which you also can find attached. So long, Rhonda reverted: --- irssi-0.8.10/config.sub +++ irssi-0.8.10.orig/config.sub @@ -3,7 +3,7 @@ # Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, # 2000, 2001, 2002, 2003, 2004, 2005 Free Software Foundation, Inc. +timestamp='2005-06-02' -timestamp='2006-02-23' # This file is (in principle) common to ALL GNU software. # The presence of a machine in this file suggests that SOME GNU software @@ -119,9 +119,8 @@ # Here we must recognize all the valid KERNEL-OS combinations. maybe_os=`echo $1 | sed 's/^\(.*\)-\([^-]*-[^-]*\)$/\2/'` case $maybe_os in + nto-qnx* | linux-gnu* | linux-dietlibc | linux-uclibc* | uclinux-uclibc* | uclinux-gnu* | \ + kfreebsd*-gnu* | knetbsd*-gnu* | netbsd*-gnu* | storm-chaos* | os2-emx* | rtmk-nova*) - nto-qnx* | linux-gnu* | linux-dietlibc | linux-newlib* | linux-uclibc* | \ - uclinux-uclibc* | uclinux-gnu* | kfreebsd*-gnu* | knetbsd*-gnu* | netbsd*-gnu* | \ - storm-chaos* | os2-emx* | rtmk-nova*) os=-$maybe_os basic_machine=`echo $1 | sed 's/^\(.*\)-\([^-]*-[^-]*\)$/\1/'` ;; @@ -172,10 +171,6 @@ -hiux*) os=-hiuxwe2 ;; - -sco6) - os=-sco5v6 - basic_machine=`echo $1 | sed -e 's/86-.*/86-pc/'` - ;; -sco5) os=-sco3.2v5 basic_machine=`echo $1 | sed -e 's/86-.*/86-pc/'` @@ -192,10 +187,6 @@ # Don't forget version if it is 3.2v4 or newer. basic_machine=`echo $1 | sed -e 's/86-.*/86-pc/'` ;; - -sco5v6*) - # Don't forget version if it is 3.2v4 or newer. - basic_machine=`echo $1 | sed -e 's/86-.*/86-pc/'` - ;; -sco*) os=-sco3.2v2 basic_machine=`echo $1 | sed -e 's/86-.*/86-pc/'` @@ -243,12 +234,12 @@ | arc | arm | arm[bl]e | arme[lb] | armv[2345] | armv[345][lb] | avr \ | bfin \ | c4x | clipper \ + | d10v | d30v | dlx | dsp16xx | dvp \ - | d10v | d30v | dlx | dsp16xx \ | fr30 | frv \ | h8300 | h8500 | hppa | hppa1.[01] | hppa2.0 | hppa2.0[nw] | hppa64 \ | i370 | i860 | i960 | ia64 \ | ip2k | iq2000 \ + | m32r | m32rle | m68000 | m68k | m88k | maxq | mcore \ - | m32r | m32rle | m68000 | m68k | m88k | maxq | mb | microblaze | mcore \ | mips | mipsbe | mipseb | mipsel | mipsle \ | mips16 \ | mips64 | mips64el \ @@ -257,7 +248,7 @@ | mips64vr4100 | mips64vr4100el \ | mips64vr4300 | mips64vr4300el \ | mips64vr5000 | mips64vr5000el \ + | mips64r5900 | mips64r5900el \ - | mips64vr5900 | mips64vr5900el \ | mipsisa32 | mipsisa32el \ | mipsisa32r2 | mipsisa32r2el \ | mipsisa64 | mipsisa64el \ @@ -266,15 +257,14 @@ | mipsisa64sr71k | mipsisa64sr71kel \ | mipstx39 | mipstx39el \ | mn10200 | mn10300 \ + | ms1 \ - | mt \ | msp430 \ - | nios | nios2 \ | ns16k | ns32k \ + | openrisc | or32 \ - | or32 \ | pdp10 | pdp11 | pj | pjl \ | powerpc | powerpc64 | powerpc64le | powerpcle | ppcbe \ | pyramid \ + | sh | sh[1234] | sh[23]e | sh[34]eb | shbe | shle | sh[1234]le | sh3ele \ - | sh | sh[1234] | sh[24]a | sh[23]e | sh[34]eb | shbe | shle | sh[1234]le | sh3ele \ | sh64 | sh64le \ | sparc | sparc64 | sparc64b | sparc86x | sparclet | sparclite \ | sparcv8 | sparcv9 | sparcv9b \ @@ -296,9 +286,6 @@ ;; m88110 | m680[12346]0 | m683?2 | m68360 | m5200 | v70 | w65 | z8k) ;; - ms1) -
Bug#424820: what about etch?
Rimas Kudelis [EMAIL PROTECTED] (13/10/2007): It would be great if the dependency of php-file on PHP4 would be removed in etch too: […] I'm afraid this won't happen. While the bug is serious on lenny/sid, getting rid of PHP4 in etch is no release goal at all… Cheers, -- Cyril Brulebois pgpYFhTUEFoNt.pgp Description: PGP signature
Bug#446462: /usr/bin/vim is left broken when alternative is manual and points to vim-full
On Sat, Oct 13, 2007 at 11:21:12AM +0200, Stefano Zacchiroli wrote: On Sat, Oct 13, 2007 at 10:43:54AM +0200, Raphael Hertzog wrote: $ LANG=C update-alternatives --display vim vim - status is manual. Uhm, are you sure this bug does apply only when the alternatives status is manual? It happened to me as well and I'm quite sure mine alternatives were set to auto. I specifically tested this upgrade both on my system and with piuparts (which I'm running again right now) and everything worked fine. I know there was some weird stuff that had to be done with alternatives for some screw ups I made pre-Etch which may or may not have caused alternatives to switch to manual mode. I remember it doing some less than ideal configuration changes but it was necessary to prevent leaving a bunch of stale links around. James, I think we can probably do an (conditional, only if set to some of the disappeared variants) update-alternatives --auto in the postinst or something like that. This would change the semantics of manual alternatives, but they would be broken anyhow, now that some variants disappeared. Unless something in our package is causing the alternatives to be changed to manual, I'd prefer not to do such special casing. Alternatives are fragile enough as it is, I'd like to limit how much we go poking around in how they're configured. NB, this is one of the reasons why I'd like dpkg to handle alternatives natively. I've had to use various hacks to attempt sane handling of alternatives when upgrades lose slave links (#411669, fixed), no longer provide alternatives, or other such situations. James -- GPG Key: 1024D/61326D40 2003-09-02 James Vega [EMAIL PROTECTED] signature.asc Description: Digital signature
Bug#446462: /usr/bin/vim is left broken when alternative is manual and points to vim-full
On Sat, Oct 13, 2007 at 11:25:49AM -0400, James Vega wrote: On Sat, Oct 13, 2007 at 11:21:12AM +0200, Stefano Zacchiroli wrote: On Sat, Oct 13, 2007 at 10:43:54AM +0200, Raphael Hertzog wrote: $ LANG=C update-alternatives --display vim vim - status is manual. Uhm, are you sure this bug does apply only when the alternatives status is manual? It happened to me as well and I'm quite sure mine alternatives were set to auto. I specifically tested this upgrade both on my system and with piuparts (which I'm running again right now) and everything worked fine. *sigh* I don't know what made piuparts succeed before but it is definitely exhibiting the reported behavior now. Looks like it's time for another update-alternatives hack. James -- GPG Key: 1024D/61326D40 2003-09-02 James Vega [EMAIL PROTECTED] signature.asc Description: Digital signature
Bug#446508: museekd: Hangs on start
Package: museekd Version: 0.1.12-1 Severity: grave Justification: renders package unusable After upgrading to 1:0.1.13, museekd started to hang when started. It outputted this line: museekd :: Version 0.1.13 :: Museek Daemon Plus And then complained about a missing config.image. After adding an image (only tried empty file and a jpeg) the config.image message disappeared, but museekd would still hang. Downgrading to 0.1.12-1 found at museek-plus.org solved the problem, the config.xml built by this musetup also refers to the same config.image. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.22-2-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages museekd depends on: ii libc6 2.6.1-1+b1 GNU C Library: Shared libraries ii libfam0 2.7.0-13 Client library to control the FAM ii libgcc1 1:4.2.1-4GCC support library ii libglib2.0-02.14.0-2 The GLib library of C routines ii libglibmm-2.4-1c2a 2.12.10-0.1 C++ wrapper for the GLib toolkit ( ii libogg0 1.1.3-2 Ogg Bitstream Library ii libsigc++-2.0-0c2a 2.0.17-2 type-safe Signal Framework for C++ ii libstdc++6 4.2.1-4 The GNU Standard C++ Library v3 ii libvorbis0a 1.2.0.dfsg-2 The Vorbis General Audio Compressi ii libxml++2.6-2 2.14.0-0.1 A C++ interface to the GNOME XML l ii libxml2 2.6.30.dfsg-2GNOME XML library ii python 2.4.4-6 An interactive high-level object-o ii zlib1g 1:1.2.3.3.dfsg-5 compression library - runtime museekd recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#445840: Bug#421053: irssi: prepared NMU to fix some pending issues
On 13/10/07 at 17:07 +0200, Gerfried Fuchs wrote: Package: irssi Followup-For: Bug #445840 Hi! I've prepared an NMU which I plan to upload on monday, with the following changelog: #v+ irssi (0.8.12-0.1) unstable; urgency=low * NMU: New upstream release (closes: #445840, 421053) Hi Gerfried, Please don't close #445840 in your NMU. I still plan to orphan irssi in the very near future if the maintainer doesn't acknowledge your NMU and go through all the unanswered/untriaged bugs. If you fear that this bug will block irssi's testing transition, you can lower it to severity:important. Thank you for your work on irssi! -- | 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]
Processed: tagging 441164
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.8 tags 441164 + sid Bug#441164: gxmms2: fails to install There were no tags set. Tags added: sid 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]
Processed: tagging 440630
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.8 tags 440630 + lenny sid Bug#440630: bsdmainutils: hexdump is lost, needs a new upload with appropriate conflicts There were no tags set. Tags added: lenny, sid 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]
Processed: tagging 440623
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.8 tags 440623 + lenny sid Bug#440623: openoffice.org-officebean: uninstallable on testing (broken dependency) There were no tags set. Tags added: lenny, sid 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]
Processed: tagging 441165
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.8 tags 441165 + sid Bug#441165: nyello: fails to install There were no tags set. Tags added: sid 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#446276: webkit: FTBFS: TCSystemAlloc.cpp:89: error: expected constructor, destructor, or type conversion before '(' token
When looking at the Makefile, I see things like this in the CXXFLAGS and LIBS: ### or --detect-prefix This seems to come from running icu-config: $ icu-config --cppflags ### icu-config: Can't find /usr/lib32/libicuuc.so - ICU prefix is wrong. ### Try the --prefix= or --exec-prefix= options ### or --detect-prefix ### icu-config: Exitting. While it should return something like: -D_REENTRANT -I/usr/include This seems be a bug in libicu36-dev, so reassigning. libicu-dev 3.8 from experimental doesn't have this problem, even though /usr/lib32/libicuuc.so isn't present either. And there is no reason it should be. I recently modified the ICU packages to build 32-bit libraries, in addition to 64-bit libraries, on amd64 and a few other 64-bit platforms since this was needed by wine. Although the library isn't present on 3.8 d1 in experimental, it is present on the real 3.8 packages which I have had ready to upload for a month but have been holding off until the boost transition finishes. I don't know why webkit is trying to use the 32-bit libraries to begin with, but I guess it looks like icu-config --cppflags is at fault. I'll try to fix this. The problem is that I don't have access to an amd64 system. According to db.debian.org/machines.cgi, pergolesi is supposed to be one, but if I check there (from dchroot sid): pergolesi% dpkg-architecture DEB_BUILD_ARCH=i386 DEB_BUILD_ARCH_OS=linux DEB_BUILD_ARCH_CPU=i386 DEB_BUILD_GNU_CPU=i486 DEB_BUILD_GNU_SYSTEM=linux-gnu DEB_BUILD_GNU_TYPE=i486-linux-gnu DEB_HOST_ARCH=i386 DEB_HOST_ARCH_OS=linux DEB_HOST_ARCH_CPU=i386 DEB_HOST_GNU_CPU=i486 DEB_HOST_GNU_SYSTEM=linux-gnu DEB_HOST_GNU_TYPE=i486-linux-gnu Am I missing something? Anyway, if I can get access to an amd64 machine, I can try to fix this once and for all. -- Jay Berkenbilt [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#423202: topal: should this package be removed?
clone 423202 -1 reassign -1 wnpp severity -1 normal retitle -1 O: topal -- Links Pine and GnuPG together thanks On 10/05/07 at 16:48 +0200, Lucas Nussbaum wrote: While reviewing packages that were not included in Etch, your package came up as a possible candidate for removal from Debian, because: * 2 RC bugs opened for a long time * unmaintained upstream * according to #383367, needs upstream work. * low popcon (12 insts) Hi, Since the situation hasn't evolved, I am now orphaning this package. I still plan to request its removal in the near future, but this orphaning could allow someone to adopt the package if appropriate. Please reply to this bug report if you feel that this package shouldn't be removed. Please also reply if you think that this package _should_ be removed, as this will allow to make the process quicker. Thank you, -- | 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]
Processed (with 1 errors): Re: Bug#423242: estraier: should this package be removed?
Processing commands for [EMAIL PROTECTED]: clone 423242 -1 Bug#423242: estraier: should this package be removed? Bug 423242 cloned as bug 446514. reassign -1 wnpp Bug#446514: estraier: should this package be removed? Bug reassigned from package `estraier' to `wnpp'. severity -1 normal Bug#446514: estraier: should this package be removed? Severity set to `normal' from `serious' retitle -1 Unknown command or malformed arguments to command. 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#423324: marked as done (ivi: should this package be removed?)
Your message dated Sat, 13 Oct 2007 18:33:52 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#423324: ivi: should this package be removed? has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: ivi Version: 0.4.pre.20031121-4+b1 Severity: serious User: [EMAIL PROTECTED] Usertags: proposed-removal Hi, While reviewing packages that were not included in Etch, your package came up as a possible candidate for removal from Debian, because: * Several Release Critical Bugs * Orphaned * Low on popcon If you think that it should be orphaned instead of being removed from Debian, please reply to this bug and tell so. If you agree, sending the following commands to [EMAIL PROTECTED] should do it (after replacing nn with this bug's number): severity nn normal reassign nn ftp.debian.org retitle nn RM: packagename -- RoM; reasons thanks For more information, see http://wiki.debian.org/ftpmaster_Removals http://ftp-master.debian.org/removals.txt If you disagree and want to continue to maintain this package, please just close this bug, preferably in an upload also fixing the other issues. Thank you, - michael ---End Message--- ---BeginMessage--- Package was already removed. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | ---End Message---
Bug#423336: marked as done (libooc-xml: should this package be removed?)
Your message dated Sat, 13 Oct 2007 18:37:14 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#423335: libooc-x11: should this package be removed? has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: libooc-xml Version: 3.2.0-2 Severity: serious User: [EMAIL PROTECTED] Usertags: proposed-removal Hi, While reviewing packages that were not included in Etch, your package came up as a possible candidate for removal from Debian, because: * Orphaned * RC Buggy * libooc-vo is outdated and aswell rc buggy (#418508) * very low on popcon If you think that it should be orphaned instead of being removed from Debian, please reply to this bug and tell so. If you agree, sending the following commands to [EMAIL PROTECTED] should do it (after replacing nn with this bug's number): severity nn normal reassign nn ftp.debian.org retitle nn RM: packagename -- RoM; reasons thanks For more information, see http://wiki.debian.org/ftpmaster_Removals http://ftp-master.debian.org/removals.txt If you disagree and want to continue to maintain this package, please just close this bug, preferably in an upload also fixing the other issues. Thank you, - michael ---End Message--- ---BeginMessage--- Packages were removed, closing. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | ---End Message---
Processed: Re: Bug#423202: topal: should this package be removed?
Processing commands for [EMAIL PROTECTED]: clone 423202 -1 Bug#423202: topal: should this package be removed? Bug 423202 cloned as bug 446513. reassign -1 wnpp Bug#446513: topal: should this package be removed? Bug reassigned from package `topal' to `wnpp'. severity -1 normal Bug#446513: topal: should this package be removed? Severity set to `normal' from `serious' retitle -1 O: topal -- Links Pine and GnuPG together Bug#446513: topal: should this package be removed? Changed Bug title to `O: topal -- Links Pine and GnuPG together' from `topal: should this package be removed?'. 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#423335: marked as done (libooc-x11: should this package be removed?)
Your message dated Sat, 13 Oct 2007 18:37:14 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#423335: libooc-x11: should this package be removed? has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: libooc-x11 Version: 20020123-3 Severity: serious User: [EMAIL PROTECTED] Usertags: proposed-removal Hi, While reviewing packages that were not included in Etch, your package came up as a possible candidate for removal from Debian, because: * Orphaned * RC Buggy * libooc-vo is outdated and aswell rc buggy (#418508) * very low on popcon If you think that it should be orphaned instead of being removed from Debian, please reply to this bug and tell so. If you agree, sending the following commands to [EMAIL PROTECTED] should do it (after replacing nn with this bug's number): severity nn normal reassign nn ftp.debian.org retitle nn RM: packagename -- RoM; reasons thanks For more information, see http://wiki.debian.org/ftpmaster_Removals http://ftp-master.debian.org/removals.txt If you disagree and want to continue to maintain this package, please just close this bug, preferably in an upload also fixing the other issues. Thank you, - michael ---End Message--- ---BeginMessage--- Packages were removed, closing. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | ---End Message---
Bug#423242: estraier: should this package be removed?
clone 423242 -1 reassign -1 wnpp severity -1 normal retitle -1 thanks On 10/05/07 at 21:57 +0200, Lucas Nussbaum wrote: While reviewing packages that were not included in Etch, your package came up as a possible candidate for removal from Debian, because: * RC buggy for 170 days without comment from the maintainer * superseded by hyperestraier according to #399138 Hi, Since the situation hasn't evolved, I am now orphaning this package. I still plan to request its removal in the near future, but this orphaning could allow someone to adopt the package if appropriate. Please reply to this bug report if you feel that this package shouldn't be removed. Please also reply if you think that this package _should_ be removed, as this will allow to make the process quicker. Thank you, -- | 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#446462: /usr/bin/vim is left broken when alternative is manual and points to vim-full
On Sat, Oct 13, 2007 at 11:43:32AM -0400, James Vega wrote: *sigh* I don't know what made piuparts succeed before but it is definitely exhibiting the reported behavior now. Looks like it's time for another update-alternatives hack. Actually, it was a typo on my part in the preinst file. I'm preparing a package now and will get it uploaded today. James -- GPG Key: 1024D/61326D40 2003-09-02 James Vega [EMAIL PROTECTED] signature.asc Description: Digital signature
Bug#446515: Subject: alien-arena: game fails to start after single player game chosen
Package: alien-arena Version: 6.05-4.1 Severity: grave Justification: renders package unusable *** Please type your report below this line *** The game gives the opening menu, allows you to change settings, allows you to chose to begin a single player game and then chokes and dies. A check of Xorg log files shows no errors that might be the culprit. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: powerpc (ppc) Kernel: Linux 2.6.22-2-powerpc Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Processed: your mail
Processing commands for [EMAIL PROTECTED]: tag 413925 pending Bug#413925: gpsprof: gpsd-clients should depend on python-support There were no tags set. Tags added: pending tag 295375 pending Bug#295375: gpsd: Please split libgps into separate packages Tags were: etch-ignore Tags added: pending tag 415519 pending Bug#415519: [INTL:nl] Dutch po-debconf translation Tags were: l10n patch Tags added: pending tag 426172 pending Bug#426172: gpsd: [INTL:es] Spanish translation for debconf template Tags were: l10n patch Tags added: pending tag 412507 pending Bug#412507: gpsd: [INTL:ja] initial Japanese debconf translation Tags were: l10n patch Tags added: pending 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#436249: package status
Hi, I really don't want to piss you off but see this fixed. What is the current status. It should not need 3 weeks to prepare a new upload should it? If some sponsoring is needed feel free to ping me. Kind regards Nico -- Nico Golde - http://ngolde.de - [EMAIL PROTECTED] - GPG: 0x73647CFF For security reasons, all text in this mail is double-rot13 encrypted. pgp7ggsOEqBZY.pgp Description: PGP signature
Bug#423202: topal: should this package be removed?
Hi, On Sat, 13 Oct 2007, Lucas Nussbaum wrote: On 10/05/07 at 16:48 +0200, Lucas Nussbaum wrote: While reviewing packages that were not included in Etch, your package came up as a possible candidate for removal from Debian, because: * 2 RC bugs opened for a long time * unmaintained upstream * according to #383367, needs upstream work. * low popcon (12 insts) Since the situation hasn't evolved, I am now orphaning this package. I still plan to request its removal in the near future, but this orphaning could allow someone to adopt the package if appropriate. [...] Upsteam isn't quite dead because it's me -- but I have, as is very clear, had too little time to carry out the upstream work. So I'm indifferent on the matter of removing the Debian package. It can always be added again if I manage to do that work. (And when I do have some spare time, there are other Debian packages higher up the priority list.) Cheers, Phil. -- Phil Brooke PGP/GnuPG key: 1024D/50973B91 2000-12-19 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 446460 is serious
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.9 severity 446460 serious Bug#446460: geotoad: Crashes with undefined method message Severity set to `serious' from `normal' 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#445779: gdb trace
Package: rdesktop
Version: 1.5.0-2+cvs20071006
Followup-For: Bug #445779
I apt-get-built from source and set gdb on a non-stripped binary:
running with DE_AT locale, crash soon:
Program received signal SIGSEGV, Segmentation fault.
free_key_translation (ptr=0x1e00) at xkeymap.c:69
69 next = ptr-next;
(gdb) l
64 {
65 key_translation *next;
66
67 while (ptr)
68 {
69 next = ptr-next;
70 xfree(ptr);
71 ptr = next;
72 }
73 }
(gdb) bt
#0 free_key_translation (ptr=0x1e00) at xkeymap.c:69
#1 0x08059d62 in add_to_keymap (keyname=value optimized out, scancode=value
optimized out, modifiers=value optimized out, mapname=0x8076540 en-us) at
xkeymap.c:95
#2 0x0805a392 in xkeymap_read (mapname=0x8076540 en-us) at xkeymap.c:424
#3 0x0805a500 in xkeymap_init () at xkeymap.c:450
#4 0x080587a9 in ui_init () at xwin.c:1651
#5 0x0804dd21 in main (argc=1, argv=0xbfe5b884) at rdesktop.c:911
running with C locale, hit enter:
Program received signal SIGSEGV, Segmentation fault.
0x08058cbd in get_key_state (state=16, keysym=65513) at xwin.c:1308
1308offset = g_mod_map-max_keypermod * modifierpos;
(gdb) l
1303if (keycode == NoSymbol)
1304return False;
1305
1306for (modifierpos = 0; modifierpos 8; modifierpos++)
1307{
1308offset = g_mod_map-max_keypermod * modifierpos;
1309
1310for (key = 0; key g_mod_map-max_keypermod; key++)
1311{
1312if (g_mod_map-modifiermap[offset + key] ==
keycode)
(gdb) bt
#0 0x08058cbd in get_key_state (state=16, keysym=65513) at xwin.c:1308
#1 0x08059b35 in handle_special_keys (keysym=65293, state=16,
ev_time=1192297181, pressed=1) at xkeymap.c:513
#2 0x080577a5 in ui_select (rdp_socket=6) at xwin.c:2062
#3 0x0805f77f in tcp_recv (s=0x80bb1e0, length=4) at tcp.c:175
#4 0x0805fac8 in iso_recv_msg (code=0x143cf7b8 Address 0x143cf7b8 out of
bounds, rdpver=0x40 Address 0x40 out of bounds) at iso.c:81
#5 0x0805fc18 in iso_recv (rdpver=0xbff2f4bf ) at iso.c:156
#6 0x080601d3 in mcs_recv (channel=0xbff2f48a, rdpver=0xbff2f4bf ) at
mcs.c:350
#7 0x08060c4b in sec_recv (rdpver=0xbff2f4bf ) at secure.c:760
#8 0x08062552 in rdp_recv (type=0xbff344eb ) at rdp.c:89
#9 0x08062b48 in rdp_loop (deactivated=0xbff34884, ext_disc_reason=0xbff34880)
at rdp.c:1380
#10 0x0806373c in rdp_main_loop (deactivated=0xbff34884,
ext_disc_reason=0xbff34880) at rdp.c:1365
#11 0x0804e1dd in main (argc=1, argv=0xbff34934) at rdesktop.c:954
thank you.
peter
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.23 (PREEMPT)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages rdesktop depends on:
ii libc6 2.6.1-5GNU C Library: Shared libraries
ii libssl0.9.8 0.9.8e-9 SSL shared libraries
ii libx11-6 2:1.0.3-7 X11 client-side library
rdesktop recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#446276: webkit: FTBFS: TCSystemAlloc.cpp:89: error: expected constructor, destructor, or type conversion before '(' token
On Sat, Oct 13, 2007 at 12:30:36PM -0400, Jay Berkenbilt wrote: When looking at the Makefile, I see things like this in the CXXFLAGS and LIBS: ### or --detect-prefix This seems to come from running icu-config: $ icu-config --cppflags ### icu-config: Can't find /usr/lib32/libicuuc.so - ICU prefix is wrong. ### Try the --prefix= or --exec-prefix= options ### or --detect-prefix ### icu-config: Exitting. While it should return something like: -D_REENTRANT -I/usr/include This seems be a bug in libicu36-dev, so reassigning. libicu-dev 3.8 from experimental doesn't have this problem, even though /usr/lib32/libicuuc.so isn't present either. And there is no reason it should be. I recently modified the ICU packages to build 32-bit libraries, in addition to 64-bit libraries, on amd64 and a few other 64-bit platforms since this was needed by wine. Although the library isn't present on 3.8 d1 in experimental, it is present on the real 3.8 packages which I have had ready to upload for a month but have been holding off until the boost transition finishes. I don't know why webkit is trying to use the 32-bit libraries to begin It's not, it just calls icu-config which seems to look for it. with, but I guess it looks like icu-config --cppflags is at fault. I'll try to fix this. The problem is that I don't have access to an amd64 system. According to db.debian.org/machines.cgi, pergolesi is supposed to be one, but if I check there (from dchroot sid): pergolesi% dpkg-architecture DEB_BUILD_ARCH=i386 DEB_BUILD_ARCH_OS=linux DEB_BUILD_ARCH_CPU=i386 DEB_BUILD_GNU_CPU=i486 DEB_BUILD_GNU_SYSTEM=linux-gnu DEB_BUILD_GNU_TYPE=i486-linux-gnu DEB_HOST_ARCH=i386 DEB_HOST_ARCH_OS=linux DEB_HOST_ARCH_CPU=i386 DEB_HOST_GNU_CPU=i486 DEB_HOST_GNU_SYSTEM=linux-gnu DEB_HOST_GNU_TYPE=i486-linux-gnu Am I missing something? Anyway, if I can get access to an amd64 machine, I can try to fix this once and for all. The chroot is called sid_amd64. Is seems to be last updates in May. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 441275
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.8 tags 441275 + lenny sid Bug#441275: ivtv-source: ivtv-fb and the X driver ivtvdev don't work any more There were no tags set. Tags added: lenny, sid 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#446276: installing ICU's build dependencies on pergolesi (for RC bug)
I'm trying to work through an amd64-only problem with the ICU packages. In particular, I need to be able to build the 32-bit libraries. In order for this to be possible, can someone install the build dependencies for ICU 3.6-6 in the sid_amd64_pure chroot on pergolesi? Here is the Build-Depends lines. Thanks. Build-Depends: cdbs, debhelper (= 4.1.0), doxygen, gcc-multilib [amd64 kfreebsd-amd64 ppc64] | gcc-4.1 ( 4.1.2) [amd64 kfreebsd-amd64 ppc64], g++-multilib [amd64 kfreebsd-amd64 ppc64] | g++-4.1 ( 4.1.2) [amd64 kfreebsd-amd64 ppc64], libc6-dev-i386 [amd64], libc0.1-dev-i386 [kfreebsd-amd64], libc6-dev-powerpc [ppc64] In particular, doxygen, gcc-multilib, g++-multilib, and libc6-dev-i386 are missing. I can work around not having doxygen, but I can't work around not having the others. Thanks. -- Jay Berkenbilt [EMAIL PROTECTED] pgpbZ4cXLPqqd.pgp Description: PGP signature
Bug#446462: marked as done (/usr/bin/vim is left broken when alternative is manual and points to vim-full)
Your message dated Sat, 13 Oct 2007 18:02:05 + with message-id [EMAIL PROTECTED] and subject line Bug#446462: fixed in vim 1:7.1-138+1 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: vim-full Version: 1:7.1-135+1 Severity: important $ LANG=C update-alternatives --display vim vim - status is manual. link currently points to /usr/bin/vim.full /usr/bin/vim.basic - priority 30 /usr/bin/vim.gnome - priority 60 Current `best' version is /usr/bin/vim.gnome. $ LANG=C ls -al /usr/bin/vim.full ls: /usr/bin/vim.full: No such file or directory $ LANG=C ls -al /usr/bin/vim lrwxrwxrwx 1 root root 21 Jan 31 2006 /usr/bin/vim - /etc/alternatives/vim $ LANG=C ls -al /etc/alternatives/vim lrwxrwxrwx 1 root root 17 Aug 11 12:09 /etc/alternatives/vim - /usr/bin/vim.full So when I type vim, it doesn't work... this is a problem that could be solved at the update-alternatives level (see #87677, #311288, #392440) but in this particular case and until update-alternatives is going to be fixed, It could make sense to detect this corner-case and update with the alternatives to point to vim.gnome since that's what you suggest as replacement. Feel free to give your input in the update-alternatives bug report mentionned above explaing in more details how you managed to create this situation. :-) And I have similar problem with various other alternatives, although I don't remember having personalized them: $ LANG=C update-alternatives --display gvim gvim - status is manual. link currently points to /usr/bin/vim.full /usr/bin/vim.gnome - priority 60 Current `best' version is /usr/bin/vim.gnome. $ LANG=C update-alternatives --display gview gview - status is manual. link currently points to /usr/bin/gvim /usr/bin/vim.gnome - priority 60 Current `best' version is /usr/bin/vim.gnome. $ LANG=C update-alternatives --display gvimdiff gvimdiff - status is manual. link currently points to /usr/bin/gvim /usr/bin/vim.gnome - priority 60 Current `best' version is /usr/bin/vim.gnome. etc. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.22-2-686 (SMP w/1 CPU core) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages vim-full depends on: ii vim-gnome1:7.1-135+1 Vi IMproved - enhanced vi editor - vim-full recommends no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: vim Source-Version: 1:7.1-138+1 We believe that the bug you reported is fixed in the latest version of vim, which is due to be installed in the Debian FTP archive: vim-common_7.1-138+1_i386.deb to pool/main/v/vim/vim-common_7.1-138+1_i386.deb vim-doc_7.1-138+1_all.deb to pool/main/v/vim/vim-doc_7.1-138+1_all.deb vim-full_7.1-138+1_all.deb to pool/main/v/vim/vim-full_7.1-138+1_all.deb vim-gnome_7.1-138+1_i386.deb to pool/main/v/vim/vim-gnome_7.1-138+1_i386.deb vim-gtk_7.1-138+1_i386.deb to pool/main/v/vim/vim-gtk_7.1-138+1_i386.deb vim-gui-common_7.1-138+1_all.deb to pool/main/v/vim/vim-gui-common_7.1-138+1_all.deb vim-lesstif_7.1-138+1_i386.deb to pool/main/v/vim/vim-lesstif_7.1-138+1_i386.deb vim-nox_7.1-138+1_i386.deb to pool/main/v/vim/vim-nox_7.1-138+1_i386.deb vim-perl_7.1-138+1_all.deb to pool/main/v/vim/vim-perl_7.1-138+1_all.deb vim-python_7.1-138+1_all.deb to pool/main/v/vim/vim-python_7.1-138+1_all.deb vim-ruby_7.1-138+1_all.deb to pool/main/v/vim/vim-ruby_7.1-138+1_all.deb vim-runtime_7.1-138+1_all.deb to pool/main/v/vim/vim-runtime_7.1-138+1_all.deb vim-tcl_7.1-138+1_all.deb to pool/main/v/vim/vim-tcl_7.1-138+1_all.deb vim-tiny_7.1-138+1_i386.deb to pool/main/v/vim/vim-tiny_7.1-138+1_i386.deb vim_7.1-138+1.diff.gz to pool/main/v/vim/vim_7.1-138+1.diff.gz vim_7.1-138+1.dsc to pool/main/v/vim/vim_7.1-138+1.dsc vim_7.1-138+1_i386.deb to pool/main/v/vim/vim_7.1-138+1_i386.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. James Vega [EMAIL PROTECTED] (supplier of updated vim package) (This message was generated automatically at their request; if you believe that there is a problem with it
