Florian Kulzer wrote:
Being broken (i.e. having an unfulfilled dependency, pre-dependency, or
conflict) is a property of the package itself and should not depend on
the package manager. The package manager, on the other hand, can help
you to resolve breakages that occur, for example, during an
On (19/02/07 22:08), Florian Kulzer wrote:
> Being broken (i.e. having an unfulfilled dependency, pre-dependency, or
> conflict) is a property of the package itself and should not depend on
> the package manager. The package manager, on the other hand, can help
> you to resolve breakages that occur
On Mon, Feb 19, 2007 at 15:40:10 -0500, H.S. wrote:
>
> Hello,
>
> I started using aptitude a few days ago. I remember that at that time it
> was showing many packages were broken and wanted to remove a bunch of
> them. I then did some operation that I now forget which made aptitude to
> 'forg
Hello,
I started using aptitude a few days ago. I remember that at that time it
was showing many packages were broken and wanted to remove a bunch of
them. I then did some operation that I now forget which made aptitude to
'forget' about those packages and to clear the cache or some such thin
4 matches
Mail list logo
