Bug#1027749: update-initramfs could diagnose attempt to run with /dev not mounted

Package: initramfs-tools Version: 0.140 Severity: wishlist When the config files specify MODULES=dep, update-initramfs tries to autodetect which modules to load. To do this, all of /proc/, /sys/, and /dev/ must be mounted. If either /proc/ or /sys/ isn't mounted, update-initramfs fails with an

Bug#911087: schroot: --preserve-environment does not preserve env vars set to ""

Roger Leigh wrote: >Please see https://gitlab.com/codelibre/schroot/merge_requests/38 for a >patch containing the fixes. This looks like an oversight/mis-design >which is corrected by this merge request to make the behaviour >consistent for all environment handling methods. Wow, thanks for

Bug#911087: schroot: --preserve-environment does not preserve env vars set to ""

Package: schroot Version: 1.6.10-3+deb9u1 The schroot --preserve-environment is supposed to preserve the user's environment variables. However it does not pass through environment variables which are set to the empty string: mnementh$ FOO=bar schroot --preserve-environment -c buster-amd64-sbuild

Bug#892087: libsdl2-dev: SDL_cpuinfo.h provokes warnings if used with -Wundef on non-x86 hosts

Package: libsdl2-dev Version: 2.0.8+dfsg1-1 Severity: normal Dear Maintainer, The SDL2 header SDL_cpuinfo.h generates gcc warnings if the program using it compiles with the -Wundef warning. (In particular, this means that QEMU builds using it fail on at least sparc hosts, since QEMU dev builds

Bug#815409: mips qemu-img segfault is due to stack not being executable

On 14 June 2016 at 12:24, Michael Tokarev wrote: > It shouldn't affect qemu-img only, other components should fail > the same way, right? Potentially, yes. It depends whether they have coroutines which happen to execute code that gets compiled into the affected floating point

Bug#815409: mips qemu-img segfault is due to stack not being executable

I investigated this qemu-img segfault, and it turns out to be due to a conflict between QEMU not marking its coroutine stacks as executable and the MIPS kernel insisting on an executable stack for floating-point emulation. Full analysis here:

Bug#816225: fontconfig ignores in user fonts.conf if in Japanese locale

Peter Maydell wrote: >fontconfig appears to ignore a user's fonts.conf list if it's >in a Japanese locale. >I have a ~/.config/fontconfig/fonts.conf which includes > > serif > > Source Serif Pro > IPAMincho > > After some experimentation I have been ab

Bug#816225: fontconfig ignores in user fonts.conf if in Japanese locale

Package: fontconfig Version: 2.11.0-6.3 Severity: normal fontconfig appears to ignore a user's fonts.conf list if it's in a Japanese locale. This might well be me failing to configure it correctly; it's very confusing :-( I have a ~/.config/fontconfig/fonts.conf which includes serif

Bug#778737: [Qemu-devel] configure: enable kvm on x32

On 12 March 2015 at 06:13, Michael Tokarev m...@tls.msk.ru wrote: Here's a trivial change to enable kvm on x32 architecture. I'm not 100% sure the result works correctly in all cases, but this is a good start and in theory everything should work. Given the pessimism expressed in this comment,

Bug#632192: [PATCH] introduce environment variables for all qemu-user options

On 31 July 2011 22:40, Johannes Schauer j.scha...@email.de wrote: Rework option parsing code for linux-user in a table-driven manner to allow environment variables for all commandline options. Also generate usage() output from option table. Thanks for this, it looks good. A couple of minor

Bug#632192: [Qemu-devel] [PATCH] introduce environment variables for all qemu-user options

On 31 July 2011 12:51, j.scha...@email.de wrote: +    if ((r = getenv(QEMU_STACK_SIZE)) != NULL) { +        guest_stack_size = strtoul(r, (char **)r, 0); +        if (guest_stack_size == 0) +            usage(); +        if (*r == 'M') +            guest_stack_size *= 1024 * 1024; +        

Bug#613200: linux-base: lilo.conf not updated to UUIDs for kernels not in /

Package: linux-base Version: 2.6.32-30 I upgraded my Debian box to squeeze today, and after the initial install new kernel and udev the system didn't boot because linux-base hadn't correctly updated lilo.conf to use UUIDs rather than /dev/hd*. My lilo.conf had a stanza for the kernel like this:

Bug#592614: valgrind: on Debian ARM EABI (armel)

just about usable on an A8. He's also reluctant to add yet another configuration that valgrind has to support, test and maintain. -- Peter Maydell -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#534120: binutils: typo in ar(1) manpage

Package: binutils Version: 2.18.1~cvs20080103-7 Severity: minor From the ar(1) manpage documentation of the 'P' option: (such archives are not POSIX complaint) Should be compliant. -- PMM -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe.

Bug#519719: /usr/share/doc/base-files/remove-base doesn't remove correct files

Package: base-files Version: 5 /usr/share/doc/base-files/README.base says that one of the things that must be done to remove the old 'base' package is: # 4. Remove all the files matching /var/lib/dpkg/info/base.*. However, the provided shell script /usr/share/doc/base-files/remove-base does

Bug#513028: coreutils: expand is not wide-character aware

Package: coreutils Version: 5.97-5.3 The POSIX documentation of the expand utility is fairly clear that it should operate in terms of column positions, not byte counts, and since the value of LC_CTYPE is used for the determination of the width in column positions each character would occupy wide

Bug#359167: bug 359167: inc: segfaults: now fixed upstream

Just a note to say that this bug has now been fixed in upstream CVS (and a variant on the offending file has been put into the upstream test suite). -- PMM -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#344182: fd leak in mhstore

Brian Ristuccia wrote: When using mhstore on a large number of messages, and writing parts to a pipe, mhstore winds up with 'too many open files' in ~/.mh_profile: mhstore-store-message/rfc822: | sa-learn --no-sync --spam - (Directory has about 800 messages) $ /usr/bin/mh/mhstore * -type

Bug#165050: closed by Bart Martens [EMAIL PROTECTED] (cbrowser: no manpage)

Debian Bug Tracking System wrote: From: Bart Martens [EMAIL PROTECTED] This software doesn't really need a man page. Anyone, feel free to write a man page, reopen the bug, and submit your man page to the bug. The Policy Manual chapter 12 says: # If no manual page is available, this is

Bug#165050: cbrowser: no manpage

Bart Martens wrote: You're right about policy. Are you interested in writing a man page for this software? Sorry, I'm afraid I don't use it any more... -- PMM -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]