biblatex blocks texlive 2017

[avitase]

Hi,

I have some problems upgrading to texlive 2017:

Code: Select all

[blocks B      ] dev-texlive/texlive-genericextra
("dev-texlive/texlive-genericextra" is blocking
dev-texlive/texlive-plaingeneric-2017)

 * Error: The above package list contains packages which cannot be
 * installed at the same time on the same system.

  (dev-texlive/texlive-genericextra-2016:0/0::gentoo, ebuild scheduled
for merge) pulled in by
    dev-texlive/texlive-genericextra required by
(dev-tex/biblatex-3.4-r1:0/0::gentoo, ebuild scheduled for merge)

  (dev-texlive/texlive-plaingeneric-2017:0/0::gentoo, installed) pulled
in by
    >=dev-texlive/texlive-plaingeneric-2017 required by
(app-text/texlive-2017:0/0::gentoo, ebuild scheduled for merge)
    dev-texlive/texlive-plaingeneric required by
(virtual/texi2dvi-0-r1:0/0::gentoo, installed)

It seems, that dev-tex/biblatex does not accept texlive 2017 and still requires the 2016 version. Is there a particular reason for this behavior? How do I fix this?

Thanks for your help.

[fedeliallalinea]

It seems, that dev-tex/biblatex does not accept texlive 2017 and still requires the 2016 version. Is there a particular reason for this behavior? How do I fix this?

It's correct, unamsk version 3.7-r1 to fix

[avitase]

ok. Thank you for your help.

[Dekalog]

I don't get it. Version 3.7-r1 also depends on texlive-genericextra. How does this solve anything?

Also, as a more general point, how is it acceptable or even possible to have to switch from a stable package to an unstable one just to be able to do a world upgrade?

[ct85711]

3.7-r1 depends on either texlive-genericextra or texlive-plaingeneric; so it does provide a solution (note you'll probably need to remove texlive-genericextra first, so it could consider texlive-plaingeneric.

How to accept an unstable package, https://wiki.gentoo.org/wiki/ACCEPT_KEYWORDS. As far as why, quite often in situations like this, it's useful as a stop-gap measure so that you can resolve your problem while you wait for the devs to make it stable. It can easily take several months before the devs even mark a new version stable.