Bug#692234: Intel DH77EB (H77): sporadic freeze and increased power consumption
On Sun, Dec 02, 2012 at 01:54:51PM +0100, Ingo wrote: > Since 2 weeks I an running kernel 3.4 from kernel.org. I used config from > Debian's 3.4.4-1~experimental.1 with "make silentoldconfig" and accepted > defaults fo 5 new items. This is a long term kernel as well and thus > still maintained. > > I started with 3.4.18, updated to 3.4.19 and now using 3.4.20. > All without any problems including VirtualBox 4.1.18 from Wheezy repo. > > This also appears a viable alternative to current 3.2? Julien Cristau wrote at bug #687442 --- New image is up at http://people.debian.org/~jcristau/linux-image-3.2.0-4.drm-amd64_3.2.34-1~jcristau.1_amd64.deb sha1sum is 1bbb6e4590e4f000739af89f3090ffc6bb9cb409. diff against svn at http://people.debian.org/~jcristau/3.2.34-1~jcristau.1.diff --- That kernel image is based on 3.2 with graphics system backported from 3.4 It would help if you can test that version too. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#681757: uninstallable meta-packages (prevents testing migration)
On Mon, Jul 16, 2012 at 10:34:06AM +0200, Michael Biebl wrote: > Source: meta-gnome3 > Version: 1:3.4+1 > Severity: serious > > Due to additional dependencies that were added recently, the gnome meta > packages are no longer installable on all architectures: > > > gnome/armel unsatisfiable Depends: aisleriot (>= 3.4) > > gnome/armhf unsatisfiable Depends: aisleriot (>= 3.4) > > gnome/ia64 unsatisfiable Depends: aisleriot (>= 3.4) > > This is due to guile-2.0 failing to build on those architectures. [1] > Afaics no bug has been filed for guile-2.0 about those build failures. Did you ask porters for help? Arm userbase grows and things should work. > > > gnome-core-devel/ia64 unsatisfiable Depends: libseed-gtk3-dev (>= 3.2) > > gnome-core-devel/mips unsatisfiable Depends: libseed-gtk3-dev (>= 3.2) > > seed has been broken on those architectures for a while and I don't > expect a fix any time soon. mips buildd ball had some issues with segfaults, it's now put offline https://lists.debian.org/debian-release/2012/07/msg00887.html so you should ask for mips giveback, maybe ia64 works now too? > > > At this point, I'd probably just arch-qualify those dependencies and > exclude those archs. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#651795: linux-3.1 is not supported by upstream
On Tue, Jul 10, 2012 at 04:26:17PM +0200, Patrick Winnertz wrote: > Hey, > > > Upstream support is irrelavant for this bug. > Nope it is not.. > > in fact this situation was exactly the same for the last two debian > releases... lustre didn't support the standard kernel in these > releases. > this is not that bad than it sounds as lustre is a very very specific > kind of software, which is rarely/not at all used by normal users. > > This specific package is needed to build the kernel modules for the > server and the client servers of lustre - and for this you really need > plain kernel.org kernels (or SLES ones). > > I would really appreciate if we could come to the agreement, as done for > the last releases also, that the support of the standard debian kernel > is no RC bug for lustre. Loosing this type of software in debian, would > be not good. Citing wikipedia: > > Because Lustre has high performance capabilities and open licensing, it > is often used in super computers. At the present time, fifteen of the > top 30 supercomputers in the world have Lustre file systems in them, > including the world's fastest TOP500 supercomputer, IBM Sequoia. > (http://en.wikipedia.org/wiki/Lustre_(file_system)) I read some basic information from homepage and Wikipedia. Looks like 2.0, 2.1, 2.2 versions have been released in last years. Shouldn't Debian package been updated to 2.x as well? If staying on 1.8, 1.8.6 and later clients can interoperate 2.x servers. But Debian package is still at 1.8.5 with some bugs that are fixed in later versions. Maybe you should ask wider opinion what to do with Lustre in Debian. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#680832: libio-async-perl: FTBFS: unsatisfiable build-dependency: perl (>= 5.15.6) but 5.14.2-12 is to be installed
On Sun, Jul 08, 2012 at 12:02:43PM -0600, gregor herrmann wrote:
> On Sun, 08 Jul 2012 18:59:34 +0200, Lucas Nussbaum wrote:
>
> > > The following packages have unmet dependencies:
> > > sbuild-build-depends-libio-async-perl-dummy : Depends: perl (>= 5.15.6)
> > > but 5.14.2-12 is to be installed
> > > E: Unable to correct problems, you have held broken packages.
> > > apt-get failed.
>
> I'm not sure what's happening here:
> The package has
> libsocket-perl | perl (>= 5.15.6)
> in B-D-I, and libsocket-perl exists in unstable since the end of
> June.
> And AFAICS libsocket-perl is not yet provided by any perl{,-modules}
> packages.
>
> Anyone with ideas?
Actually it has "perl (>= 5.15.6) | libsocket-perl (>= 1.95)" and sbuild
acts on first option only. Maybe put them in reverse?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#679964: snappy vs. snappy-player and BTS
Looks like this bug belongs to sourcepackage snappy, not binary snappy (src:snappy-player). -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#679964: snappy vs. snappy-player and BTS
On Tue, Jul 03, 2012 at 12:47:39AM +0300, Touko Korpela wrote: > Looks like this bug belongs to sourcepackage snappy, not binary snappy > (src:snappy-player). While this bug (#679964) is reported against binary package snappy BTS shows this wrong? information: Package: snappy; Maintainer for snappy is Steinar H. Gunderson ; Source for snappy is src:snappy-player. But maintainer for src:snappy-player should be "Maintainers of GStreamer packages " (Maintainer for src:snappy is Steinar H. Gunderson) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#549681: mkvmlinuz: use xz to compress vmlinuz-boxed initrd
On Sun, Jul 01, 2012 at 11:03:02AM -0400, Milan Kupcevic wrote: > On 07/01/2012 07:05 AM, Touko Korpela wrote: > >> ... > >> +if test "$post_2_6_38"; then > >> + XZ="xz --check=crc32 -8" > >> +else > >> + XZ=false > >> +fi > > > > From xz(1) manual page (you can ignore DecMem): > > Preset DictSize CompCPU CompMem DecMem > >-0 256 KiB 03 MiB1 MiB > >-1 1 MiB 19 MiB2 MiB > >-2 2 MiB 2 17 MiB3 MiB > >-3 4 MiB 3 32 MiB5 MiB > >-4 4 MiB 4 48 MiB5 MiB > >-5 8 MiB 5 94 MiB9 MiB > >-6 8 MiB 6 94 MiB9 MiB > >-7 16 MiB 6 186 MiB 17 MiB > >-8 32 MiB 6 370 MiB 33 MiB > >-9 64 MiB 6 674 MiB 65 MiB > > > > Better to use default setting "-6" that has lower memory requirement. > > > > Here is timing for re-compression from gzip to xz on Pegasos II with > Freescale 7447 1GhZ processor and 1Gb RAM: Use of -8 option isn't a good thing for systems having only 512 Mib or less memory. This operation shouldn't force to use slow swap space or OOM. > > set time compressed size > -91m43.962s9.5MB > -81m44.824s9.5MB > -61m35.097s9.6MB > -31m10.080s10.6MB > -20m45.609s10.7MB > -00m19.286s11.1MB > > I've originally decided to go with -8, mainly because the same preset is > used in mkinitramfs form initramfs-tools package. It may be worth > hearing arguments about the timing given that all presets currently > produce vmlinuz smaller than the 12MB limit, but the compression time is > very different. Your size numbers show that -8 produces only marginally smaller images. If mkinitramfs (initramfs-tools) uses -8 for xz compression, it should be changed too. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#549681: bug#549681: mkvmlinuz: use xz to compress vmlinuz-boxed initrd
On Sat, Jun 30, 2012 at 11:01:47PM -0400, Milan Kupcevic wrote: > The attached patch brings vmlinuz from about 13MB to about 9.5MB, which > is well under the 12MB limit. Downside is that xz compressing is > noticeably slower than currently used gzip, but decompressing speed > difference is not noticeable. > > I've tested it on Pegasos II machine, it boots really fast. Updated > mkvmlinuz package is waiting on mentors.debian.net for a willing sponsor > for upload. > ... > +if test "$post_2_6_38"; then > + XZ="xz --check=crc32 -8" > +else > + XZ=false > +fi >From xz(1) manual page (you can ignore DecMem): Preset DictSize CompCPU CompMem DecMem -0 256 KiB 03 MiB1 MiB -1 1 MiB 19 MiB2 MiB -2 2 MiB 2 17 MiB3 MiB -3 4 MiB 3 32 MiB5 MiB -4 4 MiB 4 48 MiB5 MiB -5 8 MiB 5 94 MiB9 MiB -6 8 MiB 6 94 MiB9 MiB -7 16 MiB 6 186 MiB 17 MiB -8 32 MiB 6 370 MiB 33 MiB -9 64 MiB 6 674 MiB 65 MiB Better to use default setting "-6" that has lower memory requirement. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#678802: osgi-core: Build does not ensure backwards compatible byte-core
If this bug is now fixed with version 4.3.0-3 , it can be marked so and closed. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#678137: git-svn: affected versions?
BTS thinks that this bug affects only unstable and stable? (no wheezy). However tags are "wheezy sid experimental". -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#678636: initramfs-tools: dm-crypt partitions not further working. No asking password to encrypt. System will not boot
On Sat, Jun 23, 2012 at 01:13:04PM +0200, Pierre Bernhardt wrote: > -- /proc/mdstat > Personalities : [raid1] [raid6] [raid5] [raid4] > md50 : active raid5 sda1[0] sdd1[3] sde1[5] > 625137664 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU] > bitmap: 1/3 pages [4KB], 65536KB chunk > > md1 : active raid1 sdc2[0] > 28812480 blocks [1/1] [U] > bitmap: 4/220 pages [16KB], 64KB chunk > > md0 : active raid1 sdc1[0] > 489856 blocks [1/1] [U] > bitmap: 0/60 pages [0KB], 4KB chunk > > unused devices: Your raid1 arrays look strange, with only one component device in each. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#678636: initramfs-tools: dm-crypt partitions not further working. No asking password to encrypt. System will not boot
On Sat, Jun 23, 2012 at 01:13:04PM +0200, Pierre Bernhardt wrote: > Package: initramfs-tools > Version: 0.106 > Severity: critical > Tags: upstream > Justification: breaks the whole system > > After patching my system 3 days ago it will not further boot up. The initramfs > prompt comes before the keypass has to been normally asked for to decrypt my > root partition with the contained lvm root vol disk group. > Before the upgrade been made I didn't hat the problem. I guess this comes with > the upgrade of the initramfs-tools from 0.103 to 0.106. > > Work around at the moment is to use cryptsetup luksOpen manually and start all > lvmvolumes before continue with the boot process by using Crtl-D. > > > > -- Package-specific info: > -- initramfs sizes > -rw-r--r-- 1 root root 11M Jun 22 13:21 /boot/initrd.img-2.6.32-5-amd64 > -- /proc/cmdline > BOOT_IMAGE=/vmlinuz-3.2.0-2-amd64 root=/dev/mapper/rootdg-root ro This lists both 2.6.32-5 and 3.2.0-2 kernels. What kernel version do you try to boot, and is its initramfs updated? By default only most recent kernel does have initramfs updated when updating packages. Your setup has many moving parts that can go wrong. Please list versions of mdadm, dmsetup, libdevmapper*, *cryptsetup* > > -- /proc/mdstat > Personalities : [raid1] [raid6] [raid5] [raid4] > md50 : active raid5 sda1[0] sdd1[3] sde1[5] > 625137664 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU] > bitmap: 1/3 pages [4KB], 65536KB chunk > > md1 : active raid1 sdc2[0] > 28812480 blocks [1/1] [U] > bitmap: 4/220 pages [16KB], 64KB chunk > > md0 : active raid1 sdc1[0] > 489856 blocks [1/1] [U] > bitmap: 0/60 pages [0KB], 4KB chunk > > > -- System Information: > Debian Release: wheezy/sid > APT prefers proposed-updates > APT policy: (500, 'proposed-updates'), (500, 'stable'), (300, 'testing'), > (200, 'unstable'), (150, 'experimental') > Architecture: amd64 (x86_64) You are using mixed system, packages may have bugs in their depends, so that manual updating or bug reporting is maybe needed. > > Kernel: Linux 3.2.0-2-amd64 (SMP w/6 CPU cores) > Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > > Versions of packages initramfs-tools depends on: > ii cpio 2.11-7 GNU cpio -- a program to manage > ar > ii klibc-utils 2.0-2 small utilities built with klibc > f > ii module-init-tools 3.12-2 tools for managing Linux kernel > mo > ii udev 175-3.1/dev/ and hotplug management > daemo > > Versions of packages initramfs-tools recommends: > ii busybox 1:1.19.3-7 Tiny utilities for small and > embed > > Versions of packages initramfs-tools suggests: > pn bash-completion(no description available) > > -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#678530: only i386 is broken
Nathan, please fix your build environment. Looks like that binNMU is needed again. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#677121: this bug seems fixed
psmisc seems to build fine now, you should close this bug -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#664944: changelog credits
Looks like patch came from Nicolas Bourdaud, not from Lucas Nussbaum. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#678347: libffado: FTBFS on powerpc
Package: libffado Version: 2.0.99+svn2163-2 Severity: serious Justification: fails to build from source (but built successfully in the past) Please look at https://buildd.debian.org/status/package.php?p=libffado 2.0.99+svn2163 fails to build on powerpc -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#677419: fdupes: When using -L and traversing filesystems, removes files
Package: fdupes Followup-For: Bug #677419 It's wrong to remove this useful option, removing causes FTBFS #678254 So -L should be fixed to fail gracefully instead -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#678254: gamera: FTBFS: fdupes: unrecognized option '--linkhard'
Followup-For: Bug #678254 This happens because: Changes: fdupes (1.50-PR2-4) unstable; urgency=low . [ Sandro Tosi ] * debian/patches/50_bts284274_hardlinkreplace.dpatch - disabled, since it's losing data if files are on different - filesystems; thanks to Mike Hommey for the report; Closes: #677419 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#678085: sorry
I'm sorry for extra commands, exim4 or gnome-keyring has a bug (#676984) that made me think that bts command failed -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#677527: gcc-4.7 issue?
Maybe it helps to recompile this package with new compiler. gcc-4.7 releases after this package was last compiled, have fixed some issues -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#675863: accountsservice: makes gdm-simple-greeter crash
Should this bug be marked fixed in version 0.6.21-4 if this is same bug as #673185 ? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#676729: feel++: FTBFS: operators.hpp:722:1: internal compiler error: Segmentation fault
On Sun, Jun 10, 2012 at 10:41:41PM +0200, Christophe Prud'homme wrote: > reassign 676729 gcc-4.7 4.7.0-12 > thanks > > On Sun, Jun 10, 2012 at 10:04 PM, Christophe Prud'homme > wrote: > > Hello > > > > I get an ice with gcc47 (see email below) > > > > I am trying to reproduce it. > > Shouldn't it be considered a gcc47 bug rather than a feel++ bug ? > > Feel++ compiles and runs fine with gcc45, gcc46 and clang31. I recommend that you change feel++ to build-depend on gcc-4.6 for now. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#552468: libsvn-web-perl: Missing dependencies
Good to see some action in old bugs too. 0.53-3.1 NMU has your name in maintainer field, is it intentional? Also last "found" message to control@b.d.o caused bug versioning mess. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668815: fix version
found 668815 0.3-3.1 notfound 668815 0.3-3.2 thanks fixing typo in reported package version... -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#631807: GCC workarounds should be dropped too
When fixing this bug, #563935 and #583881 (GCC workarounds for long time fixed bugs) should be fixed too. They are about sparc and armel arcs. Now this package is compiled unoptimized in these arcs. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#673770: Problem with NMU version?
Is this "modifying files from another package" (found by piuparts) bug specific to 1:2.22-1.1 NMU version or is it also present in 1:2.22-1? If it isn't NMU spesific then BTS version tracking should let know it. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#672678: (cryptmount #672678) unmet dependency on libdevmapper
On Wed, May 23, 2012 at 11:31:33PM +0300, Touko Korpela wrote: > > This bug blocks lvm2 from migrating to testing. Maybe cryptmount should > temporarily removed from testing? Or are tools wrong, and lvm2 update > don't make situation any worse than it's now? Has release managers opinion about this? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#672678: unmet dependency on libdevmapper
tag 672678 patch thanks This bug blocks lvm2 from migrating to testing. Maybe cryptmount should temporarily removed from testing? Or are tools wrong, and lvm2 update don't make situation any worse than it's now? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668954: Status of this bug?
Do you know if this bug "policycoreutils: /usr/bin/sandbox "Invalid argument" error" affects also wheezy version (2.1.10-1)? If so, then maintainers should update BTS status so that it knows this isn't regression. This bug prevents policycoreutils from migrating to testing. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#661069: Bug#649448: radeon (evergreen): random-looking pattern of pixels when firmware not installed
Installer has also a bug report about this (#661069). It would be good if Debian kernel radeon driver learned to fall back sensibly if running on hardware where firmware is required. Also installer should warn user about what happens if firmware is missing. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668397: pu: package wicd/1.7.0+ds1-5+squeeze1
On Thu, Apr 12, 2012 at 12:31:48AM +0200, David Paleino wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: pu > > Hello RT, > > I'm hereby requesting permission to upload a fix for wicd to p-u, bug #668397 > (CCed), CVE-2012-2095. "git diff" attached. > > The patch for stable is slightly different from the one just pushed in > unstable: namely, it needed an additional "has_profile", which was used in > pre-1.7.1 versions. I think this should be handled via Debian Security Advisory procedure. It's a root compromise after all (local but still important imho). -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#574557: Package version is wrong in bug report
Hi! I noticed that this bug has been reported against old version of qpsmtpd. Maybe archive wide consistency check that you (Petter Reinholdtsen) run got the version wrong? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#526560: closing 526560
close 526560 thanks Package is removed from sid/squeeze. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#505699: closing 505699
close 505699 thanks Package is removed from sid/squeeze. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#523475: Unfixed bugs in lenny version
Is #523475 and #517792 same bug? And is it still in 1.1.14-6 (lenny)? Also #522811 seems unfixed too. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#572920: libltdl3: Security update breaks mpg123
Package: libltdl3
Version: 1.5.26-4+lenny1
Severity: grave
Justification: renders package unusable
Libtool security update seems to have broken mpg123 (1.4.3-4). It can't find or
load output plugins. I don't know what package to blame but things should keep
working in stable.
-- System Information:
Debian Release: 5.0.4
APT prefers stable
APT policy: (900, 'stable'), (700, 'unstable'), (500, 'oldstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages libltdl3 depends on:
ii libc6 2.7-18lenny2 GNU C Library: Shared libraries
libltdl3 recommends no packages.
libltdl3 suggests no packages.
-- no debconf information
execve("/usr/bin/mpg123-alsa", ["mpg123-alsa", "-v", "../iTunes/iTunes
Music/Chorale/U"...], [/* 34 vars */]) = 0
brk(0) = 0x80f8000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7fc3000
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=48713, ...}) = 0
mmap2(NULL, 48713, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7fb7000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/libncurses.so.5", O_RDONLY) = 3
read(3,
"\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0p\243\0\0004\0\0\0\344"...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=202188, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7fb6000
mmap2(NULL, 202004, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0xb7f84000
mmap2(0xb7fb3000, 12288, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x2f) = 0xb7fb3000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/i686/cmov/libdl.so.2", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0`\n\0\0004\0\0\0H"...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=9680, ...}) = 0
mmap2(NULL, 12412, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0xb7f8
mmap2(0xb7f82000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1) = 0xb7f82000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/i686/cmov/libc.so.6", O_RDONLY) = 3
read(3,
"\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\260e\1\0004\0\0\0\4"..., 512)
= 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=1413540, ...}) = 0
mmap2(NULL, 1418864, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0xb7e25000
mmap2(0xb7f7a000, 12288, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x155) = 0xb7f7a000
mmap2(0xb7f7d000, 9840, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb7f7d000
close(3)= 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7e24000
set_thread_area({entry_number:-1 -> 6, base_addr:0xb7e246b0, limit:1048575,
seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0,
useable:1}) = 0
mprotect(0xb7f7a000, 4096, PROT_READ) = 0
munmap(0xb7fb7000, 48713) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
open("/dev/tty", O_RDWR|O_NONBLOCK|O_LARGEFILE) = 3
close(3)= 0
brk(0) = 0x80f8000
brk(0x80f9000) = 0x80f9000
open("/usr/lib/locale/locale-archive", O_RDONLY|O_LARGEFILE) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=2721184, ...}) = 0
mmap2(NULL, 2097152, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7c24000
mmap2(NULL, 929792, PROT_READ, MAP_PRIVATE, 3, 0x1b6) = 0xb7b41000
close(3)= 0
brk(0x80fa000) = 0x80fa000
brk(0x80fb000) = 0x80fb000
getuid32() = 1000
getgid32() = 1000
geteuid32() = 1000
getegid32() = 1000
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
time(NULL) = 1267980860
brk(0x80fc000) = 0x80fc000
open("/proc/meminfo", O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7fc2000
read(3, "MemTotal: 776044 kB\nMemFree"..., 1024) = 872
close(3)= 0
munmap(0xb7fc2000, 4096)= 0
brk(0x80fd000) = 0x80fd000
rt_sigaction(SIGCHLD, {SIG_DFL}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGCHLD, {SIG_DFL}, {SIG_DFL}, 8) = 0
rt
Bug#410580: (CVE-2007-0855) Preparation of the next stable Debian GNU/Linux update
On Sun, May 20, 2007 at 08:33:16PM +0200, Martin Zobel-Helas wrote: > On Sun May 20, 2007 at 17:29:19 +0300, Touko Korpela wrote: > > Unrar (source package unrar-nonfree) has CVE-2007-0855 (Stack-based buffer > > overflow) bug in etch and sarge. It has debian bug #410580 > > Maintainer didn't ask for it but should 1:3.7.3-1 be included in 4.0r1? > > yes, please upload. Unrar-nonfree is still vulnerable after last etch update. Maybe somebody should upload fixed version finally? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#441633: gcc 4.2 can't build erlang on mips and mipsel
Sergei Golovan wrote: > Version 4.2.1-6 didn't fix this bug. Errors are exactly the same. Is 4.2.1-4 (in testing currently) buggy too? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#410580: CVE-2007-0855: Stack-based buffer overflow in Unrar
Could someone prepare update for unrar-nonfree to next etch point release fixing security issues? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#443574: Several applications crash after migration from 2.10 to 2.12
reopen 443574 thanks I think this bug should stay open for couple of days util fixed wxwidgets is uploaded to prevent many programs from crashing in testing. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#439897: Patent holders on mpeg2 encoder
libavutil version: 1d.49.3.0 libavcodec version: 1d.51.38.0 libavformat version: 1d.51.10.0 built on Jun 23 2007 14:31:53, gcc: 4.1.3 20070601 (prerelease) (Debian 4.1.2-12) File formats: E mpeg2video MPEG2 video Codecs: D VSDT mpeg2video Doesn't this mean that mpeg2 encoder is disabled in 0.cvs20070307-6? (no E in mpeg2video codec line, but E shows in file formats,error maybe) Compare to unofficial ffmpeg where mpeg2 encoding is enabled: DEVSDT mpeg2video -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#437628: severity of 437628 is important, tagging 437628
# Automatically generated email from bts, devscripts version 2.10.8 severity 437628 important #etch version works only with php4 tags 437628 etch -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#287519: Here is relevant lines from xine crash (#407002)
xine: found demuxer plugin: mpeg pes demux plugin video discontinuity #1, type is 0, disc_off 0 waiting for audio discontinuity #1 audio discontinuity #1, type is 0, disc_off 0 waiting for in_discontinuity update #1 vpts adjusted with prebuffer to 37691 av_offset=0 pts spu_offset=0 pts xine_play play_internal ...done load_plugins: plugin mad will be used for audio streamtype 01. libmad: ALERT input buffer too small (22681 bytes, 16384 avail)! xiTK received SIGSEGV signal, RIP. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#442882: Known issue
Have a look in bugs #181378 (+merged) and #439931 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#443440: icedove: Segfaults with GTK 2.12
Mathias Brodala wrote: >Version: 1.5.0.10.dfsg1-3 >Trying to start Icedove after upgradingt to GTK 2.12 fails with a segfault. >Debugging output is attached. >And no, I cannot (or do not want to) upgrade to Icedove 2.0.0.4 ATM because >this way I’d lose both the Typeaheadfind and DOM inspectory extension. Please try upgrading to 1.5.0.12.dfsg1-0etch1 or 1.5.0.12.dfsg1-0etch1+lenny1 These are security/stability updates.
Bug#436277: pcre3 compiled possibly in wrong environment for i386
I noticed that binary packages for i386 (compiled in maintainers system) depend libc6 (>= 2.3.6-6) This means etch system was used for building (instead of uptodate sid) Maybe that causes some problems for i386 users. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#436210: This bug was not marked closed by 7.3-2 upload
Your pcre3 (7.3-2) upload used wrong syntax for bug closing in changelog. So maybe you should manually send (versioned) closing message to [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#443039: libmatthew-java: FTBFS: Exception in thread "main" java.lang.NullPointerException
Michael Koch wrote: >This bug was fixed in the version 0.7.8-5 But this FTBFS build used 0.7.8-6. Is this bug reappeared? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#441787: 1.4.18-1 should been uploaded with high urgency
Shouldn't releases containing security fixes be uploaded with higher urgency than low? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#428616: Can this bug be closed now?
This bug and the bug it's merged with are marked fixed (and are fixed too most likely). So maybe mail should be sent to -done (with version header) closing this bug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#413254: Is this bug fixed in 1.00-1?
You didn't ack NMU in your last upload, so BTS thinks this bug is still there. If it's fixed, you should send message to [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#412502: Is this bug fixed in 3.2.3-4?
You didn't ack NMU in your last upload, so BTS thinks this bug is still there. If it's fixed, you should send message to [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#425978: [pkg-GD-devel] Processed: found 425978 in 2.0.33-5.2
On Mon, Aug 13, 2007 at 10:33:58AM +0200, Jonas Smedegaard wrote: > Please use the BTS "fixed" tag with care: it seems to override (not > coexist with) a "done" tag for the same version. > > In this case the net result was that you reopened the bugreport, also > for version 2.0.34 and newer. What makes you to believe that? I watched BTS web page before and after my commands noticing no strangeness. The bug was closed as it should be. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#435983: mount: fails to detect LABEL=foo filesystems
- Forwarded message from James Youngman <[EMAIL PROTECTED]> - From: James Youngman <[EMAIL PROTECTED]> To: Touko Korpela <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Subject: Re: Bug#435983: mount: fails to detect LABEL=foo filesystems Cc: [EMAIL PROTECTED] X-Google-Sender-Auth: 5717268626e0dd81 On 8/9/07, Touko Korpela <[EMAIL PROTECTED]> wrote: > On Thu, Aug 09, 2007 at 09:48:45AM +0100, James Youngman wrote: > > On 8/7/07, Touko Korpela <[EMAIL PROTECTED]> wrote: > > > Please tell udev version installed. > > And please show mdadm version and configuration. # dpkg -l udev mdadm Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name VersionDescription +++-==-==- ii mdadm 2.6.2-2tool to administer Linux MD arrays (software ii udev 0.114-2/dev/ and hotplug management daemon orbital:~# cat /etc/mdadm/mdadm.conf DEVICE partitions ARRAY /dev/md1 level=raid1 num-devices=2 UUID=0e6624e4:a9cd6984:f20ceecf:919b57cd ARRAY /dev/md0 level=raid1 num-devices=2 UUID=fcd276e7:ea94c8d0:0d41aa71:22d0670d spares=1 ARRAY /dev/md2 level=raid1 num-devices=2 UUID=ca5a9e9b:b1d43782:c9b96cb6:728e3dae ARRAY /dev/md3 level=raid1 num-devices=2 UUID=54b26978:997db266:f00a6e1e:efeca1cb MAILADDR root orbital:~# cat /proc/mdstat Personalities : [raid1] md3 : active raid1 sdb3[0] sda3[1] 116312640 blocks [2/2] [UU] md2 : active raid1 sdb2[0] sda2[1] 122070208 blocks [2/2] [UU] md0 : active(auto-read-only) raid1 hda3[0] hde3[1] 995904 blocks [2/2] [UU] md1 : active raid1 hda6[0] sdb1[2](S) hde6[1] 250003392 blocks [2/2] [UU] unused devices: - End forwarded message - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#435983: mount: fails to detect LABEL=foo filesystems
On Thu, Aug 09, 2007 at 09:48:45AM +0100, James Youngman wrote: > On 8/7/07, Touko Korpela <[EMAIL PROTECTED]> wrote: > > Please tell udev version installed. And please show mdadm version and configuration. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#436651: gaim: Crashes when clicking on URL in chat window
severity 436651 grave tags 436651 moreinfo thanks Armando, you seem to use version of gaim currently in testing (beta5-11). Your apt setup is currently using stable only (maybe you changed that recently). Leaving system with some packages from newer releases that now won't be updated anymore because of only stable listed in apt config can cause bugs hard to track. I would suggest to remove gaim packages currently installed and try to install stable version back (beta5-10). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#435983: mount: fails to detect LABEL=foo filesystems
Please tell udev version installed. You are using 2.6.18-4-xen-686 kernel from etch? Is xen in use? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#435537: Already fixed
This issue is already fixed in 2.13~rc2-4 ... Recommend: nfs-common so that portmap doesn't become defacto-Required ... So this bug can be closed. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#435537: Is this bug justified?
If it's decided that this dependency is OK then shouldn't this bug be reassigned to nfs-common or ftp team (for raising nfs-common priority). (and severity grave seems too much) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#418161: acknowledged by developer (closing 418161)
>Why do you close this bug again? It's already closed a few times >with the right version. Do you for some reason think it's not closed? It wasnt closed, only tagged fixed (check BTS web log if in doubt). (tag fixed should be needed only for NMUs) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#428293: Time for security upload?
Could security team look at this and make upload for stable (and perhaps oldstable)? DoS in unstable is still there too, but that's perhaps different issue. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#320940: Status of this bug?
Is this bug relevant any longer? It was reported against sarge and now package name has changed to libapache2-mod-jk. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#396360: Maybe time for DSA?
This bug has patch included, maybe security team could do upload? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#434597: reopening 434597, severity of 434597 is grave, reassign 434597 to yaird
# Automatically generated email from bts, devscripts version 2.10.6 reopen 434597 severity 434597 grave #reassigning to yaird, you shouldn't close bugs too fast reassign 434597 yaird 0.0.12-20 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#432674: Please request binNMU for amd64
On Sun, Jul 22, 2007 at 03:22:41AM +0300, Touko Korpela wrote: > BinNMU for amd64 should fix this if package is binNMUable. > Please ask debian-release mailing list. > Same for libgnash0 Please ignore that. Seems that binNMU has been already made. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#432674: Please request binNMU for amd64
BinNMU for amd64 should fix this if package is binNMUable. Please ask debian-release mailing list. Same for libgnash0 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#432267: Is this now fixed?
This bug can be closed if it's fixed. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#433077: binNMU for amd64?
Tony Houghton wrote: >It isn't fixed. The amd64 version still depends on libcurl4-gnutls >which doesn't exist. BinNMU for amd64 should fix this if package is binNMUable. Please ask debian-release mailing list. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#432893: Failed install followed by failed remove results in installed state
What version of dpkg and its depends do you have installed? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#428509: gcc-4.1 post 4.1.2-8 breaks glibc compilation
Was this bug in gcc or glibc (or both)? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#431709: workaround
Ana Guerrero wrote: > On Wed, Jul 04, 2007 at 04:12:02PM +0200, Didrik Pinte wrote: > > Adding a DisplaySize to the Monitor section of /etc/X11/xorg.conf > > solved the problem. > Since this seems a problem in your configuration files, i'm going to > close the bug. If you find out something else about this, feel free to > re-open (and re-assign if the problem is not with qt3). I'm not sure this is a problem with his configuration file. DisplaySize shouldn't be needed at all (in default it's not there and floating point exception shouldn't happen without it). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#428293: status?
found 428293 4.17-5etch1 thanks What's status of this bug? DoS in 4.21-1 is still there too. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#431131: marking fixed version
fixed 431131 1.3-2 thanks You -done:d bug unversioned and didn't close it in changelog. I mark it fixed in 1.3-2 as you said it's now fixed. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#422605: Can this be closed?
Source package nbio is removed from sid and lenny, so maybe this can be closed if etch (stable) isn't affected? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#430485: DBus in testing
Loïc Minier wrote: >Known bug in libnet-dbus-perl; the workaround is to downgrade DBus. Should DBus have dummy RC bug to prevent it from entering testing?
Bug#430041: Please upgrade your packages
You seem to use obsolete version of binutils. Testing and unstable have 2.17cvs20070426-8. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#429736: Are older versions affected?
If versions in stable/unstable are affected, they should be marked so. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#428293: file: DoS in 4.21-1
Package: file
Version: 4.21-1
Followup-For: Bug #428293
Different issue, but here is information about DoS bug:
http://www.amavis.org/security/asa-2007-3.txt
-quote begin-
To check, if this issue has been properly fixed, please do
the following steps:
$ perl -e 'for (1..2700) {print "\n" x 10}' >0.lis
$ file 0.lis
The output
"0.lis: ASCII text"
must appear immediately, without creating a huge CPU load.
-quote end-
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (900, 'testing'), (900, 'stable'), (700, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.18-4-k7 (SMP w/1 CPU core)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages file depends on:
ii libc6 2.5-10 GNU C Library: Shared libraries
ii libmagic1 4.21-1 File type determination library us
file recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#410580: etch and sarge vulnerable
found 410580 1:3.5.2-0.1 thanks According to http://security-tracker.debian.net/tracker/CVE-2007-0855 unrar in sarge and etch is vulnerable As I understand, no updates by security team are done to nonfree packages. But could update put into point release? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#416502: Try to update depends too
You seem to have at least coreutils, libc6 and libldap2 not in their latest version in "testing". Try to update them (or apt-get/aptitude upgrade). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#415414: Raising severity because xmms-flac crashing
Package: flac Version: 1.1.2-5 Severity: grave 1.1.2-6 was uploaded with priority high and should go to etch. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#403659: sash: no longer statically linked
Package: sash Version: 3.7-7.1 Severity: grave Justification: renders package unusable NMU of this package appears to be no longer statically linked. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (950, 'testing'), (750, 'unstable'), (550, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-k7 Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages sash depends on: ii debconf [debconf-2.0] 1.5.8Debian configuration management sy ii libc6 2.3.6.ds1-8 GNU C Library: Shared libraries ii lockfile-progs 0.1.10 Programs for locking and unlocking ii passwd 1:4.0.18.1-6 change and administer password and ii zlib1g 1:1.2.3-13 compression library - runtime sash recommends no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
