Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #245169 > unrolled thread

5.15 kernel just won't do on Intel Rocket Lake...

Started byFelix Miata <mrmazda@earthlink.net>
First post2022-02-10 09:40 +0100
Last post2022-02-16 07:00 +0100
Articles 10 — 5 participants

Back to article view | Back to linux.debian.user

Contents

  5.15 kernel just won't do on Intel Rocket Lake... Felix Miata <mrmazda@earthlink.net> - 2022-02-10 09:40 +0100
    Re: 5.15 kernel just won't do on Intel Rocket Lake... David Wright <deblis@lionunicorn.co.uk> - 2022-02-10 16:30 +0100
      Re: 5.15 kernel just won't do on Intel Rocket Lake... Andrei POPESCU <andreimpopescu@gmail.com> - 2022-02-12 14:00 +0100
      Re: 5.15 kernel just won't do on Intel Rocket Lake... Felix Miata <mrmazda@earthlink.net> - 2022-02-14 06:00 +0100
        Re: 5.15 kernel just won't do on Intel Rocket Lake... Felix Miata <mrmazda@earthlink.net> - 2022-02-14 06:50 +0100
          Re: 5.15 kernel just won't do on Intel Rocket Lake... David <bouncingcats@gmail.com> - 2022-02-15 05:10 +0100
            Re: 5.15 kernel just won't do on Intel Rocket Lake... Polyna-Maude Racicot-Summerside <debian@polynamaude.com> - 2022-02-15 07:30 +0100
              Re: 5.15 kernel just won't do on Intel Rocket Lake... David <bouncingcats@gmail.com> - 2022-02-15 15:00 +0100
                Re: 5.15 kernel just won't do on Intel Rocket Lake... Andrei POPESCU <andreimpopescu@gmail.com> - 2022-02-15 19:10 +0100
                Re: 5.15 kernel just won't do on Intel Rocket Lake... Polyna-Maude Racicot-Summerside <debian@polynamaude.com> - 2022-02-16 07:00 +0100

#245169 — 5.15 kernel just won't do on Intel Rocket Lake...

FromFelix Miata <mrmazda@earthlink.net>
Date2022-02-10 09:40 +0100
Subject5.15 kernel just won't do on Intel Rocket Lake...
Message-ID<DPd9D-OQH-3@gated-at.bofh.it>
...if you have a bad BIOS, and wish to boot with more than one connected display.
https://gitlab.freedesktop.org/drm/intel/-/issues/4762 explains the issue, which
has just been announced fixed. But, it appears the fix may only be landing in
kernel 5.17rc3.

I tried to get the latest available kernel that is packaged by Debian people by
reading on

	https://wiki.debian.org/HowToUpgradeKernel
	https://wiki.debian.org/DebianExperimental

I put

	Package: linux-image
	Pin: release a=experimental
	Pin-Priority: 800

in /etc/apt/preferences.d/linux-kernel

and

	deb http://deb.debian.org/debian experimental main

in /etc/apt/sources.list, but apt-cache and aptitude don't seem to know that

<http://ftp.us.debian.org/debian/pool/main/l/linux/linux-image-5.16.0-trunk-amd64-unsigned_5.16.4-1~exp1_amd64.deb>

exists.

(# aptitude search linux-image
c   linux-image-5.10.0-9-amd64     -
c   linux-image-5.14.0-0.bpo.2-amd -
i A linux-image-5.15.0-2-amd64     - Linux 5.15 for 64-bit PCs (signed)
i A linux-image-5.15.0-3-amd64     - Linux 5.15 for 64-bit PCs (signed)
p   linux-image-5.15.0-3-amd64-dbg - Debug symbols for linux-image-5.15.0-3-
p   linux-image-5.15.0-3-amd64-uns - Linux 5.15 for 64-bit PCs
p   linux-image-5.15.0-3-cloud-amd - Linux 5.15 for x86-64 cloud (signed)
p   linux-image-5.15.0-3-cloud-amd - Debug symbols for linux-image-5.15.0-3-
p   linux-image-5.15.0-3-cloud-amd - Linux 5.15 for x86-64 cloud
p   linux-image-5.15.0-3-rt-amd64  - Linux 5.15 for 64-bit PCs, PREEMPT_RT (
p   linux-image-5.15.0-3-rt-amd64- - Debug symbols for linux-image-5.15.0-3-
p   linux-image-5.15.0-3-rt-amd64- - Linux 5.15 for 64-bit PCs, PREEMPT_RT
i   linux-image-amd64              - Linux for 64-bit PCs (meta-package)
p   linux-image-amd64-dbg          - Debugging symbols for Linux amd64 confi
p   linux-image-amd64-signed-templ - Template for signed linux-image package
p   linux-image-cloud-amd64        - Linux for x86-64 cloud (meta-package)
p   linux-image-cloud-amd64-dbg    - Debugging symbols for Linux cloud-amd64
v   linux-image-generic            -
p   linux-image-rt-amd64           - Linux for 64-bit PCs (meta-package)
p   linux-image-rt-amd64-dbg       - Debugging symbols for Linux rt-amd64 co)

which is what I found and installed using dpkg -i, resulting in this addition to
the search list:
i   linux-image-5.16.0-trunk-amd64 - Linux 5.16 for 64-bit PCs

# inxi -S
System:
  Host: ab560 Kernel: 5.16.0-trunk-amd64 x86_64 bits: 64 Console: pty pts/0
    Distro: Debian GNU/Linux bookworm/sid
#

What have I missed that prevents finding a recent kernel using package management
instead of relying on a web browser and wget?
-- 
Evolution as taught in public schools is, like religion,
	based on faith, not based on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata

[toc] | [next] | [standalone]

#245177

FromDavid Wright <deblis@lionunicorn.co.uk>
Date2022-02-10 16:30 +0100
Message-ID<DPjyp-SMN-5@gated-at.bofh.it>
In reply to#245169
On Thu 10 Feb 2022 at 03:39:26 (-0500), Felix Miata wrote:
> ...if you have a bad BIOS, and wish to boot with more than one connected display.
> https://gitlab.freedesktop.org/drm/intel/-/issues/4762 explains the issue, which
> has just been announced fixed. But, it appears the fix may only be landing in
> kernel 5.17rc3.
> 
> I tried to get the latest available kernel that is packaged by Debian people by
> reading on
> 
> 	https://wiki.debian.org/HowToUpgradeKernel
> 	https://wiki.debian.org/DebianExperimental
> 
> I put
> 
> 	Package: linux-image

Don't you need to glob this?

  Package: linux-image*

> 	Pin: release a=experimental
> 	Pin-Priority: 800
> 
> in /etc/apt/preferences.d/linux-kernel
> 
> and
> 
> 	deb http://deb.debian.org/debian experimental main
> 
> in /etc/apt/sources.list, but apt-cache and aptitude don't seem to know that
> 
> <http://ftp.us.debian.org/debian/pool/main/l/linux/linux-image-5.16.0-trunk-amd64-unsigned_5.16.4-1~exp1_amd64.deb>
> 
> exists.
> 
> (# aptitude search linux-image
> c   linux-image-5.10.0-9-amd64     -
> c   linux-image-5.14.0-0.bpo.2-amd -
> i A linux-image-5.15.0-2-amd64     - Linux 5.15 for 64-bit PCs (signed)
> i A linux-image-5.15.0-3-amd64     - Linux 5.15 for 64-bit PCs (signed)
> p   linux-image-5.15.0-3-amd64-dbg - Debug symbols for linux-image-5.15.0-3-
> p   linux-image-5.15.0-3-amd64-uns - Linux 5.15 for 64-bit PCs
> p   linux-image-5.15.0-3-cloud-amd - Linux 5.15 for x86-64 cloud (signed)
> p   linux-image-5.15.0-3-cloud-amd - Debug symbols for linux-image-5.15.0-3-
> p   linux-image-5.15.0-3-cloud-amd - Linux 5.15 for x86-64 cloud
> p   linux-image-5.15.0-3-rt-amd64  - Linux 5.15 for 64-bit PCs, PREEMPT_RT (
> p   linux-image-5.15.0-3-rt-amd64- - Debug symbols for linux-image-5.15.0-3-
> p   linux-image-5.15.0-3-rt-amd64- - Linux 5.15 for 64-bit PCs, PREEMPT_RT
> i   linux-image-amd64              - Linux for 64-bit PCs (meta-package)
> p   linux-image-amd64-dbg          - Debugging symbols for Linux amd64 confi
> p   linux-image-amd64-signed-templ - Template for signed linux-image package
> p   linux-image-cloud-amd64        - Linux for x86-64 cloud (meta-package)
> p   linux-image-cloud-amd64-dbg    - Debugging symbols for Linux cloud-amd64
> v   linux-image-generic            -
> p   linux-image-rt-amd64           - Linux for 64-bit PCs (meta-package)
> p   linux-image-rt-amd64-dbg       - Debugging symbols for Linux rt-amd64 co)
> 
> which is what I found and installed using dpkg -i, resulting in this addition to
> the search list:
> i   linux-image-5.16.0-trunk-amd64 - Linux 5.16 for 64-bit PCs
> 
> # inxi -S
> System:
>   Host: ab560 Kernel: 5.16.0-trunk-amd64 x86_64 bits: 64 Console: pty pts/0
>     Distro: Debian GNU/Linux bookworm/sid
> #
> 
> What have I missed that prevents finding a recent kernel using package management
> instead of relying on a web browser and wget?

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#245278

FromAndrei POPESCU <andreimpopescu@gmail.com>
Date2022-02-12 14:00 +0100
Message-ID<DQ0al-1iJP-5@gated-at.bofh.it>
In reply to#245177

[Multipart message — attachments visible in raw view] — view raw

On Jo, 10 feb 22, 09:27:26, David Wright wrote:
> On Thu 10 Feb 2022 at 03:39:26 (-0500), Felix Miata wrote:
> > ...if you have a bad BIOS, and wish to boot with more than one connected display.
> > https://gitlab.freedesktop.org/drm/intel/-/issues/4762 explains the issue, which
> > has just been announced fixed. But, it appears the fix may only be landing in
> > kernel 5.17rc3.
> > 
> > I tried to get the latest available kernel that is packaged by Debian people by
> > reading on
> > 
> > 	https://wiki.debian.org/HowToUpgradeKernel
> > 	https://wiki.debian.org/DebianExperimental
> > 
> > I put
> > 
> > 	Package: linux-image
> 
> Don't you need to glob this?
> 
>   Package: linux-image*

According to apt_preferences(5) it can also be a POSIX extended regular 
expression if surrounded by slashes, but in this case the glob seems 
more appropriate ;)

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [next] | [standalone]

#245358

FromFelix Miata <mrmazda@earthlink.net>
Date2022-02-14 06:00 +0100
Message-ID<DQBCV-1FQ7-1@gated-at.bofh.it>
In reply to#245177
David Wright composed on 2022-02-10 09:27 (UTC-0600):

> On Thu 10 Feb 2022 at 03:39:26 (-0500), Felix Miata wrote:

>> ...if you have a bad BIOS, and wish to boot with more than one connected display.
>> https://gitlab.freedesktop.org/drm/intel/-/issues/4762 explains the issue, which
>> has just been announced fixed. But, it appears the fix may only be landing in
>> kernel 5.17rc3.

>> I tried to get the latest available kernel that is packaged by Debian people by
>> reading on

>> 	https://wiki.debian.org/HowToUpgradeKernel
>> 	https://wiki.debian.org/DebianExperimental

>> I put

>> 	Package: linux-image

> Don't you need to glob this?

>   Package: linux-image*

It added 5.17rc kernels, but no 5.16, except the one I installed:
# aptitude search linux-image
c   linux-image-5.10.0-9-amd64    -
c   linux-image-5.14.0-0.bpo.2-am -
i A linux-image-5.15.0-2-amd64    - Linux 5.15 for 64-bit PCs (signed)
i A linux-image-5.15.0-3-amd64    - Linux 5.15 for 64-bit PCs (signed)
p   linux-image-5.15.0-3-amd64-db - Debug symbols for linux-image-5.15.0-3-
p   linux-image-5.15.0-3-amd64-un - Linux 5.15 for 64-bit PCs
p   linux-image-5.15.0-3-cloud-am - Linux 5.15 for x86-64 cloud (signed)
p   linux-image-5.15.0-3-cloud-am - Debug symbols for linux-image-5.15.0-3-
p   linux-image-5.15.0-3-cloud-am - Linux 5.15 for x86-64 cloud
p   linux-image-5.15.0-3-rt-amd64 - Linux 5.15 for 64-bit PCs, PREEMPT_RT (
p   linux-image-5.15.0-3-rt-amd64 - Debug symbols for linux-image-5.15.0-3-
p   linux-image-5.15.0-3-rt-amd64 - Linux 5.15 for 64-bit PCs, PREEMPT_RT
i   linux-image-5.16.0-trunk-amd6 - Linux 5.16 for 64-bit PCs
p   linux-image-5.17.0-rc3-amd64- - Debug symbols for linux-image-5.17.0-rc
p   linux-image-5.17.0-rc3-amd64- - Linux 5.17-rc3 for 64-bit PCs
p   linux-image-5.17.0-rc3-cloud- - Debug symbols for linux-image-5.17.0-rc
p   linux-image-5.17.0-rc3-cloud- - Linux 5.17-rc3 for x86-64 cloud
p   linux-image-5.17.0-rc3-rt-amd - Debug symbols for linux-image-5.17.0-rc
p   linux-image-5.17.0-rc3-rt-amd - Linux 5.17-rc3 for 64-bit PCs, PREEMPT_
i   linux-image-amd64             - Linux for 64-bit PCs (meta-package)
p   linux-image-amd64-dbg         - Debugging symbols for Linux amd64 confi
p   linux-image-amd64-signed-temp - Template for signed linux-image package
p   linux-image-cloud-amd64       - Linux for x86-64 cloud (meta-package)
p   linux-image-cloud-amd64-dbg   - Debugging symbols for Linux cloud-amd64
v   linux-image-generic           -
p   linux-image-rt-amd64          - Linux for 64-bit PCs (meta-package)
p   linux-image-rt-amd64-dbg      - Debugging symbols for Linux rt-amd64 co

>> 	Pin: release a=experimental
>> 	Pin-Priority: 800

>> in /etc/apt/preferences.d/linux-kernel

>> and

>> 	deb http://deb.debian.org/debian experimental main

>> in /etc/apt/sources.list, but apt-cache and aptitude don't seem to know that

>> <http://ftp.us.debian.org/debian/pool/main/l/linux/linux-image-5.16.0-trunk-amd64-unsigned_5.16.4-1~exp1_amd64.deb>

>> exists.

>> (# aptitude search linux-image
>> c   linux-image-5.10.0-9-amd64     -
>> c   linux-image-5.14.0-0.bpo.2-amd -
>> i A linux-image-5.15.0-2-amd64     - Linux 5.15 for 64-bit PCs (signed)
>> i A linux-image-5.15.0-3-amd64     - Linux 5.15 for 64-bit PCs (signed)
>> p   linux-image-5.15.0-3-amd64-dbg - Debug symbols for linux-image-5.15.0-3-
>> p   linux-image-5.15.0-3-amd64-uns - Linux 5.15 for 64-bit PCs
>> p   linux-image-5.15.0-3-cloud-amd - Linux 5.15 for x86-64 cloud (signed)
>> p   linux-image-5.15.0-3-cloud-amd - Debug symbols for linux-image-5.15.0-3-
>> p   linux-image-5.15.0-3-cloud-amd - Linux 5.15 for x86-64 cloud
>> p   linux-image-5.15.0-3-rt-amd64  - Linux 5.15 for 64-bit PCs, PREEMPT_RT (
>> p   linux-image-5.15.0-3-rt-amd64- - Debug symbols for linux-image-5.15.0-3-
>> p   linux-image-5.15.0-3-rt-amd64- - Linux 5.15 for 64-bit PCs, PREEMPT_RT
>> i   linux-image-amd64              - Linux for 64-bit PCs (meta-package)
>> p   linux-image-amd64-dbg          - Debugging symbols for Linux amd64 confi
>> p   linux-image-amd64-signed-templ - Template for signed linux-image package
>> p   linux-image-cloud-amd64        - Linux for x86-64 cloud (meta-package)
>> p   linux-image-cloud-amd64-dbg    - Debugging symbols for Linux cloud-amd64
>> v   linux-image-generic            -
>> p   linux-image-rt-amd64           - Linux for 64-bit PCs (meta-package)
>> p   linux-image-rt-amd64-dbg       - Debugging symbols for Linux rt-amd64 co)
>> 
>> which is what I found and installed using dpkg -i, resulting in this addition to
>> the search list:
>> i   linux-image-5.16.0-trunk-amd64 - Linux 5.16 for 64-bit PCs
>> 
>> # inxi -S
>> System:
>>   Host: ab560 Kernel: 5.16.0-trunk-amd64 x86_64 bits: 64 Console: pty pts/0
>>     Distro: Debian GNU/Linux bookworm/sid
>> #
>> 
>> What have I missed that prevents finding a recent kernel using package management
>> instead of relying on a web browser and wget?
-- 
Evolution as taught in public schools is, like religion,
	based on faith, not based on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata

[toc] | [prev] | [next] | [standalone]

#245360

FromFelix Miata <mrmazda@earthlink.net>
Date2022-02-14 06:50 +0100
Message-ID<DQCpj-1Guk-1@gated-at.bofh.it>
In reply to#245358
Felix Miata composed on 2022-02-13 23:53 (UTC-0500):

> David Wright composed on 2022-02-10 09:27 (UTC-0600):
 
>> On Thu 10 Feb 2022 at 03:39:26 (-0500), Felix Miata wrote:
 
>>> ...if you have a bad BIOS, and wish to boot with more than one connected display.
>>> https://gitlab.freedesktop.org/drm/intel/-/issues/4762 explains the issue, which
>>> has just been announced fixed. But, it appears the fix may only be landing in
>>> kernel 5.17rc3.
...
> # aptitude search linux-image
...
> p   linux-image-5.17.0-rc3-amd64-unsigned - Linux 5.17-rc3 for 64-bit PCs

Installing this one didn't help:
# uname -a
Linux ab560 5.17.0-rc3-amd64 #1 SMP PREEMPT Debian 5.17~rc3-1~exp1 (2022-02-11)

What search will return enough information to know when this has been replaced
with a newer rc3 build or rc4 or newer, like the following does:?
# zypper se -s nel-def | egrep -v 'devel|debug|base|src|586'
Loading repository data...
Reading installed packages...

S  | Name           | Type       | Version              | Arch   | Repository
---+----------------+------------+----------------------+--------+-------------------
il | kernel-default | package    | 5.16.7-1.1.g0503f69  | x86_64 | (System Packages)
il | kernel-default | package    | 5.16.3-4.1.gc7377e3  | x86_64 | (System Packages)
vl | kernel-default | package    | 5.16.9-4.1.g704dc30  | x86_64 | homeTiwaiSimpledrm
vl | kernel-default | package    | 5.16.8-1.1           | x86_64 | OSS
# inxi -S
System:
  Host: ab560 Kernel: 5.16.7-1.g0503f69-default x86_64 bits: 64
    Console: pty pts/0 Distro: openSUSE Tumbleweed 20220130
#
The homeTiwaiSimpledrm 5.16.7 kernel includes the fix for the thread subject
problem.

The apt*/dpkg system generally seems rather resistant to showing uninstalled
package versions, except for the aptitude "extension".
-- 
Evolution as taught in public schools is, like religion,
	based on faith, not based on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata

[toc] | [prev] | [next] | [standalone]

#245399

FromDavid <bouncingcats@gmail.com>
Date2022-02-15 05:10 +0100
Message-ID<DQXk5-1TCw-1@gated-at.bofh.it>
In reply to#245360
On Tue, 15 Feb 2022 at 10:14, David Wright <deblis@lionunicorn.co.uk> wrote:
> On Mon 14 Feb 2022 at 00:40:11 (-0500), Felix Miata wrote:
> > Felix Miata composed on 2022-02-13 23:53 (UTC-0500):
> > > David Wright composed on 2022-02-10 09:27 (UTC-0600):
> > >> On Thu 10 Feb 2022 at 03:39:26 (-0500), Felix Miata wrote:

> > The apt*/dpkg system generally seems rather resistant to showing uninstalled
> > package versions, except for the aptitude "extension".

> Come to think of it, I don't think I can help at all, beyond
> suggesting that you regularly download the names of the new
> kernels that appear in the pool itself.

> Yesterday you posted that: "apt-cache and aptitude don't seem to know that
> http://ftp.us.debian.org/debian/pool/main/l/linux/linux-image-5.16.0-trunk-amd64-unsigned_5.16.4-1~exp1_amd64.deb
> exists."

> AIUI, your apt* tools can only find what's indexed in dists/ rather
> than anything that happens to be in the pool, but I'm not familiar
> with the policy issues (as a non-developer). I don't think dpkg
> makes that its business at all.

> BTW the red line (attached) indicates that "trunk" doesn't appear
> on the page. (It's a term I don't understand.)

I found an explanation of "trunk" in Section 5.2.1 here:
  https://kernel-team.pages.debian.net/kernel-handbook/ch-versions.html

I don't know what I'm talking about, but it looks like "trunk" packages
are regularly added into NEW queue (and experimental repo?):
  https://lists.debian.org/cgi-bin/search?P=trunk&DEFAULTOP=and&B=Gdebian-kernel&SORT=0&HITSPERPAGE=50&xP=trunk

I imagine that they might be short-lived packages because they
might be quickly superceded with a later ABI name when they
transition to unstable. Just guessing, because I might learn
something when someone corrects me. I don't know much and
struggle to remember details in this area because I don't
need to regularly think about it.

[toc] | [prev] | [next] | [standalone]

#245401

FromPolyna-Maude Racicot-Summerside <debian@polynamaude.com>
Date2022-02-15 07:30 +0100
Message-ID<DQZvz-1UVt-3@gated-at.bofh.it>
In reply to#245399

[Multipart message — attachments visible in raw view] — view raw

On 2022-02-14 23:00, David wrote:
> On Tue, 15 Feb 2022 at 10:14, David Wright <deblis@lionunicorn.co.uk> wrote:
>> On Mon 14 Feb 2022 at 00:40:11 (-0500), Felix Miata wrote:
>>> Felix Miata composed on 2022-02-13 23:53 (UTC-0500):
>>>> David Wright composed on 2022-02-10 09:27 (UTC-0600):
>>>>> On Thu 10 Feb 2022 at 03:39:26 (-0500), Felix Miata wrote:
> 
>>> The apt*/dpkg system generally seems rather resistant to showing uninstalled
>>> package versions, except for the aptitude "extension".
> 
>> Come to think of it, I don't think I can help at all, beyond
>> suggesting that you regularly download the names of the new
>> kernels that appear in the pool itself.
> 
>> Yesterday you posted that: "apt-cache and aptitude don't seem to know that
>> http://ftp.us.debian.org/debian/pool/main/l/linux/linux-image-5.16.0-trunk-amd64-unsigned_5.16.4-1~exp1_amd64.deb
>> exists."
> 
>> AIUI, your apt* tools can only find what's indexed in dists/ rather
>> than anything that happens to be in the pool, but I'm not familiar
>> with the policy issues (as a non-developer). I don't think dpkg
>> makes that its business at all.
> 
>> BTW the red line (attached) indicates that "trunk" doesn't appear
>> on the page. (It's a term I don't understand.)
> 
> I found an explanation of "trunk" in Section 5.2.1 here:
>   https://kernel-team.pages.debian.net/kernel-handbook/ch-versions.html
> 
> I don't know what I'm talking about, but it looks like "trunk" packages
> are regularly added into NEW queue (and experimental repo?):
>   https://lists.debian.org/cgi-bin/search?P=trunk&DEFAULTOP=and&B=Gdebian-kernel&SORT=0&HITSPERPAGE=50&xP=trunk
> 
> I imagine that they might be short-lived packages because they
> might be quickly superceded with a later ABI name when they
> transition to unstable. Just guessing, because I might learn
> something when someone corrects me. I don't know much and
> struggle to remember details in this area because I don't
> need to regularly think about it.
> 
You make some unfounded and quick link that don't exist.
There's nothing in common between the "trunk" branch in the Linux Kernel
itself (trunk branch being used for release management purpose and
versioning) AND the Debian packaging.

https://www.debian.org/releases/

https://wiki.debian.org/DebianKernel

https://wiki.debian.org/KernelFAQ

The Debian development of the Kernel is done in it's own salsa git
repository, independent from the Linux Kernel repository. Like all other
package, there's a upstream branch that get pull into the repository
when needed.

https://salsa.debian.org/kernel-team/linux.git

https://salsa.debian.org/kernel-team/linux/-/branches

-- 
Polyna-Maude R.-Summerside
-Be smart, Be wise, Support opensource development

[toc] | [prev] | [next] | [standalone]

#245413

FromDavid <bouncingcats@gmail.com>
Date2022-02-15 15:00 +0100
Message-ID<DR6x3-1Z04-3@gated-at.bofh.it>
In reply to#245401
On Tue, 15 Feb 2022 at 17:23, Polyna-Maude Racicot-Summerside
<debian@polynamaude.com> wrote:
> On 2022-02-14 23:00, David wrote:
> > On Tue, 15 Feb 2022 at 10:14, David Wright <deblis@lionunicorn.co.uk> wrote:
> >> On Mon 14 Feb 2022 at 00:40:11 (-0500), Felix Miata wrote:
> >>> Felix Miata composed on 2022-02-13 23:53 (UTC-0500):
> >>>> David Wright composed on 2022-02-10 09:27 (UTC-0600):
> >>>>> On Thu 10 Feb 2022 at 03:39:26 (-0500), Felix Miata wrote:
> >
> >>> The apt*/dpkg system generally seems rather resistant to showing uninstalled
> >>> package versions, except for the aptitude "extension".
> >
> >> Come to think of it, I don't think I can help at all, beyond
> >> suggesting that you regularly download the names of the new
> >> kernels that appear in the pool itself.
> >
> >> Yesterday you posted that: "apt-cache and aptitude don't seem to know that
> >> http://ftp.us.debian.org/debian/pool/main/l/linux/linux-image-5.16.0-trunk-amd64-unsigned_5.16.4-1~exp1_amd64.deb
> >> exists."
> >
> >> AIUI, your apt* tools can only find what's indexed in dists/ rather
> >> than anything that happens to be in the pool, but I'm not familiar
> >> with the policy issues (as a non-developer). I don't think dpkg
> >> makes that its business at all.
> >
> >> BTW the red line (attached) indicates that "trunk" doesn't appear
> >> on the page. (It's a term I don't understand.)
> >
> > I found an explanation of "trunk" in Section 5.2.1 here:
> >   https://kernel-team.pages.debian.net/kernel-handbook/ch-versions.html
> >
> > I don't know what I'm talking about, but it looks like "trunk" packages
> > are regularly added into NEW queue (and experimental repo?):
> >   https://lists.debian.org/cgi-bin/search?P=trunk&DEFAULTOP=and&B=Gdebian-kernel&SORT=0&HITSPERPAGE=50&xP=trunk
> >
> > I imagine that they might be short-lived packages because they
> > might be quickly superceded with a later ABI name when they
> > transition to unstable. Just guessing, because I might learn
> > something when someone corrects me. I don't know much and
> > struggle to remember details in this area because I don't
> > need to regularly think about it.
> >
> You make some unfounded and quick link that don't exist.
> There's nothing in common between the "trunk" branch in the Linux Kernel
> itself (trunk branch being used for release management purpose and
> versioning) AND the Debian packaging.
>
> https://www.debian.org/releases/
>
> https://wiki.debian.org/DebianKernel
>
> https://wiki.debian.org/KernelFAQ
>
> The Debian development of the Kernel is done in it's own salsa git
> repository, independent from the Linux Kernel repository. Like all other
> package, there's a upstream branch that get pull into the repository
> when needed.
>
> https://salsa.debian.org/kernel-team/linux.git
>
> https://salsa.debian.org/kernel-team/linux/-/branches

Hi,

I'm afraid that I don't follow your point, because I don't see anywhere
that I did mention the "trunk" branch in the Linux kernel. I was
only talking about the Debian packages.

I just wrote about two places where Debian kernel packages with
"trunk" in their names are visible. But I do not know what those
packages are. If you can explain what those packages are,
what their life cycle is, and why they are named "trunk", that
would be helpful.

[toc] | [prev] | [next] | [standalone]

#245432

FromAndrei POPESCU <andreimpopescu@gmail.com>
Date2022-02-15 19:10 +0100
Message-ID<DRar0-21Ar-7@gated-at.bofh.it>
In reply to#245413

[Multipart message — attachments visible in raw view] — view raw

On Mi, 16 feb 22, 00:50:21, David wrote:
> 
> I just wrote about two places where Debian kernel packages with
> "trunk" in their names are visible. But I do not know what those
> packages are. If you can explain what those packages are,
> what their life cycle is, and why they are named "trunk", that
> would be helpful.
 
As far as I recall these are packages that don't have an ABI version 
*yet*. These are superseded by the RCx packages (both available in 
experimental only) and later by the packages with an ABI version (in 
unstable).

Or something like that ;)

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [next] | [standalone]

#245453

FromPolyna-Maude Racicot-Summerside <debian@polynamaude.com>
Date2022-02-16 07:00 +0100
Message-ID<DRlw5-28mq-3@gated-at.bofh.it>
In reply to#245413

[Multipart message — attachments visible in raw view] — view raw

Hi,

> I just wrote about two places where Debian kernel packages with
> "trunk" in their names are visible. But I do not know what those
> packages are. If you can explain what those packages are,
> what their life cycle is, and why they are named "trunk", that
> would be helpful.
> 

I don't see any kernel package with the *trunk* in the name.
The only reference to trunk appear as a branch in the repository.

Whatever what I search, none do appear.

Kernel package are named *linux*

I'm sure you can find all the info you need here.

https://wiki.debian.org/DebianKernel

https://kernel-team.pages.debian.net/kernel-handbook/
-- 
Polyna-Maude R.-Summerside
-Be smart, Be wise, Support opensource development

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web