On Mon, Feb 11, 2008 at 12:07:55AM +0000, Frans Pop wrote: > On Sunday 10 February 2008, you wrote: > > > I have not yet tried to run it manually. Suggestions on how to debug > > > the issue welcome. > > > > you can run apt-listchanges --all /path/to/a/package.deb > > OK. Tried that, and with that I _do_ get the changelog without any errors. > This also probably means that --verbose and --debug are not possible? > > I've also tried with apt-get and that fails as well, so it's not something > in aptitude. > > Because a manual call with --all did work, I also tried moving the database > (/var/lib/apt/listchanges.db) away, but that did not change anything.
debug and verbose aren't really used *sigh*. And the sole difference
between calling apt-listchanges directly with --all and the way apt
calls it is that:
(1) in the latter case it opens the db, wheres I don't think it does
with --all
(2) it takes orders from stdin wrt the packages it should look
into for changelogs.
But like said, I do nothing fancy, so there is either a problem in
python/python-apt, or also maybe in tar that I 'system()'. I really do
nothing complicated.
> > Though apt-listchanges is in python, I have no custom C extension so
> > this is likely a python _or_ a python-apt bug (the sole deps I have)
>
> Right. If you have any further debugging suggestions, please let me know.
> I'll try to get an strace, but not sure if that will succeed.
Well that should do yes, just wrap apt-listchanges in a shell script
that run strace this way:
1. rename /usr/bin/apt-listchanges to /usr/bin/apt-listchanges.py
2. create a shell script that:
exec strace -ff -o /tmp/alc.$$.trace /usr/bin/apt-listchanges.py "$@"
3. try to grok what is going on.
Though I'm not 100% sure strace works on sparc. A core may be of help
too, as there is a python-dbg and a python-apt-dbg to interpret the
backtraces.
--
·O· Pierre Habouzit
··O [EMAIL PROTECTED]
OOO http://www.madism.org
pgpfjPo2F4KIb.pgp
Description: PGP signature
