[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#658361: marked as done (accessing priority of package causes a segmentation fault)

Your message dated Tue, 19 Jun 2012 11:14:10 +0200
with message-id <20120619111214.GA11669@debian.org>
and subject line Re: Bug#658361: accessing priority of package causes a segmentation fault
has caused the Debian Bug report #658361,
regarding accessing priority of package causes a segmentation fault
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
658361: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658361
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- Package: python-apt
version: 0.7.7.1+nmu1

I get a seg fault on a Debian 5 machine when i access a package's priority. My python version is 2.5.2.

Here is a simple python script to test out the same.

import apt

cache = apt.Cache()
cache.update()
cache.open(None)
cache.upgrade()

for pkg in cache:
    print pkg.name
    print pkg.priority

This happened all on a sudden since today feb 2, 2012. I have been running it w/o any issues for past few months. initially i thought it was due to lack of no updates available, but further digging proved it to be due to accessing of priorities. And now it consistently happens. Not sure if the repository against which apt checks has been handed over to a new machine, for it used to list updates earlier. Without my upgrading, now there are 0 updates available. How is this possible?

I am running debian 5 as a VM on my laptop. I have tried it out on other standalone machines also and the problem persists.

Please contact me if you would like further information.

Thanks,

Sita


--

Sita S. Krishnakumar, PhD
+91-9003070867




--- End Message ---
--- Begin Message --- 
Source: python-apt
Source-Version: 0.7.8

On Thu, Feb 02, 2012 at 06:03:29PM +0530, sita krishnakumar wrote:
> Package: python-apt
> version: 0.7.7.1+nmu1
> 
> I get a seg fault on a Debian 5 machine when i access a package's priority.
> My python version is 2.5.2.
> 
> Here is a simple python script to test out the same.
> 
> import apt
> 
> cache = apt.Cache()
> cache.update()
> cache.open(None)
> cache.upgrade()
> 
> for pkg in cache:
>     print pkg.name
>     print pkg.priority
> 
>  This happened all on a sudden since today feb 2, 2012. I have been running
> it w/o any issues for past few months. initially i thought it was due to
> lack of no updates available, but further digging proved it to be due to
> accessing of priorities. And now it consistently happens. Not sure if the
> repository against which apt checks has been handed over to a new machine,
> for it used to list updates earlier. Without my upgrading, now there are 0
> updates available. How is this possible?

This was fixed 2008 in unstable with version 0.7.8. You probably had an
invalid package somewhere in the sources. Excerpt from the changelog:

python-apt (0.7.8) unstable; urgency=low

  [ Michael Vogt ]
  * python/cache.cc:
    - fix crash if Ver.PriorityType() returns NULL

-- Michael Vogt <mvo@debian.org>  Mon, 24 Nov 2008 10:24:30 +0200


-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.

Attachment: pgpDVBYef1Rng.pgp
Description: PGP signature


--- End Message ---
Reply to: