media-libs/freetype-2.9.1-r1 is now in portage and it still provides freetype-config, which is needed by texlive-core. Until a patch is available that uses pkg-config instead of freetype-config, the ebuild can instead depend on freetype-2.9.1-r1 instead of 2.9, as 2.9.1 has some important bug fixes. The revbump to r4 was needed to avoid blockers when doing a @world update.
*** This bug has been marked as a duplicate of bug 655052 ***
See URL field. You can safely depend on <media-libs/freetype-2.9.1-r2 now.
Why has this been closed? This is not a duplicate. This is a dep change, not a move to pkg-config.
(In reply to Lars Wendler (Polynomial-C) from comment #2) > See URL field. > > You can safely depend on <media-libs/freetype-2.9.1-r2 now. That change has been made without revbump so there is 0 guarantee the installed 2.9.1-r1 will have freetype-config.
It would be quite ugly, but a check in pkg_pretend() if has_version =media-libs/freetype-2.9.1-r1; then [[ -f "${EPREFIX}"/usr/bin/freetype-config ]] || die "re-emerge freetype" fi could do the trick in most cases. Notable exception is when previously built binpkg without freetype-config is going to be installed.
(In reply to Alexis Ballier from comment #4) > (In reply to Lars Wendler (Polynomial-C) from comment #2) > > See URL field. > > > > You can safely depend on <media-libs/freetype-2.9.1-r2 now. > > That change has been made without revbump so there is 0 guarantee the > installed 2.9.1-r1 will have freetype-config. ~arch already has freetype-2.9.1-r2 so I don't see a big problem here.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=06f93ddd92c098680b9e7e7ab1c31566fba18803 commit 06f93ddd92c098680b9e7e7ab1c31566fba18803 Author: Alexis Ballier <aballier@gentoo.org> AuthorDate: 2018-05-16 13:14:55 +0000 Commit: Alexis Ballier <aballier@gentoo.org> CommitDate: 2018-05-16 13:18:25 +0000 app-text/texlive-core: adjust freetype dep Closes: https://bugs.gentoo.org/655650 Package-Manager: Portage-2.3.36, Repoman-2.3.9 app-text/texlive-core/texlive-core-2017-r3.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Broken again with recent freetype commit: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7d9a68ef8e502f06fc968430038c3877112aef40 texlive-core still wants <freetype-2.9.1-r2 Isn't there a better solution to this issue than depending on exact (or max/min/whatever) versions?
@Lars Wendler Please stop breaking stable users. This is not acceptable. You should do your last min changes in a ~arch branch at least. @Nikos Chantziaras Please re-open this bug.
(In reply to Franz Fellner from comment #8) > Broken again with recent freetype commit: > https://gitweb.gentoo.org/repo/gentoo.git/commit/ > ?id=7d9a68ef8e502f06fc968430038c3877112aef40 > texlive-core still wants <freetype-2.9.1-r2 > > Isn't there a better solution to this issue than depending on exact (or > max/min/whatever) versions? The better solution is my patch on bug https://bugs.gentoo.org/655052. However, as you can see from the discussion it is not ready to go live.
Why does it fixed? The error is still there: WARNING: One or more updates/rebuilds have been skipped due to a dependency conflict: media-libs/freetype:2 (media-libs/freetype-2.9.1-r3:2/2::gentoo, ebuild scheduled for merge) conflicts with <media-libs/freetype-2.9.1-r2 required by (app-text/texlive-core-2017-r3:0/0::gentoo, installed)
Because it broke again. But a fix seems to be coming. You can add "=app-text/texlive-core-2017-r4 **" in /etc/portage/package.accept_keywords to get the fixed version.
adding "=app-text/texlive-core-2017-r4 **" to keywords does not fix it here (stable profile), still fails with WARNING: One or more updates/rebuilds have been skipped due to a dependency conflict: media-libs/freetype:2 (media-libs/freetype-2.9.1-r3:2/2::gentoo, ebuild scheduled for merge) conflicts with <media-libs/freetype-2.9.1-r2 required by (app-text/texlive-core-2017-r3:0/0::gentoo, installed) ^ ^^^^^^^^
(In reply to groepaz from comment #13) > <media-libs/freetype-2.9.1-r2 required by > (app-text/texlive-core-2017-r3:0/0::gentoo, installed) > ^ ^^^^^^^^ It says "-r3" so it didn't pick up the unmasking of "-r4" - are you sure you properly unmasked texlive-core? Correct config file? No misspelling?
(In reply to Anton Bolshakov from comment #9) > @Lars Wendler Please stop breaking stable users. This is not acceptable. You > should do your last min changes in a ~arch branch at least. Please stop telling me how to do my work. It's not my fault texlive-core has stupid dependency restrictions.
