stable_* tags missing for 6.6.y kernels

Open
#6,063 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
git

Research direction

Start in the repository's Release > tags view and compare the latest stable_20240124 tag with the rpi-6.6.y branch; inspect the Makefile version and the commit referenced by the 6.6.20+rpt-rpi-v8 Debian changelog. Done means the 6.6.y kernel has corresponding stable_* tags that identify the expected commit and are visible to users.

Written by the indexing model from the issue text.

Description

Describe the bug

I'm integrating RPi Linux into NixOS. I've seen the announcement that RPi OS is receiving Linux 6.6, and I've seen that the default branch of this repository is now rpi-6.6.y. However, I don't see a tag corresponding with this update. The last tag available is stable_20240124 and that corresponds to 6.1.73-based kernel.

Currently a workaround is to download the latest RPi OS image one from raspberrypi.com and mount the image to inspect usr/share/doc/linux-image-6.6.20+rpt-rpi-v8/changelog.Debian.gz which specifies the commit. However, this is inconvenient.

This is probably related to https://github.com/RPi-Distro/repo/issues/368

Steps to reproduce the behaviour

Go to https://github.com/raspberrypi/linux and select "Release > <n> tags". Select the latest tag, then commit, then "Browse Files". Open "Makefile" and notice that it's still 6.1.y kernel.

Device (s)

Raspberry Pi 4 Mod. B

System

N/A

Logs

No response

Additional context

No response

Dominant language
C
Stars
13.2k
Forks
5.5k
Avg merge
2d 21h
Merged PRs (30d)
21

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from raspberrypi/linux

All issues in raspberrypi/linux

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.