Your message dated Tue, 25 Jul 2006 21:47:14 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#322856: fixed in libggi 1:2.2.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 Tue, 25 Jul 2006 21:47:14 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#366726: fixed in libggi 1:2.2.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 Tue, 25 Jul 2006 21:47:14 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#297147: fixed in libggi 1:2.2.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
On Tue, Jul 25, 2006 at 09:16:12PM -0300, Gustavo Noronha Silva wrote:
> Hey!
>
> Em Tue, 25 Jul 2006 04:25:15 +0200
> David Weinehall <[EMAIL PROTECTED]> escreveu:
>
> > /usr/share/python-support/python-kiwi/kiwi-1.9.8.egg-info/SOURCES.txt
> > /var/lib/python-support/python2.4/kiwi-1.9.8.egg-inf
Your message dated Tue, 25 Jul 2006 19:47:18 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#379876: fixed in sgt-puzzles 6739-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 message dated Tue, 25 Jul 2006 19:17:02 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#379247: fixed in wmbattery 2.26
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
Package: rsrce
Version: 0.2.1
Severity: serious
Tags: pending
There's a problem with the way htons() is used by the code for parsing
resource forks in resource.c, which causes a failure when reading files
on big-endian architectures. This bug has been reported and a patch
has been provided by Piot
Processing commands for [EMAIL PROTECTED]:
> clone 379527 -1
Bug#379527: sgt-puzzles: help of puzzles not working
Bug 379527 cloned as bug 379876.
> retitle -1 sgt-puzzles: help files stored in /usr/share/doc against policy
> 12.3
Bug#379876: sgt-puzzles: help of puzzles not working
Changed Bug
Hey!
Em Tue, 25 Jul 2006 04:25:15 +0200
David Weinehall <[EMAIL PROTECTED]> escreveu:
> /usr/share/python-support/python-kiwi/kiwi-1.9.8.egg-info/SOURCES.txt
> /var/lib/python-support/python2.4/kiwi-1.9.8.egg-info/SOURCES.txt
> Traceback (most recent call last):
> File "/usr/sbin/update-python-
clone 375835 -1
reassign -1 nice
severity 375835 important
thanks
On Tue, Jul 25, 2006 at 12:04:06PM -0400, Mike O'Connor wrote:
> The line the compilation of nice fails on is:
> CLASSPATH=classes JAVA="kaffe -Dnice.inlined=classes-inline"
> bin/nicec.bootstrap --exclude-runtime -d classes.old
Artur R. Czechowski wrote:
> Package: gajim
> Version: 0.10.1-4
> Severity: serious
>
> Setting up gajim (0.10.1-4) ...
> Traceback (most recent call last):
> File "/usr/bin/pycentral", line 1375, in ?
> main()
> File "/usr/bin/pycentral", line 1369, in main
> rv = action.run(global_op
Processing commands for [EMAIL PROTECTED]:
> clone 375835 -1
Bug#375835: nice: FTBFS (amd64+i386): java/lang/StackOverflowError
Bug 375835 cloned as bug 379871.
> reassign -1 nice
Bug#379871: nice: FTBFS (amd64+i386): java/lang/StackOverflowError
Bug reassigned from package `kaffe' to `nice'.
>
Your message dated Tue, 25 Jul 2006 16:17:04 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#379820: fixed in knetworkmanager 0.09+0.1r560817-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
Can confirm this bug.
Doesn't work with the "libxt-dev" package removed, works with
"libxt-dev" package installed. Patch included.
--
Thomas Perl -- em: [EMAIL PROTECTED]
im: [EMAIL PROTECTED] | ww: www.perli.net
--- wmbattery-2.25/debian/control 2006-01-25 05:55:17.0 +0100
+++ wmbattery
Hi,
is there any progress with this bug? It's been open for nearly a
month now.
I understand that you're working on a new version in the svn repo,
but fixing this ASAP in unstable would be a good idea.
Either by preparing an upload based on 1.9.33-0.1 + patch or by
getting the code in the svn in s
On Tue, Jul 25, 2006 at 12:46:30PM +1000, Brendan O'Dea wrote:
> Ryan believes that the problem with MIPS is a kernel issue, and was
> planning to upgrade the kernel on the buildds soonish.
>
> As far as hppa goes, perl-5.8.8-5 successfully autobuilt on bld-3, then
> -6 failed on the same machine.
Your message dated Tue, 25 Jul 2006 16:02:16 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#379824: fixed in kpowersave 0.6.2-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
Package: rxvt-unicode
Version: 7.8-1
Severity: grave
Justification: renders package unusable
The package is build with gcc4.2 from experimental and thus depends on
libgcc1 from experimental which causes it to be uninstallable in Sid:
rxvt-unicode: Depends: libgcc1 (>= 1:4.2-20060707) but 1:4.1.1
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.20
> # off-by-one finger error
> tags 378511 - wontfix
Bug#378511: libxml2-dev: libxml2.la's dependency_libs contains -lz, but
zlib1g-dev|libz-dev is not depended upon anymore
Tags were:
Your message dated Tue, 25 Jul 2006 15:47:05 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#379826: fixed in kdesvn 0.9.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 you
Package: lib32bz2-1.0
Version: 1.0.3-3
Severity: serious
Justification: Policy 6.6(4)
lib32bz2-1.0 and lib32bz2-dev install their files into /usr/lib32.
However, that path is a symlink (owned by libc6-i386) to
/emul/ia32-linux/usr/lib, which other packages should populate
*directly*.
-- System In
Package: mock
Version: 0.4-3
Severity: serious
Justification: Policy 6.6(4)
On amd64, mock installs libselinux-mock.so into /usr/lib64, which is
actually a libc6-owned symlink to /usr/lib, in which
libselinux-mock.so should directly live on all architectures, even
those that certain other distribu
Processing commands for [EMAIL PROTECTED]:
> severity 378617 important
Bug#378617: abcde: internal error: cddb-choice not recorded
Severity set to `important' from `grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(admi
Processing commands for [EMAIL PROTECTED]:
> severity 379848 normal
Bug#379848: depends on libkrb5-dev and suggests heimdal-dev, but libkrb5-dev
conflicts heimdal-dev
Severity set to `normal' from `serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug
Steve Langasek wrote:
> On Tue, Jul 25, 2006 at 05:22:20PM +0530, Kumar Appaiah wrote:
>> On Tue, Jul 25, 2006 at 06:23:17PM +0800, LI Daobing wrote:
>>> -- System Information:
>>> Debian Release: testing/unstable
>>> APT prefers unstable
>>> APT policy: (500, 'unstable')
>>> Architecture: amd64
severity 379848 normal
thanks
* RISKO Gergely [Tue, 25 Jul 2006 22:50:49 +0200]:
> Package: libpq-dev
> Version: 8.1.4-4
> Severity: serious
> There is no reason to suggest a package, which can't be installed while
> the dependent ones are.
But it is not of release critical severity, either. Re
Processing commands for [EMAIL PROTECTED]:
> tag 379744 + fixed
Bug#379744: python-goopy: no python file in this package
There were no tags set.
Tags added: fixed
> quit
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator,
Your message dated Tue, 25 Jul 2006 13:47:52 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#366831: fixed in asclassic 1.1b-29
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 Tue, 25 Jul 2006 13:47:52 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#350782: fixed in asclassic 1.1b-29
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: cyrus-sasl2
Severity: serious
SSIA, it seems that libpq-dev's libkrb5-dev dependency is a new thing.
Don't know, how to fix, since we want psql modules and heimdal kerberos
modules too...
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500,
Package: libpq-dev
Version: 8.1.4-4
Severity: serious
There is no reason to suggest a package, which can't be installed while
the dependent ones are.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.20
> reassign 379807 libxml2-dev
Bug#379807: Causes other packages to FTBFS
Bug reassigned from package `libxml2' to `libxml2-dev'.
> severity 378511 grave
Bug#378511: libxml2-dev: libxml
Your message dated Tue, 25 Jul 2006 13:47:52 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#346652: fixed in asclassic 1.1b-29
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 Tue, 25 Jul 2006 22:01:38 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Package: pcmciautils
Severity: serious
Justification: Policy 9.3.1
# cat /var/lib/dpkg/info/pcmciautils.postinst
[...]
# Remove shutdown and reboot links;
# this init script does not need them.
if dpkg --compare-versions "$2" lt 014-2; then
Your message dated Tue, 25 Jul 2006 21:55:22 +0200
with message-id <[EMAIL PROTECTED]>
and subject line removed
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 t
Your message dated Tue, 25 Jul 2006 21:50:25 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Aurelien is on holidays. Can someone please NMU.
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Your message dated Tue, 25 Jul 2006 22:19:35 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 25 Jul 2006 21:55:22 +0200
with message-id <[EMAIL PROTECTED]>
and subject line removed
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 t
Your message dated Tue, 25 Jul 2006 22:18:04 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 25 Jul 2006 21:55:22 +0200
with message-id <[EMAIL PROTECTED]>
and subject line removed
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 t
Your message dated Tue, 25 Jul 2006 22:18:04 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 25 Jul 2006 22:19:35 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 25 Jul 2006 22:18:04 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 25 Jul 2006 22:01:38 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
* Martin Michlmayr <[EMAIL PROTECTED]> [2006-07-25 21:02:45 +0200]:
> Package: scribus
> Version: 1.2.4.1.dfsg-1
> Severity: serious
>
> Your package fails to build from source because it doesn't recognize
> Autoconf 2.60. A patch similar to
> http://websvn.kde.org/branches/KDE/3.5/kde-common/ad
Your message dated Tue, 25 Jul 2006 22:03:48 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 25 Jul 2006 22:18:04 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 25 Jul 2006 22:25:48 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#379828: FTBFS: doesn't recognize autoconf 2.60
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 cas
Your message dated Tue, 25 Jul 2006 22:21:45 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 25 Jul 2006 22:18:04 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 25 Jul 2006 22:03:48 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 25 Jul 2006 22:01:38 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Package: kde-style-polyester
Version: 0.9.2-1
Severity: serious
Your package fails to build from source because it doesn't recognize
Autoconf 2.60. A patch similar to
http://websvn.kde.org/branches/KDE/3.5/kde-common/admin/cvs.sh?rev=555946&r1=543983&r2=555946
should fix this problem. For some b
Package: kdesvn
Version: 0.8.5-1
Severity: serious
Your package fails to build from source because it doesn't recognize
Autoconf 2.60. A patch similar to
http://websvn.kde.org/branches/KDE/3.5/kde-common/admin/cvs.sh?rev=555946&r1=543983&r2=555946
should fix this problem. For some background, pl
Package: kdegames
Version: 4:3.5.2-1
Severity: serious
Your package fails to build from source because it doesn't recognize
Autoconf 2.60. A patch similar to
http://websvn.kde.org/branches/KDE/3.5/kde-common/admin/cvs.sh?rev=555946&r1=543983&r2=555946
should fix this problem. For some background
Package: xwnc
Version: 0.3.3-8
Severity: serious
Your package fails to build from source because it doesn't recognize
Autoconf 2.60.
> Automatic build of xwnc_0.3.3-8 on prehension by sbuild/sparc 0.47
...
> sh bootstrap
> found automake version: 1.7.9 (1.7.x or better required)
> found libtool
Package: kpowersave
Version: 0.6.2-1
Severity: serious
Your package fails to build from source because it doesn't recognize
Autoconf 2.60. A patch similar to
http://websvn.kde.org/branches/KDE/3.5/kde-common/admin/cvs.sh?rev=555946&r1=543983&r2=555946
should fix this problem. For some background
Package: kxmleditor
Version: 1.1.4-3
Severity: serious
Your package fails to build from source because it doesn't recognize
Autoconf 2.60. A patch similar to
http://websvn.kde.org/branches/KDE/3.5/kde-common/admin/cvs.sh?rev=555946&r1=543983&r2=555946
should fix this problem. For some background
Package: kile
Version: 1:1.9.1-1
Severity: serious
Your package fails to build from source because it doesn't recognize
Autoconf 2.60. A patch similar to
http://websvn.kde.org/branches/KDE/3.5/kde-common/admin/cvs.sh?rev=555946&r1=543983&r2=555946
should fix this problem. For some background, pl
For reference, the discussion is at
http://lists.debian.org/debian-devel/2006/07/msg00961.html
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: keybled
Version: 0.65-6
Severity: serious
Your package fails to build from source because it doesn't recognize
Autoconf 2.60. A patch similar to
http://websvn.kde.org/branches/KDE/3.5/kde-common/admin/cvs.sh?rev=555946&r1=543983&r2=555946
should fix this problem. For some background, pl
Package: klog
Version: 0.3.3-2
Severity: serious
Your package fails to build from source because it doesn't recognize
Autoconf 2.60. A patch similar to
http://websvn.kde.org/branches/KDE/3.5/kde-common/admin/cvs.sh?rev=555946&r1=543983&r2=555946
should fix this problem. For some background, plea
Package: yakuake
Version: 2.7.5-1
Severity: serious
Your package fails to build from source because it doesn't recognize
Autoconf 2.60. A patch similar to
http://websvn.kde.org/branches/KDE/3.5/kde-common/admin/cvs.sh?rev=555946&r1=543983&r2=555946
should fix this problem. For some background, p
Processing commands for [EMAIL PROTECTED]:
> clone 379628 -1
Bug#379628: ntfsresize: resizing a Vista NTFS partition leads to corrupted
partition
Bug 379628 cloned as bug 379835.
> reassign -1 partman-partitioning 40
Bug#379835: ntfsresize: resizing a Vista NTFS partition leads to corrupted
par
Package: scribus
Version: 1.2.4.1.dfsg-1
Severity: serious
Your package fails to build from source because it doesn't recognize
Autoconf 2.60. A patch similar to
http://websvn.kde.org/branches/KDE/3.5/kde-common/admin/cvs.sh?rev=555946&r1=543983&r2=555946
should fix this problem. For some backgr
Package: kdeedu
Version: 4:3.5.2-1
Severity: serious
Your package fails to build from source because it doesn't recognize
Autoconf 2.60. A patch similar to
http://websvn.kde.org/branches/KDE/3.5/kde-common/admin/cvs.sh?rev=555946&r1=543983&r2=555946
should fix this problem. For some background,
Package: konserve
Version: 0.10.3-2.1
Severity: serious
Your package fails to build from source because it doesn't recognize
Autoconf 2.60. A patch similar to
http://websvn.kde.org/branches/KDE/3.5/kde-common/admin/cvs.sh?rev=555946&r1=543983&r2=555946
should fix this problem. For some backgroun
Package: knetworkmanager
Version: 0.09+0.1r550737-1
Severity: serious
Your package fails to build from source because it doesn't recognize
Autoconf 2.60. A patch similar to
http://websvn.kde.org/branches/KDE/3.5/kde-common/admin/cvs.sh?rev=555946&r1=543983&r2=555946
should fix this problem. For
Package: kdbg
Version: 2.0.4-1
Severity: serious
Your package fails to build from source because it doesn't recognize
Autconf 2.60. A patch similar to
http://websvn.kde.org/branches/KDE/3.5/kde-common/admin/cvs.sh?rev=555946&r1=543983&r2=555946
should fix this problem. For some background, pleas
Your message dated Tue, 25 Jul 2006 11:47:23 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#379536: fixed in hydrogen-drumkits 0.9.3.20060702-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 th
Package: ksubtile
Version: 1.2-4
Severity: serious
Your package fails to build from source because it doesn't recognize
Autoconf 2.60. A patch similar to
http://websvn.kde.org/branches/KDE/3.5/kde-common/admin/cvs.sh?rev=555946&r1=543983&r2=555946
should fix this problem. For some background, pl
Package: quiteinsanegimpplugin
Version: 0.3-6
Severity: serious
Your package fails to build from source because it doesn't recognize
Autoconf 2.60. A patch similar to
http://websvn.kde.org/branches/KDE/3.5/kde-common/admin/cvs.sh?rev=555946&r1=543983&r2=555946
should fix this problem. For some b
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.20
> # please take care of your bug state!
> notfound 364800 2.32-2
Bug#364800: no answer to dnsmasq broadcasts
Bug marked as not found in version 2.32-2.
(By the way, this Bug is current
Your message dated Tue, 25 Jul 2006 20:41:04 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 25 Jul 2006 20:44:20 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 25 Jul 2006 20:44:20 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 25 Jul 2006 20:44:20 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 25 Jul 2006 20:39:59 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 25 Jul 2006 20:44:20 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Package: libxml2
Severity: grave
A number of packages fail with a "cannot find -lz" error due to
libxml2.
- Forwarded message from Steve Langasek <[EMAIL PROTECTED]> -
From: Steve Langasek <[EMAIL PROTECTED]>
Subject: Re: Build failure: cannot find -lz
Date: Tue, 25 Jul 2006 11:16:30 -0
Your message dated Tue, 25 Jul 2006 11:32:20 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#376403: fixed in xcalendar-i18n 4.0.0.i18p1-14
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 cas
Your message dated Tue, 25 Jul 2006 20:39:34 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 25 Jul 2006 11:32:20 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#346794: fixed in xcalendar-i18n 4.0.0.i18p1-14
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 cas
Your message dated Tue, 25 Jul 2006 20:42:19 +0200
with message-id <[EMAIL PROTECTED]>
and subject line removed
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 t
Your message dated Tue, 25 Jul 2006 20:44:20 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 25 Jul 2006 20:42:19 +0200
with message-id <[EMAIL PROTECTED]>
and subject line removed
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 t
Your message dated Tue, 25 Jul 2006 20:44:20 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 25 Jul 2006 20:44:20 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 25 Jul 2006 11:47:26 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#194985: fixed in lphdisk 0.9.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 yo
Your message dated Tue, 25 Jul 2006 20:41:04 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 25 Jul 2006 20:44:20 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 25 Jul 2006 20:45:19 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
Your message dated Tue, 25 Jul 2006 11:32:16 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#379752: fixed in gst-plugins-bad0.10 0.10.3-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, 25 Jul 2006 20:44:51 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 t
On Tue, Jul 25, 2006 at 05:22:20PM +0530, Kumar Appaiah wrote:
> On Tue, Jul 25, 2006 at 06:23:17PM +0800, LI Daobing wrote:
> > -- System Information:
> > Debian Release: testing/unstable
> > APT prefers unstable
> > APT policy: (500, 'unstable')
> > Architecture: amd64 (x86_64)
> > Shell: /bin
On 7/25/06, Hans Fugal <[EMAIL PROTECTED]> wrote:
From README.Debian:
The scansyn and scansynx opcodes have a license incompatible with the
Debian Free Software Guidelines. They have therefore been omitted from
this build of Csound.
If the files sneaked back into the source tarball someho
Your message dated Tue, 25 Jul 2006 18:52:27 +0200
with message-id <[EMAIL PROTECTED]>
and subject line libgnatprj4.1 needs prio optional in the override file
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
Package: silc-toolkit
Version: 0.9.12-4.3
Severity: serious
Justification: Policy 8.4
$ dpkg-deb --contents libsilc-1.0-2_0.9.12-4.3_i386.deb |grep 'so '
lrwxrwxrwx root/root 0 2006-07-25 18:07 ./usr/lib/libsilc.so ->
libsilc-1.0.so.2.1.0
lrwxrwxrwx root/root 0 2006-07-25 18:07 ./
1 - 100 of 179 matches
Mail list logo
