Your message dated Tue, 24 Jul 2007 06:17:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#434338: fixed in libfontbox-java 0.1.0.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
Your message dated Tue, 24 Jul 2007 06:17:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#434031: fixed in kqemu 1.3.0~pre11-6
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 no
Package: ttf-sil-gentium
Version: 1.02+dfsg-3
Severity: grave
Justification: renders package unusable
ttf-sil-gentium conflicts with its transition package ttf-gentium, making
ttf-gentium uninstallable, and thus making any package which depends on
ttf-gentium (such as tuxtype) uninstallable as wel
Your message dated Tue, 24 Jul 2007 03:02:10 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#425913: fixed in kdepim 4:3.5.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 y
Your message dated Tue, 24 Jul 2007 03:02:10 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#425621: fixed in kdepim 4:3.5.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 y
Luk Claes wrote:
> [...]
> Not following policy because of some sid users' inconvenience is not the way
> to go IMHO.
>
> Note that we are thinking about fixing it globally somehow...
That makes sense and is good news. Thanks for the info.
Kevin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
w
Your message dated Tue, 24 Jul 2007 02:02:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#421956: fixed in xemacs21 21.4.20-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 n
Processing commands for [EMAIL PROTECTED]:
> # the following bugs are closed by packages in NEW
> #
> tags 430286 pending
Bug#430286: ldbl128 transition for alpha, powerpc, sparc, s390
Tags were: patch sid lenny
Tags added: pending
> tags 433214 pending
Bug#433214: gambas2: Please remove udeb
Tag
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.5ubuntu2
> severity 404125 grave
Bug#404125: libpoe-component-jabber-perl: new upstream version available: 1.21
Severity set to `grave' from `normal'
>
End of message, stopping processin
On Mon, 23 Jul 2007, Kees Cook wrote:
Hi! Thanks for reporting this.
It looks like this is actually a problem in libpoe-component-jabber-perl
(see bug #404125). I suspect I can work around it with some Perl
tricks, but in the meantime I will raise the priority of the other bug.
Thanks. Sorr
Hi! Thanks for reporting this.
It looks like this is actually a problem in libpoe-component-jabber-perl
(see bug #404125). I suspect I can work around it with some Perl
tricks, but in the meantime I will raise the priority of the other bug.
On Mon, Jul 23, 2007 at 10:46:15PM +0100, Reuben Thoma
* Mykola Nikishov <[EMAIL PROTECTED]> [2007-07-23 23:48]:
> Package: syncropated
> Version: 0.2.0-0ubuntu4
I cannot find this package in Debian and the version information
suggests you obtained in from Ubuntu. If you confirm this, I'll close
this bug in the Debian bug tracker. Please open a new
Your message dated Mon, 23 Jul 2007 22:17:11 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#430485: fixed in libnet-dbus-perl 0.33.5-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
Your message dated Mon, 23 Jul 2007 22:17:11 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#430202: fixed in libnet-dbus-perl 0.33.5-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
Your message dated Mon, 23 Jul 2007 22:17:11 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#430485: fixed in libnet-dbus-perl 0.33.5-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
Your message dated Mon, 23 Jul 2007 22:17:11 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#430485: fixed in libnet-dbus-perl 0.33.5-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
Your message dated Mon, 23 Jul 2007 22:17:11 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#431826: fixed in libnet-dbus-perl 0.33.5-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
Your message dated Mon, 23 Jul 2007 22:17:11 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#431826: fixed in libnet-dbus-perl 0.33.5-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
Your message dated Mon, 23 Jul 2007 22:17:11 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#430669: fixed in libnet-dbus-perl 0.33.5-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
Your message dated Mon, 23 Jul 2007 22:17:11 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#430669: fixed in libnet-dbus-perl 0.33.5-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
Your message dated Mon, 23 Jul 2007 22:17:11 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#430657: fixed in libnet-dbus-perl 0.33.5-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
Your message dated Mon, 23 Jul 2007 22:17:11 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#430657: fixed in libnet-dbus-perl 0.33.5-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
Your message dated Mon, 23 Jul 2007 22:17:11 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#430657: fixed in libnet-dbus-perl 0.33.5-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
Your message dated Mon, 23 Jul 2007 22:17:11 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#430657: fixed in libnet-dbus-perl 0.33.5-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
Your message dated Mon, 23 Jul 2007 22:17:11 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#430202: fixed in libnet-dbus-perl 0.33.5-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
Your message dated Mon, 23 Jul 2007 22:17:11 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#430202: fixed in libnet-dbus-perl 0.33.5-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
Your message dated Mon, 23 Jul 2007 22:17:11 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#430202: fixed in libnet-dbus-perl 0.33.5-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
Your message dated Mon, 23 Jul 2007 22:17:11 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#430485: fixed in libnet-dbus-perl 0.33.5-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
Your message dated Mon, 23 Jul 2007 22:17:11 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#430669: fixed in libnet-dbus-perl 0.33.5-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
Your message dated Mon, 23 Jul 2007 22:17:11 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#430657: fixed in libnet-dbus-perl 0.33.5-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
Your message dated Mon, 23 Jul 2007 22:17:11 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#430669: fixed in libnet-dbus-perl 0.33.5-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
Your message dated Mon, 23 Jul 2007 22:17:11 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#430657: fixed in libnet-dbus-perl 0.33.5-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
Your message dated Mon, 23 Jul 2007 22:17:11 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#431826: fixed in libnet-dbus-perl 0.33.5-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
Your message dated Mon, 23 Jul 2007 22:17:11 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#431826: fixed in libnet-dbus-perl 0.33.5-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
Your message dated Mon, 23 Jul 2007 22:17:11 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#430669: fixed in libnet-dbus-perl 0.33.5-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
Your message dated Mon, 23 Jul 2007 22:17:11 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#430669: fixed in libnet-dbus-perl 0.33.5-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
Your message dated Mon, 23 Jul 2007 22:17:11 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#430202: fixed in libnet-dbus-perl 0.33.5-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
Your message dated Mon, 23 Jul 2007 22:17:11 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#430485: fixed in libnet-dbus-perl 0.33.5-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
Your message dated Mon, 23 Jul 2007 22:17:11 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#431826: fixed in libnet-dbus-perl 0.33.5-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
Your message dated Mon, 23 Jul 2007 22:17:11 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#430485: fixed in libnet-dbus-perl 0.33.5-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
Your message dated Mon, 23 Jul 2007 22:17:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#432543: fixed in iso-codes 1.3-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
Your message dated Mon, 23 Jul 2007 22:17:11 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#430202: fixed in libnet-dbus-perl 0.33.5-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
Your message dated Mon, 23 Jul 2007 22:17:11 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#431826: fixed in libnet-dbus-perl 0.33.5-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
On Thursday 12 July 2007, Alex Henry wrote:
> The bug has manifested again!
To quote my previous email:
> > It would be really nice if we could get several pieces of interesting
> > information.
> >
> > Is it just a plain text file on your local harddrive? or do you use nfs?
> > or some netwo
Package: jirc
Version: 0.5-1
Severity: grave
Justification: renders package unusable
When I run jirc I get the following error:
$ jirc
Can't locate POE/Preprocessor.pm in @INC (@INC contains:
/home/rrt/local/share/perl5 /etc/perl /usr/local/lib/perl/5.8.8
/usr/local/share/perl/5.8.8 /usr/lib/pe
Processing commands for [EMAIL PROTECTED]:
> forwarded 428972 http://bugzilla.gnome.org/show_bug.cgi?id=459726
Bug#428972: doxygen: Segfault after reading Doxyfile
Noted your statement that Bug has been forwarded to
http://bugzilla.gnome.org/show_bug.cgi?id=459726.
> tags 428972 + upstream
Bug#4
clone 434344 -1
reassign -1 libmasonx-interp-withcallbacks-perl 1.16-1
retitle 434344 libhtml-mason-perl: missing dependency on libhtml-parser-perl
retitle -1 libmasonx-interp-withcallbacks-perl: change in HTML::Mason 1.36
breaks the tests
tag -1 patch
thanks
On Mon, Jul 23, 2007 at 05:56:11PM +0
Processing commands for [EMAIL PROTECTED]:
> clone 434344 -1
Bug#434344: libmasonx-interp-withcallbacks-perl - FTBFS: Can't locate
HTML/Entities.pm in @INC
Bug 434344 cloned as bug 434445.
> reassign -1 libmasonx-interp-withcallbacks-perl 1.16-1
Bug#434445: libmasonx-interp-withcallbacks-perl -
Josip Rodin ha scritto:
On Sat, Jul 21, 2007 at 03:53:53PM +0200, Josip Rodin wrote:
Can we avoid removing this package, and instead just build the up to date
version from it? It has sources for 1.x and 2.x in the same source package.
If nobody disagrees, I'll take it over, modify it to buil
Package: pysycache
Followup-For: Bug #433197
I updated python-pygame up to 1.7.1release-4.1+b1 and problem has
disappeared.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'gutsy'), (99, 'unstable'), (9,
'experimental'), (1, 'stable')
Package: syncropated
Version: 0.2.0-0ubuntu4
Severity: grave
Tags: patch
Justification: renders package unusable
While starting with Python 2.4 it dies with:
Traceback (most recent call last):
File "/usr/bin/syncropated", line 24, in ?
from syncropated.Syncropated import init_app; init_app(
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.1
> merge 431721 434425
Bug#431721: ekg: security update version 1:1.7~rc2-1etch1 fails to install on
etch
Bug#434425: ekg cannot be installed.
Merged 431721 434425.
>
End of message, s
Package: apt-show-versions
Version: 0.10
Severity: serious
Justification: apt-show-versions installable in Etch
In this specific machine I get this error, but I've tried in other etch's and
can't reproduce this.
Any idea of what's going wrong here?
# aptitude install apt-show-versions
Reading
-- Forwarded message --
Date: 2007-07-23 06:47:21 +0200
From: Okan Arikan <[EMAIL PROTECTED]>
Subject: Re: pixie is now officially part of debian
Hi Gurkan,
Yes, we're working on this problem. The next version of Pixie has an
updated interpreter that should play
Package: ekg
Version: 1:1.7~rc2-1etch1
Severity: grave
Dist/Arch: debian-stable, i386.
ekg refuses to install on debian-stable.
Here's the log of the install.
[log]
# apt-get install ekg
Reading package lists... Done
Building dependency tree... Done
Some packages could not be installed. This ma
Your message dated Mon, 23 Jul 2007 19:02:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#434358: fixed in cl-sql 3.8.6.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 now y
Hello,
I want to confirm this bug. It seems coincidentally that the problem
arose when libgmime2.0-2 was upgraded from 2.2.9-1 to 2.2.10-1. ;)
Paul
--
PhD Student @ Eindhoven | email: [EMAIL PROTECTED]
University of Technology, The Netherlands | JID: [EMAIL PROTECTED]
>>>
Processing commands for [EMAIL PROTECTED]:
> severity 434275 important
Bug#434275: zdiff show no difference when comparing two gzipped files
Severity set to `important' from `serious'
>
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking syste
Package: lustre
Version: 1.6.0.1-1
Severity: critical
Tags: upstream confirmed
Justification: causes serious data loss
Hello,
using 1.6.0.1-1 with kernel 2.6.18 can result in complete filesystem
corruption.
https://bugzilla.lustre.org/show_bug.cgi?id=11039
1.6.1 (not yet released) will fix this
Your message dated Mon, 23 Jul 2007 18:33:35 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#432345: fixed in lustre 1.6.0.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
Package: kvirc
Version: 2:3.2.4-5
Severity: grave
Tags: security
Justification: user security hole
Nothing more to say beyond what is in the CVE report:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-2951
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy
Processing commands for [EMAIL PROTECTED]:
> owner 434410 !
Bug#434410: suitesparse: FTBFS: ld: cannot find -lmetis
Owner recorded as "Daniel Rus Morales" <[EMAIL PROTECTED]>.
> fixed 434410 3.0.0-5
Bug#434410: suitesparse: FTBFS: ld: cannot find -lmetis
Bug marked as fixed in version 3.0.0-5.
>
Zack Weinberg writes:
> 0.36 should be ready in a few days; upstream proceeds with boost
> removal, but it won't happen for that release. More likely 0.37. My
> inclination is to leave Architecture: alone for the 0.36 release --
> perhaps it will miraculously start working on arm, after all.
Agr
Processing commands for [EMAIL PROTECTED]:
> severity 434275 serious
Bug#434275: zdiff show no difference when comparing two gzipped files
Severity set to `serious' from `normal'
>
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system adm
Processing commands for [EMAIL PROTECTED]:
> tags 434031 +pending
Bug#434031: kqemu-source: doesn't build with 2.6.22
Tags were: patch
Tags added: pending
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian
Package: librudiments0.30ldbl
Version: 0.30-2
Severity: serious
Justification: Policy 7.5
A dist-upgrade just failed because dpkg didn't let librudiments0.30ldbl take
over the library which is owned by librudiments0.30 (I don't paste the usual
message because it's in french here).
You should conf
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.6
> tags 429022 + lenny sid
Bug#429022: haskell-src-exts: needs update for ghc 6.6.1
There were no tags set.
Tags added: lenny, sid
>
End of message, stopping processing here.
Please con
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.6
> found 434344 1:1.36-1
Bug#434344: libmasonx-interp-withcallbacks-perl - FTBFS: Can't locate
HTML/Entities.pm in @INC
Bug marked as found in version 1:1.36-1.
>
End of message, stopp
Package: suitesparse
Version: 3.0.0-4
Severity: serious
Hi,
Your package is failing to build with the following error:
/usr/bin/ld: cannot find -lmetis
collect2: ld returned 1 exit status
make[5]: *** [libcholmod.so.1.2] Error 1
Kurt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subj
Processing commands for [EMAIL PROTECTED]:
> reassign 434225 fuse
Bug#434225: ntfs-3g: FTBFS: cannot find -lselinux
Bug reassigned from package `ntfs-3g' to `fuse'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrat
reassign 434225 fuse
thanks
On Mon, Jul 23, 2007 at 10:31:41AM +0200, Cyril Brulebois wrote:
> "Adam Cécile (Le_Vert)" <[EMAIL PROTECTED]> (23/07/2007):
> > Hi,
>
> Hi,
>
> [yeah, let's forget about honouring the Reply-To, that's considered a
> good practice (#434149). Anyway, submitter added ba
Package: kdelibs4c2a
Version: 4:3.5.7.dfsg.1-2
Severity: critical
--- Please enter the report below this line. ---
I upgraded my Sid today and ldconfig give me this output:
ldconfig: Datei »/usr/lib/libkjs.so.1« ist am Ende abgeschnitten
ldconfig: Datei »/usr/lib/libkhtml.so.4« ist am Ende abg
I have found an easy way to fix this problem on the following webpage :
http://forums.debian.net/viewtopic.php?p=85884&sid=253f85fa345866026fbf582e1c54e2b3
Basically you just need to change every 'sda' to 'hda' in your /etc/fstab
file, and also in the entries for the new kernel in your /boot/grub
Riku Voipio wrote:
> 8 months later it is certain that this package isn't needed, no? iwl3945
> works with in-kernel stack and iwlwifi is going to replace that anyway.
it seems so, yes, as the guy (intending) to take care about ipw2200-ap
didn't show up with a package up to now.. requesting it's r
Your message dated Mon, 23 Jul 2007 17:51:53 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing now that the package has been removed from the archive
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
hi guys,
On Mon, Jul 23, 2007 at 05:28:54PM +0200, gregor herrmann wrote:
> > So... No, I'm using the regular Sid version :-/ I even ran a 'pbuilder
> > update'. It's even scarier: Now _one_ of the tests fails:
>
> Hu, that's really scary.
i can perfectly reproduce the reported error in my sid(a
Your message dated Mon, 23 Jul 2007 17:51:53 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing now that the package has been removed from the archive
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
On Mon, 23 Jul 2007 09:34:23 -0500, Gunnar Wolf wrote:
> > > ...I'm still puzzled on why libmasonx-interp-withcallbacks-perl builds
> > > correctly under my pbuilder :)
> > Is it possible that you have libhtml-mason-perl's from testing
> > installed? It doesn't "use" HTML::Entities but handles the
hi,
just for the record: tidev-modules have been removed from unstable:
http://packages.qa.debian.org/t/tidev-modules/news/20070612T081240Z.html
see also:
http://bugs.debian.org/362162
it seems like those kernel modules are now part of the mainstream kernel, so
are probably still working.
b
gregor herrmann dijo [Mon, Jul 23, 2007 at 05:01:05PM +0200]:
> > ...I'm still puzzled on why libmasonx-interp-withcallbacks-perl builds
> > correctly under my pbuilder :)
>
> Is it possible that you have libhtml-mason-perl's from testing
> installed? It doesn't "use" HTML::Entities but handles th
Kevin Rosenberg wrote:
> Bastian Blank wrote:
>> An arch-any dependency is no reason to make a package also arch-any.
>
> There's a clear reason below. Whether you agree with the reason is a
> separate issue.
>
>> Packages are only moved into testing if they are up-to-date.
>
> That's true. Howe
On Mon, 23 Jul 2007 07:50:32 -0500, Gunnar Wolf wrote:
> > > t/09cgi...Can't locate HTML/Entities.pm in @INC (@INC
> > contains: /build/user/libmasonx-interp-withcallbacks-perl-1.16/blib/lib
> > /build/user/libmasonx-interp-withcallbacks-perl-1.16/blib/arch
> > /build/user/libmason
Processing commands for [EMAIL PROTECTED]:
> tags 430286 + patch
Bug#430286: ldbl128 transition for alpha, powerpc, sparc, s390
Tags were: sid lenny
Tags added: patch
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administr
tags 430286 + patch
thanks
Hi,
Attached is the diff for my openexr 1.2.2-4.4 NMU.
--
Adeodato Simó dato at net.com.org.es
Debian Developer adeodato at debian.org
Listening to: Astrud
Adeodato Simó <[EMAIL PROTECTED]> (23/07/2007):
> The build on mipsel was tried a month an a half later than on other
> arches, so it build against Qt 4.3 instead of 4.2; seems that would've
> been the issue.
At least the package builds fine currently, in an i386 sid chroot, i.e.
against Qt 4.3.
Bastian Blank wrote:
> An arch-any dependency is no reason to make a package also arch-any.
There's a clear reason below. Whether you agree with the reason is a
separate issue.
> Packages are only moved into testing if they are up-to-date.
That's true. However, the change I made fixed a bug for
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.6
> package libfontbox-java
Ignoring bugs not assigned to: libfontbox-java
> tags 434338 + pending
Bug#434338: libfontbox-java - FTBFS: dh_install: libfontbox-java missing files
There we
Hello,
I could reproduce this bug, but only when I updated semantic only,
eg. when I updated cedet-common, eieio and ede, the semantic was
configurable again.
Can you reproduce the bug with these packages on their unstable versions?
Or, can you run dpkg-reconfigure semantic right now?
If it is
Processing commands for [EMAIL PROTECTED]:
> reassign 434344 libhtml-mason-perl
Bug#434344: libmasonx-interp-withcallbacks-perl - FTBFS: Can't locate
HTML/Entities.pm in @INC
Bug reassigned from package `libmasonx-interp-withcallbacks-perl' to
`libhtml-mason-perl'.
> thanks
Stopping processing
reassign 434344 libhtml-mason-perl
thanks
Michael Ablassmeier dijo [Mon, Jul 23, 2007 at 10:28:55AM +0200]:
> Package: libmasonx-interp-withcallbacks-perl
> Version: 1.16-1
> Severity: serious
> User: [EMAIL PROTECTED]
> Usertags: qa-ftbfs-20070717
>
> hi,
>
> while doing an archive wide package
Please test wengophone from unstable (2.1.1.dfsg0-1). It contains many
changes and probably could fix your problem.
Best Regards
--
-
|Marco Nenciarini| Debian/GNU Linux Developer - Plug Member |
| [EMAIL PROTECTED] | h
Package: nvidia-kernel-source
Version: 100.14.11-1
Severity: grave
Justification: renders package unusable
When typing "debian/rules binary_modules" as said in
"/usr/share/doc/nvidia-kernel-source/README.Debian":
cat: /usr/src/linux-headers-2.6.22-1/include/linux/version.h: No such file or
direc
Package: python-qt4
Version: 4.2-1
Severity: serious
Hello. From
http://buildd.debian.org/fetch.cgi?&pkg=python-qt4&ver=4.2-1&arch=mipsel&stamp=1184888555&file=log:
make[2]: Entering directory `/build/buildd/python-qt4-4.2/build-2.5/QtCore'
g++ -c -pipe -fPIC -O2 -Wall -W -D_REENTRANT -DQT_NO_DEB
[ Monday 23 July 2007 ]
| Package: libsuitesparse
| Version: 3.0.0-4
| Severity: serious
| Justification: Policy 2.2.1
|
|
| $ apt-cache show libsuitesparse
| [...]
| Depends: [...], libparmetis3.1
| [...]
| $ apt-cache show libparmetis3.1
| [...]
| Section: non-free/libs
| [...]
suitesparse is not
Package: libsuitesparse
Version: 3.0.0-4
Severity: serious
Justification: Policy 2.2.1
$ apt-cache show libsuitesparse
[...]
Depends: [...], libparmetis3.1
[...]
$ apt-cache show libparmetis3.1
[...]
Section: non-free/libs
[...]
Gabor
-- System Information:
Debian Release: lenny/sid
APT prefe
Processing commands for [EMAIL PROTECTED]:
> severity 434227 important
Bug#434227: kdm: autologin: auto-lock fails when switching terminals
Severity set to `important' from `grave'
> tags 434227 + upstream
Bug#434227: kdm: autologin: auto-lock fails when switching terminals
Tags were: security
Ta
severity 434227 important
tags 434227 + upstream
thanks
Hi,
It is an known upstream bug. They don't know if it is a X or KDM bug.
i lower the bug report severity as kdm autologin feature can be turned off.
cheers,
Fathi
Your message dated Mon, 23 Jul 2007 11:47:05 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#434253: fixed in zeroc-ice 3.2.0-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 is now
Hi.
I have the same problem here. With the following messages:
~$ mail-notification
(mail-notification:3727): GLib-GObject-WARNING **: specified instance size
for type `MNGMimeStreamVFS' is smaller than the parent type's `GMimeStream'
instance size
(mail-notification:3727): GLib-GObject-WARN
Processing commands for [EMAIL PROTECTED]:
> forwarded 434227 http://bugs.kde.org/show_bug.cgi?id=125318
Bug#434227: kdm: autologin: auto-lock fails when switching terminals
Noted your statement that Bug has been forwarded to
http://bugs.kde.org/show_bug.cgi?id=125318.
>
End of message, stopping
1 - 100 of 129 matches
Mail list logo
