Migration to libdb4.6

Bug #199240 reported by Miguel Ruiz
6
Affects Status Importance Assigned to Milestone
reprepro (Debian)
Fix Released
Unknown
reprepro (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: reprepro

As Server Team, we're trying to move away from libdb4.3

This package needs to update its libdb dependency.

Cheers!

Revision history for this message
Miguel Ruiz (mruiz) wrote :

I'm working on it.

Changed in reprepro:
assignee: nobody → mruiz
status: New → In Progress
Changed in reprepro:
status: Unknown → New
Revision history for this message
Miguel Ruiz (mruiz) wrote :

Upstream (Debian) would update the libdb dependency in the future if a testing plan is applied (new code).

From the bug report:

"While it might be possible to switch to a newer libdb, I don't want to do so before I can properly test it with the new code, which includes putting it in private production use, which includes working on etch."

Cheers!

Changed in reprepro:
status: New → Fix Released
Miguel Ruiz (mruiz)
Changed in reprepro:
assignee: mruiz → nobody
Revision history for this message
Fabrice Coutadeur (fabricesp) wrote :

Will be fixed in Jaunty with 3.8.2-1ubuntu1 (will use libdb4.7)

Changed in reprepro:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.