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 e

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 ther

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 al

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 att

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#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

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 fr

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

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. P

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) Fil

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

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

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 assi

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 we

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 remo

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

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-20

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.ma

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, si

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 you

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

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 4

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. T

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 progr

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 c

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 admi

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'. > retitl

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

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 4

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 a

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, >

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]

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, > >

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

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

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#3

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, > > Whil

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 th

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 4233

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

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, th

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 c

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

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

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: > >

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

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

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'. > retitl

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-

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'. > retitl

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 cas

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

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

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/

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 regu

Bug#423317: ppscsi: should this package be orphaned?

On 11/05/07 at 22:35 +0200, Eduard Bloch wrote: > #include > * 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 inclu

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'. > retitl

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: scs

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

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 orpha

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 4233

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 i

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.de

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 mainta

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 bei

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 upstr

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

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?

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

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

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

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.

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, sto

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

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.

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-pr

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, becau

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#

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

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 th

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: t

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 th

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 c

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'

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 Xo

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: pendin

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 se

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

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

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 fau

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/lib3

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 proces

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

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 yo

Bug#446524: linhdd: Execute error: /usr/bin/linHDD line 411

Package: linhdd Version: 0.4-2 Severity: grave Justification: renders package unusable When I try to run linHDD it gives this error: Traceback (most recent call last): File "/usr/bin/linHDD", line 559, in ? main() File "/usr/bin/linHDD", line 554, in main DriveWin() File "/usr/bin/l

Bug#446505: marked as done (wesnoth: not meant for unstable)

Your message dated Sat, 13 Oct 2007 18:17:14 + with message-id <[EMAIL PROTECTED]> and subject line Bug#446505: fixed in wesnoth 1:1.2.7-2 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

Bug#423322: Maintainership of SWI-Prolog

Lucas Nussbaum wrote: > > I will be very much grateful for its up-to-date and complete version. > > Chris, could you give us an update on that? I have half-packaged the latest upstream, just a few of the extra packages (like -xpce, etc.) are now missing. In a few days so I can also try it on amd

Processed: (pas de sujet)

Processing commands for [EMAIL PROTECTED]: > severity 446508 normal Bug#446508: museekd: Hangs on start Severity set to `normal' from `grave' > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bug

  1   2   >