Hi Andrei, Didier,
Thanks for your new feedbacks.
As agreed, I posted to debian-backports [*] and, the following day, there was
my package linux-image-5.10.0-0.bpo.4-amd64 available in my repository.
Maybe it's juste a coincidence or a swift reaction, cannot tell as I didn't
receive an
Le 01/04/2021 à 10:02, Andrei POPESCU a écrit :
On Mi, 31 mar 21, 22:54:59, l0f...@tuta.io wrote:
[...]
Is linux-signed-amd64 the source of linux-image-amd64?
[...]
I suppose there are some constraints here but it would be (apparently)
easier if the names were matching ^^
Using different
On Mi, 31 mar 21, 22:54:59, l0f...@tuta.io wrote:
> Hi,
>
> 30 mars 2021, 08:16 de andreimpope...@gmail.com:
>
> > $ rmadison linux-signed-amd64
> > linux-signed-amd64 | 4.19.118+2+deb10u1~bpo9+1 | stretch-backports | source
> > linux-signed-amd64 | 4.19.171+2| stable
Hi,
30 mars 2021, 08:16 de andreimpope...@gmail.com:
> $ rmadison linux-signed-amd64
> linux-signed-amd64 | 4.19.118+2+deb10u1~bpo9+1 | stretch-backports | source
> linux-signed-amd64 | 4.19.171+2| stable| source
> linux-signed-amd64 | 4.19.181+1|
On Sun 28 Mar 2021 at 19:46:07 (+0200), l0f...@tuta.io wrote:
>
> By the way, what is image-5.10.0-0.bpo.4* serie for?Is it only related to
> "Change ABI number to 0.bpo.4"? Do I need that?
I guess you have to read the changes file to find that out.
On Ma, 30 mar 21, 00:06:26, l0f...@tuta.io wrote:
> Hi Andrei,
>
> 29 mars 2021, 22:09 de andreimpope...@gmail.com:
>
> > Sorry, quoted wrong line, I meant this:
> >
> >> linux-image-5.10.0-0.bpo.4-amd64-unsigned/buster-backports
> >> 5.10.19-1~bpo10+1 amd64
> >>
> Haha, I was wondering why you
Hi Andrei,
29 mars 2021, 22:09 de andreimpope...@gmail.com:
> Sorry, quoted wrong line, I meant this:
>
>> linux-image-5.10.0-0.bpo.4-amd64-unsigned/buster-backports 5.10.19-1~bpo10+1
>> amd64
>>
Haha, I was wondering why you were comparing 5.10 with 5.9^^
Actually, I maintain my position. The
On Lu, 29 mar 21, 22:45:02, Andrei POPESCU wrote:
> On Du, 28 mar 21, 19:46:07, l0f...@tuta.io wrote:
> >
> > 22 mars 2021, 12:17 de andreimpope...@gmail.com:
> >
> > > When Linux has significant updates the package name changes as well to
> > > signal that e.g. out-of-tree modules must be
On Du, 28 mar 21, 19:46:07, l0f...@tuta.io wrote:
>
> 22 mars 2021, 12:17 de andreimpope...@gmail.com:
>
> > When Linux has significant updates the package name changes as well to
> > signal that e.g. out-of-tree modules must be recompiled.
> >
> > Try this instead:
> >
> > apt list
Hi Harry,
22 mars 2021, 01:12 de wea...@riseup.net:
> You may be looking at the unsigned version and may have to wait 24 hours
> for the signed one to come through the repositories, if that's what you
> are running.
>
Thanks for your message but 24 hours don't seem to be enough here...
Maybe
Hi,
Sorry for the late reply.
Thanks everyone for providing answers to me.
22 mars 2021, 04:00 de geoff.re...@gmail.com:
> You're probably missing the metapackage, linux-image-amd64.
>
You are right!
Now I've installed linux-image-amd64 but my system still doesn't notify me
regarding any
On Ma, 23 mar 21, 11:45:05, David Wright wrote:
>
> If I search on https://packages.debian.org/index for
> linux-image-5.10.0-0.bpo. in buster-backports/any,
> then I see the same six matches for
> linux-image-5.10.0-0.bpo.4…amd64, where, as before,
> "…" stands for cloud, rt, and nothing.
>
>
On Tue 23 Mar 2021 at 10:39:07 (+0200), Andrei POPESCU wrote:
> On Lu, 22 mar 21, 18:53:54, The Wanderer wrote:
> >
> > If I search https://packages.debian.org/source/testing/linux for those
> > package names, I find linux-image-5.10.0-4-amd64-unsigned, but I do not
> > find
Hello
from what I understand:
- in Bullseye, as indicated in its webpage on the Debian packages
website, the linux-image-5.10.0-4-amd64 binary package is built from the
linux-signed-amd64 source package
- the purpose of Debian Backports is to provide to Stable users binary
packages of
On Lu, 22 mar 21, 18:53:54, The Wanderer wrote:
>
> If I search https://packages.debian.org/source/testing/linux for those
> package names, I find linux-image-5.10.0-4-amd64-unsigned, but I do not
> find linux-image-5.10.0-4-amd64 itself - even though apt reports that it
> is, in fact, present.
>
(There's a suggestion of a possible answer for the OP to check out, down
at the bottom of this message.)
On 2021-03-22 at 07:49, Andrei POPESCU wrote:
> On Lu, 22 mar 21, 07:26:27, The Wanderer wrote:
>
>> On 2021-03-22 at 07:22, Andrei POPESCU wrote:
>>
>>> In any case, backports is, by
The Wanderer wrote:
> On 2021-03-22 at 03:31, didier gaumet wrote:
...
>> There is a linux-image-5.10.0-0.bpo.3-amd64 package but
>> linux-image-5.10.0-0.bpo.4-amd64 has yet to be uploaded
>> (linux-image-5.10.0-0.bpo.4-amd64-unsigned is there already)
>
> Are you sure that's it?
>
> I thought the
On Lu, 22 mar 21, 07:26:27, The Wanderer wrote:
> On 2021-03-22 at 07:22, Andrei POPESCU wrote:
> >
> > In any case, backports is, by definition, lagging behind testing.
>
> Yes, but that should only be reflected in the fact that the package
> version is different, not in which packages are
On 2021-03-22 at 07:22, Andrei POPESCU wrote:
> On Lu, 22 mar 21, 07:11:46, The Wanderer wrote:
>
>> On 2021-03-22 at 03:31, didier gaumet wrote:
>>
>>> Hello,
>>>
>>> There is a linux-image-5.10.0-0.bpo.3-amd64 package but
>>> linux-image-5.10.0-0.bpo.4-amd64 has yet to be uploaded
>>>
On Lu, 22 mar 21, 07:11:46, The Wanderer wrote:
> On 2021-03-22 at 03:31, didier gaumet wrote:
>
> > Hello,
> >
> > There is a linux-image-5.10.0-0.bpo.3-amd64 package but
> > linux-image-5.10.0-0.bpo.4-amd64 has yet to be uploaded
> > (linux-image-5.10.0-0.bpo.4-amd64-unsigned is there already)
On Du, 21 mar 21, 23:28:04, l0f...@tuta.io wrote:
>
> apt policy doesn't see any newer version as well:
>
> $ apt policy linux-image-5.10.0-0.bpo.3-amd64
> linux-image-5.10.0-0.bpo.3-amd64:
> Installed: 5.10.13-1~bpo10+1
> Candidate: 5.10.13-1~bpo10+1
> Version table:
> ***
On 2021-03-22 at 03:31, didier gaumet wrote:
> Hello,
>
> There is a linux-image-5.10.0-0.bpo.3-amd64 package but
> linux-image-5.10.0-0.bpo.4-amd64 has yet to be uploaded
> (linux-image-5.10.0-0.bpo.4-amd64-unsigned is there already)
Are you sure that's it?
I thought the same thing at first,
Hello,
There is a linux-image-5.10.0-0.bpo.3-amd64 package but
linux-image-5.10.0-0.bpo.4-amd64 has yet to be uploaded
(linux-image-5.10.0-0.bpo.4-amd64-unsigned is there already)
l0f...@tuta.io wrote:
$ apt policy linux-image-5.10.0-0.bpo.3-amd64
linux-image-5.10.0-0.bpo.3-amd64:
Installed: 5.10.13-1~bpo10+1
Candidate: 5.10.13-1~bpo10+1
Version table:
*** 5.10.13-1~bpo10+1 100
100 http://deb.debian.org/debian buster-backports/main amd64 Packages
Hi,
I'm running the following kernel:
$ uname -a
Linux 5.10.0-0.bpo.3-amd64 #1 SMP Debian 5.10.13-1~bpo10+1 (2021-02-11) x86_64
GNU/Linux
Backports repository is configured:
$ cat /etc/apt/sources.list
deb http://deb.debian.org/debian/ buster main contrib non-free
deb-src
25 matches
Mail list logo
