The proposed solution is in the tracker
2.73 bumped to EAPI=5, closing
Why do you think it's required to set EAPI to 5? It was working fine with latest x86 portage, but now emerge offers me to downgrade this package! # emerge -pv transmission These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild UD ] net-p2p/transmission-2.61 [2.73] USE="(-ayatana) -gtk -lightweight -qt4 -xfs" 0 kB Total: 1 package (1 downgrade), Size of downloads: 0 kB # emerge -pv \=net-p2p/transmission-2.73 These are the packages that would be merged, in order: Calculating dependencies... done! !!! All ebuilds that could satisfy "=net-p2p/transmission-2.73" have been masked. !!! One of the following masked packages is required to complete your request: - net-p2p/transmission-2.73::gentoo (masked by: EAPI 5) The current version of portage supports EAPI '4'. You must upgrade to a newer version of portage before EAPI masked packages can be installed. For more information, see the MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook.
# emerge --version Portage 2.1.11.9 (hardened/linux/x86, gcc-4.5.4, glibc-2.15-r3, 3.5.7-gentoo i686)
(In reply to comment #2) > Why do you think it's required to set EAPI to 5? It was working fine with > latest x86 portage, but now emerge offers me to downgrade this package! Both, Portage that can handle EAPI=5 and transmission-2.73 are in ~arch for x86. If you want ~arch transmission, use ~arch Portage. EAPI=5 automatically sets --disable-silent-rules to the build system that fixes this bug.
(In reply to comment #3) > # emerge --version > Portage 2.1.11.9 (hardened/linux/x86, gcc-4.5.4, glibc-2.15-r3, 3.5.7-gentoo > i686) To use eapi5, you need to have a new portage version, so, please wait a bit[1], resync and retry. [1]: https://bugs.gentoo.org/show_bug.cgi?id=440852#c7
(In reply to comment #4) > Both, Portage that can handle EAPI=5 and transmission-2.73 are in ~arch for > x86. > > If you want ~arch transmission, use ~arch Portage. I want latest transmission not because of bugs in ebuilds but because of bugs in previous transmission versions. I don't know why transmission-2.73.ebuild isn't stable and it doesn't care me as a regular user while it works. I used ~x86 accept_keywords particular for transmission-2.73 and it was working fine for me with EAPI=4. So, downgrading was very surprising. (In reply to comment #5) > To use eapi5, you need to have a new portage version, so, please wait a > bit[1], resync and retry. > > [1]: https://bugs.gentoo.org/show_bug.cgi?id=440852#c7 Thank you for good news and the link.
(In reply to comment #6) > I used ~x86 accept_keywords particular for > transmission-2.73 and it was working fine for me with EAPI=4. So, > downgrading was very surprising. but it is legimate to change EAPI long as KEYWORDS of sys-apps/portage and the ebuild using the newer EAPI match that's how Portage works :-)
