3Q-2017:move dev-texlive/texlive-langdutch dev-texlive/texlive-langeuropean 3Q-2017:move dev-texlive/texlive-langdanish dev-texlive/texlive-langeuropean 3Q-2017:move dev-texlive/texlive-documentation-turkish dev-texlive/texlive-langeuropean 3Q-2017:move dev-texlive/texlive-documentation-slovenian dev-texlive/texlive-langeuropean 3Q-2017:move dev-texlive/texlive-documentation-finnish dev-texlive/texlive-langeuropean 3Q-2017:move dev-texlive/texlive-documentation-dutch dev-texlive/texlive-langeuropean 3Q-2017:move dev-texlive/texlive-langswedish dev-texlive/texlive-langeuropean 3Q-2017:move dev-texlive/texlive-langlatin dev-texlive/texlive-langeuropean 3Q-2017:move dev-texlive/texlive-langlatvian dev-texlive/texlive-langeuropean 3Q-2017:move dev-texlive/texlive-langcroatian dev-texlive/texlive-langeuropean 3Q-2017:move dev-texlive/texlive-langnorwegian dev-texlive/texlive-langeuropean 3Q-2017:move dev-texlive/texlive-langhungarian dev-texlive/texlive-langeuropean 3Q-2017:move dev-texlive/texlive-langarmenian dev-texlive/texlive-langeuropean 3Q-2017:move dev-texlive/texlive-langfinnish dev-texlive/texlive-langeuropean 3Q-2017:move dev-texlive/texlive-langlithuanian dev-texlive/texlive-langeuropean pkgmove is for *moving* packages, not *merging* them. This construct can effectively create an invalid state where the PM is requested to create two packages with *identical* identifiers which is impossible. Please remove those entries ASAP, and use proper blockers and/or metapackages instead.
3Q-2017:move dev-texlive/texlive-documentation-korean dev-texlive/texlive-langcjk 3Q-2017:move dev-texlive/texlive-documentation-japanese dev-texlive/texlive-langcjk 3Q-2017:move dev-texlive/texlive-documentation-chinese dev-texlive/texlive-langcjk 3Q-2017:move dev-texlive/texlive-documentation-vietnamese dev-texlive/texlive-langother 3Q-2017:move dev-texlive/texlive-documentation-thai dev-texlive/texlive-langother 3Q-2017:move dev-texlive/texlive-langvietnamese dev-texlive/texlive-langother 3Q-2017:move dev-texlive/texlive-langtibetan dev-texlive/texlive-langother 3Q-2017:move dev-texlive/texlive-langturkmen dev-texlive/texlive-langother 3Q-2017:move dev-texlive/texlive-langhebrew dev-texlive/texlive-langother 3Q-2017:move dev-texlive/texlive-documentation-ukrainian dev-texlive/texlive-langcyrillic 3Q-2017:move dev-texlive/texlive-documentation-serbian dev-texlive/texlive-langcyrillic 3Q-2017:move dev-texlive/texlive-documentation-russian dev-texlive/texlive-langcyrillic 3Q-2017:move dev-texlive/texlive-documentation-mongolian dev-texlive/texlive-langcyrillic 3Q-2017:move dev-texlive/texlive-documentation-bulgarian dev-texlive/texlive-langcyrillic 3Q-2017:move dev-texlive/texlive-langmongolian dev-texlive/texlive-langcyrillic
Also these (which have an existing package as their destination): move dev-texlive/texlive-documentation-arabic dev-texlive/texlive-langarabic move dev-texlive/texlive-documentation-spanish dev-texlive/texlive-langspanish move dev-texlive/texlive-documentation-portuguese dev-texlive/texlive-langportuguese move dev-texlive/texlive-documentation-polish dev-texlive/texlive-langpolish move dev-texlive/texlive-documentation-italian dev-texlive/texlive-langitalian move dev-texlive/texlive-documentation-german dev-texlive/texlive-langgerman move dev-texlive/texlive-documentation-french dev-texlive/texlive-langfrench move dev-texlive/texlive-documentation-english dev-texlive/texlive-langenglish move dev-texlive/texlive-documentation-czechslovak dev-texlive/texlive-langczechslovak move dev-texlive/texlive-texinfo dev-texlive/texlive-plainextra I have removed all dev-texlive package moves from 3Q-2017. Let's hope there were not too many users left with such old texlive versions. (In reply to Michał Górny from comment #0) > Please remove those entries ASAP, and use proper blockers and/or > metapackages instead. Looks like blockers are already in place. Anything that remains to be done here? Last rites (sort of pointless if the packages are gone already)?
> (In reply to Michał Górny from comment #0) > > Please remove those entries ASAP, and use proper blockers and/or > > metapackages instead. > > Looks like blockers are already in place. Anything that remains to be done > here? Last rites (sort of pointless if the packages are gone already)? The idea behind those moves is not to make some upgrade path work but rather to be nicer with users and avoid having every single texlive update being a stress test for $PM blocker resolution algorithm.
(In reply to Alexis Ballier from comment #3) > The idea behind those moves is not to make some upgrade path work but rather > to be nicer with users and avoid having every single texlive update being a > stress test for $PM blocker resolution algorithm. Yeah, but the problem is that the package move mechanism wasn't meant for that type of operation (as explained in bug 668820). One possible workaround is to convert the old package(s) into a metapackage that installs nothing but rdepends on its replacement. And maybe outputs a postinst warning that the user should remove the old package. (In the concrete case, there could have been e.g. dev-texlive/texlive-langdutch-2013 with RDEPEND on tl-langeuropean.)
(In reply to Ulrich Müller from comment #4) > (In reply to Alexis Ballier from comment #3) > > The idea behind those moves is not to make some upgrade path work but rather > > to be nicer with users and avoid having every single texlive update being a > > stress test for $PM blocker resolution algorithm. > > Yeah, but the problem is that the package move mechanism wasn't meant for > that type of operation (as explained in bug 668820). > > One possible workaround is to convert the old package(s) into a metapackage > that installs nothing but rdepends on its replacement. And maybe outputs a > postinst warning that the user should remove the old package. (In the > concrete case, there could have been e.g. dev-texlive/texlive-langdutch-2013 > with RDEPEND on tl-langeuropean.) Not worth it. Removing the moves was the right call. They usually come way too late anyway since moves can't happen until *all* arches have stabilized it, so stable users of major arches still suffer usually.
(In reply to Alexis Ballier from comment #5) > (In reply to Ulrich Müller from comment #4) > > (In reply to Alexis Ballier from comment #3) > > > The idea behind those moves is not to make some upgrade path work but rather > > > to be nicer with users and avoid having every single texlive update being a > > > stress test for $PM blocker resolution algorithm. > > > > Yeah, but the problem is that the package move mechanism wasn't meant for > > that type of operation (as explained in bug 668820). > > > > One possible workaround is to convert the old package(s) into a metapackage > > that installs nothing but rdepends on its replacement. And maybe outputs a > > postinst warning that the user should remove the old package. (In the > > concrete case, there could have been e.g. dev-texlive/texlive-langdutch-2013 > > with RDEPEND on tl-langeuropean.) > > Not worth it. Removing the moves was the right call. They usually come way > too late anyway since moves can't happen until *all* arches have stabilized > it, so stable users of major arches still suffer usually. The only drawback is that I can't cleanup old blockers and have to keep accumulating blockers since 10 years of texlive.
You don't need to keep blockers forever.
(In reply to Andreas Sturmlechner from comment #7) > You don't need to keep blockers forever. I wish that was the case. We're living on another timeline here. I think that back in 2011 or 2012 I still had to point a few bug reports to the migration guide from tetex to texlive as this was still causing issues...
