19 Jul
2013
19 Jul
'13
1:39 p.m.
Hi On Thu, Jul 18, 2013 at 11:40 PM, Lukas Jirkovsky <l.jirkovsky@gmail.com> wrote:
I'm strongly against the idea of automatic orphaning. Sometimes the package may be outdated simply because the new version doesn't work or has some serious issues.
In this case the maintainer should unmark the package and clearly explain in comments why the package cannot be upgraded to the new version. Ideally maintainer should also work with upstream on resolving the issues. But silently leave the package in "out-of-date" state forever is not the best solution neither.