client.c && ./a.out
$gcc-4.9 -W -Wall -O1 client.c && ./a.out
$
Petr
On Mon, Aug 11, 2014 at 12:15 PM, Steve Langasek wrote:
> On Mon, Aug 11, 2014 at 11:49:16AM -0700, Petr Vandrovec wrote:
>> Hi,
>> it seems to be gcc bug. For inexplicable reason compiler optimiz
Hi,
it seems to be gcc bug. For inexplicable reason compiler optimized
'if (cp && *cp)' to just 'if (*cp)' :-(
Changing 'char *cp' to 'char * volatile cp' at line 468 in
support/export/client.c is enough to explain to gcc that it has no
idea what it is doing, and fixes the crash.
I think that
Hello,
it seems that DNS resolver is grossly confused, and sends
two DNS requests on same socket back to back (strace below is
from 'lynx http://www.jeep.com'). In first one DNS server
responded only to second packet sent by resolver, and resolve
failed (after that mdns was tried, and eventually
Package: dash
Version: 0.5.5.1-1
Severity: critical
Hello,
new dash has some serious problems with waiting on spawned
processes, which completely breaks apt-move - at the end apt-move spawns
pipe as shown below:
p...@gwy:~$ cat /tmp/err
20768 tty4 S+ 0:00 \_ dash /usr/bin/apt-
Hello,
it is still not quite right. To work around 4.6p1-1 bug I enabled
'PasswordAuthenticaion yes' in sshd config file, and it worked great.
But for 4.6p1-2 I'm prompted for password, and then thing crashes (Works
fine with key based authentication):
petr-dev3:/var/log# ssh localhost -l
Lucas Nussbaum wrote:
During a rebuild of all packages in sid, your package failed to build on i386.
Fix below should fix problem. Probably time to release ncpfs-2.2.7, it
looks really bad that there is 2000+ warnings in the build.
n
option error.
Maybe it could be default for tar's POSIX mode, but I have no idea why GNU mode
behavior should be changed in any way.
Petr Vandrovec
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ian: Not found in archive", 49) = 49
12530 write(2, "\n", 1) = 1
...
Please, if you must introduce some new options, make '--wildcards' default so
you do not change behavior in backward incompatible way. Or, if you are
absolutely sure that no other program on the world besides apt-listchanges
depends on this behavior, feel free to reassign this to apt-listchanges. But
I'm absolutely sure that apt-listchanges is not only program which depends on
this behavior (as I've written couple of tools which depend on this as well)...
Thanks,
Petr Vandrovec
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
s Herbert is upstream maintainer
for both dash and apt-move, it probably does not matter a lot, as it
ends up in his mailbox this way or another.
For Debian I would apply patch below, which removes dash/ash detection and
forces dash through #!.
ity.
See bug 339024 for apt-move's half of story.
Thanks,
Petr Vandrovec
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hello,
due to pure luck (new ssh crashed on all my systems except one) I've found
workaround - default_realm in [libdefaults] in /etc/krb5.conf must not be
empty. "default_realm = " crashes, "default_realm = x" works...
Petr
--
11 matches
Mail list logo
