Package: alsa-utils
Version: 1.1.8-2
Tags: patch
/etc/init.d/alsa-utils initscript contains an unnecessary "sleep 1" at
store_levels(), delaying shutdown by one second when using sysvinit.
Proposed fix:
diff --git a/debian/init b/debian/init
index e6a6e92..403c17f 100755
--- a/debian/init
+++
Package: initscripts
Version: 2.93-8
Second (part of the) issue described in #915671, namely, wrong /tmp
permissions when it is symlinked to a non-existent location was not
previously fixed.
Not that I care very much about this feature, but for consistency it
should be either fixed or removed.
> This is *WRONG*, it will also return 0 if /tmp is not a symlink.
Wow, my bad, sorry for the noise. Should not have really mixed C and
shell code in my head.
> (Also, use test -h instead of test -L for symlinks, cf. the
> GNU autoconf texinfo manual, *Limitations of Builtins::)
>
> What about
Package: initscripts
Version: 2.93-1
In /usr/share/doc/initscripts/README.Debian it is documented that /tmp
could be a symlink to (for example) /run/tmp. This feature was
implemented in version 2.88dsf-13.3 (see
https://salsa.debian.org/debian/sysvinit/commit/3bec14850 ).
But currently it does
Package: pdns-recursor
Version: 3.6.2-1
Sometimes during shutdown, pdns-recursor init script causes 30 second
long delay. The problem appears to be in --retry=HUP/30/TERM/5/KILL/5
option to start-stop-daemon in stop() function of /etc/init.d/pdns-recursor.
I see no particular need in using
I disagree. pdns-recursor cleanly exits on the first HUP, and the
TERM/KILL will never be triggered.
If pdns-recursor doesn't immediately exit, something's fishy.
No objection here.
In other news, the systemd unit file for pdns-recursor doesn't do
anything fancy, and a stop would run the
This is indeed broken on old kernels. My kernel is 2.6.35.14, own build.
Steps to reproduce:
1. boot into an old kernel
2. mount any ntfs filesystem
3. type ls /mnt, it will print:
ls: cannot access /mnt: Input/output error
I have bisected it to the following upstream commit:
Two more things I would like to know :
- which cpu are you using (32 or 64 bits) ?
64 bit cpu and system, amd64.
- what were your ./configure options for compiling
ntfs-3g ? At least, what is the output of ntfs-3g -help
No options were used. The build environment is current debian sid.
I
Package: libc6
Version: 2.3.6.ds1-13etch2
This program produces wrong output on etch arm
(compiler version/flags/etc doesn't matter):
#include stdio.h
int main (void)
{
printf (%llu\n, 450ULL);
return 0;
}
$ ./a.out
0826408960
$
--
To UNSUBSCRIBE, email to
Package: ospics
Version: 0.72d-2
File /usr/share/ospics/Debian.png fails integrity check:
$ pngcheck /usr/share/ospics/Debian.png
/usr/share/ospics/Debian.png CRC error in chunk IDAT (actual 55757ba0, should
be 5dcbdc43)
$
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
tag 325050 upstream
forwarded 325050 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23567
thanks
Analysed and reported to upstream developers.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
This bug is known, and was fixed by upstream maintainers in cvs head
and deerpark branch, see https://bugzilla.mozilla.org/show_bug.cgi?id=293307
for details.
Here is a backported patch for this bug:
diff -urN a/modules/libpr0n/src/imgLoader.cpp
b/modules/libpr0n/src/imgLoader.cpp
---
This bug most probably caused by bug in gcc's alias analysis, namely
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22591
which is still present in debian's gcc (4.0.1-2) but fixed in current
4.0 branch. There are at least two solutions: either wait for next debian
revision of gcc package or
13 matches
Mail list logo