> But if dpkg can rely on the frontend to not remove any dependencies
> of the packages to be removed, the procedure is simple.
>
> try 1: find a package with no reverse-depends. remove it.
>...
Yes I also think this is a solution.
However it might be easier to change the following behavior:
>
# [1]
severity 579790 serious
quit
Moritz Beyreuther wrote:
> On Sat, Jul 17, 2010 at 08:56:51AM -0500, Jonathan Nieder wrote:
>> Moritz Beyreuther wrote:
> dpkg: dependency problems prevent removal of courier-mta:
Oh, right; --auto-deconfigure only applies to Conflicts and Breaks,
not newly uns
>On Sat, Jul 17, 2010 at 08:56:51AM -0500, Jonathan Nieder wrote:
> Moritz Beyreuther wrote:
>
> > The following does not do the job::
> >
> > dpkg --auto-deconfigure --force-depends --force-remove-essential \
> > --remove courier-mta courier-base courier-authdaemon \
> > cour
Moritz Beyreuther wrote:
> The following does not do the job::
>
> dpkg --auto-deconfigure --force-depends --force-remove-essential \
> --remove courier-mta courier-base courier-authdaemon \
> courier-authlib-userdb courier-authlib
What happens when you leave out the --force-
Ciao Jonathan,
thanks for your fast reply, not sure that I got it right. The
following does not do the job::
dpkg --auto-deconfigure --force-depends --force-remove-essential \
--remove courier-mta courier-base courier-authdaemon \
courier-authlib-userdb courier-authlib
Howeve
Jonathan Nieder wrote:
> severity 579790 important
More thoughts.
1. --force-depends makes semantics hard to reason about, but the
algorithm is actually very simple (from src/packages.c):
| The criteria for satisfying a dependency vary with the various
| tries. In try 1 we treat the depende
severity 579790 important
quit
Hi Moritz,
Moritz Beyreuther wrote:
> /usr/bin/dpkg --status-fd 11 --force-depends --force-remove-essential
> --remove courier-mta courier-base courier-authdaemon courier-authlib-userdb
> courier-authlib
>
> However courier-authlib is deinstalled first which brea
7 matches
Mail list logo
