Your message dated Fri, 24 Feb 2006 23:17:08 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#343355: fixed in flex 2.5.31-38
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
Your message dated Fri, 24 Feb 2006 19:47:20 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#354194: fixed in tar 1.15.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
Processing commands for [EMAIL PROTECTED]:
> tag 353135 patch
Bug#353135: libtest-pod-perl: FTBFS with perl 5.8.8
There were no tags set.
Tags added: patch
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debia
tag 353135 patch
thanks
This is actually a bug in libtest-builder-tester, but it has been
superseded by libtest-simple-perl, so the attached patch makes
libtest-pod-perl build-depend on the latter instead, which fixes its
build.
--
Matt
diff -ru libtest-pod-perl-1.20-orig/debian/control
libtest
Processing commands for [EMAIL PROTECTED]:
> tag 350688 patch
Bug#350688: gcc-2.95: FTBFS with new make
There were no tags set.
Tags added: patch
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs dat
Howdy,
According to both the upstream Changes and libtest-simple-perl's
dependencies, libtest-builder-tester has been merged into
libtest-simple-perl. Should this package be removed?
--
Matt
signature.asc
Description: Digital signature
tag 350688 patch
thanks
The attached patch integrates Daniel's patch into the build system.
It fixes the problem on PowerPC.
--
Matt
diff -Nru gcc-2.95-2.95.4.ds15-orig/debian/patches/p-make-lang.dpatch
gcc-2.95-2.95.4.ds15/debian/patches/p-make-lang.dpatch
--- gcc-2.95-2.95.4.ds15-orig/debian/
Processing commands for [EMAIL PROTECTED]:
> reassign 354217 linux-image-2.6.15-1-686-smp
Bug#354217: DEVPTS_FS not present at linux-image-2.6.15-1-686-smp
Warning: Unknown package 'linux-image-2.6.15-1-686-sm'
Bug reassigned from package `linux-image-2.6.15-1-686-sm' to
`linux-image-2.6.15-1-686
Hi Jonathan,
ifplugd is working fine for me here, let's see if we can get a little
more information and see what's wrong.
You are using 0.26-2.1, is it safe to assume that you upgraded from
0.26-2? Near as I can tell, the only change made in this NMU was a
in the path to the hotplug functions.
reassign 354217 linux-image-2.6.15-1-686-smp
tags 354217 -experimental
close 345217
quit
On Fri, Feb 24, 2006 at 02:09:26PM +0100, marlon wrote:
> Package: linux-image-2.6.15-1-686-sm
> Severity: grave
> Tags: experimental
> Justification: renders package unusable
> DEVPTS_FS not present at linux
Your message dated Sat, 25 Feb 2006 02:43:26 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#349988: fixed in kdbg 2.0.3-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
Your message dated Fri, 24 Feb 2006 18:40:57 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#354229: lastfmsubmitd: man pages misplaced (and
uncompressed)
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If thi
Your message dated Fri, 24 Feb 2006 18:02:20 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Done
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Your message dated Fri, 24 Feb 2006 15:02:16 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#347162: fixed in xine-lib 1.1.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 y
Your message dated Fri, 24 Feb 2006 14:47:13 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#354198: fixed in newlib 1.14.0-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 yo
Your message dated Fri, 24 Feb 2006 15:02:16 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#347162: fixed in xine-lib 1.1.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 y
Your message dated Fri, 24 Feb 2006 15:02:16 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#347162: fixed in xine-lib 1.1.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 y
Your message dated Fri, 24 Feb 2006 15:02:16 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#347162: fixed in xine-lib 1.1.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 y
Your message dated Fri, 24 Feb 2006 15:02:16 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#346488: fixed in xine-lib 1.1.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 y
Your message dated Fri, 24 Feb 2006 15:02:16 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#346488: fixed in xine-lib 1.1.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 y
Your message dated Fri, 24 Feb 2006 15:02:16 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#346488: fixed in xine-lib 1.1.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 y
Your message dated Fri, 24 Feb 2006 15:02:16 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#346488: fixed in xine-lib 1.1.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 y
Your message dated Fri, 24 Feb 2006 15:02:16 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#345499: fixed in xine-lib 1.1.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 y
Your message dated Fri, 24 Feb 2006 15:02:16 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#345499: fixed in xine-lib 1.1.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 y
Your message dated Fri, 24 Feb 2006 15:02:16 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#345499: fixed in xine-lib 1.1.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 y
Your message dated Fri, 24 Feb 2006 15:02:16 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#345499: fixed in xine-lib 1.1.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 y
Your message dated Fri, 24 Feb 2006 15:02:16 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#342208: fixed in xine-lib 1.1.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 y
Your message dated Fri, 24 Feb 2006 15:02:16 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#337997: fixed in xine-lib 1.1.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 y
Your message dated Fri, 24 Feb 2006 15:02:16 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#337997: fixed in xine-lib 1.1.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 y
Your message dated Fri, 24 Feb 2006 15:02:16 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#337997: fixed in xine-lib 1.1.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 y
Your message dated Fri, 24 Feb 2006 15:02:16 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#337997: fixed in xine-lib 1.1.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 y
Your message dated Fri, 24 Feb 2006 15:02:16 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#337996: fixed in xine-lib 1.1.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 y
Your message dated Fri, 24 Feb 2006 15:02:16 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#332919: fixed in xine-lib 1.1.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 y
Your message dated Fri, 24 Feb 2006 15:02:16 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#332919: fixed in xine-lib 1.1.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 y
Your message dated Fri, 24 Feb 2006 15:02:16 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#328184: fixed in xine-lib 1.1.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 y
Your message dated Fri, 24 Feb 2006 15:02:16 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#328168: fixed in xine-lib 1.1.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 y
Your message dated Fri, 24 Feb 2006 15:02:16 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#326935: fixed in xine-lib 1.1.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 y
Your message dated Fri, 24 Feb 2006 15:02:16 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#325960: fixed in xine-lib 1.1.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 y
Your message dated Fri, 24 Feb 2006 15:02:16 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#323276: fixed in xine-lib 1.1.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 y
Your message dated Fri, 24 Feb 2006 15:02:16 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#320317: fixed in xine-lib 1.1.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 y
Your message dated Fri, 24 Feb 2006 15:02:16 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#318838: fixed in xine-lib 1.1.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 y
Your message dated Fri, 24 Feb 2006 15:02:16 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#288189: fixed in xine-lib 1.1.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 y
Processing commands for [EMAIL PROTECTED]:
> severity 354132 critical
Bug#354132: asterisk: Upgrading destroys astdb
Severity set to `critical'.
> merge 354240 354132
Bug#354132: asterisk: Upgrading destroys astdb
Bug#354240: Removes custom directories and viles under /var/lib/asterisk
Merged 354
Your message dated Fri, 24 Feb 2006 14:32:08 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#354263: fixed in surfraw 2.1.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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 24 Feb 2006 14:09:29 -0800
Steve Langasek <[EMAIL PROTECTED]> wrote:
> On Fri, Feb 24, 2006 at 04:24:55PM -0500, Mike O'Connor wrote:
> > Is there any drawback to just switching the default dependency to
> > be on yaird instead of initramfs-to
Package: kitty
Version: kitty_0.9.2-1
Followup-For: Bug #348498
Exactly the same errors on ppc. It simply doesn't build.
-- System Information:
Debian Release: testing/unstable
APT prefers experimental
APT policy: (990, 'experimental'), (990, 'unstable')
Architecture: powerpc (ppc)
Shell: /
On Fri, Feb 24, 2006 at 04:24:55PM -0500, Mike O'Connor wrote:
> Is there any drawback to just switching the default dependency to be on
> yaird instead of initramfs-tools?
Yes. You can't install yaird on upgrade from a 2.4 kernel.
And currently, you can't install initramfs-tools on upgrade from
Your message dated Fri, 24 Feb 2006 13:55:05 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#350744: gliv aborted
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 responsib
On Fri, Feb 24, 2006 at 09:47:46PM +0200, Timo Aaltonen wrote:
> Could you test forcing on the client side to mount it with udp. The patch
> changes the default to tcp (maybe that could be reverted..).
% sudo mount -oudp -v foo.example.com:/tftpboot /mnt
mount: no type was given - I'll assume nf
Is there any drawback to just switching the default dependency to be on
yaird instead of initramfs-tools?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: surfraw
Version: 2.1.2
Severity: grave
Justification: renders package unusable
Setting up surfraw (2.1.2) ...
dpkg: error processing surfraw (--configure):
subprocess post-installation script returned error exit status 10
Errors were encountered while processing:
surfraw
E: Sub-process
Hi
Could you test forcing on the client side to mount it with udp. The patch
changes the default to tcp (maybe that could be reverted..).
The patch is old, but that should just show that it's stable =)
t
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe
Hey Mark,
I maintain Test::Builder::Tester under Debian, and it appears that it
is broken under perl 5.8.8. It's being tracked as bug debian bug 353134
(bugs.debian.org/353134). If you wouldn't mind taking some time to take
a look at it, that'd be great. I'm willing to help with whatever y
tags 348390 + patch
thanks
Hi,
this simple patch disables the build of kernel modules (which seems
brittle and unnecessary), but reinstates all drivers in the daemon
itself.
I've used it successfully for some weeks now.
diff -ru lirc-0.7.2-/debian/rules lirc-0.7.2/debian/rules
--- lirc-0.7.2-/d
Your message dated Fri, 24 Feb 2006 10:32:06 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#354075: fixed in util-linux 2.12r-8
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 Fri, 24 Feb 2006 10:17:32 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#346827: fixed in xmms-jack 0.16-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 y
Processing commands for [EMAIL PROTECTED]:
> tags 348390 + patch
Bug#348390: lirc: Irman driver stopped to work after upgrade
There were no tags set.
Tags added: patch
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administ
Processing commands for [EMAIL PROTECTED]:
> severity 354075 serious
Bug#354075: Does not mount with NFS user server
Severity set to `serious'.
>
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian B
Processing commands for [EMAIL PROTECTED]:
> severity 353918 important
Bug#353918: mount: mounted wrong filesystem
Severity set to `important'.
>
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian B
Processing commands for [EMAIL PROTECTED]:
> tag 354230 + fixed
Bug#354230: freqtweak: ships redundant, uncompressed, misplaced man page
There were no tags set.
Tags added: fixed
> quit
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
I think it is unfair to hold back kaffeine because of gstreamer bugs. If you
have a problem with gstreamer then don't upload the kaffeine-gstreamer
package.
Kaffeine is a solid application in my experience. And things are pretty quiet
bug-reporting-wise on the kaffeine user mailinglist
([EMAIL
Processing commands for [EMAIL PROTECTED]:
> tag 353918 + unreproducible
Bug#353918: mount: mounted wrong filesystem
There were no tags set.
Tags added: unreproducible
>
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
Hi
Attached the patch for the version I uploaded. Please respond if
you think that the attached patch won't work.
Cheers
Luk
--
Luk Claes - http://people.debian.org/~luk - GPG key 1024D/9B7C328D
Fingerprint: D5AF 25FB 316B 53BB 08E7 F999 E544 DE07 9B7C 328D
diff -u freqtweak-0.6.1/debian/c
Aaron M. Ucko writes:
> I see two uploads from yesterday, of 0.19-1 and 0.20-1, both in time
> for dinstall. In looking at the latter, I see that its setup.py omits
> the relevant path component.
Er, sorry, I meant 0.22 which is subsequent to 0.20 and still in the
queue at the moment.
--
thing
Processing commands for [EMAIL PROTECTED]:
> reopen 354229
Bug#354229: lastfmsubmitd: man pages misplaced (and uncompressed)
Bug reopened, originator not changed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator
Your message dated Fri, 24 Feb 2006 12:10:10 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#354229: lastfmsubmitd: man pages misplaced (and
uncompressed)
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If thi
merge 354240 354132
thanks
I had this symlink:
/var/lib/asterisk -> /asterisk/lib
It turns out that one of the asterisk maintainer scripts must be blowing
away that symlink and then creating a directory at /var/lib/asterisk.
This was responsible for the astdb appearing to disappear, and for the
Package: asterisk
Version: 1:1.2.4.dfsg-6
Severity: critical
Justification: causes serious data loss
Installing this package removed *ALL* local sound recordings, which we
had installed under /var/lib/asterisk/localsounds.
This may also be responsible for #354132.
-- System Information:
Debian R
Steve Langasek wrote:
> On Thu, Feb 23, 2006 at 11:16:59PM +0800, LUK ShunTim wrote:
>
>
[snipped]
>
> Aha. Ok, this is not a bug in gliv. The invalid free happens inside scim,
> which is not a dependency of gliv at all. There is a known bug involving
> scim, in which scim and the applicati
Package: libgtk2.0-bin
Version: 2.8.12-1
Severity: serious
Hi. Here is the output of apt-get dist-upgrade:
# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Calculating upgrade...Done
The following packages have been kept back:
gdk-imlib1 libc6-dev libfreety
Your message dated Fri, 24 Feb 2006 16:08:35 +0100 (CET)
with message-id <[EMAIL PROTECTED]>
and subject line snd-doc fails to install
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 res
Upstream has updated the KRGB patch to 1.2, and included a memory leak fix
too.
Here's the updated patch.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Ta
Package: freqtweak
Version: 0.6.1-1.2
Severity: serious
Justification: Policy 9.1.1
I just noticed that freqtweak ships a redundant, uncompressed copy of
its man page in /usr/share/man1, which is not sanctioned by the FHS.
Could you please drop this copy (but keep the compressed one under
/usr/sha
Package: lastfmsubmitd
Version: 0.20-1
Severity: serious
Justification: Policy 9.1.1; 12.1
lastfmsubmitd's actual man pages seem to have wound up in
/usr/share/man1 rather than /usr/share/man/man1 (which consequently
now contains dangling symlinks that called my attention to the
problem.) Presuma
Package: dspam
Version: 3.6.4-1
Severity: serious
Hi,
your package failed to build from source because it build-depends on
libmysqlclient14-dev which is not available anymore.
| Automatic build of dspam_3.6.4-1 on odin by sbuild/sparc 79
| Build started at 20060224-0719
Package: linux-image-2.6.15-1-686-sm
Severity: grave
Tags: experimental
Justification: renders package unusable
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/b
Package: amule-daemon
Version: 2.1.0-3
Severity: grave
Justification: renders package unusable
Executing /etc/init.d/amuled as root the daemon fails to start
without meaningful output.
This is the output of /usr/bin/amuled launched as a normal user
(user with a running amule configuration in ~/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Schepler wrote:
> Package: libspf
> Version: 0.999-1.0.0-p3-2
> Severity: serious
>
> From my pbuilder build log:
>
> ...
> debian/rules build
> dh_testdir
> CFLAGS="-Wall -g -O2" ./configure \
> --host=i486-linux-gnu \
>
Your message dated Fri, 24 Feb 2006 03:32:11 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#345092: fixed in sphinx2 0.6-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
Your message dated Fri, 24 Feb 2006 03:17:26 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#346805: fixed in xdaliclock 2.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
Processing commands for [EMAIL PROTECTED]:
> severity 346474 important
Bug#346474: libxml-sax-writer-perl: Dropped output when encoding to non utf8
Severity set to `important'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
severity 346474 important
thanks
First off, truncated output becuase you've chosen an unreasonable
charset conversion is not a case of data loss, as the original files
haven't been modulated in any way; it's merely a case of undesirable
output. I'm lowering the severity below the RC threshold beca
Processing commands for [EMAIL PROTECTED]:
> severity 337584 important
Bug#337584: libxml-xpath-perl: xpath fails without internet connection
Severity set to `important'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(admin
Drew Parsons wrote:
> I think you've now successfully arranged your system so that your
> default user limit is 8192, correct? You've now
> set /etc/security/limits.conf to provide that. So when you login, ulimit
> -n already shows 8192, and your ant build is good to go, correct? Did
> you make
severity 337584 important
thanks
If the DTD is unavailable and the document actually uses the DTD, not
retrieving the remote DTD will result in different output than if the
remote DTD is present.
What you probably should be doing is providing the DTD that you want
to use to create these XML files
First off, the test is failing if HTML::Entities is installed, as
HTML::Entities escapes things that escapehtml itself doesn't deal with
(which probably is a bug), like ' => '.
Secondly, test 37 in 3b-multipage.t is failing because the script is
testing for the true return of a function which doe
On Thu, 2006-02-23 at 16:19 +0100, Christoffer Hammarström wrote:
>
> How about only setting the ulimit to 1024 if it's lower than 1024?
>
> I want to contribute something useful to this discussion :)
> I believe something like the following patch should fix the problem:
>
> --- xprint 200
Processing commands for [EMAIL PROTECTED]:
> severity 350359 important
Bug#350359: libapache-mod-perl unable to install or remove - breaks apt.
Severity set to `important'.
> tag 350359 unreproducible
Bug#350359: libapache-mod-perl unable to install or remove - breaks apt.
There were no tags set.
severity 350359 important
tag 350359 unreproducible
thanks
I attempted to reproduce this bug in a fresh sid chroot and was unable
to do so; as there isn't any additional detail which can be used to
figure out what exactly happened here, I'm downgrading and marking it
as unreproducible.
Apache Mai
Package: steghide
Version: 0.5.1-7
Severity: serious
From my pbuilder build log:
...
if g++ -DHAVE_CONFIG_H -I. -I. -I.. -DLOCALEDIR=\"/usr/share/locale\" -O2
-Wall -MT MHashPP.o -MD -MP -MF ".deps/MHashPP.Tpo" \
-c -o MHashPP.o `test -f 'MHashPP.cc' || echo './'`MHashPP.cc; \
Package: gnat-glade
Version: 3.15p-8
Severity: serious
From my pbuilder build log:
...
: # Building gnatdist
gnatmake -Pgnatdist.gpr -o gnatdist
gnatdist.gpr:2:06: unknown project file: "/usr/share/ada/adainclude/gnatvsn.gpr"
gnatmake: "gnatdist.gpr" processing failed
make: *** [gnatdist] Error 4
Package: kernel-source-2.2.25
Version: 2.2.25-4
Severity: serious
From my pbuilder build log:
...
== making target debian/stamp-kernel-conf [new prereqs: .config
Makefile]==
/usr/bin/makeARCH=i386 \
oldconfig
make[2]: Entering directory `/tmp/buildd/kernel-source-2.2.
Your message dated Fri, 24 Feb 2006 10:31:55 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in libsigc++-1.2_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 your res
Package: loop-aes-source
Version: 3.1c-2
Severity: serious
From my pbuilder build log:
...
dh_installdocs
dh_install
cp: cannot stat `./debian/patches': No such file or directory
dh_install: command returned error code 256
make: *** [binary-indep] Error 1
--
Daniel Schepler
Package: e2undel
Version: 0.8-7
Severity: serious
From my pbuilder build log:
...
gcc -Wall -g -o e2undel e2undel-file.o\
find_del.o log.o apprentice.o ascmagic.o is_tar.o softmagic.o -lext2fs
-lcom_err -lss
gcc: e2undel-file.ofind_del.o: No such file or directory
make[1]: *** [e2undel-f
Package: newlib
Version: 1.14.0-1
Severity: serious
From my pbuilder build log:
...
make[3]: Entering directory `/tmp/buildd/newlib-1.14.0/_build/etc'
for f in standards.info configure.info; do \
if test -f ../../etc/`echo $f | sed -e 's/.info$/.texi/'`; then \
if /usr/bin/m
Package: mailfilter
Version: 0.6.2-1
Severity: serious
From my pbuilder build log:
...
if g++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include -I../src
-DLOCALEDIR=\"/usr/share/locale\" -I../intl -Wall -Wno-deprecated -g -O2 -MT
mailfilter.o -MD -MP -MF ".deps/mailfilter.Tpo" \
-c -o mai
Package: autoproject
Version: 0.17-1
Severity: serious
From my pbuilder build log:
...
dh_gencontrol
dh_gencontrol: Compatibility levels before 4 are deprecated.
dpkg-gencontrol: warning: no utmp entry available and LOGNAME not defined;
using uid of process (0)
dpkg-architecture: warning: no utm
Package: tar
Version: 1.15.1-2
Severity: serious
Justification: fails to build from source
Hi,
tar 1.15.1-3 FTBFS on many archs with the following error:
[...]
/bin/sh /build/buildd/tar-1.15.1/config/missing --run autom4te
--language=autotest -I . testsuite.at -o testsuite.tmp
/build/buildd/tar
Your message dated Fri, 24 Feb 2006 09:38:15 +0100
with message-id <[EMAIL PROTECTED]>
and subject line fixed in libsigc++-2.0, not libsigc++-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 n
1 - 100 of 103 matches
Mail list logo
