On Sat, Mar 31, 2012 at 07:24:53PM +0200, Rene Engelhard wrote:
On Sat, Mar 31, 2012 at 07:10:17PM +0200, Christoph Anton Mitterer wrote:
I deleted some log file manually and then the upgrade of all packages
worked (after three iterations or so); however, still with endless
errors, that a
On Sat, Mar 31, 2012 at 09:00:01PM +0200, Rene Engelhard wrote:
On Sat, Mar 31, 2012 at 08:43:23PM +0200, Mario 'BitKoenig' Holbe wrote:
aptitude safe-upgrade fails the same. terminal-capture attached.
omg. safe-upgrade.. on sid...
Of course, what else?
full-upgrade tries to purge half
Package: grub-pc
Version: 1.99-15
Severity: grave
Hello,
starting with 1.99-15 grub-pc fails to install:
Setting up grub-pc (1.99-15) ...
/usr/sbin/grub-setup: warn: Your core.img is unusually large. It won't fit in
the embedding area..
/usr/sbin/grub-setup: warn:
Package: libxcb1
Version: 1.8-1
Severity: critical
Justification: makes unrelated software on the system break
Hello,
since libxcb1 upgraded to 1.8-1 alsamixer segfaults on startup.
Downgrading libxcb1 to 1.7-4 fixes this.
The system is a typical workstation with all the
On Thu, Jan 26, 2012 at 10:05:16PM +0100, Mario 'BitKoenig' Holbe wrote:
root@darkside:~# COLUMNS=72 dpkg -l libxcb1 | grep ^i
ii libxcb11.7-4 X C Binding
Uhm, of course this has to be
ii libxcb11.8-1 X C Binding
... as is proven below:
root@darkside
On Thu, Jan 26, 2012 at 11:14:52PM +0100, Cyril Brulebois wrote:
Mario 'BitKoenig' Holbe mario.ho...@tu-ilmenau.de (26/01/2012):
root@darkside:~# echo q | alsamixer
Segmentation fault (core dumped)
Please get us more info about that???
I can't reproduce it here, also with gnome/pulseaudio
On Fri, Jan 27, 2012 at 12:22:28AM +0100, Cyril Brulebois wrote:
Julien Cristau jcris...@debian.org (27/01/2012):
Core was generated by `alsamixer'.
Program terminated with signal 11, Segmentation fault.
#0 0x7f96c1c34fd0 in snd_mixer_class_unregister ()
from
Hello,
On Fri, May 27, 2011 at 04:32:56PM +0200, Julian Andres Klode wrote:
On Tue, 2011-05-24 at 15:45 +0200, Mehdi Dogguy wrote:
On 05/04/2011 16:48, Julian Andres Klode wrote:
As I wrote some time ago, the APT team would like to disable
the old python-apt API for Python 2.X now.
Are
Package: racoon
Version: 1:0.8.0-4
Severity: grave
Hello,
the new init-script from 1:0.8.0-4 causes a dependency loop and hence
makes the package uninstallable:
Setting up racoon (1:0.8.0-4) ...
Installing new version of config file /etc/init.d/racoon ...
insserv:
Hello Steve,
On Wed, Jun 08, 2011 at 05:17:23PM -0700, Steve Langasek wrote:
The attached (untested) patch is based on an IRC conversation with Aurélien
yesterday about this bug. If there are any other copies of ld-2.x.so in
/lib that dpkg doesn't know about, we should abort the upgrade until
On Fri, Jun 10, 2011 at 10:26:39AM +0200, Mario 'BitKoenig' Holbe wrote:
I did a quick survey over all my Debian machines and found /lib/ld.so
together with the Mar 7 2001 timestamp, as already mentioned by Haegar
and others, on all older systems, i.e. systems initially installed
several years
Package: console-setup
Version: 1.71
Severity: grave
Hello,
if a system's keymap needs to be loaded during the initramfs stage,
initramfs-tools' /usr/share/initramfs-tools/hooks/keymap looks for
/etc/console-setup/cached.kmap.gz
and copies it to the initramfs.
Package: evolution-mapi
Version: 0.30.3-2
Severity: grave
Justification: renders package unusable
Hello,
evolution-mapi 0.30.3-2 cannot be installed anymore on unstable, because
it's built against an old evolution version. Please update the package
to the current version 0.32.2.
Thanks for
Package: bashdb
Version: 4.2.0.6-1
Severity: serious
Hello,
bashdb 4.2.0.6-1 started to ship
/usr/share/info/dir.gz
which is very likely not intentional.
First of all, this file is usually managed by install-info and thus gets
overwritten regularly which causes bashdb's package
On Wed, Feb 23, 2011 at 09:33:59AM -0600, Oleksandr Moskalenko wrote:
* Mario 'BitKoenig' Holbe mario.ho...@tu-ilmenau.de [2011-02-23 10:56:25
+0100]:
bashdb 4.2.0.6-1 started to ship
/usr/share/info/dir.gz
workaround. I wonder if the install-info behavior should be directed
On Wed, Feb 23, 2011 at 10:36:38AM -0600, Oleksandr Moskalenko wrote:
It's upstream code in the makefiles and tests that calls install-info. That
call produces the dreaded /usr/share/info/dir.gz
Well, the issues on non-Debian systems should be similar to ours if
upstream installs that dir.gz.
Package: zutils
Version: 0.9~rc2-2
Severity: critical
Hello,
zutils diverts binaries in /bin but installs its replacements to
/usr/bin. This makes the respective commands unavailable as long as
/usr/bin is not (yet) mounted.
I'm aware of the libstdc++ dependency that prevents zutils from being
Package: user-setup
Version: 1.32
Severity: grave
Hello,
user-setup 1.32 fails to install:
Preparing to replace user-setup 1.31 (using .../user-setup_1.32_all.deb) ...
Unpacking replacement user-setup ...
Setting up user-setup (1.32) ...
Template parse error near `description...@latin.utf-8:
package grub-pc
fixed 589854 1.98+20100802-1
thanks
Hello,
this bug doesn't seem to appear (anymore?) with 1.98+20100802-1:
Setting up grub-pc (1.98+20100802-1) ...
Installing new version of config file /etc/grub.d/05_debian_theme ...
Installation finished. No error
Hello Colin,
got a bit more time for debugging...
Short: it reads the right device but returns data from the wrong device.
Long: ... read on :)
I modified ext2.c to read some more blocks around the ext2 superblock to
see what's going on (and enough blocks to make sure some of them are not
cached
On Sat, Jul 24, 2010 at 06:36:01AM +0200, Mario 'BitKoenig' Holbe wrote:
On Thu, Jul 22, 2010 at 09:37:15PM +0100, Colin Watson wrote:
Could you try 1.98+20100722-1 once it's available? I think it may fix
this.
Sad to say: nope, it doesn't...
/usr/sbin/grub-probe: info: opening md0
package grub-pc
unmerge 589854
thanks
On Sat, Jul 24, 2010 at 11:44:00PM +0100, Colin Watson wrote:
In that case, Mario, please undo your incorrect merging of your bug with
Achim's, since they manifestly have different causes.
--
We are the Bore. Resistance is futile. You will be bored.
On Sat, Jul 24, 2010 at 11:44:00PM +0100, Colin Watson wrote:
In that case, Mario, please undo your incorrect merging of your bug with
Achim's, since they manifestly have different causes.
I'm just going to bounce my newer comments to 589854, please don't get
confused. I have no idea how to do
On Thu, Jul 22, 2010 at 09:37:15PM +0100, Colin Watson wrote:
Could you try 1.98+20100722-1 once it's available? I think it may fix
this.
Sad to say: nope, it doesn't...
Setting up grub-pc (1.98+20100722-1) ...
/usr/sbin/grub-probe: error: unknown filesystem.
Auto-detection of a filesystem
package grub-pc
severity 589854 grave
merge 589854 589873
thanks
On Wed, Jul 21, 2010 at 10:06:51PM +0100, Colin Watson wrote:
sh -x /usr/sbin/grub-install $(readlink -f
/dev/disk/by-id/ata-WDC_WD1002FBYS-02A6B0_WD-WMATV5728872)
... and post the output to this bug.
I'm not Achim, but since
Package: qtoctave
Version: 0.9.1-1
Severity: grave
Hello,
qtoctave upgrade to 0.9.1-1 fails due to a file-conflict with
quicktime-utils:
Preparing to replace qtoctave 0.8.2+dfsg-2 (using
.../qtoctave_0.9.1-1_i386.deb) ...
Unpacking replacement qtoctave ...
dpkg: error processing
Package: fetch-crl
Version: 2.8.4-1
Severity: grave
Hello,
fetch-crl fails to install:
Unpacking fetch-crl (from .../fetch-crl_2.8.4-1_all.deb) ...
Processing triggers for man-db ...
Setting up fetch-crl (2.8.4-1) ...
update-rc.d: error: start|stop arguments not terminated by .
usage:
Package: ocrfeeder
Version: 0.6.6-1
Severity: serious
Hello,
ocrfeeder fails to install:
Selecting previously deselected package ocrfeeder.
Unpacking ocrfeeder (from .../ocrfeeder_0.6.6-1_all.deb) ...
dpkg: error processing /var/cache/apt/archives/ocrfeeder_0.6.6-1_all.deb
(--unpack):
trying
Package: extlinux
Version: 2:3.83+dfsg-2
Severity: serious
Hello,
the installation of extlinux fails due to a file-conflict with syslinux:
Unpacking extlinux (from .../extlinux_2%3a3.83+dfsg-2_i386.deb) ...
dpkg: error processing
/var/cache/apt/archives/extlinux_2%3a3.83+dfsg-2_i386.deb
Package: dstat
Version: 0.7.0-1
Severity: serious
Hello,
the installation of dstat fails due to a compile error in postinst:
Preparing to replace dstat 0.6.9-1 (using .../archives/dstat_0.7.0-1_all.deb)
...
Unpacking replacement dstat ...
Processing triggers for man-db ...
Setting up dstat
Package: rtmpdump
Version: 1.9-0.0
Severity: serious
Hello,
the installation of rtmpdump fails due to a file-conflict with
flvstreamer:
Unpacking rtmpdump (from .../rtmpdump_1.9-0.0_i386.deb) ...
dpkg: error processing /var/cache/apt/archives/rtmpdump_1.9-0.0_i386.deb
(--unpack):
trying to
On Mon, Nov 23, 2009 at 03:06:04PM +, Martin Michlmayr wrote:
* Mario 'BitKoenig' Holbe mario.ho...@tu-ilmenau.de [2009-11-23 13:01]:
Package: rtmpdump
Version: 1.9-0.0
This pacage doesn't seem to be in Debian. Do you know where you got
I'm sorry, this was my fault - I just forgot
Package: ninja
Version: 0.1.2-4
Severity: serious
Hello,
ninja's postinst fails due to the shipped conffile:
Preparing to replace ninja 0.1.2-3 (using .../ninja_0.1.2-4_i386.deb) ...
Unpacking replacement ninja ...
Setting up ninja (0.1.2-4) ...
/etc/init.d/ninja: 27: escalation: not found
Package: cryptsetup
Version: 2:1.0.7-2
Severity: grave
Hello,
cryptsetup 1.0.7-2 recommends to replace vol_id and un_vol_id by blkid
and un_blkid. Both of these scripts depend on /sbin/blkid.
However, /sbin/blkid is not available in the initramfs image.
Considering your changelog statement that
Package: acct
Version: 6.4~pre1-8
Severity: serious
Hello,
acct 6.4~pre1-8 started to ship
/usr/share/info/dir.gz
which is very likely not intentional.
First of all, this file is usually managed by install-info and thus gets
overwritten regularly which causes acct's package checksums to
On Sat, Aug 22, 2009 at 01:30:56PM -0400, Frédéric Brière wrote:
Alright, I'll go ahead and commit this fix.
Now where you have agreed on how to handle this file, you could probably
also find a solution for /etc/logcheck/ignore.d.server/ntp - which is
shipped in logcheck-database as well as ntp
On Tue, Jul 21, 2009 at 12:49:13PM +0200, Mario 'BitKoenig' Holbe wrote:
If you think about an upgrade-path for the conf-files, I'm not sure
whether unchanged obsolete conffiles get removed automagically in the
meantime or not.
I now got a peek on 2.13.2-31.
It seems /etc/default/timidity
Package: timidity
Version: 2.13.2-29
Severity: serious
Hello,
timidity's init-script test for the existence of
/usr/share/doc/timidity-daemon violates the Debian policy 12.3.:
Packages must not require the existence of any files in
`/usr/share/doc/' in order to function.
A far more clean split
On Tue, Jul 21, 2009 at 12:12:25PM +0200, Joost Yervante Damad wrote:
The reason I didn't take that approach is because I couldn't easily provide a
transparent upgrade path here, but since indeed the current approach violates
policy I think I will go for /etc/init.d/timidity in
On Sun, Nov 30, 2008 at 02:13:42PM +0100, Jarek Kami?ski wrote:
What about handling it via kernel module autoloading? oss-compat would
create /dev/{audio,dsp} and OSS would get loaded only when it's needed.
Apart from kernel module autoloading being out of date...
What about just not installing
On Sun, Nov 30, 2008 at 09:11:52PM +0100, Sven Joachim wrote:
Am 30.11.2008 um 14:29 schrieb Mario 'BitKoenig' Holbe:
What about just not installing oss-compat when you don't like to have
the OSS-emu modules loaded?
Unfortunately this is not possible for many people, any KDE program
On Mon, Nov 03, 2008 at 09:33:21AM +0100, Michael Meskes wrote:
The big question is why does it work on all my systems. Hmm...
Hmmm, /etc/init.d/watchdog restart should fail on your systems as well.
It doesn't print any errors, you only see the problem in syslog and when
you check your processes
Package: lynx
Version: 2.8.6-2.1
Severity: serious
Hello,
with 2.8.6-2.1 lynx stopped linking against a SSL library and thus lynx
complains when it is requested to open a https:// URL:
Alert!: This client does not contain support for HTTPS URLs.
However, the package still claims to
On Fri, Jun 27, 2008 at 07:57:46PM +0200, Andreas Metzler wrote:
(currently shipped in package lynx-cur) the only thing to fix this
bug is to stop providing lynx-ssl.
Yes.
Why should this bug be severity serious?
Because the package claims things it cannot hold. It's just as formal as
Package: rar
Version: 1:3.8b2-1
Severity: grave
Hello,
rar 1:3.8b2-1 fails to install:
Preparing to replace rar 1:3.7.1-2 (using .../rar_1%3a3.8b2-1_i386.deb) ...
dpkg: error processing /var/cache/apt/archives/rar_1%3a3.8b2-1_i386.deb
(--unpack):
subprocess pre-installation script returned
Package: ike
Version: 2.0.3+dfsg-1
Severity: serious
Hello,
the ike package installation fails if racoon is present on the system:
Setting up ike (2.0.3+dfsg-1) ...
Starting Shrew Soft IKE daemon...ii : reading config /etc/iked.conf
!! : socket bind failed
daemon network configuration failed
(
Package: python-ctypes
Version: 1.0.2-4
Severity: serious
Hello,
currently, python-ctypes does not install due to it's dependency on
libffi4 which has intentionally stopped building by the gcc-maintainers
starting with gcc-4.3 (4.3.0-4) - see also #479115.
Could you please instead depend on
Package: libdigest-md4-perl
Version: 1.5.dfsg-1.2
Severity: serious
Hello,
perl currently transits from 5.8.8 to 5.10.0. This breaks
libdigest-md4-perl which depends on perlapi-5.8.8. Could you please
instead depend on perlapi-5.10.0.
Thanks for your work regards
Mario
--
I heard, if you
On Sat, Sep 22, 2007 at 06:54:04AM +, Debian Bug Tracking System wrote:
* Bug fix: fvwm: postinst fails, thanks to Mario #39;BitKoenig#39;
Holbe. Added a Section field to doc-base file. Funny thing is, this
did not fail to install for me -- I wonder why. (Closes:
Package: fvwm
Version: 1:2.5.23-1
Severity: serious
Hello,
postinst of 1:2.5.23-1 fails:
Setting up fvwm (1:2.5.23-1) ...
Error in `/usr/share/doc-base/fvwm', line 12: `Section' value not specified
dpkg: error processing fvwm (--configure):
subprocess post-installation script returned error
Package: watchdog
Version: 5.3-1
Severity: grave
Hello,
since 5.3-1 wd_keepalive stores it's pid in /KA_PIDFILE and not in
/var/run/wd_keepalive.pid anymore. This breaks the wd_keepalive
init-script.
Thanks for your work regards
Mario
--
Oh Du mein Koenig ... Eine Netzgroesse schrieb mal
Package: xterm
Version: 222-2
Severity: grave
Hello,
xterm 222-2 fails to install:
Setting up xterm (222-2) ...
Installing new version of config file /etc/X11/app-defaults/KOI8RXTerm ...
error in control file: `Format' value not specified at /usr/sbin/install-docs
line 699,
On Thu, Nov 16, 2006 at 05:58:58AM -0800, Steve Langasek wrote:
done -- in the general case you get a 30 return /after/ it's been shown to
the user, since the first time it's called is normally when it does get
displayed...
Ah, now I got it - and I can also explain it now :)
The messages which
Package: gradm
Version: 1.9.15-2.1
Severity: grave
Hello,
gradm version 1.9.15-2.1 fails to install:
Preconfiguring packages ...
gradm failed to preconfigure, with exit status 30
(Reading database ... 229400 files and directories currently installed.)
Preparing to replace gradm 1.9.15-2 (using
On Wed, Nov 15, 2006 at 11:01:51PM -0800, Steve Langasek wrote:
On Wed, Nov 15, 2006 at 04:38:39PM +0100, Mario 'BitKoenig' Holbe wrote:
gradm version 1.9.15-2.1 fails to install:
Are you trying to use the non-interactive front-end?
for debconf? No, my debconf frontend is Dialog.
I think
Hi,
On Fri, Nov 10, 2006 at 04:18:15AM -0800, Debian Bug Tracking System wrote:
#396716: irda-utils: fails to install,
It has been closed by Alberto Gonzalez Iniesta [EMAIL PROTECTED].
* Added '-e' to sysctl calls so that a bad kernel/package
configuration won't stop the package
Package: lirc-modules-source
Version: 0.8.0-9
Severity: grave
Hello,
building lirc-modules from 0.8.0-9 on kernel 2.4.27 works well, but a
subsequent modprobe lirc_dev freezes the whole system (at least until a
kernel-watchdog issues a hard reboot). Reverting back to
lirc-modules-source 0.8.0-7
Package: acct
Version: 6.4~pre1-1
Severity: grave
Hello,
the new package version tries to completely avoid a user-configurable
path to the acct-logfile, but is not consistent there, since the
init-script still relies on ACCT_LOGFILE being set, which results in:
[EMAIL PROTECTED]:~# debsums -as
Package: irda-utils
Version: 0.9.18-3
Severity: grave
Hi,
irda-utils fails to install because the init-script fails to start:
Setting up irda-utils (0.9.18-3) ...
depmod: *** Unresolved symbols in /lib/modules/2.4.27/CiscoVPN/cisco_ipsec
Starting IrDA service: irattacherror: net.irda.discovery
Package: xen-hypervisor-3.0.3-rc1-i386
Version: 3.0.3~rc1+hg11686-1
Severity: grave
Hello,
xen-hypervisor-3.0.3-rc1-i386 fails to install:
Setting up xen-hypervisor-3.0.3-rc1-i386 (3.0.3~rc1+hg11686-1) ...
Searching for GRUB installation directory ...
No GRUB directory found.
To create a
On Thu, Oct 12, 2006 at 08:30:08AM +0200, Mario 'BitKoenig' Holbe wrote:
xen-hypervisor-3.0.3-rc1-i386 fails to install:
Oh, and it does also fail to purge:
# dpkg --purge xen-hypervisor-3.0.3-rc1-i386
(Reading database ... 229724 files and directories currently installed.)
Removing xen
On Wed, Oct 11, 2006 at 03:59:36PM +0200, Thijs Kinkhorst wrote:
On Wed, 2006-10-11 at 15:03 +0200, Mario 'BitKoenig' Holbe wrote:
Oh, in that case... could you please try with version 3.95-2 and see
if this behaves the same?
Same experience - just noise.
Interesting.
Did xawtv ever work
On Wed, Oct 11, 2006 at 03:59:36PM +0200, Thijs Kinkhorst wrote:
Same experience - just noise.
Oh, and what exactly do you mean with just noise, you don't mean the
usual black-white noise (the ant war or whatever you like to name it)
on empty channels, do you?
Did you configure xawtv with
Package: gpar2
Version: 0.3-1
Severity: grave
Hello,
the installation of gpar2 fails - probably due to a missing
existence-guard for the call to update-desktop-database or
a missing dependency on desktop-file-utils:
Setting up gpar2 (0.3-1) ...
/var/lib/dpkg/info/gpar2.postinst: line 23:
Package: libquicktime0
Version: 1:0.9.10+debian-2
Severity: grave
Hello,
upgrading to libquicktime0 1:0.9.10+debian-2 causes fbtv and xawtv (and
very likely others from the same source, too) to core immediately on
startup.
Downgrading to the previous version (libquicktime0 1:0.9.7-0.6+b1)
package xserver-xorg
reopen 385078
thanks
On Thu, Oct 05, 2006 at 08:19:17PM -0700, Debian Bug Tracking System wrote:
#385078: xserver-xorg: impossible mouse configuration other than
/dev/input/mice,
It has been closed by David Nusinow [EMAIL PROTECTED].
* Make /dev/input/mice the default
Hi,
On Sun, Sep 17, 2006 at 05:54:43PM -0400, José Parrella wrote:
Please try this patch. I'm not a bash (nor debconf!) guru but I think
that it address your concerns regarding the non-interactivity for the
mouse device setting. Please let me know if the patch works for you.
Well, I would
On Mon, Sep 18, 2006 at 12:41:32PM -0400, José Parrella wrote:
Indeed. I do not mean to steal their work (and actually the Developer's
I didn't mean stealing too, I meant more like fiddling into their plans.
Like, if they are working on it currently and you NMU something
inbetween, this would
package fbtv
reopen 384791
thanks
On Tue, Sep 05, 2006 at 12:32:31AM +0200, Aurelien Jarno wrote:
They have failed due to a temporary problem, but the buildd maintainers
of those architecture haven't requeued them. I will ask them.
Hmmm, this seems to take a while. I'll reopen then bug to
On Sat, Sep 02, 2006 at 11:48:15AM -0700, Debian Bug Tracking System wrote:
From: Aurelien Jarno [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
This bug has been fixed in version 3.95-4, closing it.
Hm, do you probably have an idea why especially the arm and i386
versions are not yet built?
Thanks
Package: oss-compat
Version: 0.0.1
Severity: serious
Hello,
oss-compat fails to install on 2.4.27:
Setting up oss-compat (0.0.1) ...
modprobe: Can't locate module snd-seq-oss
dpkg: error processing oss-compat (--configure):
subprocess post-installation script returned error exit status 255
Package: xserver-xorg
Version: 1:7.0.23
Severity: serious
Hello,
upgrading xserver-xorg from 6.9.0.dfsg.1-6 to 1:7.0.23 broke my
previously running X:
No core pointer
Fatal server error:
failed to initialize core devices
This is because xserver-xorg.config forces mouse
Package: fbtv
Version: 3.95-3
Severity: grave
Hello,
with 3.95-3 fbtv stopped working:
[EMAIL PROTECTED]:/home/holbe% fbtv
using linux console font /usr/share/consolefonts/lat1-16.psf.gz
map: vt03 = fb0
mmap: Invalid argument
[1]1818 exit 1 fbtv
[EMAIL PROTECTED]:/home/holbe%
Package: sendmail-bin
Version: 8.13.4-3sarge2
Severity: grave
Tags: sarge, security
Hello,
the just released security fix package 8.13.4-3sarge2 does not install
on sarge, because it depends on libsasl2 (= 2.1.19.dfsg1) while on
sarge only libsasl2 (2.1.19-1.5sarge1) is available.
Package:
On Fri, Apr 21, 2006 at 08:30:08PM +0200, Lars Bahner wrote:
This bug should be solved when imake settles. Nothing to be done at this
end for now.
do you by chance have an idea already, when this will happen?
Thanks for your work regards
Mario
--
delta talk softly and carry a keen sword
Package: reportbug
Version: 3.21
Severity: grave
Hello,
the post-installation script of reportbug 3.21 fails:
Setting up reportbug (3.21) ...
Compiling /usr/share/reportbug/reportbug_submit.py ...
File /usr/share/reportbug/reportbug_submit.py, line 354
while failed != True:
^
package cgiirc
tags 365680 + patch
thanks
On Tue, May 02, 2006 at 10:30:11PM +0200, Elrond wrote:
To create a new package:
- Place the .dpatch in debian/patches
- Add 50_client-c_bufferoverflow_fix.dpatch to
debian/patches/
- Add 50_client-c_bufferoverflow_fix to debian/patches/00list
-
On Thu, May 04, 2006 at 04:55:39PM +0200, Martin Schulze wrote:
Are you going to update the package in sid as well?
We're preparing a new version for sid, which of course will include the
fix, too. But this will take a few days longer, so...
Or should the package propagate via stable-security?
Hi,
On Tue, May 02, 2006 at 10:15:37AM +0800, Paul Wise wrote:
Upstream has just released 0.5.8, which fixes a buffer overflow in
client.c amongst other things. The 0.5.8 timeline can be seen here:
Just as a short-term reply and for documentation reasons regarding this
issue:
The Debian
On Tue, May 02, 2006 at 08:46:28PM +0100, David Leadbeater wrote:
Mario: It does affect all configurations, just because the
configuration file says client-perl.cgi it doesn't stop someone
accessing client.cgi as the package builds client.cgi and puts it
Yes, i missed that in the first
Package: lvm2
Version: 2.02.02-1
Severity: grave
Hello,
the lvm2 package fails to install at least on systems running a kernel
2.6.12.
A debconf message box appears during the installation, telling:
Running kernel TOO old
Your running kernel is 2.6.12. lvm2 since 2.02.00 does not work with
On Wed, Mar 22, 2006 at 09:18:13AM -0800, Debian Bug Tracking System wrote:
From: Bastian Blank [EMAIL PROTECTED]
On Wed, Mar 22, 2006 at 02:37:22PM +0100, Mario 'BitKoenig' Holbe wrote:
I'm not sure whether this is intentional or not.
It is.
Could you then please at least comment a little
Package: libsensors3
Version: 1:2.10.0-2
Severity: grave
Hello,
since 2.10.0-2 libsensors doesn't support kernel 2.4 proc interface
anymore (although it suggests it would), with 2.10.0-1 everything did
work well:
[EMAIL PROTECTED]:~# dpkg -i
Package: cdrdao
Version: 1:1.2.1-5
Severity: serious
Hello,
while 1:1.2.1-4 did coexist well with cue2toc, 1:1.2.1-5 doesn't do
anymore:
Preparing to replace cdrdao 1:1.2.1-4 (using .../cdrdao_1%3a1.2.1-5_i386.deb)
...
Unpacking replacement cdrdao ...
dpkg: error processing
Package: dumputils
Version: 0.4-6
Severity: serious
Hello,
dumputils modifies /etc/dumputils.conf in it's postinst script, which is
against Debian Policy 10.7.3.
This behaviour did lead to a) DUMP_FLAGS=0 appended to my dumputils.conf
although I had DUMP_FLAGS=1 manually configured there (this
On Wed, Sep 28, 2005 at 07:02:34PM +0300, Alexander Gattin wrote:
merge 330526 330247
thanks
IMHO it's better to have all these grave conflicts
with manpages-XX merged in single place.
Well, unfortunately, 330247 was for login (which was why I didn't report
a dup for login yesterday) and is
On Mon, Apr 25, 2005 at 12:34:52PM +0200, Joerg Dorchain wrote:
exspected. After the the first dis- and reconnect (i.e. after 24h) pppd
eats up all cpu time. The reconnect itself works as expected, but the
systems becomes notably slow with pppd playing cpu-hog.
...
with fd 13 and 14 being
87 matches
Mail list logo
