I also suffered this boot problem.
Thanks to (not so well documented) feature in update-initramfs, postinst
of udev only updates the latest kernel. Thus I was able to boot with
older kernel.
The latest initramfs-tools seems to solved the issue for booting and
starting with latest udev.
If
On Sun, Aug 20, 2006 at 02:34:47AM +0200, Alexander Sack [EMAIL PROTECTED]
wrote:
Mike, can you take a look? Appears to be related with xulrunner
transition. So maybe you have an idea what the reason might be.
I didn't try to reproduce the bug and see the backtrace to verify my
assumptions,
On Sun, Aug 20, 2006 at 08:53:27AM +0200, Mike Hommey [EMAIL PROTECTED] wrote:
On Sun, Aug 20, 2006 at 02:34:47AM +0200, Alexander Sack [EMAIL PROTECTED]
wrote:
Mike, can you take a look? Appears to be related with xulrunner
transition. So maybe you have an idea what the reason might be.
On Sun, Aug 20, 2006 at 04:12:06AM +0200, Jeroen van Wolffelaar wrote:
And I have no idea about:
kernel-patch-2.4.27-apus
This one can go too. Actually, i believe it is part of the
kernel-source-2.4.27-powerpc or whatever its name was source package, which
can go also.
Friendly,
Sven Luther
Processing commands for [EMAIL PROTECTED]:
tags 383859 +unreproducible
Bug#383859: Failed to install nullmailer 1:1.0.3-2
There were no tags set.
Tags added: unreproducible
tags 383859 +moreinfo
Bug#383859: Failed to install nullmailer 1:1.0.3-2
Tags were: unreproducible
Tags added: moreinfo
On Sun, Aug 20, 2006 at 10:00:57AM +0200, Norbert Tretkowski wrote:
I'm unable to reproduce this problem. Could you please replace the
set -e
in /var/lib/dpkg/info/nullmailer.postinst with
set -x
and send me the complete output when processing the package again?
tags 383859 +unreproducible
tags 383859 +moreinfo
thanks
* Kanru Chen wrote:
Errors were encountered while processing:
nullmailer
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up nullmailer (1.03-2) ...
dpkg: error
Oi Gustavo,
On Fri, Aug 18, 2006 at 12:20:29AM -0300, Gustavo Noronha Silva wrote:
Some of my Python packages should simply require a binNMU to be in
shape with the new python package which is 2.4:
ruledispatch (python-dispatch)
pyprotocols (python-protocols)
turbojson (python-turbojson)
Processing commands for [EMAIL PROTECTED]:
retitle 383147 [arm] doc doesn't build on arm
Bug#383147: gst-plugins-base0.10 (arm/unstable): FTBFS: Segmentation fault
Changed Bug title.
severity 383147 minor
Bug#383147: [arm] doc doesn't build on arm
Severity set to `minor' from `serious'
tags
Your message dated Sun, 20 Aug 2006 01:32:11 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#381386: fixed in gs-esp 8.15.2.dfsg.1-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
Your message dated Sun, 20 Aug 2006 01:32:11 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#381386: fixed in gs-esp 8.15.2.dfsg.1-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
retitle 383147 [arm] doc doesn't build on arm
severity 383147 minor
tags 383147 + help upstream confirmed
tags 383147 + arm
stop
Hi,
On Sun, Aug 13, 2006, Luk Claes wrote:
Can you please look into the FTBFS on arm [1] and either fix the problem
if it's a problem in the package or
Your message dated Sun, 20 Aug 2006 01:32:11 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#382250: fixed in gs-esp 8.15.2.dfsg.1-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
Your message dated Sun, 20 Aug 2006 01:32:11 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#382250: fixed in gs-esp 8.15.2.dfsg.1-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
* Kanru Chen wrote:
++ exec /usr/share/debconf/frontend /var/lib/dpkg/info/nullmailer.postinst
configure 1:1.02-8
dpkg: error processing nullmailer (--configure):
subprocess post-installation script returned error exit status 128
Errors were encountered while processing:
nullmailer
So
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.9.20
tags 383304 sid
Bug#383304: python-dispatch: Must be updated for python 2.4
There were no tags set.
Tags added: sid
End of message, stopping processing here.
Please contact me if
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.9.20
tags 383331 sid
Bug#383331: omniidl4 uninstallable due to python transition
There were no tags set.
Tags added: sid
End of message, stopping processing here.
Please contact me if
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.9.20
tags 381818 sid
Bug#381818: Uninstallable due to unmet dep on pike7.6-core (= 7.6.75-99)
There were no tags set.
Tags added: sid
End of message, stopping processing here.
Please
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.9.20
tags 383830 sid
Bug#383830: mapserver: FTBFS: build-dep on missing libgdal1-1.3.2-dev
There were no tags set.
Tags added: sid
End of message, stopping processing here.
Please
Your message dated Sun, 20 Aug 2006 03:02:08 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#383449: fixed in acpi-support 0.86-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
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.9.20
reassign 383426 omniidl4
Bug#383426: omnievents: FTBFS: build-depends on python 2.4
Bug reassigned from package `omnievents' to `omniidl4'.
merge 383331 383426
Bug#383331: omniidl4
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.9.20
tags 383279 sid
Bug#383279: depends: python2.3
There were no tags set.
Tags added: sid
End of message, stopping processing here.
Please contact me if you need assistance.
Debian
On Sun, Aug 20, 2006 at 04:12:06AM +0200, Jeroen van Wolffelaar wrote:
On Fri, Aug 18, 2006 at 06:55:26PM +0200, maximilian attems wrote:
retitle 376771 RM: kernel-image-2.4.27-2-* -- RoM
thanks
in accordance with the d-i team any 2.4 kernel-image package
can be removed from unstable
Package: fetchmail
Version: 6.3.4-4
Severity: grave
Justification: renders package unusable
I have been using fetchmail for many years - it runs every 10 minutes
fetching from a few accounts. The mail is then fed into a local
exim, because I used to have several users on this machine.
Processing commands for [EMAIL PROTECTED]:
severity 379920 grave
Bug#379920: freetype: buffer overflow [CVE-2006-3467]
Severity set to `grave' from `important'
stop
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator,
On Sun, Aug 20, 2006 at 01:33:10AM +0300, Yavor Doganov wrote:
I rebuilt mysql-dfsg-5.0 5.0.22-4 with DEB_BUILD_OPTIONS=nostrip on a
Pentium IV and installed the unstripped libmysqlclient15off library.
The backtrace is different:
(gdb) r -C /dev/null -bV
Starting program: /usr/sbin/exim4 -C
Your message dated Sun, 20 Aug 2006 04:02:11 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#383779: fixed in slang-slirp 1.9.0-1-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
Your message dated Sun, 20 Aug 2006 04:02:11 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#383777: fixed in slang-slirp 1.9.0-1-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
On Sun, Aug 20, 2006 at 11:16:11AM +0200, Norbert Tretkowski wrote:
* Kanru Chen wrote:
++ exec /usr/share/debconf/frontend /var/lib/dpkg/info/nullmailer.postinst
configure 1:1.02-8
dpkg: error processing nullmailer (--configure):
subprocess post-installation script returned error exit
This will be fixed in base-files 3.1.15.
Thanks a lot for the report.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
found 383779 1.9.0-1-3
thanks
It's still failing to build with the same error.
Kurt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
I tried your tips with update-initramfs, now the modules will be loaded
at booting my system, but I still get this warnings/errors.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing commands for [EMAIL PROTECTED]:
found 383779 1.9.0-1-3
Bug#383779: FTBFS on amd64: not creating PIC code?
Bug marked as found in version 1.9.0-1-3.
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator,
Your message dated Sun, 20 Aug 2006 04:17:03 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#383493: fixed in base-files 3.1.15
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
Processing commands for [EMAIL PROTECTED]:
tags 383859 -unreproducible
Bug#383859: Failed to install nullmailer 1:1.0.3-2
Tags were: moreinfo unreproducible
Tags removed: unreproducible
tags 383859 -moreinfo
Bug#383859: Failed to install nullmailer 1:1.0.3-2
Tags were: moreinfo
Tags removed:
tags 383859 -unreproducible
tags 383859 -moreinfo
tags 383859 +confirmed
thanks
* Kanru Chen wrote:
I found the problem. Actually I have two smarthosts in
/etc/nullmailer/remotes, separated by newlines.
If I remove one of them, the --configure goes without any problem.
According to
Your message dated Sun, 20 Aug 2006 05:47:13 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#379200: fixed in bluez-utils 3.1-4
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 message dated Sun, 20 Aug 2006 14:02:29 +0100
with message-id [EMAIL PROTECTED]
and subject line Fixed in experimental
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
Processing commands for [EMAIL PROTECTED]:
severity 380869 serious
Bug#380869: Python transition (#2): you are building a private python module !
Severity set to `serious' from `important'
tags 380869 + patch
Bug#380869: Python transition (#2): you are building a private python module !
There
Your message dated Sun, 20 Aug 2006 06:17:31 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#383555: fixed in udev 0.097-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 your
Processing commands for [EMAIL PROTECTED]:
package slang-slirp
Ignoring bugs not assigned to: slang-slirp
tags 383779 confirmed
Bug#383779: FTBFS on amd64: not creating PIC code?
There were no tags set.
Tags added: confirmed
thanks
Stopping processing here.
Please contact me if you need
Subject: vtk failed to build from sources
Package: vtk
Severity: serious
*** Please type your report below this line ***
debuild fails after apt-get source vtk on a up to date sid (whereas
/usr/lib/pbuilder/pbuilder-satisfydepends says all the build dependances are
installed.)
Here is debuild
Your message dated Sun, 20 Aug 2006 06:32:19 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#367221: fixed in quodlibet 0.23-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
package slang-slirp
tags 383779 confirmed
thanks
* Kurt Roeckx [EMAIL PROTECTED] [2006-08-20 13:32]:
found 383779 1.9.0-1-3
thanks
It's still failing to build with the same error.
Indeed. I thought that #383777 and #383779 were related to each other
and closed both of them in
reassign 383829 cmake 2.4.3-1
# set severity to critical since it brake others package(s?)
severity 383829 critical
notfound 383829 2.2.3-1
thanks, control, you are my reassigning bitch ;-p
This is a bug/regression in cmake, as this package compiles fine with
cmake 2.2.3-1. I'll be looking into
Processing commands for [EMAIL PROTECTED]:
reassign 383829 cmake 2.4.3-1
Bug#383829: libapache2-mod-xmlrpc2: FTBFS: missing build-dep ?
Bug reassigned from package `libapache2-mod-xmlrpc2' to `cmake'.
# set severity to critical since it brake others package(s?)
severity 383829 critical
Your message dated Sun, 20 Aug 2006 07:53:30 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#376602: 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 responsibility to
Processing commands for [EMAIL PROTECTED]:
tags 378712 =
Bug#378712: RM: zope-ttwtype -- RoM; obsolete
Tags were: patch
Tags set to:
severity 378712 normal
Bug#378712: RM: zope-ttwtype -- RoM; obsolete
Severity set to `normal' from `serious'
severity 382907 normal
Bug#382907: RM:
I took the liberty of uploading your package, so that the RC bug would be
fixed.
Please, keep an eye on the other important bugs you have. Some of them
look like they should actually be RC as well
--
Love,
Marga
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
What version of cmake was pbuilder using?
(Maybe I need to bump up the versioned depends upon cmake.)
I'll try to duplicate this result...
-Maitland
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Your message dated Sun, 20 Aug 2006 08:17:13 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#381919: fixed in qgo 1.5.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 now your
Your message dated Sun, 20 Aug 2006 09:00:17 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#381185: 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 responsibility to
Your message dated Sun, 20 Aug 2006 10:04:04 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#383772: fixed in openjade 1.4devel1-17
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
Package: libchm-bin
Version: 0.38-2
Severity: serious
Justification: Policy 9.1.1
$ dpkg-query --listfiles libchm-bin
/.
/usr
/usr/bin
/usr/bin/bin
/usr/bin/bin/chm_http
/usr/bin/bin/enum_chmLib
/usr/bin/bin/enumdir_chmLib
/usr/bin/bin/extract_chmLib
/usr/bin/bin/test_chmLib
/usr/share
Your message dated Sun, 20 Aug 2006 10:47:09 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#382618: fixed in slat 2.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 your
The second FTBFS is due to a bashism in syscheck.sh which upstream is
already aware of.
I'm attaching a patch that fixes that problem.
--
Love
Marga
--- spl-0.9i/syscheck.sh2006-05-28 10:36:41.0 -0300
+++ spl-marga/syscheck.sh 2006-08-20 14:44:21.07690 -0300
@@
Processing commands for [EMAIL PROTECTED]:
tags 381646 fixed
Bug#381646: Uninstallable since binNMU
Tags were: patch
Tags added: fixed
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
So, the first FTBFS was due to /proc not being mounted, or /dev/fd not
symliking to where it should.
The problem was the use of ( ... ), that required creating a file in
/dev/fd. I changed the script so that this is not necessary (by using a
pipe instead of a temporary file).
I tested this in
Hi Martin,
You forgot attach the patch :)
Ana
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Yes, please the missing patch! I'd really appreciate it.
- Jarno
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing commands for [EMAIL PROTECTED]:
forwarded 379657 http://tcpreplay.synfin.net/trac/ticket/81
Bug#379657: tcpreplay_2.99+3.0.beta9-1(ia64/unstable): FTBFS: compile errors
(no field ipbuff)
Noted your statement that Bug has been forwarded to
http://tcpreplay.synfin.net/trac/ticket/81.
* Norbert Tretkowski wrote:
* Andras Horvath wrote:
but the -smp is still suffering from the same SCSI problems..
Confirmed, I'll investigate next weekend.
I think I have a patch which fixes this problem, building a new kernel
currently...
Norbert
--
To UNSUBSCRIBE,
forwarded 379657 http://tcpreplay.synfin.net/trac/ticket/81
tags 379657 + upstream confirmed
thanks
Am Sonntag, den 20.08.2006, 02:12 +0200 schrieb Tobias Klauser:
Hello Tobias,
This seems to be caused by code enclosed in #ifdef FORCE_ALIGN which,
according to configure.in is defined on ia64.
Processing commands for [EMAIL PROTECTED]:
severity 382907 serious
Bug#382907: RM: mozilla-locale-fr -- RoM
Severity set to `serious' from `normal'
clone 382907 -1
Bug#382907: RM: mozilla-locale-fr -- RoM
Bug 382907 cloned as bug 383935.
reassign -1 mozilla-locale-fr
Bug#383935: RM:
Package: tulip
Version: tulip
Severity: grave
Justification: renders package unusable
This package is completely broken I just wanted to put that in
1) The package requires libOSMesa but does not have it as a dependency
2) The package is linked against the wrong libOSMesa.so.6, this should
be
Dear Mr Lusk,
your public-genetic-algorithms library pgapack is since many years part of
the Debian GNU/Linux distribution.
It was found recently that the license of pgapack means that pgapack is not
really free software. The license of pgapack restricts the selling of
derivative works.
The
On 20/08/06 19:24, Ana Guerrero wrote:
You forgot attach the patch :)
Oops! There's really very little to be done as cdbs does all the work.
--
Martin Orr
diff -NbarU2 memaid-pyqt-0.2.5.orig/debian/control
memaid-pyqt-0.2.5/debian/control
--- memaid-pyqt-0.2.5.orig/debian/control
Processing commands for [EMAIL PROTECTED]:
reopen 378608
Bug#378608: nss-mdns - FTBFS: error: tag name CXX already exists
'reopen' is deprecated when a bug has been closed with a version;
use 'found' or 'submitter' as appropriate instead.
Bug reopened, originator not changed.
thanks
Stopping
Processing commands for [EMAIL PROTECTED]:
reassign 381182 nvidia-glx-legacy
Bug#381182: apt continue in th instaltion script altru the packages was not
installed.
Bug reassigned from package `nvidia-glx,nvidia-glx-legacy' to
`nvidia-glx-legacy'.
forcemerge 372252 381182
Bug#372252:
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.9.20
package mdadm mdadm-udeb
Ignoring bugs not assigned to: mdadm mdadm-udeb
tags 381057 + pending
Bug#381057: make mdadm use homehost for initramfs
Tags were: confirmed
Tags added:
Hi,
Here's a use case where having initramfs-tools unconditionally update
initramfs images is a bad thing (at the very least, violating the
principal of least surprise).
I had a machine that was had a poorly supported sata_mv chipset; dapper
nor sarge w/ 2.6.15/2.6.16 images would install onto
found 383777 1.9.0-1-5
thanks
Hi,
We're still seeing this error in 1.9.0-1-5.
Kurt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
reopen 378608
thanks
The problem's not caused by CDBS... it's caused by however you are
regenerating the build system.
$ tar --list -v -zf nss-mdns_0.8.orig.tar.gz | grep configure$
-rwxrwxr-x 1000/1027709706 2006-04-30 00:36 nss-mdns-0.8/configure
$ ls -l
Processing commands for [EMAIL PROTECTED]:
found 383777 1.9.0-1-5
Bug#383777: FTBFS on 64-bit: Segmentation fault ../../safe_slsh
Bug marked as found in version 1.9.0-1-5.
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
Le 20 août vers 12:05, Margarita Manterola écrivait:
I took the liberty of uploading your package, so that the RC bug would be
fixed.
thanks a lot for the NAU (non advocate upload) !!
;-)
Please, keep an eye on the other important bugs you have. Some of them
look like they should actually
On Sun, Aug 20, 2006 at 04:25:53PM -0400, Andres Salomon wrote:
Here's a use case where having initramfs-tools unconditionally update
initramfs images is a bad thing (at the very least, violating the
principal of least surprise).
you use an plural, which is wrong.
initramfs-tools updates the
* Kurt Roeckx [EMAIL PROTECTED] [2006-08-20 23:01]:
found 383777 1.9.0-1-5
thanks
Hi,
We're still seeing this error in 1.9.0-1-5.
Thanks, I have already noticed it. I reached a point now that I cannot
debug further by uploading new versions of the package and looking at the
autobuilder
Package: samba
Version: 3.0.23b-2
Followup-For: Bug #382429
Here's a very naive approach at resolving the issue with the
autobuilders:
---
--- source/lib/interfaces.c 2005-07-28 15:19:45.0 +0200
+++ interfaces.c.naive-fix 2006-08-20 23:58:41.0 +0200
@@ -397,7 +397,7 @@
On Sun, 20 Aug 2006 23:26:32 +0200 maximilian attems wrote:
On Sun, Aug 20, 2006 at 04:25:53PM -0400, Andres Salomon wrote:
I had a machine that was had a poorly supported sata_mv chipset;
dapper nor sarge w/ 2.6.15/2.6.16 images would install onto it. I
had to make a custom cd w/
vtk 5.0.1-1 is making use of dh_python, and
it and mayavi_1.5-2 have been seen running
correctly with python2.4 as the default python.
There may be additional refinements to improve
python policy compliance, but I have uploaded
vtk_5.0.1-1 and mayavi_1.5-2 to support the
transition to python2.4
OK,
I have just successfully built vtk 5.0.1
in a pbuilder environment.
Perhaps you were trying vtk 4.4.2 and filed
a duplicate of bug #379240? Your bug report
doesn't say, but since 5.0.1 is still new,
I am guessing that you saw the bug on version
4.4.2-10.
-Maitland
--
To UNSUBSCRIBE, email
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.9.20
notfound 330890 0.94.0-15
Bug#330890: dia: Arbitrary code execution when importing a .svg file
Bug marked as not found in version 0.94.0-15.
(By the way, this Bug is currently marked
Processing commands for [EMAIL PROTECTED]:
merge 383888 379240
Bug#379240: FTBFS: Attempt to add link library vtkCommonPython which is not a
library target
Bug#383888: vtk failed to build from sources
Merged 379240 383888.
End of message, stopping processing here.
Please contact me if you
Processing commands for [EMAIL PROTECTED]:
retitle 383829 cmake: broke compatibility between 2.2 and 2.4
Bug#383829: libapache2-mod-xmlrpc2: FTBFS: missing build-dep ?
Changed Bug title.
clone 383829 -1 -2
Bug#383829: cmake: broke compatibility between 2.2 and 2.4
Bug 383829 cloned as bugs
Ok, I've been looking this for a while now and I'm not sure what to do.
The problem is that cmake changed the way it links binaries between 2.2
and 2.4, before the linking line was directly included in the Makefiles,
like:
mod_xmlrpc.so: CMakeFiles/mod_xmlrpc.dir/build.make
@echo Linking
Well, Exim's error before it just drops the connection isn't selling
fetchmail a hint that there's no progress beyond that point.
The question is: why does fetchmail not skip over the offending
messages? It may or may not try to bounce them, depending on your
configuration, but should mark them
Your message dated Sun, 20 Aug 2006 17:02:13 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#382263: fixed in mdadm 2.5.3.git200608202239-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
Processing commands for [EMAIL PROTECTED]:
# command block for Debian BTS control
package fetchmail
Ignoring bugs not assigned to: fetchmail
tags 383870 upstream
Bug#383870: fetchmail: Fetchmail duplicates my SPAM every 10 minutes - ARGH!
There were no tags set.
Tags added: upstream
# claim
Your message dated Sun, 20 Aug 2006 17:02:13 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#383688: fixed in mdadm 2.5.3.git200608202239-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
Your message dated Sun, 20 Aug 2006 17:02:13 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#383688: fixed in mdadm 2.5.3.git200608202239-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
Your message dated Sun, 20 Aug 2006 17:02:13 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#382450: fixed in mdadm 2.5.3.git200608202239-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
Your message dated Sun, 20 Aug 2006 17:02:13 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#383688: fixed in mdadm 2.5.3.git200608202239-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
Your message dated Sun, 20 Aug 2006 17:02:13 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#382263: fixed in mdadm 2.5.3.git200608202239-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
Your message dated Sun, 20 Aug 2006 17:02:13 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#382263: fixed in mdadm 2.5.3.git200608202239-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
Why do you consider this package unusable? I'm testing it and it seems
to work fine.
ok, you are right. I'm not so experienced on python.
it could be interesting to have a 'python2.3' version, I copied manually
Please notice that the directory that you mention is not needed in the actual
(demoting to serious, tagging upstream, retitling)
Additional info:
fetchmail 6.3.4 and older do NOT log out of the upstream server after
SIGPIPE (I don't know the rationale behind this - it's not in the
comments), which prevents the deletions from happening properly.
Retitling the bug
Your message dated Sun, 20 Aug 2006 17:02:13 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#382450: fixed in mdadm 2.5.3.git200608202239-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
Processing commands for [EMAIL PROTECTED]:
severity 383935 important
Bug#383935: mozilla-locale-fr: depends on mozilla
Severity set to `important' from `serious'
block 383935 by 382907
Bug#383935: mozilla-locale-fr: depends on mozilla
Was not blocked by any bugs.
Blocking bugs of 383935 added:
Your message dated Sun, 20 Aug 2006 17:02:13 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#382480: fixed in mdadm 2.5.3.git200608202239-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
Your message dated Sun, 20 Aug 2006 17:02:13 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#382450: fixed in mdadm 2.5.3.git200608202239-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
1 - 100 of 115 matches
Mail list logo
