Processing commands for [EMAIL PROTECTED]:
> tags 341669 patch
Bug#341669: libfwbuilder-dev: Broken upload
Tags were: fixed
Tags added: patch
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs databas
On Wed, Dec 21, 2005 at 09:13:01PM -0800, Joshua Kwan wrote:
> Package: vim-runtime
> Version: 1:6.4-004+1
> Severity: grave
>
> Unpacking replacement vim-runtime ...
> dpkg: error processing
> /var/cache/apt/archives/vim-runtime_1%3a6.4-004+2_all.deb (--unpack):
> trying to overwrite `/usr/bin/
tags 341669 patch
thanks
On Wed, Dec 21, 2005 at 09:51:21AM -0800, Jeremy T. Bouse wrote:
> Steve Langasek wrote:
> >Are you suggesting that you had this right in 2.0.9-3, and the NMUer
> >reverted it in 2.0.9-3.1?
>What I'm saying, is that with the exception of the NMU done by
> yourself S
Your message dated Wed, 21 Dec 2005 23:02:10 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#341379: fixed in gnome-apt 0.4.9-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
On Tue, 20 Dec 2005, Fran�ois-Denis Gonthier wrote:
Erlang 10.b.9 is just around the corner, and it's probably not too late to
upload it with your patch.
Could you please download the current version of the erlang 10.b.9 package
and try to build it on Sparc? It's at http://neutronic.mine.nu/un
Package: vim-runtime
Version: 1:6.4-004+1
Severity: grave
Unpacking replacement vim-runtime ...
dpkg: error processing
/var/cache/apt/archives/vim-runtime_1%3a6.4-004+2_all.deb (--unpack):
trying to overwrite `/usr/bin/vimtutor', which is also in package vim-common
dpkg-deb: subprocess paste kil
On Wed, Dec 21, 2005 at 08:25:52PM -0800, Max Alekseyev wrote:
> Steve Langasek wrote:
> >>This is the output of valgrind with libc6-dbg:
> >Ok, most of this looks like pretty typical garbage output, with a few
> >messages related to locales and themes that I don't usually see. Are you
> >using
Steve Langasek wrote:
This is the output of valgrind with libc6-dbg:
Ok, most of this looks like pretty typical garbage output, with a few
messages related to locales and themes that I don't usually see. Are you
using any particular gtk theme here?
I use Smokey Blue theme.
Do you see the
Processing commands for [EMAIL PROTECTED]:
> reassign 339419 d4x 2.5.6-2
Bug#339419: d4x crashes in strlen () from /lib64/libc.so.6
Bug reassigned from package `libglib2.0-0' to `d4x'.
> tags 339419 patch
Bug#339419: d4x crashes in strlen () from /lib64/libc.so.6
Tags were: moreinfo confirmed
Tag
reassign 339419 d4x 2.5.6-2
tags 339419 patch
thanks
On Wed, Dec 21, 2005 at 01:05:10PM -0800, Max Alekseyev wrote:
> Steve Langasek wrote:
> >valgrind?
> This is the output of valgrind with libc6-dbg:
Ok, most of this looks like pretty typical garbage output, with a few
messages related to loc
Subject: lxr: genxref halts on DB_File compatibility error message
Package: lxr
Version: 0.3.1-2
Severity: grave
Justification: renders package unusable
*** Please type your report below this line ***
# .../bin/genxref 2.6.12-at91
DB_File needs compatible versions of libdb & db.h
you hav
Package: xlockmore
Version: 5.13-2.1
Followup-For: Bug #318123
Tags: patch
The general design issue here is that xlock (unlike e.g. xscreensaver
which kills the X server along with) gives access to the screen when
it is killed by a signal, i.e. any way to crash it becomes an
authentication bypass
Package: avahi-utils
Version: 0.6.1-1
Severity: grave
Justification: renders package unusable
The avahi-utils package is for architecture 'all' yet it contains binaries for
the powerpc architecture:
$ avahi-resolve
bash: /usr/bin/avahi-resolve: cannot execute binary file
$ file /usr/bin/avahi-re
Package: avahi-discover
Version: 0.6.1-1
Severity: grave
Justification: renders package unusable
It seems avahi-discover depends on libavahi-common0 when it should depend on
libavahi-common3.
$ sudo apt-get install -t unstable avahi-discover
Reading package lists... Done
Building dependency tree.
Your message dated Wed, 21 Dec 2005 16:47:09 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#323736: fixed in motion 3.2.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 you
Processing commands for [EMAIL PROTECTED]:
> reassign 344347 mozilla-firefox-locale-da-dk
Bug#344347: mozilla-locale-da-dk: mozilla-firefox-locale-da-dk uninstallable in
unstable
Warning: Unknown package 'mozilla-locale-da-dk'
Bug reassigned from package `mozilla-locale-da-dk' to
`mozilla-firefo
reassign 344347 mozilla-firefox-locale-da-dk
thanks
Ooops, I accidentally reported this against the wrong package. It
should really be against mozilla-firefox-locale-da-dk.
Regards
/Rasmus
--
-- [ Rasmus "Møffe" Bøg Hansen ] ---
I don't suffer from insanity,
Your message dated Wed, 21 Dec 2005 15:47:09 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#344201: fixed in asis 3.15p-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 your
Package: mozilla-locale-da-dk
Severity: grave
Justification: renders package unusable
mozilla-firefox-locale-da-dk (and probably all locales in
mozilla-firefox-locale-all)
is uninstallable in unstable with firefox 1.5 uploaded.
Update to the 1.5 translations is probably needed.
Regards
/Rasmus
Your message dated Wed, 21 Dec 2005 15:16:08 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#339231: fixed in mercator 0.2.4-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 y
Your message dated Wed, 21 Dec 2005 14:52:28 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#330902: fixed in bmp-alarm 0.6.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 it is now
Your message dated Wed, 21 Dec 2005 14:52:28 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#272859: fixed in bmp-alarm 0.6.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 it is now
Your message dated Wed, 21 Dec 2005 14:03:48 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#336983: fixed in qemu 0.7.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 your
Package: libextractor-python
Version: 0.5.1-2
Severity: grave
Justification: renders package unusable
Script started on Mi 21 Dez 2005 22:06:12 CET
[EMAIL PROTECTED]:~/tmp$ python ./extract.py
Traceback (most recent call last):
File "./extract.py", line 27, in ?
xtract = extractor.Extractor(
Your message dated Wed, 21 Dec 2005 15:25:30 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#343444: bug is gone
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 responsibi
grep-dctrl -P libtagcoll-dev dists/sid/main/binary-amd64/Packages
Package: libtagcoll-dev
Priority: optional
Section: libdevel
Installed-Size: 10628
Maintainer: Enrico Zini <[EMAIL PROTECTED]>
Architecture: amd64
Source: tagcoll
Version: 1.5.1-1+b1
Depends: tdb-dev, zlib1g-dev
Recommends: pkg-confi
> Hi,
>
> Although there are a few interesting gcc warnings, the bug does not show after
> recompiling.
>
> --
> Confucius say: He who play in root, eventually kill tree.
> Saludos /\/\ /\ >< `/
Hi,
That's true for me. After recompiling this bug doesn't show but another
ones (less important) a
Processing commands for [EMAIL PROTECTED]:
> reassign 343444 dialog
Bug#343444: netenv segmentation fault
Bug reassigned from package `bash' to `dialog'.
>
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator
On Wed, Dec 21, 2005 at 05:04:58PM +0100, Frank K??ster wrote:
> Tobias Knieper <[EMAIL PROTECTED]> wrote:
>
> > Hello,
> > i made a dist-upgrade this morning and the bug is gone. apt upgraded only a
> > few (six or seven) packages. Is it possible to find out which packages my
> > system upgrade
On Wed, Dec 21, 2005 at 08:52:37PM +0100, Martin Schulze wrote:
> I've added
>
> CVE-2005-3536
>
> Missing input sanitising of the topic type allows remote attackers
> to inject arbitrary SQL commands.
ack.
> CVE-2005-3537
>
> Missing request validation permitted remote attackers t
Jeroen van Wolffelaar wrote:
> On Tue, Dec 20, 2005 at 06:54:18AM +0100, Martin Schulze wrote:
> > Thijs Kinkhorst wrote:
> > > On Mon, 2005-12-19 at 06:53 +0100, Martin Schulze wrote:
> > > > Thanks. Could somebody explain the issues that were fixed which have no
> > > > security relevance? From
Package: xscreensaver
Version: 4.23-3
Severity: serious
Justification: no longer builds from source
Hello,
trying to build the package from source I did the following:
# apt-get source xscreensaver
# apt-get build-dep xscreensaver (as root)
# cd xscreensaver-4.23
# dpkg-buildpackage -rfakeroot
Processing commands for [EMAIL PROTECTED]:
> severity 329738 serious
Bug#329738: kpilot: kpilotdaemon capitalization error
Bug#329737: kpilot: configuration window empty
Severity set to `serious'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking s
On Wed, Dec 21, 2005 at 07:13:49PM +0100, Thomas Zander wrote:
> Oh, sorry for incorrectly concluding it must be a problem with the libapt.
> You state that it must be a problem with the amd64 archive, which I'm
> sorry to say does not mean much to me.
The Debian amd64 port is not yet distributed
On Tue, Dec 20, 2005 at 10:33:26AM -0600, Manoj Srivastava wrote:
> tags 344046 +wontfix
> thanks
> This is still a bug in GCC.
> > By this standard, almost all toolchain bugs would be
> > release-critical bugs. This is not reasonable;
> I beg to differ. We should not be shippin
Your message dated Wed, 21 Dec 2005 11:02:10 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#329851: fixed in gabber 0.8.8-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 now you
On Wed, Dec 21, 2005 at 10:22:56AM -0600, Duane Meyer wrote:
> Package: openssh-server
> Version: 1:4.2p1-5
> Severity: grave
> Justification: renders package unusable
> This all seems to have started since the last update I ran on or around the
> 19th of December 2005 which included a new 2.4.27
On Wed, Dec 21, 2005 at 07:59:06PM +0100, Loïc Minier wrote:
> On Wed, Dec 21, 2005, Steve Langasek wrote:
> > All that will do is let you look at the value passed to strlen(); it won't
> > tell you much about why it's wrong or where it came from.
> I imaginated it would help tracing a 64 bits ->
Your message dated Wed, 21 Dec 2005 10:47:11 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#301390: fixed in libjavascript-perl 0.55-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
Just wanted to chime in: I have the same problem. I purged
emacs-snapshot, but apparently that didn't fix anything.
My quick and very dirty workaround: put the following into your .gnus
file.
(setq load-path (cons (concat "/usr/share/emacs21/site-lisp/bbdb") load-path))
(setq load-path (cons (co
On Wed, Dec 21, 2005, Steve Langasek wrote:
> All that will do is let you look at the value passed to strlen(); it won't
> tell you much about why it's wrong or where it came from.
I imaginated it would help tracing a 64 bits -> 32-bits cast would that
be the problem here.
What do you suggest?
On Wed, Dec 21, 2005 at 01:58:13PM +0100, Loïc Minier wrote:
> > (gdb) bt
> > #0 0x2c900e60 in strlen () from /lib64/libc.so.6
> The actual crash happens here, probably because a borken address was
> passed to strlen().
> > #1 0x2c49670a in std::string::compare () from
> > /
What I'm saying, is that with the exception of the NMU done by
yourself Steve there have been problems with every NMU done. As well,
again with all but the exception of you, they were done with disregard
to the Developer reference regarding NMUs and how they should be done.
Because of th
Package: qgo
Version: 1.0.3-2
Followup-For: Bug #320260
after discussing with Eric Dorland about the automake1.7 problems, he
told me that I don't need libtool because qgo doesn't build shared
libraries
so given all the problems with the version used in the upstream source,
I'm postponing the "li
Oh, sorry for incorrectly concluding it must be a problem with the libapt.
You state that it must be a problem with the amd64 archive, which I'm
sorry to say does not mean much to me.
Can you please advice where I should open a bugreport so this issue is
correctly registered?
Thanks
On Wednes
Hello,
this morning I upgraded the following package:
dialog - Displays user-friendly dialog boxes from shell scripts
On December, 15th i upgraded
2005-12-15 07:45:37 upgrade dialog 1.0-20051107-1 1.0-20051207-1
Today i upgraded:
2005-12-21 08:09:29 upgrade dialog 1.0-20051207-1 1.0-20051219-1
Package: cryptsetup
Version: 20050111-4+b1
Severity: grave
Justification: renders package unusable
After last nights upgrade to cryptsetup 20050111-4+b1, I'm unable to map new or
existing devices. Only by relinking to libdevmapper1.01 does it work.
gozer:/tmp# dd if=/dev/zero of=test bs=1M coun
Your message dated Wed, 21 Dec 2005 09:46:38 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#344291: libapt-front-dev: depends on missing libtagcoll-dev
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 i
On Wed, Dec 21, 2005 at 06:06:03AM -0800, Jeremy T. Bouse wrote:
> This would be because of rushed NMU that I did not do.
Are you suggesting that you had this right in 2.0.9-3, and the NMUer
reverted it in 2.0.9-3.1?
--
Steve Langasek Give me a lever long enough and a Free
Package: openssh-server
Version: 1:4.2p1-5
Severity: grave
Justification: renders package unusable
This all seems to have started since the last update I ran on or around the
19th of December 2005 which included a new 2.4.27 Kernel.
Some time ago, I needed to set an environment variable to fix w
Tobias Knieper <[EMAIL PROTECTED]> wrote:
> Hello,
> i made a dist-upgrade this morning and the bug is gone. apt upgraded only a
> few (six or seven) packages. Is it possible to find out which packages my
> system upgraded?
If you use aptitude, it's in /var/log/aptitude; I think dpkg does not
y
Package: libapt-front-dev
Severity: grave
Justification: renders package unusable
doing an install I get;
The following packages have unmet dependencies:
libapt-front-dev: Depends: libtagcoll-dev (>= 1.5) but it is not installable
Depends: libtagcoll-dev (< 1.6) but it is not
On Wed, Dec 21, 2005 at 03:40:50PM +0100, Tobias Knieper wrote:
> Hello,
> i made a dist-upgrade this morning and the bug is gone. apt upgraded only a
> few (six or seven) packages. Is it possible to find out which packages my
> system upgraded?
Recent dpkg keeps a log in .
--
Clear skies,
Just
On Wed, 2005-12-21 at 10:07 +0100, David Härdeman wrote:
> Jonathan Brandmeyer wrote:
> > /dev/mapper is empty except for control
>
> Does running "vgscan"
Does not exist in the initramfs.
> and/or "vgchange -ay" from the initramfs shell create
> any nodes in /dev/mapper?
Yes it does. Howeve
Hello,
i made a dist-upgrade this morning and the bug is gone. apt upgraded only a
few (six or seven) packages. Is it possible to find out which packages my
system upgraded?
Regards,
Tobias
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL
Package: gnome-splashscreen-manager
Version: 0.2-1
Followup-For: Bug #314310
as in subject, gnome-splashscreen-manager runs without problem if
executed as root.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, '
This would be because of rushed NMU that I did not do. I'll fix it
when I get 2.0.10 ready for upload.
Regards,
Jeremy
Matthijs Mohlmann wrote:
>Package: libfwbuilder6c2a
>Severity: serious
>Justification: Policy 7.3
>
>Hi,
>
>The package fails to upgrade from libfwbuilder6c2 to libf
On Wed, Dec 21, 2005 at 08:44:59AM +0100, Nicolas DEGAND wrote:
> Le Mercredi 21 Décembre 2005 02:52, Daniel Jacobowitz a écrit :
> > On Tue, Dec 20, 2005 at 01:19:20PM +0100, Nicolas DEGAND wrote:
> > > Package: libc6
> > > Version: 2.3.5-8.1
> > > Severity: grave
> > >
> > > X.org do not start at
Hi,
On Wed, Dec 21, 2005, Max Alekseyev wrote:
> They called libglib2.0-0-dbg and libgtk2.0-0-dbg here.
Examining the second backtrace still doesn't point at them, my comments
are below.
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 1098918240 (LWP 23033
Thomas Bushnell BSG <[EMAIL PROTECTED]>
Date: Tue, 11 Oct 2005 23:50:44 -0700:
> Ron <[EMAIL PROTECTED]> writes:
>
>> Package: gdk-imlib1
>> Version: 1.9.14-22
>> Severity: critical
>> Justification: breaks unrelated software
>>
>> Unless there is something big I am missing, gdk-imlib should
>> c
Your message dated Wed, 21 Dec 2005 03:47:12 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#340755: fixed in ispell-fi 0.7-17
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 Wed, 21 Dec 2005 03:47:12 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#326025: fixed in ispell-fi 0.7-17
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
Loïc Minier wrote:
Please provide a backtrace of the crash with libglib2.0-dbg and
libgtk2.0-dbg installed. If these libraries don't appear in the
backtrace, it's unlikely a Glib or Gtk bug.
They called libglib2.0-0-dbg and libgtk2.0-0-dbg here.
These are new backtraces from all 4 threads:
Hi,
On Sat, Nov 19, 2005, Cai Qian wrote:
> This bug is caused by mismatch versions between libgtk2.0-0 (2.8.3-1) and
> libglib2.0-0 (2.6.10-1) in unstable. If use both 2.8 or 2.6, d4x will not
> crash.
The updates went as follow:
- initially, gtk 2.6 and glib 2.6 were in unstable and t
Your message dated Wed, 21 Dec 2005 02:02:08 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#344150: fixed in vim 1:6.4-004+2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now yo
Le mardi 20 décembre 2005 à 22:07 -0800, Steve Langasek a écrit :
> If this is a bug in a library, it must be a bug in glib for failing to
> maintain compatibility between 2.6 and 2.8. But there is insufficient
> information in the bug log to demonstrate that this is a lib bug.
I doubt that's a
Jonathan Brandmeyer wrote:
> /dev/mapper is empty except for control
Does running "vgscan" and/or "vgchange -ay" from the initramfs shell create
any nodes in /dev/mapper?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: libfwbuilder6c2a
Severity: serious
Justification: Policy 7.3
Hi,
The package fails to upgrade from libfwbuilder6c2 to libfwbuilder6c2a, I
think this has to do with wrong Conflicts/Replaces pair. Please add
libfwbuilderc2 to Conflicts and Replaces and this problem is fixed.
Regards,
Mat
68 matches
Mail list logo