Steve Langasek [EMAIL PROTECTED] writes:
On Fri, Apr 06, 2007 at 01:39:35AM +0200, Fabian Pietsch wrote:
--- /usr/share/initramfs-tools/scripts/functions.orig
+++ /usr/share/initramfs-tools/scripts/functions
@@ -231,6 +231,7 @@
;;
esac
mknod /dev/root b ${major}
Package: wacom-kernel-source
Version: 0.7.4.1-6
Severity: grave
Here is what happens during package installation:
8:01 [EMAIL PROTECTED] /usr/src# LANG=C apt-get -f install
Reading package lists... Done
Building dependency tree... Done
0 upgraded, 0 newly installed, 0 to remove
Your message dated Fri, 06 Apr 2007 07:17:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#416816: fixed in idjc 0.6.11-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Fri, 06 Apr 2007 07:47:02 +
with message-id [EMAIL PROTECTED]
and subject line Bug#417995: fixed in initramfs-tools 0.85g
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 Subhashis,
Have you ever used this card reader successfully under any other operating
systems? It's certainly possible that this is a kernel bug, since this
class of hardware only recently became supported by Linux, but the error
message in question could also be a hardware fault so we should
Package: libx11-6
Version: 2:1.0.3-7
Severity: critical
Justification: breaks unrelated software
After upgrading libx11-6 to the security update as in version 1.0.3-7
made opera segfault every time I tried to start it. Downgrading to
version 1.0.3-6 fixes it.
Yes, I know that opera isn't open
Hi Marcelo,
Seeing how this bug was for all intents and purposes introduced by an NMU,
and it's a bug we ought to have fixed for etch, I've prepared a 0-day NMU to
fix it. The patch is attached; note that this NMU fixes *two*
strict-aliasing errors in io.c, not just the one in the patch provided
forcemerge 417816 418016
retitle 417816 libx11-6: upgrade to 2:1.0.3-7 makes opera segfault at
startup
thank you
Yes, it has already been reported on the Debian/Gentoo/Opera/Xorg BTS. But I
don't think anybody posted an interesting backtrace yet, so it's kind of
hard to know what's going on.
Your message dated Fri, 06 Apr 2007 10:02:24 +
with message-id [EMAIL PROTECTED]
and subject line Bug#399761: fixed in lib3ds 1.2.0-4.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
Processing commands for [EMAIL PROTECTED]:
forcemerge 417816 418016
Bug#417816: libx11 bug
Bug#418016: Recent security update of libx11-6 (1.0.3-7) made opera segfault
Forcibly Merged 417816 418016.
retitle 417816 libx11-6: upgrade to 2:1.0.3-7 makes opera segfault at
Bug#417816: libx11 bug
tags 417859 + moreinfo
thanks
Am Donnerstag, den 05.04.2007, 03:46 +0200 schrieb Cheli Pineda Ferrer:
Package: banshee
Version: 0.11.3+dfsg-2
Severity: grave
Justification: renders package unusable
Banshee crashs when I try to create an intelligent list whith the next
options:
Processing commands for [EMAIL PROTECTED]:
tags 417859 + moreinfo
Bug#417859: banshee crashes when I try to create a intelligent list
There were no tags set.
Tags added: moreinfo
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.10.2
found 418021 2:1.0.3-7
Bug#418021: libx11-6: Recent security update 1.0.3-7 causes segfaults in
XPutImage
Bug marked as found in version 2:1.0.3-7.
notfound 418021 2:1.0.3-6
Hi Steve,
I have used this card reader earlier in windows (XP) to read the SD
memory Card without any problem (it is also mentioned in the bug report).
Cheers
Subhashis
On Fri, 6 Apr 2007, Steve Langasek wrote:
Hi Subhashis,
Have you ever used this card reader successfully under any other
Package: firebird1.5-super
Version: 1.5.4.4910rel-3
Severity: grave
Justification: renders package unusable
Hi,
here is the problem:
Setting up firebird1.5-super (1.5.4.4910rel-3) ...
* Not starting Firebird 1.5 server manager
/etc/init.d/firebird1.5-super: line 69: VER: unbound variable
It works properly with banshee (0.12.0+dfsg-2) from Experimental.
Thanks a lot.
Cheli
--
sip: [EMAIL PROTECTED]
jid1: [EMAIL PROTECTED]
jid2: [EMAIL PROTECTED]
Visita mi bitacora: http://cheli.aradaen.com
pgp97AtmmfM23.pgp
Description: PGP signature
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.10.2
tags 418031 pending
Bug#418031: firebird1.5-super: postinst failure because of VER unbound variable
There were no tags set.
Tags added: pending
End of message, stopping processing
Your message dated Fri, 06 Apr 2007 12:17:04 +
with message-id [EMAIL PROTECTED]
and subject line Bug#417021: fixed in netkit-rwho 0.17-9
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
Upgrading to 1.0.3-7 brakes other software - causing segfaults in
XPutImage call, rdesktop is affected and unusable.
This seems to happen on machine with direct rendering disabled, the
same setup on accelerated Xorg works fine.
could you install libx11-6-dbg and get a backtrace with gdb
Hi Sam and Larry,
Sam Hocevar wrote:
I don't know what went wrong the first time, I tried
again and Electric Fence found it. Please test.
It works for me on both broken2.jp2 and broken4.jp2.
Your patch works, with all broken*.jp2 files. Here is a slightly
better one that checks the
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.9.27
package graphicsmagick graphicsmagick-dbg graphicsmagick-imagemagick-compat
graphicsmagick-libmagick-dev-compat libgraphics-magick-perl
libgraphicsmagick++1
Hi,
Sigh... I understand it is nice if we had copyright section but
after all this was note.
On Fri, Apr 06, 2007 at 01:47:50AM +0200, Javier Fernández-Sanguino Peña wrote:
On Thu, Apr 05, 2007 at 11:02:00PM +0200, Francesco Poli wrote:
Thank you for agreeing to the licensing[1], could
Processing commands for [EMAIL PROTECTED]:
clone 414370 -1
Bug#414370: graphicsmagick: Couple of segfaults in PICT coder
Bug 414370 cloned as bug 418052.
retitle -1 graphicsmagick: Heap overflow in GrayscalePseudoClassImage()
Bug#418052: graphicsmagick: Couple of segfaults in PICT coder
eyck -
As the author of the patch that apparently broke your application,
this report totally baffles me. Can you confirm that downgrading
to libx11-6 version 2:1.0.3-6 removes the problem?
Are you able to patch and rebuild test versions of libx11?
If so, one quick thing to try is to put back
Package: imagemagick
Version: 7:6.2.4.5.dfsg1-0.14
Severity: grave
Tags: security
Justification: user security hole
Hi,
here is the problem:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-1797
Multiple integer overflows in ImageMagick before 6.3.3-5 allow remote
attackers to execute
On Fri, 06 Apr 2007 00:37:24 +0200 Frans Pop wrote:
On Thursday 05 April 2007 23:02, Francesco Poli wrote:
Obviously enough, I'm *not* going to dig into the CVS logs to
collect a comprehensive list of individual contributors, unless I
first receive agreements from an encouraging number of
On Fri, Apr 06, 2007 at 08:57:45AM -0700, [EMAIL PROTECTED] wrote:
eyck -
As the author of the patch that apparently broke your application,
this report totally baffles me. Can you confirm that downgrading
to libx11-6 version 2:1.0.3-6 removes the problem?
C.f.
Your message dated Fri, 06 Apr 2007 20:32:13 +
with message-id [EMAIL PROTECTED]
and subject line Bug#416016: fixed in libembperl-perl 2.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
Your message dated Fri, 06 Apr 2007 20:32:13 +
with message-id [EMAIL PROTECTED]
and subject line Bug#395870: fixed in libembperl-perl 2.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
On Fri, Apr 06, 2007 at 04:04:47PM +0200, Roland Stigge wrote:
Hi Sam and Larry,
Sam Hocevar wrote:
I don't know what went wrong the first time, I tried
again and Electric Fence found it. Please test.
It works for me on both broken2.jp2 and broken4.jp2.
Your patch works, with all
On Thu, Mar 22, 2007, Marc 'HE' Brockschmidt wrote:
| gtk-doc: Running scanner libebook-scan
| Scan failed:
| make[6]: *** [scan-build.stamp] Error 255
gtkdoc-scanobj generates a C source file, builds it, and runs it to
introspect some objects of the API. Sometimes this segfaults or dies
On Fri, Apr 06, 2007 at 11:42:15PM +0900, Osamu Aoki wrote:
Hi,
Sigh... I understand it is nice if we had copyright section but
after all this was note.
Well, now it's a document over 50 pages long (for most architectures,
anyway). So it should have its own license section.
If
On Fri, 6 Apr 2007 23:42:15 +0900 Osamu Aoki wrote:
[...]
If Francesco feels strong about this issue, he should at least put his
effort to send out licensing clarification notice to all involved with
contactable address and give us how they respond to the licensing
clarification to the GPL2
On Friday 06 April 2007 23:59, Javier Fernández-Sanguino Peña wrote:
a) add the GPL license, as it should have had when it moved from b-f's
CVS to the DDP
Add the whole GPL licence with all translation problems that brings?
Please not! Let's just have a simple statement and a reference to
Package: python-central
Version: 0.5.13
Severity: serious
Trying to upgrade fails. Trying to rerun looks like this:
# dpkg --configure -a
Setting up python2.4-minimal (2.4.4-3) ...
Linking and byte-compiling packages for runtime python2.4...
Traceback (most recent call last):
File
Package: python2.4-minimal
Version: 2.4.4-3
Severity: serious
Justification: breaks upgrade
Hi, the latest python upgrade fails:
Setting up python2.4-minimal (2.4.4-3) ...
Linking and byte-compiling packages for runtime python2.4...
Traceback (most recent call last):
File /usr/bin/pycentral,
Processing commands for [EMAIL PROTECTED]:
reassign 418109 python-central
Bug#418109: Python upgrade bug
Bug reassigned from package `python2.4-minimal' to `python-central'.
forcemerge 418108 418109
Bug#418108: python-central: UnboundLocalError: local variable 'config'
referenced before
reassign 418109 python-central
forcemerge 418108 418109
thanks
On Fri, Apr 06, 2007 at 03:41:23PM -0700, H. S. Teoh wrote:
Hi, the latest python upgrade fails:
Setting up python2.4-minimal (2.4.4-3) ...
Linking and byte-compiling packages for runtime python2.4...
Traceback (most recent call
Hello:
Maybe a backtrace could be of help. Just follow the following procedure:
1- Repeat the problem, so you get the 100% cpu usage.
2- Go to a console (graphical, text or remote) and after log in
issue: gdb -p $(pidof kded)
3- Enable logging to a file: set log on
4- Get a
On Sat, Apr 07, 2007 at 12:12:19AM +0200, Frans Pop wrote:
On Friday 06 April 2007 23:59, Javier Fernández-Sanguino Peña wrote:
a) add the GPL license, as it should have had when it moved from b-f's
CVS to the DDP
Add the whole GPL licence with all translation problems that brings?
Your message dated Sat, 07 Apr 2007 03:17:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#379895: fixed in yacas 1.0.57-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, 07 Apr 2007 03:17:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#379261: fixed in yacas 1.0.57-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, 07 Apr 2007 03:17:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#399227: fixed in yacas 1.0.57-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, 07 Apr 2007 03:17:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#332298: fixed in yacas 1.0.57-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, 07 Apr 2007 03:17:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#266283: fixed in yacas 1.0.57-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, 07 Apr 2007 03:17:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#399226: fixed in yacas 1.0.57-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, 07 Apr 2007 03:17:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#382783: fixed in yacas 1.0.57-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, 07 Apr 2007 03:17:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#338164: fixed in yacas 1.0.57-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: python-central
Version: 0.5.13
Followup-For: Bug #418108
I am guessing that the fix to the problem can be as simple as adding a
line global config under global _defaults in the failed script:
--- /usr/share/pycentral-data/pyversions.py.orig2007-04-06
23:23:10.0 -0400
The byte-compile takes a small eternity, but Ilguiz's fix solves the problem
on my system. All failing packages now install properly.
Your message dated Sat, 07 Apr 2007 04:47:02 +
with message-id [EMAIL PROTECTED]
and subject line Bug#416495: fixed in mozplugger 1.8.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
Package: python-central
Version: 0.5.13
Followup-For: Bug #418108
Hi, as per suggested fix I modified
/usr/share/pycentral-data/pyversions.py
to include the line
global config
I'm not sure how to byte compile so I left that alone.
Tried to install blender again (this bug is causing
52 matches
Mail list logo
