Dropped in 2.1.
Unable to check for sanity: > package masked: dev-games/ogre-2.1
That is because I have no means to test these arches. And as the 2.1 series is brand new and GPU centric, I cowardly refused to add these blindly. If someone can test x86 and arm, those could be re-added.
(In reply to Sven Eden from comment #2) > That is because I have no means to test these arches. And as the 2.1 series > is brand new and GPU centric, I cowardly refused to add these blindly. > > If someone can test x86 and arm, those could be re-added. That's ok, but have a look at: https://devmanual.gentoo.org/keywording/index.html "If a new version introduces new dependencies which are not available on some architectures, then you should file a bug or ask on IRC before you upgrade the ebuild. If you really need to get the ebuild added in a hurry, for example, for a security fix, then you should drop any KEYWORDS which are causing problems and CC the relevant architectures on the bug — you must file a new bug to the architecture in question regarding this if no bug is already available." (It's also sensible to drop like you did, just remember to file a bug) The arch teams will test it out, likely when unmasked. Thanks for the info!
Time to unmask, do we think?
Unable to check for sanity: > no match for package: dev-games/ogre-2.1
(In reply to Sam James from comment #4) > Time to unmask, do we think? ping
I'm going to test and keyword 2.1 version on arm and x86. However, we should probably keep it masked for a while longer until all issues with revdeps have been fixed
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a75e161cf68b1b96526b6188c83ab5075e9f7239 commit a75e161cf68b1b96526b6188c83ab5075e9f7239 Author: Jakov Smolić <jsmolic@gentoo.org> AuthorDate: 2022-02-12 12:11:37 +0000 Commit: Jakov Smolić <jsmolic@gentoo.org> CommitDate: 2022-02-12 12:11:37 +0000 dev-games/ogre: keyword 2.1-r1 for ~x86 Bug: https://bugs.gentoo.org/740424 Signed-off-by: Jakov Smolić <jsmolic@gentoo.org> dev-games/ogre/ogre-2.1-r1.ebuild | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=81779448cf643cb3aabc1b90b767011ca049534f commit 81779448cf643cb3aabc1b90b767011ca049534f Author: Sam James <sam@gentoo.org> AuthorDate: 2022-03-02 05:07:09 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-03-02 05:07:09 +0000 profiles: add references to ogre masks Bug: https://bugs.gentoo.org/834468 Bug: https://bugs.gentoo.org/740424 Signed-off-by: Sam James <sam@gentoo.org> profiles/package.mask | 2 ++ 1 file changed, 2 insertions(+)
I have taken out Ogre-2.1 in PR https://github.com/gentoo/gentoo/pull/28652 as it should be having its own category dev-games/ogre-next instead. When I added an experimental ogre-next ebuild to dev-games/ogre, it looked like development on OGRE "classic" would be going away in favor of OGRE-next. Obviously this is not the case, so ogre-next should be considered separately from classic OGRE.