Your message dated Fri, 19 Aug 2005 22:32:09 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#323343: fixed in obby 0.2.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 your
Your message dated Fri, 19 Aug 2005 22:32:09 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#323323: fixed in obby 0.2.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 your
Processing commands for [EMAIL PROTECTED]:
tag 274705 + patch
Bug#274705: mv: --reply doesn't work
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
tag 274705 + patch
thanks
So the relevant code seems to be in src/copy.c, where it checks if
--reply=no was set _and_ the file isn't overwritable; or if -i was
set, or if no option was given and the file isn't overwritable. So
--reply=no has an effect when you do:
touch a b
chmod
Anthony Towns aj@azure.humbug.org.au wrote:
tag 274705 + patch
thanks
So the relevant code seems to be in src/copy.c, where it checks if
--reply=no was set _and_ the file isn't overwritable; or if -i was
set, or if no option was given and the file isn't overwritable. So
--reply=no has an
OoO En cette matinée ensoleillée du jeudi 18 août 2005, vers 09:18,
Francesco Paolo Lovergine [EMAIL PROTECTED] disait:
Shouldn't this bug be tagged security ? Moreover, since it is marked
as closed in the BTS, will it be tracked correctly in the future ?
Being now enabled versioning in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello
Am Fr den 19. Aug 2005 um 22:34 schrieb Adeodato Simó:
Severity: grave
The package has no Binary, no /usr/share/doc/kdm or other necesarry
stuff. I wonder why nobody saws this before.
Please check your facts before submitting bugs
Your message dated Sat, 20 Aug 2005 16:51:43 +0900
with message-id [EMAIL PROTECTED]
and subject line soundtracker_0.6.7-6_i386.changes ACCEPTED
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: xfce4-sensors-plugin
Version: 0.6.1-1
Severity: serious
Justification: fails to build from source
xfce4-sensors-plugin failed to build on all buildds, duplicated on my
sparc pbuilder.
if test pre = pre ; then \
cd . libtoolize -c -f ; \
fi
/bin/sh: libtoolize: command not
Blars Blarson [EMAIL PROTECTED] (20/08/2005):
Package: xfce4-sensors-plugin
Version: 0.6.1-1
Severity: serious
Justification: fails to build from source
/bin/sh: libtoolize: command not found
Hi.
Should be easily fixed by adding 'libtoolize' in the Build-depends.
Cheers,
--
Cyril
tags 319849 + security
found 319849 1.2.10-15
thanks
done
On Sat, Aug 20, 2005 at 09:35:39AM +0200, Vincent Bernat wrote:
OoO En cette matinée ensoleillée du jeudi 18 août 2005, vers 09:18,
Francesco Paolo Lovergine [EMAIL PROTECTED] disait:
Shouldn't this bug be tagged security ?
Processing commands for [EMAIL PROTECTED]:
tags 323956 security
Bug#323956: mutt: Buffer overflow in handler.c possibly allows code execution
by maliciously crafted email
There were no tags set.
Tags added: security
thanks
Stopping processing here.
Please contact me if you need assistance.
Package: libsablevm1
Version: 1.11.3-1
Severity: serious
[EMAIL PROTECTED]:/# apt-get install libsablevm1
Reading package lists... Done
Building dependency tree... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the
On Saturday, 20 August 2005 09:35, Klaus Ethgen wrote:
Hello
Am Fr den 19. Aug 2005 um 22:34 schrieb Adeodato Simó:
Severity: grave
The package has no Binary, no /usr/share/doc/kdm or other necesarry
stuff. I wonder why nobody saws this before.
Please check your facts before
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.9.4
severity 275892 serious
Bug#275892: r-noncran-lindsey build with gcc-3.4
Severity set to `serious'.
End of message, stopping processing here.
Please contact me if you need
Processing commands for [EMAIL PROTECTED]:
tag #324039 +fixed-upstream
Bug#324039: vlc: Fails to initialize libxosd
There were no tags set.
Tags added: fixed-upstream
tag #324031 +fixed-upstream
Bug#324031: vlc: FTBFS on 64 bit arches: error: cast from 'void*' to 'int'
loses precision
There
Package: libclanlib2c2
Version: 0.6.5-1-2.3
Severity: grave
Justification: renders package unusable
The package libclanlib2c2 is empty, save for a
/usr/share/doc/libclanlib2c2 directory. It should contain
the shared libclanCore library, unless I'm mistaken...
-- System Information:
Debian
Hi Kevin,
On Fri, Aug 19, 2005 at 10:13:05AM +0200, Kevin Glynn wrote:
Steve Langasek writes:
On Fri, Aug 19, 2005 at 08:03:38AM +0200, Kevin Glynn wrote:
These errors have been fixed upstream, but I don't have access to CVS
so I can't extract the patch.
Thanks for the
Hi,
As the bugs #275892 and #302873 are preventing r-noncran-lindsey to be
build, and as they are open for a very long time, I am preparing an NMU
of this package.
You will find attached the patch of this NMU. I'll upload it in 3 days
unless you oppose.
Bye,
Aurelien
--
.''`. Aurelien
Processing commands for [EMAIL PROTECTED]:
reassign 323967 kdelibs-data
Bug#323967: kicker: All icons, menu entries gone
Bug reassigned from package `kicker' to `kdelibs-data'.
severity 323967 serious
Bug#323967: kicker: All icons, menu entries gone
Severity set to `serious'.
merge 323747
Hi Manolo,
I can't reproduce the bug on my machine (i386). Can you provide an strace ?
--
Regards,
Lior Kaplan
[EMAIL PROTECTED]
http://www.Guides.co.il
Debian GNU/Linux unstable (SID)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
Dear Paul
Upstream has provided a patch[1] for this issue that I tested and found
that it works very well[2], which is now in debian nsis 2.08-3, which
I'll be uploading to debian mentors once I can find a fix for the
BgImage segfault.
Tested the examples again and those worked great.
On Saturday, 20 August 2005 13:44, Klaus Ethgen wrote:
Hello,
Am Sa den 20. Aug 2005 um 11:36 schrieb Isaac Clerencia:
Can you tell me how can you have kdm installed in your system without
having kdelibs, kdelibs-bin or qt installed?
I don't know. This was the result of a normal apt-get
Processing commands for [EMAIL PROTECTED]:
tag 322232 + fixed
Bug#322232: xdiskusage: uninstallable in sid (depends on libfltk1.1c102 (=
1.1.6) which is UNAVAILABLE)
There were no tags set.
Tags added: fixed
quit
Stopping processing here.
Please contact me if you need assistance.
Debian bug
* Klaus Ethgen [Sat, 20 Aug 2005 14:16:10 +0200]:
Am Sa den 20. Aug 2005 um 13:48 schrieb Adeodato Simó:
This is the best _sincere_ advice I can give to you: stop using
unstable.
Well, I have no problemes by myself using unstable but if there is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Sa den 20. Aug 2005 um 13:48 schrieb Adeodato Simó:
This is the best _sincere_ advice I can give to you: stop using
unstable.
Well, I have no problemes by myself using unstable but if there is
something not working this is a bug and I will
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Sa den 20. Aug 2005 um 13:48 schrieb Adeodato Simó:
This is the best _sincere_ advice I can give to you: stop using
unstable.
By the way, it is no problem for me working arround bugs. But I think,
reporting bugs to help finding and finaly
This bug has already been fixed in version 2.71. There are many report
already fixed about it, please check them.
Regards
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Cyril Brulebois [EMAIL PROTECTED] (20/08/2005):
Should be easily fixed by adding 'libtoolize' in the Build-depends.
Hi back.
I tried this but this was not sufficient. I'd like to add that the
problem seems to be located in the CDBS call to:
/usr/share/cdbs/1/class/autotools-files.mk
at the
Your message dated Sat, 20 Aug 2005 06:02:06 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#302088: fixed in hf 0.7.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 it is now your
On Saturday, 20 August 2005 14:16, Klaus Ethgen wrote:
Am Sa den 20. Aug 2005 um 13:48 schrieb Adeodato Simó:
This is the best _sincere_ advice I can give to you: stop using
unstable.
Well, I have no problemes by myself using unstable but if there is
something not working this is a bug
Processing commands for [EMAIL PROTECTED]:
severity 323941 serious
Bug#323941: php4-rrdtool: Please update to be compatible with librrd2
Severity set to `serious'.
tags 323941 pending
Bug#323941: php4-rrdtool: Please update to be compatible with librrd2
There were no tags set.
Tags added:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Sa den 20. Aug 2005 um 14:00 schrieb Isaac Clerencia:
Adeodato asked some days ago to not dist-upgrade your KDE until he tells
otherwise. You can recover a working KDE by following some advices in
messages sent to the debian-kde mailing list
Package: kmail
Version: 4:3.3.2-3
Followup-For: Bug #317098
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.10
Locale: [EMAIL
Package: grub
Version: 0.95+cvs20040624-17
Severity: grave
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-686
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages grub depends on:
ii libc6 2.3.2.ds1-22
Package: ivi
Version: 0.4.pre.20031121-2
Severity: serious
I've been working to get IVI 1.0.x into Debian. This is a bit tricky,
since it is now implemented as an Eclipse plugin, and Eclipse itself is
slowly getting a working version into Debian.
The 0.4.x series of IVI is really outdated, and
Processing commands for [EMAIL PROTECTED]:
reassign 324147 kdelibs-data
Bug#324147: kde: After upgrade, KDE menus dissapear
Bug reassigned from package `kde' to `kdelibs-data'.
severity 324147 serious
Bug#324147: kde: After upgrade, KDE menus dissapear
Severity set to `serious'.
merge 323747
Processing commands for [EMAIL PROTECTED]:
reassign 324147 kdelibs-data
Bug#324147: kde: After upgrade, KDE menus dissapear
Bug#323747: kdelibs-data: upgrading from 4:3.3.2-6.1 to 4:3.4.2-1 broke kicker
konqueror more
Bug#323967: kicker: All icons, menu entries gone
Bug reassigned from
Package: util-linux
Version: 2.12p-6
Severity: serious
Justification: Policy 10.4
hwclock{,first}.sh use == in some tests.
POSIX test requires single = (and -eq would be even better if these
tests are intended to compare numbers).
-- System Information:
Shell: /bin/sh linked to /bin/dash
--
reassign 324147 kdelibs-data
severity 324147 serious
merge 323747 324147
thanks
On Saturday 20 August 2005 10:38 am, Xabier Villar wrote:
Package: kde
Severity: important
After an upgrade, KDE menus dissapear, and are not regenerated even if I
rename .kde. Menu items in kcontrol and
Your message dated Sat, 20 Aug 2005 08:32:06 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#323819: fixed in evolution-sharp 0.8-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
Hi Kurt,
What architecture are you using ? I see this error in the buildd
logs, but for arm and sparc only. That makes me wonder about an
arch-specific packagin bug of gcj on those archs.
On Mon, Aug 01, 2005 at 08:49:50PM +0200, Kurt Roeckx wrote:
Your package is failing to build with the
On Friday 19 August 2005 21:01, Bastian Blank wrote:
- the problem is not there in the 686 image.
On request from waldi, I've compiled a -386 kernel (using gcc-4.0) with
one change in ./debian/arch/i386/config.386:
- CONFIG_CC_OPTIMIZE_FOR_SIZE=y
+ # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
The
Package: mozilla-firefox
Version: 1.0.4-2sarge2
Followup-For: Bug #322239
I don't think this bug is solved. I had the same problem just now after
an upgrade to the latest version. After reading this bug report I ran
ldconfig and tried the things I tried earlier again. Now firefox doesn't
seem to
found 323119 0.8.1-2
thanks
The build still fails due to missing CLN:
checking for pthread_create in -lpthread... yes
checking for cln-config... /usr/bin/cln-config
checking for CLN - version = 1.1.0... no
*** Could not run CLN test program, checking why...
*** The test program failed to compile
Processing commands for [EMAIL PROTECTED]:
found 323119 0.8.1-2
Bug#323119: qalculate-gtk: ftbfs [sparc] The cln-config script installed by CLN
could not be found
Bug marked as found in version 0.8.1-2.
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug
hoi :)
On Sat, Aug 20, 2005 at 09:30:45AM -0700, Blars Blarson wrote:
The build still fails due to missing CLN:
checking for pthread_create in -lpthread... yes
checking for cln-config... /usr/bin/cln-config
checking for CLN - version = 1.1.0... no
*** Could not run CLN test program,
Package: openvpn
Version: 2.0-1
Severity: grave
Tags: security, fixed-upstream
OpenVPN 2.0-1 contains serveral security related problems as described in
CAN-2005-2531 CAN-2005-2532 CAN-2005-2533 CAN-2005-2534.
Fixed upstream in Version 2.0.1, changelog avaible here:
On Sat, Aug 20, 2005 at 07:00:06PM +0200, Martin Waitz wrote:
no, it's not the same way.
previously, it couldn't find cln-config, because libcln-dev was missing.
now it does, but it can't compile a test program.
could you please send me the config.log from your machine?
Attached.
--
Package: printconf
Version: 0.7.4.14
Severity: grave
Justification: renders package unusable
I just types apt-get install printconf and I did get this error message :
Paramétrage de printconf (0.7.4.14) ...
Traceback (most recent call last):
File /usr/bin/printconf, line 107, in ?
for q
retitle 322211 gkrellm: please port to libgnutls12
severity 322211 wishlist
thanks
cu
Adrian
--
Is there not promise of rain? Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
Only a promise, Lao Er said.
Processing commands for [EMAIL PROTECTED]:
retitle 322211 gkrellm: please port to libgnutls12
Bug#322211: gkrellm can accidentially be compiled with OpenSSL
Changed Bug title.
severity 322211 wishlist
Bug#322211: gkrellm: please port to libgnutls12
Severity set to `wishlist'.
thanks
Stopping
Your message dated Sat, 20 Aug 2005 11:47:06 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#323051: fixed in libimage-exiftool-perl 5.53-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
Processing commands for [EMAIL PROTECTED]:
tags 218624 +pending
Bug#218624: krb4: Patch for GNU/Hurd
Tags were: patch
Tags added: pending
tags 318516 +pending
Bug#318516: krb4: FTBFS: static declaration of 'revoke' follows non-static
declaration
Tags were: patch
Tags added: pending
thanks
tags 218624 +pending
tags 318516 +pending
thanks
Hi,
I have uploaded an NMU to DELAYED/3-day which fixed #218624 and #318516.
If you plan to fix those bugs yourself, just upload during the next
three days.
This is NMU changelog entry:
krb4 (1.2.2-11.3) unstable; urgency=low
.
*
Your message dated Sat, 20 Aug 2005 13:17:12 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#323386: fixed in kismet 2005.08.R1-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 Sat, 20 Aug 2005 13:17:12 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#317838: fixed in kismet 2005.08.R1-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 Sat, 20 Aug 2005 13:17:18 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#323293: fixed in poedit 1.3.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 it is now your
[Steve Langasek]
however, there are currently no packages in Debian which use
libodbcinstq1 except for unixodbc-bin,
At the moment unixodbc-dev is uninstallable in unstable, and this make
it impossible to compile mapserver in unstable. mapserver
build-depend on unixodbc-dev, and it is
I get the same bug, since 'dash' is my default scriping shell. Attached
is a patch for '/etc/cron.daily/standard'.
Hope this helps...
--- /etc/cron.daily/standard 2005-08-11 03:06:18.0 -0400
+++ /tmp/standard 2005-08-20 16:52:03.0 -0400
@@ -62,7 +62,7 @@
df -P --type=ext2
Hello
Thanks for the patch.
A few questions about the patch as I do not understand why you
changed a few things.
On Fri, Aug 19, 2005 at 10:40:36AM -0700, Matt Kraai wrote:
Package: steghide
Version: 0.5.1-5
Severity: serious
Tags: patch
steghide fails to build because it contains a
On Sat, Aug 20, 2005 at 04:47:21PM +0200, Michel van der Klei wrote:
Package: grub
Version: 0.95+cvs20040624-17
Severity: grave
After a kernel upgrade last night my system fails to boot.
It was caused by a wrongly updated menu.lst which pointed to
a wrong kernel location:
It pointed to:
On Sat, Aug 20, 2005 at 02:38:53PM -0700, Steve Langasek wrote:
On Sat, Aug 20, 2005 at 04:47:21PM +0200, Michel van der Klei wrote:
Package: grub
Version: 0.95+cvs20040624-17
Severity: grave
After a kernel upgrade last night my system fails to boot.
It was caused by a wrongly updated
tags 324017 moreinfo unreproducible
thanks
On Fri, Aug 19, 2005 at 03:45:58PM -0400, Rick Friedman wrote:
Package: cron
Version: 3.0pl1-88
Severity: grave
Justification: renders package unusable
The cron daemon runs as normal until a cronjob starts up. Actually, I
don't even know if the
Processing commands for [EMAIL PROTECTED]:
severity 321172 normal
Bug#321172: [rejected] -m owner make segfault iptables
Severity set to `normal'.
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs
Package: cron
Version: 3.0pl1-88
Followup-For: Bug #324017
Below is the output of strace when a cronjob should've started (I should
add that the job that was supposed to run was in root's crontab):
chisum:~# strace -p 12697 -f
Process 12697 attached - interrupt to quit
setup()
Your message dated Sat, 20 Aug 2005 16:02:10 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#321281: fixed in gcompris 6.5.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
On Sunday, August 21, 2005 at 12:15AM, Javier Fern?ndez-Sanguino Pe?a wrote:
I'm sorry but I can't reproduce this and you're the only one seeing this.
I'm pretty sure that if 3.0pl1-88 introduce a bug of this kind I would
be flooded with similar bug reports already since it is a base package.
On Saturday 20 August 2005 07:21 pm, Mike Hokenson wrote:
I'm having this problem also, but haven't tried 3.0pl1-87. I'm also having
problems with my clock running too fast, so I'm frequently running ntpdate
until I can figure out what's going on when I get back to work on Monday.
Not sure if
On Sat, Aug 20, 2005 at 07:28:25PM -0400, Rick Friedman wrote:
It certainly seems more than coincidental to me that your strace shows the
same seg fault that my strace shows... immediately after opening
crontabs/root.
Oh, and BTW, the only change in -88 that might affect cron's behaviour
is
On Sat, Aug 20, 2005 at 07:11:19PM -0400, Rick Friedman wrote:
Package: cron
Version: 3.0pl1-88
Followup-For: Bug #324017
Below is the output of strace when a cronjob should've started (I should
add that the job that was supposed to run was in root's crontab):
Not very useful. Although
On Sunday, August 21, 2005 at 01:57AM, Javier Fern?ndez-Sanguino Pe?a wrote:
On Sat, Aug 20, 2005 at 07:28:25PM -0400, Rick Friedman wrote:
Oh, and BTW, the only change in -88 that might affect cron's behaviour
is either SElinux support or the enabling of pam_limits.so. You might
want to review
On Sat, Aug 20, 2005 at 07:11:43PM -0500, Mike Hokenson wrote:
In -88, u-scontext is set to NULL if get_security_context() fails (i
think) and in free_user() there's a freecon() call on u-scontext but no
NULL check. Maybe that's where the problem is?
Your assessment looks quite correct.
Your message dated Sat, 20 Aug 2005 17:17:06 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#324193: fixed in lm-sensors 1:2.9.1-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
Your message dated Sat, 20 Aug 2005 17:32:04 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#324017: fixed in cron 3.0pl1-90
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
On Sat, Aug 20, 2005 at 07:51:17PM -0500, Mike Hokenson wrote:
I just noticed I was building cron w/out selinux support. :P
Yes, I guessed as much :-)
Here's a backtrace of a -g:
(..)
Which still pretty much leads back to the same place...
Yes.
I'm not sure what your patch looks
On Sat, Aug 20, 2005 at 07:51:17PM -0500, Mike Hokenson wrote:
I'm not sure what your patch looks like, but just testing for a NULL
u-scontext didn't work, I had to do this:
Aggg.. you are right, I don't think clearly this late, the problem is that
u-scontext is undefined, that's why free()
On Sat, Aug 20, 2005 at 08:21:35PM -0500, Mike Hokenson wrote:
If it only contains the NULL pointer check, it won't (already tried), Rick
will probably be able to confirm this when he updates. I'm not familiar
with the mirroring system, do you think it'll appear shortly or is there a
place
On Sunday, August 21, 2005 at 03:20AM, Javier Fern?ndez-Sanguino Pe?a wrote:
On Sat, Aug 20, 2005 at 07:51:17PM -0500, Mike Hokenson wrote:
I'm not sure what your patch looks like, but just testing for a NULL
u-scontext didn't work, I had to do this:
Aggg.. you are right, I don't think
Unfortunately, Javier is correct. I have received no emails from him. For some
reason, Verizon, in its infinite wisdom, is blocking email from that domain.
Anyway, I will let you know what happens once I can update tomorrow.
Regards,
Rick
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with
On Sat, Aug 20, 2005 at 06:04:02PM +0200, Yann Dirson wrote:
Hi Kurt,
What architecture are you using ? I see this error in the buildd
logs, but for arm and sparc only. That makes me wonder about an
arch-specific packagin bug of gcj on those archs.
I'm seeing this on amd64.
Kurt
--
Your message dated Sat, 20 Aug 2005 21:17:05 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#323735: fixed in mlterm 2.9.2-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 Sat, 20 Aug 2005 21:17:05 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#302231: fixed in mlterm 2.9.2-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
Package: imms
Version: 2.0.3-2
Severity: grave
Tags: patch,sid
Justification: renders package unusable
immsd will repeatedly segfault as soon as XMMS connects to its socket. The
underlying problem is a bug (feature?) with initstate_r() from
libc6(2.3.5). See also a
84 matches
Mail list logo
