Bug#771379: linux-image-3.16-0.bpo.3-amd64: backport kernels not booting when root file system is on an LVM volume

[lee <lee@yagibdah.de>]

Bastian Blank <waldi@debian.org> writes:

> On Sat, Nov 29, 2014 at 08:06:28PM +0000, Ben Hutchings wrote:
>> apt-get fails to resolve this unless you add
>> 'initramfs-tools/wheezy-backports' or '-t wheezy-backports' to the
>> install command
>
> The backports documentation asks users to use "-t …".

Ok, well, can't it just work as intended?

I'm using aptitude both in GUI mode and from the commandline, depending
on what I'm doing, and when I install a package from backports, like the
kernel, I just expect that aptitude will resolve dependencies correctly
as usual without further ado, i. e. install the initramfs-tools from
backports when the backports kernel requires them.

And I might install packets from backports along with packets not from
backports in the same go.  All the packets from backports show up in
aptitude among the ones not from backports.  Hence it is very illogical
that I should need to do something in particular to resolve dependencies
for some of the packages I'm about to install.


-- 
Again we must be afraid of speaking of daemons for fear that daemons
might swallow us.  Finally, this fear has become reasonable.