Just for the archives...
On Sb, 12 ian 19, 19:31:11, dot...@gmail.com wrote:
>
> Good question. I upgrade my sid regularly and don't mess with the kernel: I
[...]
> Unfortunately no other kernel installed and, unless I go and dig into
> snapsot, at the moment in sid no other kernel version numb
On 14/01/19 11:20 PM, Vincent Lefevre wrote:
> On 2019-01-11 09:52:04 -0500, Michael Stone wrote:
>> On Fri, Jan 11, 2019 at 09:55:45AM +0100, dot...@gmail.com wrote:
>>> I recently came across an inconsistency in sid that it seems difficult (to
>>> me)
>>> to overcome.
>>>
>>> A kernel package na
On 2019-01-11 09:52:04 -0500, Michael Stone wrote:
> On Fri, Jan 11, 2019 at 09:55:45AM +0100, dot...@gmail.com wrote:
> > I recently came across an inconsistency in sid that it seems difficult (to
> > me)
> > to overcome.
> >
> > A kernel package named linux-image-4.19.0-1-amd64-unsigned provide
On Fri, Jan 11, 2019 at 3:52 PM Michael Stone wrote:
> How did you get the unsigned kernel installed in the first place? It's
> not typically installed, and I don't see any dependencies that would pull
> it in. If it weren't installed there'd be no problem. :)
Good question. I upgrade my sid re
On Fri, Jan 11, 2019 at 09:55:45AM +0100, dot...@gmail.com wrote:
I recently came across an inconsistency in sid that it seems difficult (to me)
to overcome.
A kernel package named linux-image-4.19.0-1-amd64-unsigned provides the running
kernel but, since few days ago, it creates conflicts with
I recently came across an inconsistency in sid that it seems difficult (to
me) to overcome.
A kernel package named linux-image-4.19.0-1-amd64-unsigned provides the
running kernel but, since few days ago, it creates conflicts with the
metapackage linux-image-amd64 (bercause it depends on
linux-imag
6 matches
Mail list logo
