tl;dr: You use deborphan wrong. The last paragraph of this mail
describes the fix that depends an unreleased deborphan version.
I'll send an update when it hits unstable.
* Martin-Éric Racine [2012-06-09 12:24 +0300]:
2012/5/14 Carsten Hey cars...@debian.org:
Since it does not
* Carsten Hey [2012-06-09 13:37 +0200]:
A proper fix for both packages, upgrade-system and grml-live, is
depending on a yet not released deborphan with a --recursive option and
running apt-get remove `deborphan` instead of of your loop. I'll drop
you a mail when such a deborphan release gets
2012/6/9 Carsten Hey cars...@debian.org:
* Carsten Hey [2012-06-09 13:37 +0200]:
A proper fix for both packages, upgrade-system and grml-live, is
depending on a yet not released deborphan with a --recursive option and
running apt-get remove `deborphan` instead of of your loop. I'll drop
you
* Martin-Éric Racine [2012-06-09 14:50 +0300]:
2012/6/9 Carsten Hey cars...@debian.org:
* Carsten Hey [2012-06-09 13:37 +0200]:
A proper fix for both packages, upgrade-system and grml-live, is
depending on a yet not released deborphan with a --recursive option and
running apt-get remove
2012/6/9 Carsten Hey cars...@debian.org:
You have problems with endless loops because you do not check for
already seen packages and deborphan fixes this for you in a proper way
so that there is no need to run deborphan in a loop.
No. The loop used to break on multiarch systems because
* Martin-Éric Racine [2012-06-09 15:16 +0300]:
2012/6/9 Carsten Hey cars...@debian.org:
You have problems with endless loops because you do not check for
already seen packages and deborphan fixes this for you in a proper way
so that there is no need to run deborphan in a loop.
No. The
6 matches
Mail list logo
