Oops, my last reply went directly to Michael instead of going to the BTS
as well.
My attached patch is what I'm now using on i386 and amd64 and it seems
to be working well The debug output now looks like this:
# unattended-upgrade --debug
...
http://cdn.debian.net/debian/pool/main/p/python-a
On Fri, Sep 24, 2010 at 07:28:08PM +0100, Steven Chamberlain wrote:
> On 24/09/10 18:33, Steven Chamberlain wrote:
> >>python/acquire.cc: In function 'PyObject* PkgAcquireNew(PyTypeObject*,
> >>PyObject*, PyObject*)':
> >>python/acquire.cc:331: warning:
> >>'pkgAcquire::pkgAcquire(pkgAcquireStatus*
On Fri, Sep 24, 2010 at 07:28:08PM +0100, Steven Chamberlain wrote:
> On 24/09/10 18:33, Steven Chamberlain wrote:
> >>python/acquire.cc: In function 'PyObject* PkgAcquireNew(PyTypeObject*,
> >>PyObject*, PyObject*)':
> >>python/acquire.cc:331: warning:
> >>'pkgAcquire::pkgAcquire(pkgAcquireStatus*
On Fri, Sep 24, 2010 at 07:28:08PM +0100, Steven Chamberlain wrote:
> On 24/09/10 18:33, Steven Chamberlain wrote:
> >>python/acquire.cc: In function 'PyObject* PkgAcquireNew(PyTypeObject*,
> >>PyObject*, PyObject*)':
> >>python/acquire.cc:331: warning:
> >>'pkgAcquire::pkgAcquire(pkgAcquireStatus*
On 24/09/10 18:33, Steven Chamberlain wrote:
python/acquire.cc: In function 'PyObject* PkgAcquireNew(PyTypeObject*,
PyObject*, PyObject*)':
python/acquire.cc:331: warning:
'pkgAcquire::pkgAcquire(pkgAcquireStatus*)' is deprecated (declared at
/usr/include/apt-pkg/acquire.h:352)
Actually, here's
On 24/09/10 17:47, Michael Vogt wrote:
I would appreciate feedback if the different python-apt
version make a difference. I more suspect that its the new apt/libapt
(the amount of changes in python-apt is relatively small), any more
findings/information about that will help.
Hi!
I just finish
On Fri, Sep 24, 2010 at 05:05:02PM +0100, Steven Chamberlain wrote:
> On 24/09/10 15:29, Anthony Callegaro wrote:
> >Can you try a 32 bits version or do you want me to give you a SSH access
> >to one test VZ ?
[..]
> python-apt 0.7.96.1 works fine, but is only installable with older
> packages apt-
On 24/09/10 15:29, Anthony Callegaro wrote:
Can you try a 32 bits version or do you want me to give you a SSH access
to one test VZ ?
Hi,
I've made a 32-bit squeeze VE and was able to reproduce this issue
straight away.
I thought Soeren was experiencing the bug on amd64 because that was
me
On Fri, 2010-09-24 at 12:56 +0100, Steven Chamberlain wrote:
> Also I made an amd64 squeeze VE two weeks ago with only 384MB RAM to see
> if I could reproduce this. But unattended-upgrades has been working
> correctly for two weeks now. It's applied updates almost every day. So
> I don't current
On Fri, 2010-09-24 at 12:56 +0100, Steven Chamberlain wrote:
> Hi,
>
> On 24/09/10 06:47, Joerg Platte wrote:
> > Am Thursday, 23. September 2010 schrieb Anthony Callegaro:
> >> On Tue, 2010-09-21 at 13:55 +0200, Soeren Sonnenburg wrote:
> >>> The only further info I could provide is that this is
Hi,
On 24/09/10 06:47, Joerg Platte wrote:
Am Thursday, 23. September 2010 schrieb Anthony Callegaro:
On Tue, 2010-09-21 at 13:55 +0200, Soeren Sonnenburg wrote:
The only further info I could provide is that this is a virtual
server with relatively little memory (1G)
Hmmm, on my old pentium
On Fri, 2010-09-24 at 07:47 +0200, Joerg Platte wrote:
> Hmmm, on my old pentium 4 box it crashes as well. There is no virtualization
> involved here but the computer has only 1GB of memory.
>
> Grüße,
> Jörg
Thanks for the additional input. I can confirm this isn't a memory size
issue in openV
Am Thursday, 23. September 2010 schrieb Anthony Callegaro:
> On Tue, 2010-09-21 at 13:55 +0200, Soeren Sonnenburg wrote:
> > The only further info I could provide is that this is a virtual server
> > with relatively little memory (1G)
> >
> > Soeren
>
> Well that might be it. Both servers having
On Tue, 2010-09-21 at 13:55 +0200, Soeren Sonnenburg wrote:
> The only further info I could provide is that this is a virtual server
> with relatively little memory (1G)
>
> Soeren
Well that might be it. Both servers having issues are Containers running
in openVZ for me as well.
I am very busy a
On Tue, 2010-09-21 at 10:34 +0100, Anthony Callegaro wrote:
> Hello all,
>
> Just to add my 2cents
>
> I have the exact same gdb dump as Soeren, so I don't see the point in
> posting them again.
>
> Le lundi 13 septembre 2010 à 19:59 +0100, Steven Chamberlain a écrit :
> > It may be possible to
Hello all,
Just to add my 2cents
I have the exact same gdb dump as Soeren, so I don't see the point in
posting them again.
Le lundi 13 septembre 2010 à 19:59 +0100, Steven Chamberlain a écrit :
> It may be possible to narrow it down to the exact line, if someone able
> to reproduce this issue c
On Fri, 2010-09-17 at 14:23 +0100, Steven Chamberlain wrote:
> Hi Soeren,
>
> Could you please try this again with package python-apt-dbg installed?
> I think that will provide some of the missing information in the backtrace.
OK, here is more:
# gdb --args python /usr/bin/unattended-upgrades
G
Hi Soeren,
Could you please try this again with package python-apt-dbg installed?
I think that will provide some of the missing information in the backtrace.
On 17/09/10 04:23, Soeren Sonnenburg wrote:
# gdb --args python /usr/bin/unattended-upgrades
...
(gdb) bt
#0 __strlen_sse2 () at ..
Can you try to run the process under valgrind to get more information
from the crash?
unattended-upgrades do not segfault for me, so I am unable too
reproduce the problem.
Happy hacking,
--
Petter Reinholdtsen
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subjec
On 13/09/10 16:08, Anthony Callegaro wrote:
Checking: lighttpd ([""])
Checking: wget ([""])
pkgs that look like they should be upgraded: apache2-utils
apache2.2-bin
apache2.2-common
libusb-0.1-4
lighttpd
wget
Fetched 0B in 0s
(0B/s)
Segmentation fault
For comparison, here's what happens on my o
Hi Soeren,
I just upgraded unattended-upgrades to 0.62 on amd64 and I don't see any
problems with it.
Do you still get the segfault when using either the --debug or --dry-run
option? If so, perhaps you could post the out from --debug which should
show at which point the segfault happens.
Package: unattended-upgrades
Version: 0.62
Severity: grave
Tags: squeeze
any ideas? calling apt-get upgrade on the cmdline just works fine
-- System Information:
Debian Release: squeeze/sid
APT prefers oldstable
APT policy: (500, 'oldstable'), (500, 'testing'), (500, 'stable')
Architecture:
22 matches
Mail list logo
