Summary: | sys-libs/db - and upgrade info to pkg_postinst | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Carsten Lohrke (RETIRED) <carlo> |
Component: | New packages | Assignee: | Carsten Lohrke (RETIRED) <carlo> |
Status: | RESOLVED CANTFIX | ||
Severity: | enhancement | CC: | base-system, caleb, pauldv, riff |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Carsten Lohrke (RETIRED)
2007-06-12 22:54:05 UTC
feel free to add what you would like to see. carlo: it should probably be added to the package that is changing between slots of berkdb. If you still want it, go ahead and add it yourself. *** Bug 212422 has been marked as a duplicate of this bug. *** No response from carlo. It does need to be on the actual app, because berkdb dump+restore isn't valid in many cases anyway (need to use the app-specific dump/restore because of key issues). Or just keep the app linked to the same slot of DB. (In reply to comment #4) > No response from carlo. Yeah - sorry - I tend to loose track of my bugs, unfortunately. > It does need to be on the actual app, because berkdb dump+restore isn't valid > in many cases anyway (need to use the app-specific dump/restore because of key > issues). Or just keep the app linked to the same slot of DB. Right, it's not a solution, but raises awareness. Iirc I opened the bug because of a forums post, seeing someone struggling with bdb updates and not understanding that his db's wouldn't be updated transparently. Your last sentence implies to keep n++ bdb versions forever... :/ Also Portage's current --depclean functionality stupidly only keeps the latest slot, so it's likely users get bitten. |