Am Mittwoch, 14. Juni 2017, 07:27:45 CEST schrieb Uwe Haider:
> emerge -auDtv world gives me this:
> 
[snip blockers]
> 
> The problem is all requested texlive-related packages are keyworded (
> ~amd64):
> 
>  eix -I texlive
> [I] app-text/texlive-core
>      Verfügbare Versionen:   2012-r1 ~2012-r3 ~2013-r3 2014-r4 2015-r1
> ~2016-r5 {X cjk doc +luajittex source tk xetex}
>      Installierte Versionen: 2015-r1(11:35:54 27.05.2017)(X luajittex
> -cjk -doc -source -tk -xetex)
>      Startseite:             http://tug.org/texlive/
>      Beschreibung:           A complete TeX distribution
> 
> [I] dev-texlive/texlive-basic
>      Verfügbare Versionen:   2012 ~2013 2014 2015 ~2016 {doc +luajittex
> source}
>      Installierte Versionen: 2015(22:45:08 28.03.2017)(luajittex -doc
> -source)
>      Startseite:             http://www.tug.org/texlive/
>      Beschreibung:           TeXLive Essential programs and files
> 
> [I] dev-texlive/texlive-metapost
>      Verfügbare Versionen:   2012 ~2013 2014 2015 ~2016 {doc source}
>      Installierte Versionen: 2015(22:45:17 28.03.2017)(-doc -source)
>      Startseite:             http://www.tug.org/texlive/
>      Beschreibung:           TeXLive MetaPost and Metafont packages

Those packages were stabilised less than a week ago, so I'm wondering:  When 
did you last 
sync the portage tree?  Do you use eix-sync?  When was the last time you ran 
eix-update?  
Because that eix output looks outdated (it's also missing the texlive 2017 
versions).

> Why are they requested by portage for the update? Is keywording them the
> only way to update my system?

See above.

However, regarding the blockers: you will likely have to manually unmerge a few 
packages 
before portage can continue.

HTH
-- 
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to