Bug#477751: dh_installcatalogs: Don't readd catalog on every upgrade to the super catalog

reassign 477751 debhelper retitle 477751 dh_installcatalogs: Don't readd catalog on every upgrade to the super catalog thanks Am Freitag, den 25.04.2008, 00:35 +0200 schrieb Jörg Sommer: > Package: docbook-xml > Version: 4.5-5 > Severity: serious > Justification: Policy 10.7.3 > > Hi, > > poli

Processed: Re: Bug#477968: yafray: FTBFS: src/yafraycore/color.h:37: error: expected constructor, destructor, or type conversion before 'class'

Processing commands for [EMAIL PROTECTED]: > tag 477968 confirmed Bug#477968: yafray: FTBFS: src/yafraycore/color.h:37: error: expected constructor, destructor, or type conversion before 'class' There were no tags set. Tags added: confirmed > thanks Stopping processing here. Please contact me i

Bug#477239: marked as done (exim4-base: empty argument in init.d prevents starting)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477239: fixed in exim4 4.69-3 has caused the Debian Bug report #477239, regarding exim4-base: empty argument in init.d prevents starting to be marked as done. This means that you claim that

Bug#477194: marked as done (exim4: Starting MTA:exim: incompatible command-line options or arguments)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477562: fixed in exim4 4.69-3 has caused the Debian Bug report #477562, regarding exim4: Starting MTA:exim: incompatible command-line options or arguments to be marked as done. This means

Bug#477194: marked as done (exim4: Starting MTA:exim: incompatible command-line options or arguments)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477239: fixed in exim4 4.69-3 has caused the Debian Bug report #477239, regarding exim4: Starting MTA:exim: incompatible command-line options or arguments to be marked as done. This means

Bug#477239: marked as done (exim4-base: empty argument in init.d prevents starting)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477194: fixed in exim4 4.69-3 has caused the Debian Bug report #477194, regarding exim4-base: empty argument in init.d prevents starting to be marked as done. This means that you claim that

Bug#477239: marked as done (exim4-base: empty argument in init.d prevents starting)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477258: fixed in exim4 4.69-3 has caused the Debian Bug report #477258, regarding exim4-base: empty argument in init.d prevents starting to be marked as done. This means that you claim that

Bug#477236: marked as done (exim4-daemon-heavy: restart of exim4 fails after pdate )

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477194: fixed in exim4 4.69-3 has caused the Debian Bug report #477194, regarding exim4-daemon-heavy: restart of exim4 fails after pdate to be marked as done. This means that you claim tha

Bug#477236: marked as done (exim4-daemon-heavy: restart of exim4 fails after pdate )

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477562: fixed in exim4 4.69-3 has caused the Debian Bug report #477562, regarding exim4-daemon-heavy: restart of exim4 fails after pdate to be marked as done. This means that you claim tha

Bug#477258: marked as done (Fails to start because of incorrect command-line arguments)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477562: fixed in exim4 4.69-3 has caused the Debian Bug report #477562, regarding Fails to start because of incorrect command-line arguments to be marked as done. This means that you claim

Bug#477194: marked as done (exim4: Starting MTA:exim: incompatible command-line options or arguments)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477258: fixed in exim4 4.69-3 has caused the Debian Bug report #477258, regarding exim4: Starting MTA:exim: incompatible command-line options or arguments to be marked as done. This means

Bug#477236: marked as done (exim4-daemon-heavy: restart of exim4 fails after pdate )

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477236: fixed in exim4 4.69-3 has caused the Debian Bug report #477236, regarding exim4-daemon-heavy: restart of exim4 fails after pdate to be marked as done. This means that you claim tha

Bug#477194: marked as done (exim4: Starting MTA:exim: incompatible command-line options or arguments)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477236: fixed in exim4 4.69-3 has caused the Debian Bug report #477236, regarding exim4: Starting MTA:exim: incompatible command-line options or arguments to be marked as done. This means

Bug#477562: marked as done (exim4-daemon-light: init script fails to start: incompatible command-line options or arguments)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477258: fixed in exim4 4.69-3 has caused the Debian Bug report #477258, regarding exim4-daemon-light: init script fails to start: incompatible command-line options or arguments to be marked

Bug#476977: Security fix in new upstream release

severity 476977 important stop Am Sonntag, 20. April 2008 schrieb Lars Wilke: > The fixed security problems are grave, if you have > directories writable by the webserver in you docroot (in most > windows server the complete docroot writable by default, but > many linux servers are also set up

Bug#477562: marked as done (exim4-daemon-light: init script fails to start: incompatible command-line options or arguments)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477239: fixed in exim4 4.69-3 has caused the Debian Bug report #477239, regarding exim4-daemon-light: init script fails to start: incompatible command-line options or arguments to be marked

Bug#477258: marked as done (Fails to start because of incorrect command-line arguments)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477258: fixed in exim4 4.69-3 has caused the Debian Bug report #477258, regarding Fails to start because of incorrect command-line arguments to be marked as done. This means that you claim

Bug#477562: marked as done (exim4-daemon-light: init script fails to start: incompatible command-line options or arguments)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477562: fixed in exim4 4.69-3 has caused the Debian Bug report #477562, regarding exim4-daemon-light: init script fails to start: incompatible command-line options or arguments to be marked

Bug#477258: marked as done (Fails to start because of incorrect command-line arguments)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477236: fixed in exim4 4.69-3 has caused the Debian Bug report #477236, regarding Fails to start because of incorrect command-line arguments to be marked as done. This means that you claim

Bug#477236: marked as done (exim4-daemon-heavy: restart of exim4 fails after pdate )

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477258: fixed in exim4 4.69-3 has caused the Debian Bug report #477258, regarding exim4-daemon-heavy: restart of exim4 fails after pdate to be marked as done. This means that you claim tha

Bug#477239: marked as done (exim4-base: empty argument in init.d prevents starting)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477562: fixed in exim4 4.69-3 has caused the Debian Bug report #477562, regarding exim4-base: empty argument in init.d prevents starting to be marked as done. This means that you claim that

Bug#476987: marked as done (exim4-daemon-light: fails to install: incompatible command-line options or arguments)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#476987: fixed in exim4 4.69-3 has caused the Debian Bug report #476987, regarding exim4-daemon-light: fails to install: incompatible command-line options or arguments to be marked as done.

Processed: Re: Bug#476977: Security fix in new upstream release

Processing commands for [EMAIL PROTECTED]: > severity 476977 important Bug#476977: Security fix in new upstream release Severity set to `important' from `critical' > stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator,

Bug#477562: marked as done (exim4-daemon-light: init script fails to start: incompatible command-line options or arguments)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477236: fixed in exim4 4.69-3 has caused the Debian Bug report #477236, regarding exim4-daemon-light: init script fails to start: incompatible command-line options or arguments to be marked

Bug#477562: marked as done (exim4-daemon-light: init script fails to start: incompatible command-line options or arguments)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477194: fixed in exim4 4.69-3 has caused the Debian Bug report #477194, regarding exim4-daemon-light: init script fails to start: incompatible command-line options or arguments to be marked

Bug#477194: marked as done (exim4: Starting MTA:exim: incompatible command-line options or arguments)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477194: fixed in exim4 4.69-3 has caused the Debian Bug report #477194, regarding exim4: Starting MTA:exim: incompatible command-line options or arguments to be marked as done. This means

Bug#477258: marked as done (Fails to start because of incorrect command-line arguments)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477194: fixed in exim4 4.69-3 has caused the Debian Bug report #477194, regarding Fails to start because of incorrect command-line arguments to be marked as done. This means that you claim

Bug#477258: marked as done (Fails to start because of incorrect command-line arguments)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477239: fixed in exim4 4.69-3 has caused the Debian Bug report #477239, regarding Fails to start because of incorrect command-line arguments to be marked as done. This means that you claim

Bug#477236: marked as done (exim4-daemon-heavy: restart of exim4 fails after pdate )

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477239: fixed in exim4 4.69-3 has caused the Debian Bug report #477239, regarding exim4-daemon-heavy: restart of exim4 fails after pdate to be marked as done. This means that you claim tha

Bug#477239: marked as done (exim4-base: empty argument in init.d prevents starting)

Your message dated Fri, 25 Apr 2008 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#477236: fixed in exim4 4.69-3 has caused the Debian Bug report #477236, regarding exim4-base: empty argument in init.d prevents starting to be marked as done. This means that you claim that

Bug#477964: gnat-4.3: FTBFS: grep: ../libgnatvsn/gnatvsn.ads: No such file or directory

severity 477964 important tags 477964 moreinfo merge 477964 465671 thanks I built the package built successfully without any problem on i386 and amd64, and the buildds successfully on all other architectures. Two days ago. Since you build with 8 parallel threads, I think this is another symptom

Bug#477961: libnet-z3950-perl: FTBFS: Nonexistent build-dependency: libyaz2-dev

On Sat, 26 Apr 2008 02:44:31 +0200, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build on i386. > > E: Package libyaz2-dev has no installation candidate Yup, it's libyaz3-dev now. But libnet-z3950-perl will become a transitional dummy package anyway, i

Processed: tagging 477961

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.26 > tags 477961 + pending Bug#477961: libnet-z3950-perl: FTBFS: Nonexistent build-dependency: libyaz2-dev There were no tags set. Tags added: pending > End of message, stopping processi

Processed: Re: Bug#477964: gnat-4.3: FTBFS: grep: ../libgnatvsn/gnatvsn.ads: No such file or directory

Processing commands for [EMAIL PROTECTED]: > severity 477964 important Bug#477964: gnat-4.3: FTBFS: grep: ../libgnatvsn/gnatvsn.ads: No such file or directory Severity set to `important' from `serious' > tags 477964 moreinfo Bug#477964: gnat-4.3: FTBFS: grep: ../libgnatvsn/gnatvsn.ads: No such f

Bug#477974: undeclared conflicts with package john

Package: john-data Version: 1.7.2.-1 Severity: grave Selecting previously deselected package john-data. Unpacking john-data (from .../john-data_1.7.2-1_all.deb) ... dpkg: error processing /var/cache/apt/archives/john-data_1.7.2-1_all.deb (--unpack): trying to overwrite `/usr/share/john/password

Bug#475905: egroupware-felamimail: Missing package dependencies

Am Sonntag, 13. April 2008 schrieb Michael Tuschik: > egroupware-felamimail doesn't work after installation via apt-get. I > installed two additional packages "php-auth" and "php-net-imap" > and now felamimail works ok. Could you be more specific about what errors you see? It is quite possible t

Bug#471060: Processed: 'dh_installinit -n' does not fix the problem.

On Fri, Apr 25, 2008 at 01:38:39PM -0400, Joey Hess wrote: > AFAIK, start-stop-daemon still defaults to refusing to stop a daemon if > the executable has changed from the executable it initially started. Ie: "still defaults" - since when? i've never seen that behaviour. start-stop-daemon uses pi

Processed: reassign 477930 to scons

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.6 > reassign 477930 scons 0.98.0-1 Bug#477930: kio-locate: FTBFS: does not find Qt/KDE includes Bug reassigned from package `kio-locate' to `scons'. > thanks Stopping processing here. Pl

Bug#477930: reassign 477930 to scons

# Automatically generated email from bts, devscripts version 2.9.6 reassign 477930 scons 0.98.0-1 thanks kio-locate can be built on a clean&updated sid chroot as long as scons < 0.98.0-1 scons >= 0.98.0-1 does not set: -I/usr/include/kde/ -I/usr/include/qt3 Which is: admin/kde.py: env.Append(

Processed: retitle 477751 to dh_installcatalogs: Don't readd catalog on every upgrade to the catalog

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.26 > retitle 477751 dh_installcatalogs: Don't readd catalog on every upgrade to > the catalog Bug#477751: docbook-xml: Don't readd your catalog on every upgrade to the super catalog Cha

Bug#417061: marked as done (FTBFS with GCC 4.3: identifier 'static_assert' will become a keyword in C++0x)

Your message dated Sat, 26 Apr 2008 00:17:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#417061: fixed in holotz-castle 1.3.10-1 has caused the Debian Bug report #417061, regarding FTBFS with GCC 4.3: identifier 'static_assert' will become a keyword in C++0x to be marked as don

Bug#424598: marked as done (FTBFS: conflicting types for 'readlink')

Your message dated Fri, 25 Apr 2008 19:52:29 -0500 with message-id <[EMAIL PROTECTED]> and subject line gnome-find has been removed from Debian, closing #424598 has caused the Debian Bug report #424598, regarding FTBFS: conflicting types for 'readlink' to be marked as done. This means that you cl

Bug#353882: marked as done (oftpd: Remote DoS vulnerability)

Your message dated Fri, 25 Apr 2008 20:00:46 -0500 with message-id <[EMAIL PROTECTED]> and subject line oftpd has been removed from Debian, closing #353882 has caused the Debian Bug report #353882, regarding oftpd: Remote DoS vulnerability to be marked as done. This means that you claim that the

Bug#423149: marked as done (kxmleditor handles entity references incorrectly)

Your message dated Fri, 25 Apr 2008 19:55:30 -0500 with message-id <[EMAIL PROTECTED]> and subject line kxmleditor has been removed from Debian, closing #423149 has caused the Debian Bug report #423149, regarding kxmleditor handles entity references incorrectly to be marked as done. This means th

Bug#474856: marked as done (lordsawar: FTBFS: cwchar:52:24: error: wchar.h: No such file or directory)

Your message dated Sat, 26 Apr 2008 01:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#474856: fixed in lordsawar 0.0.8-2 has caused the Debian Bug report #474856, regarding lordsawar: FTBFS: cwchar:52:24: error: wchar.h: No such file or directory to be marked as done. This

Bug#476066: Patch to fix 476066.

tags 476066 + patch thanks Hi! Please find attached a patch to fix this bug, by unexporting the compiler flags set by dpkg-buildpackage. HTH. Kumar -- Kumar Appaiah, 458, Jamuna Hostel, Indian Institute of Technology Madras, Chennai - 600 036 diff -Nru --exclude changelog wml-2.0.11ds1/debian/

Processed: Patch to fix 476066.

Processing commands for [EMAIL PROTECTED]: > tags 476066 + patch Bug#476066: wml: FTBFS: configure: warning: CFLAGS=-g -O2: invalid host type There were no tags set. Tags added: patch > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system adminis

Bug#474792: Patch to fix 474792

tags 474792 + patch thanks Hi! Please find attached a patch to fix this bug by adding the missing #include in the problematic file. HTH. Kumar -- Kumar Appaiah, 458, Jamuna Hostel, Indian Institute of Technology Madras, Chennai - 600 036 diff -Nru --exclude changelog debtags-edit-1.3/src/TagM

Processed: Patch to fix 474792

Processing commands for [EMAIL PROTECTED]: > tags 474792 + patch Bug#474792: debtags-edit: FTBFS: TagMenu.tcc:74: error: 'auto_ptr' was not declared in this scope There were no tags set. Tags added: patch > thanks Stopping processing here. Please contact me if you need assistance. Debian bug t

Processed: reopening a bug

Processing commands for [EMAIL PROTECTED]: > reopen 472630 Bug#472630: audacious-crossfade: audacious segfaults Bug reopened, originator not changed. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, De

Bug#477962: tellico: FTBFS: Nonexistent build-dependency: libyaz2-dev

User: [EMAIL PROTECTED] > Usertags: qa-ftbfs-20080425 qa-ftbfs > Justification: FTBFS on i386 > > Hi, > > During a rebuild of all packages in sid, your package failed to build on i386. > > This rebuild was done with gcc 4.3 instead of gcc 4.2, because gcc 4.3 is now >

Bug#477438: roundup - security update broke my installation

Hi Toni, thanks... I'm terribly sorry for the mistake, and guess I have created a fix (tested yesterday or so by Floris) which is to say "escape=1" instead of the original "escape=0" in the offending position (your line number is correct, Floris' not). Could you please try to see if running with

Bug#474530: Patch to fix 474530 and 455673

tags 474530 + patch tags 455673 + patch thanks (CCing Alexander and James who were interested in NMUing this a while back). Hi! Please find attached a patch to fix this bug. I now can say for sure that this fixes the FTBFS, but it fails to build with the new g++ snapshot (4.4.0). But I guess tha

Bug#476806: marked as done (AssertionError when archiving empty maildirs)

Your message dated Sat, 26 Apr 2008 05:32:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#476806: fixed in archivemail 0.7.2-3 has caused the Debian Bug report #476806, regarding AssertionError when archiving empty maildirs to be marked as done. This means that you claim that th

Processed: Patch to fix 474530 and 455673

Processing commands for [EMAIL PROTECTED]: > tags 474530 + patch Bug#474530: debian-xcontrol - FTBFS: error: ISO C++ forbids declaration of 'auto_ptr' with no type There were no tags set. Bug#455673: FTBFS with GCC 4.3: missing #includes Tags added: patch > tags 455673 + patch Bug#455673: FTBFS

Bug#455673: [Fwd: Patch to fix 474530 and 455673]

Forwarded to present information. Kumar -- Kumar Appaiah, 458, Jamuna Hostel, Indian Institute of Technology Madras, Chennai - 600 036 --- Begin Message --- tags 474530 + patch tags 455673 + patch thanks (CCing Alexander and James who were interested in NMUing this a while back). Hi! Please fi

Processed: fixed 477068 in 1.8.1.13-1

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.26 > fixed 477068 1.8.1.13-1 Bug#477068: xulrunner_1.9~b5-2(mips/experimental): FTBFS: expected constructor, destructor, or type conversion before 'XPTC_InvokeByIndex' Bug marked as fixe

Bug#477694: FTBFS: ext/threads/t/stress_re.t fails sporadically on sparc

On Fri, Apr 25, 2008 at 10:29:03PM +0200, Florian Weimer wrote: > * Niko Tyni: > > > It doesn't show up on my own sparc uniprocessor host, which has the > > Etch kernel, so it's either specific to new kernels or SMP hosts. As it > > works on sperger in the sid chroot, it would seem that newer vers

<    1   2   3