Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

Package removal "obsolete (to be r...

vrws
2011-06-13
2012-10-17
  • vrws
    vrws
    2011-06-13

    Today while updating my package list I became aware that some of the packages
    were marked "obsolete (to be removed)".

    I deselected the box to keep the package but was greeted with the message
    "This package must be removed."

    I cannot conceive a reason why a package I need for my documentation MUST BE
    REMOVED. This will break TeXing all documents using these packages (PTSans,
    PTSerif and AEB_Pro in my case).

    Is this behavior intended? And if so, why?

     
  • U_Fischer
    U_Fischer
    2011-06-15

    I don't see a reason why it should happen if it wasn't intended. They can be
    varioius reasons why a package is removed (e.g. license problems). But in this
    case I would say that the packages has been reordered. The files from PTSans
    eg are as far as I can see now in the "paratype" package, and some files from
    AEB_pro I found in various "acro..." packages.

    Also: The files are on CTAN. The package manager of miktex makes it easier to
    install them, but is not vital. You can always add files manually to your
    miktex installation.

    Ulrike Fischer

     
  • vrws
    vrws
    2011-06-17

    Hi Ulrike,

    thanks a lot for the answer. I hadn't realized that the PT* packages now
    appear in "paratype".

    But a licensing problem should never be a reason to force a package from my
    computer, even if it doesn't follow the Debian Free Software rules etc.
    Therefore I would like a message why a package is removed (especially when I'm
    not allowed to keep it). I.e. instead of "obsolete (to be removed)" something
    like "obsolete (repackaged)".

    Again, thanks a lot for your helpful answer,
    Volker RW Schaa