since a week or so a new version of discord is out, but the gentoo ebuild did not receive an update so far Reproducible: Always Steps to Reproduce: 1.emerge --sync 2.emerge discord 3.
The latest seems out for me. Are you on stable?
(In reply to Nick Sarnie from comment #1) > The latest seems out for me. Are you on stable? discord is normally bumped straight-to-stable given old is always broken on bumps.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e6d45fceaad0b5633b65b7132bac43463d4d7510 commit e6d45fceaad0b5633b65b7132bac43463d4d7510 Author: Ionen Wolkens <ionen@gentoo.org> AuthorDate: 2023-05-10 13:57:14 +0000 Commit: Ionen Wolkens <ionen@gentoo.org> CommitDate: 2023-05-10 13:59:28 +0000 net-im/discord: stabilize 0.0.27 for amd64 For future reference, there's no problem with always bumping this one straight-to-stable and dropping old at same time given that without workarounds the old is immediately broken and useless. Exceptions may be experimental revbump changes and similar. Closes: https://bugs.gentoo.org/906036 Signed-off-by: Ionen Wolkens <ionen@gentoo.org> net-im/discord/discord-0.0.27.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
i have obviously been on stable. I added discord to package.keywords. 0.0.27 installed fine. solved thank you
(In reply to Ionen Wolkens from comment #2) > (In reply to Nick Sarnie from comment #1) > > The latest seems out for me. Are you on stable? > > discord is normally bumped straight-to-stable given old is always broken on > bumps. this time it has not been bumped to stable for a week or longer...
(In reply to Ionen Wolkens from comment #2) > discord is normally bumped straight-to-stable given old is always broken on > bumps. Yeah sorry I missed it this time.
(In reply to Nick Sarnie from comment #6) > (In reply to Ionen Wolkens from comment #2) > > discord is normally bumped straight-to-stable given old is always broken on > > bumps. > > Yeah sorry I missed it this time. np, looking closer I assume it was because of the appindicator revbump which was done to ~arch (which is fine in itself given it wasn't a new version, but then got copied to ~arch for the bump)
