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.

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

Hardcoded kernel versions in scripts needs to be updated with each new kernel release #501

Open
jorritnutma opened this issue Oct 17, 2017 · 15 comments

Comments

@jorritnutma
Copy link

Hi, today I've build the zip but first had to change the kernel version from 4.9.0-3 to 4.9.0-4 in update.sh and build.sh because the linux-imagekernel-image-4.9.0-3-rpi is not in the repos anymore. Could you please update the files?

@Mausy5043
Copy link
Contributor

I'd love it if someone could provide a solution where we don't need to hardcode the kernel package name.

@olmari
Copy link
Contributor

olmari commented Oct 20, 2017

I wonder would some repo have symlink to latest images, so we could refer to that... I tried to look around a little but yet to see any obvous method to achieve this...

@olmari
Copy link
Contributor

olmari commented Oct 21, 2017

For now, I made plain old manual update on pull request #502

@Mausy5043
Copy link
Contributor

Closing issue since the problem is resolved.

@JedMeister
Copy link

Closing issue since the problem is resolved.

Do you mean the specific issue (wrong kernel version) or the generic issue (hard coded kernel version required)?

FWIW, if Raspbian don't already, the way to fix it properly would be for a meta package to be produced which always depends on the latest kernel. When a new kernel package is released, a new metapackage would be released depending on the new kernel. Obviously that's outside the scope of this project though...

@olmari
Copy link
Contributor

olmari commented Jan 3, 2018

@JedMeister
Specific issue.

If only there would be symlink or something similar on the site kernel is downloaded to allways latest kernel, would immediately solve much of this problem.

@JedMeister
Copy link

Cheers.

Like I say, a generically named Raspbian meta package would be the ideal way to resolve this IMO. It's the way that Debian have always done it AFAIK.

@olmari
Copy link
Contributor

olmari commented Jan 3, 2018

Metapackage in raspbian itself won't help us here, we need an way to get latest kernel from download server directly... Unless someone else knows better way and programs it :)

@Mausy5043
Copy link
Contributor

curl http://archive.raspbian.org/raspbian/pool/main/l/linux-4.9/ |grep linux-image |awk -F\" '{print $2}' gives:

linux-image-4.9.0-4-rpi-dbg_4.9.51-1%2brpi1~jessie_armhf.deb
linux-image-4.9.0-4-rpi-dbg_4.9.51-1%2brpi3%2bb1_armhf.deb
linux-image-4.9.0-4-rpi-dbg_4.9.51-1%2brpi3_armhf.deb
linux-image-4.9.0-4-rpi2-dbg_4.9.51-1%2brpi1~jessie_armhf.deb
linux-image-4.9.0-4-rpi2-dbg_4.9.51-1%2brpi3%2bb1_armhf.deb
linux-image-4.9.0-4-rpi2-dbg_4.9.51-1%2brpi3_armhf.deb
linux-image-4.9.0-4-rpi2_4.9.51-1%2brpi1~jessie_armhf.deb
linux-image-4.9.0-4-rpi2_4.9.51-1%2brpi3%2bb1_armhf.deb
linux-image-4.9.0-4-rpi2_4.9.51-1%2brpi3_armhf.deb
linux-image-4.9.0-4-rpi_4.9.51-1%2brpi1~jessie_armhf.deb
linux-image-4.9.0-4-rpi_4.9.51-1%2brpi3%2bb1_armhf.deb
linux-image-4.9.0-4-rpi_4.9.51-1%2brpi3_armhf.deb

wget -O - http://archive.raspbian.org/raspbian/pool/main/l/linux-4.9/ |grep linux-image |awk -F\" '{print $2}' gives the same.

So, at buildtime something should be possible.

Then, busybox wget -O - http://archive.raspbian.org/raspbian/pool/main/l/linux-4.9/ |busybox grep linux-image |busybox awk -F\" '{print $2}' gives this:

linux-image-4.9.0-4-rpi-dbg_4.9.51-1%2brpi1~jessie_armhf.deb
linux-image-4.9.0-4-rpi-dbg_4.9.51-1%2brpi3%2bb1_armhf.deb
linux-image-4.9.0-4-rpi-dbg_4.9.51-1%2brpi3_armhf.deb
linux-image-4.9.0-4-rpi2-dbg_4.9.51-1%2brpi1~jessie_armhf.deb
linux-image-4.9.0-4-rpi2-dbg_4.9.51-1%2brpi3%2bb1_armhf.deb
linux-image-4.9.0-4-rpi2-dbg_4.9.51-1%2brpi3_armhf.deb
linux-image-4.9.0-4-rpi2_4.9.51-1%2brpi1~jessie_armhf.deb
linux-image-4.9.0-4-rpi2_4.9.51-1%2brpi3%2bb1_armhf.deb
linux-image-4.9.0-4-rpi2_4.9.51-1%2brpi3_armhf.deb
linux-image-4.9.0-4-rpi_4.9.51-1%2brpi1~jessie_armhf.deb
linux-image-4.9.0-4-rpi_4.9.51-1%2brpi3%2bb1_armhf.deb
linux-image-4.9.0-4-rpi_4.9.51-1%2brpi3_armhf.deb

which implies that in the installer something should be possible also... ❓

@JedMeister
Copy link

@olmari

Metapackage in raspbian itself won't help us here, we need an way to get latest kernel from download server directly..

Of course! Sorry for the noise...

@olmari
Copy link
Contributor

olmari commented Jan 9, 2018

@Mausy5043 We'd still need to know what of those image(s) we want and hope "formatting" never change. but at least would be step forward for sure. Maybe we should first ask from raspbian maintainers if an symlink(s) in server could be made to allways point newest/most relevant images.. And that would be that in all its glory =) (not that I have been too active with this either :) )

@Mausy5043 Mausy5043 reopened this Jan 9, 2018
@Mausy5043
Copy link
Contributor

Ref: requested support.

@Mausy5043
Copy link
Contributor

The Raspbian team isn't very forthcoming.

@plugwash
Copy link

I guess I have to spoonfeed you guys ;) (the .txt extension is just to keep github happy)
getlatestpackage.txt

@goranche
Copy link
Contributor

goranche commented Mar 8, 2018

@plugwash oh, come on, in python?!? anyone can do that: shell, baby, shell 😂

😉 a bit more serious: thanks 👍
I'll try to find some time for this project again and see what's up and what can be done

@diederikdehaas diederikdehaas changed the title Raspbian repo changed kernel version to 4.9.0-4 Hardcoded kernel versions in scripts needs to be updated with each new release Dec 24, 2020
@diederikdehaas diederikdehaas changed the title Hardcoded kernel versions in scripts needs to be updated with each new release Hardcoded kernel versions in scripts needs to be updated with each new kernel release Dec 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants