Is it OK to stabilize =dev-db/virtuoso-odbc-6.1.4 ? If so, please CC arches and add STABLEREQ keyword. Stabilization of this package has been repoman-checked on the following arches: x86, amd64
Does this make sense without dev-db/virtuoso-server?
No, not really. I mean it should work in theory (interface is iodbc after all), still odbc driver and server application shares quite a *lot* of code.
Arches please stabilize: =dev-db/virtuoso-odbc-6.1.4 =dev-db/virtuoso-server-6.1.4 Target: amd64 ppc ppc64 x86
I've just committed 6.1.4-r1, which fixes the buffer overflow from bug 364683. Please hold off on stabilizing for a little while until the revision-bumped version has been in the tree long enough to be stabilized.
This is not an enhancement but a severe bug downgrading gawk-4 which is already marked stable on major arch's.
(In reply to comment #4) > I've just committed 6.1.4-r1, which fixes the buffer overflow from bug > 364683. Please hold off on stabilizing for a little while until the > revision-bumped version has been in the tree long enough to be stabilized. gawk-4.0.0.ebuild:KEYWORDS="~alpha amd64 arm hppa ~ia64 ~m68k ~mips ppc ppc64 ~s390 ~sh ~sparc x86 ~sparc-fbsd ~x86-fbsd" ^ The tree is broken *right now* for amd64, ppc, ppc64, x86. Arch's, please continue stabilizing soon as possible to unbreak the stable tree.
ppc/ppc64 stable
amd64 stable
x86 stable. Last arch, closing.