[Aptitude-devel] weird aptitude behavior with "grub" package?

Sven Joachim svenjoac at gmx.de
Sat Sep 5 07:51:55 UTC 2009


On 2009-09-05 09:25 +0200, Miles Bader wrote:

> Sven Joachim <svenjoac at gmx.de> writes:
>>> (I _can_ install "grub-pc" explicitly, so there's no obvious conflict)
>>
>> There is, grub-pc conflicts with grub.  I'll file a bug report on that
>> issue.
>
> Hmm.
>
> Shouldn't this sort of situation cause _some_ kind of complaint from
> aptitude?  I mean, it just removes the "grub" package despite it not
> being marked "auto", and _doesn't_ attempt to replace it with anything
> else.

Yes, aptitude should really warn.  Even the experimental aptitude
version does not tell anything when trying to install grub in a chroot:

,----
| # LANG=C aptitude -V -D -v install grub
| Reading package lists... Done
| Building dependency tree       
| Reading state information... Done
| Reading extended state information      
| Initializing package states... Done
| No packages will be installed, upgraded, or removed.
| 0 packages upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
| Need to get 0B of archives. After unpacking 0B will be used.
| Writing extended state information... Done
| Reading package lists... Done             
| Building dependency tree       
| Reading state information... Done
| Reading extended state information      
| Initializing package states... Done
| 
| Current status: 0 broken [+0], 4 updates [+0], 194 new [+0].
`----

I'm 90% sure that this must have been reported already, but right now I
cannot find a matching bug among the 500+ outstanding reports.

Sven



More information about the Aptitude-devel mailing list