Package: dpkg
Version: 1.17.19
Followup-For: Bug #766242
I am seeing this, too.
-- System Information:
Debian Release: 7.7
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux
I too see dpkg hang in the configure phase and consuming all the
memory it can get.
strace didn't yield anything useful apart from repeated brk() calls.
C.
--
,''`. Christian Hofstaedtler z...@debian.org
: :' : Debian Developer
`. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03
`-
Control: severity -1 serious
On Tue, 2014-10-21 at 14:07:48 -0400, Zack Weinberg wrote:
Package: dpkg
Version: 1.17.19
Severity: grave
Justification: renders package unusable
It appears to work for many people, so I'd say it's not unusable. :)
During a routine upgrade I noticed dpkg
Christian Hofstaedtler z...@debian.org (2014-10-21):
I too see dpkg hang in the configure phase and consuming all the
memory it can get.
strace didn't yield anything useful apart from repeated brk() calls.
In these situations, something like gdb would probably more helpful than
strace. (At
* Cyril Brulebois k...@debian.org [141021 22:03]:
Christian Hofstaedtler z...@debian.org (2014-10-21):
I too see dpkg hang in the configure phase and consuming all the
memory it can get.
strace didn't yield anything useful apart from repeated brk() calls.
In these situations,
Hi!
On Tue, 2014-10-21 at 21:17:24 +0200, Christian Hofstaedtler wrote:
I too see dpkg hang in the configure phase and consuming all the
memory it can get.
strace didn't yield anything useful apart from repeated brk() calls.
Actually the most useful thing to use in such cases is something
Package: dpkg
Version: 1.17.19
Followup-For: Bug #766242
Hi,
I'm also suffering from this bug. As I do not have dpkg symbols, the
gdb backtrace is not really useful. I give you nonetheless in case you
still have the debug symbols: with the adresses in the backtrace, you
will be able to find
Hi!
On Tue, 2014-10-21 at 23:08:51 +0200, Vincent Danjean wrote:
Package: dpkg
Version: 1.17.19
Followup-For: Bug #766242
Here is the log of a other call of sudo dpkg --configure -a -D7
Note that the log file (uncompressed) is about 615M.
Thanks, although I've already reproduced this
Package: dpkg
Version: 1.17.19
Followup-For: Bug #766242
Hi (again)
Looking at the trace I sent you, it seems that the perl package was involve.
As any --configure call to dpkg (directly or indirectly with apt) was blocking,
I tried to manually explicitely configure perl:
njean@eyak:~$ sudo
On Tue, 21 Oct 2014 23:26:57 +0200 Guillem Jover guil...@debian.org wrote:
Thanks, although I've already reproduced this with Zack's database,
as I mentioned earlier I'm already looking into fixing this. I'll be
uploading a fixed packages probably early tomorrow.
attached is a 115 MB log from
Hi!
Ok, I've got a fix now that solves this problem, I'll be running the
functional test suite, and adding few more tests to it, to catch this
issue and possibly some other ones, and will be uploading tomorrow,
after I've woken up and done the above.
Thanks for the logs! But there's no need to
11 matches
Mail list logo
