reassign 521860 db found 521860 4.7.25-6 thanks On Thu, Apr 02, 2009 at 10:39:35AM +0200, Raphael Rigo wrote: > Steve Langasek wrote: > > If db4.7_dump works at all, I would expect pam_userdb to be able to handle > > the file as well. Do you get any useful information out of pam_userdb using > > the 'debug' option when using this old db file?
> I couldn't recover my old DB file but I remember that although > db4.7_dump could parse the headers, using "db4.7_dump -d a file.db" > which should have dumped everything, only the metadata was displayed, > not the data itself. Ok, I can confirm this here with a simple test case that registers as version: 7 according to db_dump: creating it with db3_load I'm unable to see the data, creating it with db4.2_load I am. My understanding is that this is supposed to be supported since it's a version 7 db in both cases, so I'm reassigning this to the db package. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
