[Pkg-db-devel] Bug#469139: It isn't a libdb4.6 bug !
Vincent Lefevre
vincent at vinc17.org
Thu Apr 17 07:41:34 UTC 2008
On 2008-04-17 09:18:09 +0200, tech at mediaforest.net wrote:
>> Here too. What to do wasn't clear, so:
>>
>> # db4.6_dump /var/lib/apt/listchanges.db > db.dump
>> # rm /var/lib/apt/listchanges.db
>> # db4.5_load /var/lib/apt/listchanges.db < db.dump
>
> This workaround could work well if only db4 was installed on my box,
> but I only have db3 :( and I get the issue on every apt-get upgrade
> or install attempt
You need to install the packages that provide these commands. Only
libdb4.5 is needed by apt-listchanges currently: apt-listchanges
depends on python-apt, which depends on python, which depends on
python2.4, which depends on libdb4.5.
>> Traceback (most recent call last):
>> File "/usr/bin/apt-listchanges", line 227, in ?
>> main()
>> File "/usr/bin/apt-listchanges", line 148, in main
>> seen.close()
>> File "/usr/lib/python2.4/bsddb/__init__.py", line 237, in close
>> v = self.db.close()
>> bsddb.db.DBRunRecoveryError: (-30975, 'DB_RUNRECOVERY: Fatal error, run database recovery -- PANIC: fatal region error detected; run recovery')
>
> The bug isn't linked to libdb4.6
Why not?
--
Vincent Lefèvre <vincent at vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)
More information about the Pkg-db-devel
mailing list