Hi,
I get the same seg fault on a Debian 5 machine. My version info as follows:
python 2.5.2
python-apt 0.7.7.1+nmu1
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, how come there are 0 updates available now?
Anyways here is a simple python script to test out the same.
Hi,
I get the same seg fault on a Debian 5 machine. My version info as follows:
python 2.5.2
python-apt 0.7.7.1+nmu1
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, how come there are 0 updates available now?
Anyways 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
I look forward to some responses. Thanks,
Sita