Processing commands for cont...@bugs.debian.org:
> severity 521860 grave
Bug#521860: libpam-modules: libdb upgrade silently breaks pam_userdb.so
Severity set to `grave' from `grave'
> quit
Stopping processing here.
Please contact me if you need assistance.
Debian bug
severity 521860 grave
quit
On Fri, Apr 03, 2009 at 06:29:10AM +, Clint Adams wrote:
> - if (PGNO(meta) == PGNO_BASE_MD && !F_ISSET(dbp, DB_AM_RECOVER))
> + if (PGNO(meta) == PGNO_BASE_MD && meta->dbmeta.last_pgno > 0 &&
> !F_ISSET(dbp, DB_AM_RECOVER))
> +
On Thu, Apr 02, 2009 at 09:27:13AM +, Debian Bug Tracking System wrote:
> Bug#521860: libpam-modules: libdb upgrade silently breaks pam_userdb.so
> Bug marked as found in version 4.7.25-6.
Possible fix; I'll add more information once I have Internet.
diff --git a/btree/bt_ope
Processing commands for cont...@bugs.debian.org:
> reassign 521860 db
Bug#521860: libpam-modules: libdb upgrade silently breaks pam_userdb.so
Bug reassigned from package `libpam-modules' to `db'.
> found 521860 4.7.25-6
Bug#521860: libpam-modules: libdb upgrade silently breaks p
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
> >
Steve Langasek a écrit :
> 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 don't know where to put the 'debug' option... I have generated t
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.
On Tue, Mar 31, 2009 at 12:11:57AM +0200, Benoît MERLET wrote:
> I ran into the same bug.
> I have a backup of the inital db file which was created years ago with
> this command :
> db3_load -T -t hash -f login.txt login.db
> The workaround was to re-generate the db file using db4.7_load.
>
Raphael Rigo a écrit :
Steve Langasek wrote:
tags 521860 moreinfo
thanks
On Mon, Mar 30, 2009 at 04:49:09PM +0200, Raphael Rigo wrote:
Package: libpam-modules
Version: 1.0.1-9
Severity: grave
Justification: renders package unusable
A recent upgrade in libpam-modules makes it depend on libdb4.7
Processing commands for cont...@bugs.debian.org:
> tags 521860 moreinfo
Bug#521860: libpam-modules: libdb upgrade silently breaks pam_userdb.so
There were no tags set.
Tags added: moreinfo
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking
Steve Langasek wrote:
> tags 521860 moreinfo
> thanks
>
> On Mon, Mar 30, 2009 at 04:49:09PM +0200, Raphael Rigo wrote:
>> Package: libpam-modules
>> Version: 1.0.1-9
>> Severity: grave
>> Justification: renders package unusable
>
>> A recent upgrade in libpam-modules makes it depend on libdb4.7,
tags 521860 moreinfo
thanks
On Mon, Mar 30, 2009 at 04:49:09PM +0200, Raphael Rigo wrote:
> Package: libpam-modules
> Version: 1.0.1-9
> Severity: grave
> Justification: renders package unusable
> A recent upgrade in libpam-modules makes it depend on libdb4.7, unfortunately
> it seems DB files cr
On Mon, Mar 30, 2009 at 04:49:09PM +0200, Raphael Rigo wrote:
> A recent upgrade in libpam-modules makes it depend on libdb4.7, unfortunately
> it seems DB files created with a previous version are NOT compatible with
> version 4.7. This makes pam logins based on userdb break silently, with no
> er
Package: libpam-modules
Version: 1.0.1-9
Severity: grave
Justification: renders package unusable
A recent upgrade in libpam-modules makes it depend on libdb4.7, unfortunately
it seems DB files created with a previous version are NOT compatible with
version 4.7. This makes pam logins based on userd
14 matches
Mail list logo
