Bug#215239: libdb4.2 and apt

[Matt Zimmerman <mdz@debian.org>]

On Fri, Apr 30, 2004 at 08:53:54AM -0400, Clint Adams wrote:

> It works for me, though I don't know that I'm doing the same thing.
> If I use atp-ftparchive from sid, I create a
> cache.db: Berkeley DB (Hash, version 5, native byte-order)
> Then, I copy the directory of debs and .db file to a machine with
> db4.2-using apt-ftparchive, run the same command, and it
> upgrades it to
> cache.db: Berkeley DB (Hash, version 7, native byte-order)
> 
> If I do it from scratch, I get
> cache.db:    Berkeley DB (Hash, version 8, native byte-order)
> 
> Is your cache.db older than Hash version 5?

What I did was to use apt-ftparchive on my PC (0.6.21) to create the db:

mizar:[~/temp] apt-ftparchive --db ftparchive-mizar.db packages /space/cache/apt/archives >/dev/null
ftparchive-mizar.db: Berkeley DB (Hash, version 5, native byte-order)
mizar:[~/temp/temp] file ftparchive-mizar.db 
ftparchive-mizar.db: Berkeley DB (Hash, version 5, native byte-order)

then use a tree with your patch:

mizar:[.../apt/build/bin] LD_LIBRARY_PATH=. ./apt-ftparchive --db ~/temp/ftparchive-mizar.db packages /space/cache/apt/archives > /dev/null
E: Unable to open DB file /home/mdz/temp/temp/ftparchive-mizar.db: Invalid argument

W: DB is old, attempting to upgrade 
E: Unable to open DB file /home/mdz/temp/temp/cache.db-hurd: Invalid argument

Apparently, it tried to upgrade it, and then failed when opening the
resulting db.

I'm uploading ftparchive-mizar.db to people.d.o/~mdz/temp/ now.

-- 
 - mdz