| Summary: | sys-libs/db-6.0.30 version bump | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Arfrever Frehtes Taifersar Arahesis <arfrever.fta> |
| Component: | [OLD] Core system | Assignee: | Gentoo's Team for Core System packages <base-system> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | reuben-gentoo-bugzilla |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Arfrever Frehtes Taifersar Arahesis
2014-03-11 20:50:19 UTC
Simply renaming the ebuild file from db-6.0.20-r1.ebuild to db-6.0.30.ebuild and then regenerating the digest results in a compilable and functional db-6.0.30 for me. I've been able to remove db-5* on a couple of test systems without issue - a few packages (iproute, perl, pam and postfix) needed rebuilding but then succesfully compiled against the newer version. The last upstream blocker I had on my systems which depended on version 5 of db was Postfix, but this has been addressed in the official Postfix-20140512 snapshot which will probably hit portage in the next few days (going by past history). Release notes indicate that db6 should also now work with PHP - it didn't with 6.0.20. I realise we're probably quite a long way off db6 becoming unmasked but it would be good to update the current 6.0 ebuild in portage to the latest Oracle release, especially given it seems no actual changes to the ebuild file itself are required. +*db-6.0.30 (20 May 2014) + + 20 May 2014; Lars Wendler <polynomial-c@gentoo.org> +db-6.0.30.ebuild: + Version bump (bug #504248). + |
