commit bf878c27023b60b95dc0ed7fbece859ea3b385e7 Author: David Seifert <soap@gentoo.org> Date: Sun Dec 24 22:43:10 2017 +0100 media-plugins/audacious-plugins: Remove old Closes: https://bugs.gentoo.org/558228 Closes: https://bugs.gentoo.org/562094 Closes: https://bugs.gentoo.org/564498 Closes: https://bugs.gentoo.org/584392 Package-Manager: Portage-2.3.19, Repoman-2.3.6 commit 21583681656bc8cbd1a4a7f0c6939966a765b54c Author: David Seifert <soap@gentoo.org> Date: Sun Dec 24 22:41:10 2017 +0100 media-sound/audacious: Remove old Closes: https://bugs.gentoo.org/564498 Closes: https://bugs.gentoo.org/584392 Closes: https://bugs.gentoo.org/596834 Closes: https://bugs.gentoo.org/605042 Closes: https://bugs.gentoo.org/611272 Package-Manager: Portage-2.3.19, Repoman-2.3.6 Stable keywords dropped for all architectures, most keywords removed. How could this happen?
Will audacious become stable again anytime soon?
Stabilisation depends on bug 640672 (3.10 version bump).
30 days have passed, JFYI.
nothing to do here for qa
Anyone wanting to stabilise audacious should probably open a new bug then.
You didn't fix anything. Please set a proper Resolution instead, that is if you think you can speak for a team and for the person who caused the problem. If that is the case, and the solution would be to stabilise newer versions, then this bug report can be repurposed to request that.
If you genuinely cared about media-sound/audacious you could have started stabilisation weeks ago.