Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

linux-raspberrypi 4.19.y is not considered stable #410

Closed
pbrkr opened this issue Apr 11, 2019 · 5 comments · Fixed by #414
Closed

linux-raspberrypi 4.19.y is not considered stable #410

pbrkr opened this issue Apr 11, 2019 · 5 comments · Fixed by #414

Comments

@pbrkr
Copy link
Collaborator

pbrkr commented Apr 11, 2019

Looking upstream today I've seen the following issue reported by @schnitzeltony: raspberrypi/linux#2931

On this issue it's been made clear that the rpi-4.19.y kernel branch is not considered stable and rebasing of this branch will likely continue. The rebasing is causing regular fetch errors for myself and other users.

I recommend we switch the default kernel version back to 4.14 in this layer.

@kraj, @agherzan: Any thoughts on this? It's a shame to move backwards but I don't think we can leave the default kernel on a branch that's being regularly rebased.
@kraj
Copy link
Collaborator

kraj commented Apr 11, 2019

We should add rebaseable=1 to SRC_URI until upstream gets their act together and starts respecting default public branches.

@agherzan
Copy link
Owner

What is rebaseable doing?

@kraj
Copy link
Collaborator

kraj commented Apr 16, 2019

it keeps the old SHA along even on refresh it will find the old SHA

@agherzan
Copy link
Owner

This assumes that you have the repo fetched. Which sounds like a weak assumption, isn't it?

@pbrkr
Copy link
Collaborator Author

pbrkr commented Apr 17, 2019

Setting rebaseable=1 doesn't fix things for us as we're not maintaining a downloads mirror.

pbrkr added a commit that referenced this issue Apr 21, 2019
@pbrkr
linux-raspberrypi: Switch default back to 4.14.y
5a3919f 
The 4.19.y kernel is not yet considered stable upstream as discussed in
the following GitHub issues:

#410
raspberrypi/linux#2931

Signed-off-by: Paul Barker <paul@betafive.co.uk>
@pbrkr pbrkr mentioned this issue Apr 21, 2019
Merged
agherzan pushed a commit that referenced this issue Apr 24, 2019
@pbrkr @agherzan
linux-raspberrypi: Switch default back to 4.14.y
348d572 
The 4.19.y kernel is not yet considered stable upstream as discussed in
the following GitHub issues:

#410
raspberrypi/linux#2931

Signed-off-by: Paul Barker <paul@betafive.co.uk>
daregit pushed a commit to daregit/yocto-combined that referenced this issue May 22, 2024
@pbrkr @agherzan
src/meta-raspberrypi:linux-raspberrypi: Switch default back to 4.14.y
b058532 
The 4.19.y kernel is not yet considered stable upstream as discussed in
the following GitHub issues:

agherzan/meta-raspberrypi#410
raspberrypi/linux#2931

Signed-off-by: Paul Barker <paul@betafive.co.uk>
daregit pushed a commit to daregit/yocto-combined that referenced this issue May 22, 2024
@pbrkr @agherzan
src/meta-raspberrypi:linux-raspberrypi: Switch default back to 4.14.y
ea4cd23 
The 4.19.y kernel is not yet considered stable upstream as discussed in
the following GitHub issues:

agherzan/meta-raspberrypi#410
raspberrypi/linux#2931

Signed-off-by: Paul Barker <paul@betafive.co.uk>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update 4.14.y kernel & make default, drop 4.9.y kernel agherzan/meta-raspberrypi
3 participants
@kraj @pbrkr @agherzan