Can we stabilise dev-db/slony1-2.2.9 please? Needed for gcc-10. Thanks!
No. We're going to wait for 2.2.10 which will mature in less than 2 weeks.
(In reply to Aaron W. Swenson from comment #1) > No. We're going to wait for 2.2.10 which will mature in less than 2 weeks. Can we keep a bug open then to keep track? (Possibly rename this bug and mark the whiteboard.) It’s quite hard to keep on top of which packages are still broken in stable.
Please do, for gcc-10 and gentoo!
ping
Please stabilize the following target: =dev-db/slony1-2.2.10 ~amd64 ~ppc ~x86
ppc done
amd64 stable
x86 stable. Closing.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=328b93871ab666098e7509b148fc32f92c03575c commit 328b93871ab666098e7509b148fc32f92c03575c Author: Jakov Smolic <jakov.smolic@sartura.hr> AuthorDate: 2021-01-24 16:37:53 +0000 Commit: David Seifert <soap@gentoo.org> CommitDate: 2021-01-24 16:37:53 +0000 dev-db/slony1: Remove old Bug: https://bugs.gentoo.org/762943 Signed-off-by: Jakov Smolic <jakov.smolic@sartura.hr> Signed-off-by: David Seifert <soap@gentoo.org> dev-db/slony1/Manifest | 6 ---- dev-db/slony1/slony1-2.2.6.ebuild | 64 --------------------------------- dev-db/slony1/slony1-2.2.7.ebuild | 62 -------------------------------- dev-db/slony1/slony1-2.2.9.ebuild | 74 --------------------------------------- 4 files changed, 206 deletions(-)