Bug#413933: marked as done (zorp: policy.boot cannot be found)

Your message dated Mon, 19 Mar 2007 07:32:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#413933: fixed in zorp 3.0.8-0.3 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#413216: gcc-avr includes GFL docs with cover texts and invariant sections

Hi Håkan, Can you give an ETA for fixing this bug? Per the posted release schedule, if a maintainer fix isn't uploaded in the next week I'll have to either NMU the package or remove it (and reverse-deps) from etch (probably NMU, now that Matthias has provided enough information that it should be

Processed: severity of 415398 is important

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.27 > severity 415398 important Bug#415398: apt-cacher causes corruption when used with Ubuntu and Debian archives Severity set to `important' from `grave' > End of message, stopping proc

Bug#413933: zorp: policy.boot cannot be found

Hi Attila, I've prepared an NMU for this bug. The NMU patch, with the autogenerated parts stripped out, is attached. Unfortunately the autogenerated parts are quite large because the package lacked a proper clean target, so this NMU includes a patch to strip those out in the interest of future c

Bug#415398: apt-cacher causes corruption when used with Ubuntu and Debian archives

Package: apt-cacher Version: 1.5.3 Severity: grave In many instances, the Debian and Ubuntu archives have different packages with the same name. In the apt-cacher cache, these pairs of packages collide with each other, resulting in corruption of one of them: $ wget http://archive.ubuntu.com/ubu

Bug#413216: gcc-avr includes GFL docs with cover texts and invariant sections

> > see debian/rules.unpack in the gcc-4.1 source for a list, plus the > > INSTALL directory needs to be removed. > > I've tried to provide a patch that fixes this. I took the list of files > from the gcc-4.1 package and wrote new Makefile snippet to "clean" the > included tarballs. The patch is

Processed: tagging 415385, tagging 415387

Processing commands for [EMAIL PROTECTED]: > tags 415385 + security Bug#415385: xulrunner security bugs There were no tags set. Tags added: security > tags 415387 + security upstream fixed-upstream Bug#415387: security issues in icedove There were no tags set. Tags added: security, upstream, fixe

Bug#415393: uim: is not upgradable from uim 1.2

Package: uim Version: 1:1.4.1-1 Severity: grave Tags: experimental It seems #385637 comes again. ... Unpacking replacement uim-xim ... Preparing to replace uim-utils 1:1.2.1-9 (using .../uim-utils_1%3a1.4.1-1_amd64.deb) ... Unpacking replacement uim-utils ... Preparing to replace uim-gtk2.0 1:1

Bug#415385: xulrunner security bugs

On Mon, Mar 19, 2007 at 01:43:36AM +0100, Alexander Sack wrote: > Package: icedove > Version: 1.8.0.9-1 > Severity: critical > > xulrunner has security issues which are fixed in 1.8.0.10-3 > xulrunner (1.8.0.10-1) unstable; urgency=low [ Mike Hommey ] * New upstream release (taken from

Bug#413968: [php-maint] xmlrpc-epi turns out to be libxmlrpc in php

OK, folks. You have the wrong bug report. #413968 is a bug to clamsmtp, and I REALLY don't think PHP is involved here. Please find the correct bug # and start sending emails there. Thank you, Chad (not a PHP guy) -- Chad Walstrom <[EMAIL PROTECTED]> http://www.wookimus.net/

Bug#415387: security issues in icedove

On Sun, Mar 18, 2007 at 06:52:44PM -0700, Steve Langasek wrote: > On Mon, Mar 19, 2007 at 01:42:28AM +0100, Alexander Sack wrote: > > Package: icedove > > Version: 1.5.0.9.dfsg1-1 > > Severity: critical > > > icedove 1.5.0.9 has security issues which got fixed in 1.5.0.10 > > What security issues

Bug#413397: marked as done (ifcico: purging the package fails (update-inetd unavailable))

Your message dated Mon, 19 Mar 2007 02:17:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#413397: fixed in ifmail 2.14tx8.10-19.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

Bug#413397: ifcico: purging the package fails (update-inetd unavailable)

On Sun, Mar 18, 2007 at 06:21:28PM -0700, Steve Langasek wrote: > tags 413397 patch > thanks > Ok, the attached patch has the following properties: Well, except it also has the property of a basic shell syntax error in the postrm. ;) Here's the fixed patch. -- Steve Langasek

Bug#415386: marked as done (security issues in testing)

Your message dated Sun, 18 Mar 2007 18:50:49 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#415386: security issues in testing 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#415387: security issues in icedove

On Mon, Mar 19, 2007 at 01:42:28AM +0100, Alexander Sack wrote: > Package: icedove > Version: 1.5.0.9.dfsg1-1 > Severity: critical > icedove 1.5.0.9 has security issues which got fixed in 1.5.0.10 What security issues? -- Steve Langasek Give me a lever long enough and a Free O

Bug#413397: ifcico: purging the package fails (update-inetd unavailable)

tags 413397 patch thanks Hi Marco, Ok, the attached patch has the following properties: - local admin changes are preserved by only removing the entry on package purge - we assume (with reason) that if update-inetd is not present, we're no longer responsible for removing any entries from ine

Processed: Re: ifcico: purging the package fails (update-inetd unavailable)

Processing commands for [EMAIL PROTECTED]: > tags 413397 patch Bug#413397: ifcico: purging the package fails (update-inetd unavailable) Tags were: pending Tags added: patch > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (adm

Bug#415385: xulrunner security bugs

Package: icedove Version: 1.8.0.9-1 Severity: critical xulrunner has security issues which are fixed in 1.8.0.10-3 - Alexander -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#415387: security issues in icedove

Package: icedove Version: 1.5.0.9.dfsg1-1 Severity: critical icedove 1.5.0.9 has security issues which got fixed in 1.5.0.10 - Alexander -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#415386: security issues in testing

Package: iceape Version: 1.0.7-3 Severity: critical Security issues got fixed in 1.0.8 - Alexander -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#393691: Is this bug (ikvm FTBFS on amd64) still relevant?

Brian M. Carlson wrote: > Is this bug still relevant? ikvm has successfully built on amd64 since > this bug was filed, and it works on my amd64 machine. ISTR that some > bug was present in Mono a few months ago, and that might have affected > the build environment. I've never had it working, and

Bug#414790: marked as done (CVE-2007-1420: Single Row Subselect DoS)

Your message dated Sun, 18 Mar 2007 21:32:07 + with message-id <[EMAIL PROTECTED]> and subject line Bug#414790: fixed in mysql-dfsg-5.0 5.0.32-7etch1 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#415026: marked as done (mysql-dfsg-5.1_5.1.16beta-1(sparc/experimental): FTBFS: misparses /proc/cpuinfo)

Your message dated Sun, 18 Mar 2007 21:02:07 + with message-id <[EMAIL PROTECTED]> and subject line Bug#415026: fixed in mysql-dfsg-5.1 5.1.16beta-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

Bug#415367: tex-guy - writes outside of the build directory

Package: tex-guy Version: 1.2.4-7 Severity: serious The tex-guy build writes outside of the build directory. | $ grep ln configure.in | head -n 1 | (cd .. && ln -s tex-guy-1.2.4 tex-guy) Bastian -- A father doesn't destroy his children. -- Lt. Carolyn Palamas, "Who Mourns for A

Bug#415026: marked as done (mysql-dfsg-5.1_5.1.16beta-1(sparc/experimental): FTBFS: misparses /proc/cpuinfo)

Your message dated Sun, 18 Mar 2007 20:32:09 + with message-id <[EMAIL PROTECTED]> and subject line Bug#415026: fixed in mysql-dfsg-5.0 5.0.32-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

Bug#382764: marked as done (ogre-contrib: FTBFS (gcc-4.1): extra qualification 'Ogre::Image::' on member 'loadDynamicImage')

Your message dated Sun, 18 Mar 2007 20:32:10 + with message-id <[EMAIL PROTECTED]> and subject line Bug#382764: fixed in ogre-contrib 1.0.6-1.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

Bug#415362: Security fix included in GNU file 4.20

Package: file Version: 4.19-1 Severity: grave Tags: security X-Debbugs-Cc: [EMAIL PROTECTED] According to the changelog included in the GNU file 4.20 tarball at , this version includes a security fix: 2007-02-08 17:30 Christos Zoulas <[EMAIL PROTECTED]>

Bug#415348: marked as done (uqm: file conflict with uqm-content)

Your message dated Sun, 18 Mar 2007 19:47:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#415348: fixed in uqm 0.6.2.dfsg-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 y

Processed: severity of 415343 is important

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.27 > severity 415343 important Bug#415343: installation-report: GRUB Error 15 at first boot. Severity set to `important' from `grave' > End of message, stopping processing here. Please c

Processed: severity of 409285 is important

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.27 > severity 409285 important Bug#409285: lilo: inaccessible inaccessible Severity set to `important' from `grave' > End of message, stopping processing here. Please contact me if you n

Bug#404891: marked as done (Fans unreliable under load, permanent memory leak)

Your message dated Sun, 18 Mar 2007 19:50:57 +0100 with message-id <[EMAIL PROTECTED]> and subject line Patch committed to CVS, bug fixed 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

Bug#415348: uqm: file conflict with uqm-content

Package: uqm Version: 0.6.2.dfsg-1 Severity: serious Hello Joey, There is an error when upgrading the package from etch to sid, it should Replaces uqm-content: Preparing to replace uqm 0.5.0-3 (using .../tmp/uqm_0.6.2.dfsg-1_amd64.deb) ... Unpacking replacement uqm ... dpkg: error processing /tm

Processed: Apparently upstream for libmp3-info-perl flattened its namespace?

Processing commands for [EMAIL PROTECTED]: > tag 397069 + patch Bug#397069: mp3roaster: Missing dependency on nonexistant package There were no tags set. Tags added: patch > severity 397069 grave Bug#397069: mp3roaster: Missing dependency on nonexistant package Severity set to `grave' from `norma

Bug#415345: extcalc_0.7.0-1(hppa/unstable): FTBFS: compile errors

Package: extcalc Version: 0.7.0-1 Severity: serious There was an error while trying to autobuild your package: > Automatic build of extcalc_0.7.0-1 on bld-3 by sbuild/hppa 98 > Build started at 20070318-0947 [...] > ** Using build dependencies supplied by package: > Build-Depen

Bug#410403: Oops.

Oops. Disregard that last message. I meant to send it to a different bug, from a different package, that I patched. -Brandon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#414075: marked as done (CVE-2007-1246: DMO decoder heap allocation overflow)

Your message dated Sun, 18 Mar 2007 15:02:12 + with message-id <[EMAIL PROTECTED]> and subject line Bug#414075: fixed in mplayer 1.0~rc1-12etch 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

Bug#413476: marked as done (concalc - FTBFS: error: 'powl' was not declared in this scope)

Your message dated Sun, 18 Mar 2007 15:02:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#413476: fixed in concalc 0.7.0-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#411727: marked as done ("When installed in d-i, uswsusp creates broken uswsusp.conf with devfs style dev-nodes")

Your message dated Sun, 18 Mar 2007 14:47:34 + with message-id <[EMAIL PROTECTED]> and subject line Bug#411727: fixed in uswsusp 0.3~cvs20060928-7 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

Processed: severity of 415318 is important

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.1 > severity 415318 important Bug#415318: mldonkey-server: Cannot start after a power failure Severity set to `important' from `serious' > End of message, stopping processing here. Plea

Bug#415318: marked as done (mldonkey-server: Cannot start after a power failure)

Your message dated Sun, 18 Mar 2007 14:58:18 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#415318: mldonkey-server: Cannot start after a power failure 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#415318: mldonkey-server: Cannot start after a power failure

"spiral voice" <[EMAIL PROTECTED]> writes: > Hi, > > MLdonkey core supports a parameter > > -pid : directory for pid file > > where to place pid files. > > Support for this option was added in mldonkey-server-2.8.1-3: > > * Using -pid option of mlnet to create the pidfile, closes: #341615. > >

Processed (with 1 errors): Debian-caused problem

Processing commands for [EMAIL PROTECTED]: > severity 409285 grave Bug#409285: lilo: inaccessible inaccessible Severity set to `grave' from `normal' > title 409285 lilo: inaccessible (patched to death) Unknown command or malformed arguments to command. > thanks Stopping processing here. Please

Processed: Manage bug 414885

Processing commands for [EMAIL PROTECTED]: > retitle 414885 postgresql support is not ready for etch release Bug#414885: Bug 6634: Can't upload "big" images with Postgresql Changed Bug title to postgresql support is not ready for etch release from Bug 6634: Can't upload "big" images with Postgres

Bug#415318: mldonkey-server: Cannot start after a power failure

Hi, MLdonkey core supports a parameter -pid : directory for pid file where to place pid files. Support for this option was added in mldonkey-server-2.8.1-3: * Using -pid option of mlnet to create the pidfile, closes: #341615. Unstable has already version 2.8.3-1 of mldonkey-server, due to

Bug#411727: uswsusp: resume_device set to devfs-like name (under D-I), always prevents hibernation

On Sat, Mar 17, 2007 at 12:41:44AM +0100, Tim Dijkstra wrote: > For reference, an updated package can be found at : > http://www.famdijkstra.org/~tdykstra/debian/uswsusp/uswsusp_0.3~cvs20060928-7_i386.changes Uploaded, but dak is currently stuck so there's no telling when it will reach the archiv

Bug#382764: NMU for ogre-contrib

I'm doing an NMU to get this RC bug out to delayed+1 I'm using the patch by Andreas (Thanks Andreas). -- GNU/Linux registered user #224950 Proud Egyptian GNU/Linux User Group Member. Life powered by Debian, Homepage: www.foolab.org -- Don't send me any attachment in Micro$oft (.DOC, .PPT) format

Bug#415233: gpgme1.0: FTBFS: Can't find GNU Pth

On Sun, Mar 18, 2007 at 12:10:25PM +0100, Kurt Roeckx wrote: > On Sun, Mar 18, 2007 at 01:23:43AM +0100, Jose Carlos Garcia Sogo wrote: > > > > Hi, > > > > I don't know why this didn't happen in my i386 pbuilder also. Perhaps > > there is some other package dependeing on libpth-dev in i386 bu

Bug#415317: marked as done (bluez-utils: Should depend on dbus)

Your message dated Sun, 18 Mar 2007 12:30:20 +0100 with message-id <[EMAIL PROTECTED]> and subject line [Pkg-bluetooth-maintainers] Bug#415317: bluez-utils: Should depend on dbus has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt wit

Processed: Re: Bug#415315: gnome-applets: does not include source for gweather/Locations.xml

Processing commands for [EMAIL PROTECTED]: > severity 415315 important Bug#415315: gnome-applets: does not include source for gweather/Locations.xml Severity set to `important' from `serious' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system

Bug#415315: gnome-applets: does not include source for gweather/Locations.xml

severity 415315 important thanks On Sun, Mar 18, 2007 at 10:58:20AM +0100, Piotr Engelking wrote: > Package: gnome-applets > Version: 2.14.3-4 > Severity: serious > Justification: Policy 2.2.1 > The gweather/Locations.xml file seems to be autogenerated from > gweather/Locations.xml.in, which isn'

Bug#415233: gpgme1.0: FTBFS: Can't find GNU Pth

On Sun, Mar 18, 2007 at 01:23:43AM +0100, Jose Carlos Garcia Sogo wrote: > > Hi, > > I don't know why this didn't happen in my i386 pbuilder also. Perhaps > there is some other package dependeing on libpth-dev in i386 but not in > other arches This seems to be a difference in the configure

Bug#415318: mldonkey-server: Cannot start after a power failure

Package: mldonkey-server Version: 2.8.1-2etch1 Severity: serious If the power supply fails while the daemon was running, it cannot be started after boot-up. Starting MLDonkey: mlnet file[s] should no exist: /var/lib/mldonkey/mlnet.pid -- delete it first First, it's against the Debian policy to

Processed: tagging bugs that are closed by packages in NEW as pending

Processing commands for [EMAIL PROTECTED]: > # the following bugs are closed by packages in NEW > # > tags 381506 pending Bug#381506: More elegant fix for 368991 (the banshee crash) There were no tags set. Tags added: pending > tags 400163 pending Bug#400163: liboil: [wishlist] liboil0.3-dbg Ther

Bug#415317: bluez-utils: Should depend on dbus

Package: bluez-utils Version: 3.1-3.1 Severity: serious Without a locally installed dbus daemon, hcid doesn't start. Therefore, bluez-utils must depend on dbus. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500,

Processed: Re: Bug#415316: yaz: FTBFS: /usr/bin/ld: cannot find -lssl

Processing commands for [EMAIL PROTECTED]: > severity 415316 important Bug#415316: yaz: FTBFS: /usr/bin/ld: cannot find -lssl Severity set to `important' from `serious' > tags 415316 moreinfo unreproducible Bug#415316: yaz: FTBFS: /usr/bin/ld: cannot find -lssl There were no tags set. Tags added:

Bug#415316: yaz: FTBFS: /usr/bin/ld: cannot find -lssl

severity 415316 important tags 415316 moreinfo unreproducible thanks On Sun, Mar 18, 2007 at 11:22:59AM +0100, Julien Danjou wrote: > Package: yaz > Version: 2.1.18-2 > Severity: serious > There was a problem while autobuilding your package: > > Automatic build of yaz_2.1.18-2 on nasya by sbuild/

Bug#415217: syck: FTBFS: pyext.c:9:20: error: Python.h: No such file or directory

severity 415217 important thanks On Sat, Mar 17, 2007 at 09:25:54AM +0100, Julien Danjou wrote: > Package: syck > Version: 0.55-3.3 > Severity: serious > There was a problem while autobuilding your package: > > copying ypath.py -> build/lib.linux-sparc64-2.4 > > copying ydump.py -> build/lib.linu

Processed: Re: Bug#415217: syck: FTBFS: pyext.c:9:20: error: Python.h: No such file or directory

Processing commands for [EMAIL PROTECTED]: > severity 415217 important Bug#415217: syck: FTBFS: pyext.c:9:20: error: Python.h: No such file or directory Severity set to `important' from `serious' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking s

Bug#415316: yaz: FTBFS: /usr/bin/ld: cannot find -lssl

Package: yaz Version: 2.1.18-2 Severity: serious Hello, There was a problem while autobuilding your package: > Automatic build of yaz_2.1.18-2 on nasya by sbuild/sparc 0.52 > Build started at 20070317-1914 > ** ... > spa

Bug#415315: gnome-applets: does not include source for gweather/Locations.xml

Package: gnome-applets Version: 2.14.3-4 Severity: serious Justification: Policy 2.2.1 The gweather/Locations.xml file seems to be autogenerated from gweather/Locations.xml.in, which isn't included in the Debian source package. Please include it. (While this is a violation of section 1 of the et

Processed: Re: ifcico: purging the package fails (update-inetd unavailable)

Processing commands for [EMAIL PROTECTED]: > tags 413397 -patch Bug#413397: ifcico: purging the package fails (update-inetd unavailable) Tags were: pending patch Tags removed: patch > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administr

Bug#413397: ifcico: purging the package fails (update-inetd unavailable)

tags 413397 -patch thanks The suggested patch is flawed. There's no reason to limit update-inetd's actions to cases when the postinst is called with 'configure'; the other options for postinst are abort-upgrade, abort-remove, and abort-deconfigure, and if the removal commands are going to be move

Bug#413968: [php-maint] xmlrpc-epi turns out to be libxmlrpc in php

On Sun, Mar 11, 2007 at 01:56:42PM +0100, sean finney wrote: > On Sun, 2007-03-11 at 17:44 +1100, Paul TBBle Hampson wrote: >> I'm suggesting either. I'm happy to maintain the package seperately, but >> I intend to go through the differences between the versions and confirm >> that they are compati