kernel-debs: fix: don't try to package linux-libc-dev if only packaging dtb

[rpardini]

kernel-debs: fix: don't try to package linux-libc-dev if only packaging dtb

• kernel-debs: fix: don't try to package linux-libc-dev if only packaging dtb
  Fixes: 22511b3

[ColorfulRhino]

Looking good

[pyavitz]

Why is this package even being provided? It is already available in each distro.

[SteeManMI]

Why is this package even being provided? It is already available in each distro.

@pyavitz See #6408 for the discussion on the recent re-addition of this package

[pyavitz]

Why is this package even being provided? It is already available in each distro.

@pyavitz See #6408 for the discussion on the recent re-addition of this package

Thanx.

In my opinion linux-libc-dev should always be created when building an armbian kernel

I don't see why.

as the kernel versions often differ greatly from the ones natively in the distros.

Is that actually a problem?

I build kernels all the time and run them on focal to noble and bullseye to bookworm and beyond. I have yet to experience a problem that would require me to install this package.

linux-headers always installs linux-libc-dev as a dependency, so it is not enough. headers provided by linux-libc-dev are used by almost all libraries and programs (e.g. openssl, libc, samba, curl,....).

By this logic, wouldn't it make more sense that we use the linux-libc-dev that those libs and programs are expecting?

---

This is yet another case of Armbian creating problems for itself.

[amazingfate]

I build kernels all the time and run them on focal to noble and bullseye to bookworm and beyond. I have yet to experience a problem that would require me to install this package.

For example, AV1 stateless v4l2 uAPI is merged to v6.5, if I want to build gstreamer/ffmpeg/chromium supporting stateless v4l2 av1 decoding I have to install linux-libc-dev, but this package in jammy is 5.15. If edge mainline kernel doesn't provide this package, this is a not full-featured kernel.

[pyavitz]

I build kernels all the time and run them on focal to noble and bullseye to bookworm and beyond. I have yet to experience a problem that would require me to install this package.

For example, AV1 stateless v4l2 uAPI is merged to v6.5, if I want to build gstreamer/ffmpeg/chromium supporting stateless v4l2 av1 decoding I have to install linux-libc-dev, but this package in jammy is 5.15. If edge mainline kernel doesn't provide this package, this is a not full-featured kernel.

Is this provided via PPA?

[amazingfate]

I build kernels all the time and run them on focal to noble and bullseye to bookworm and beyond. I have yet to experience a problem that would require me to install this package.

For example, AV1 stateless v4l2 uAPI is merged to v6.5, if I want to build gstreamer/ffmpeg/chromium supporting stateless v4l2 av1 decoding I have to install linux-libc-dev, but this package in jammy is 5.15. If edge mainline kernel doesn't provide this package, this is a not full-featured kernel.

Is this provided via PPA?

I packaged chromium with v4l2-request support in a ppa for jammy: https://launchpad.net/~liujianfeng1994/+archive/ubuntu/chromium. You can see there is a linux package which provides only one deb linux-libc-dev for stateless v4l2 uAPI that chromium uses. I may stop these backporting works because noble is coming and bookworm-backports has updated linux-libc-dev to 6.6.

[rpardini]

By this logic, wouldn't it make more sense that we use the linux-libc-dev that those libs and programs are expecting?

I tried, I removed it during armbian-next, then fought for 2 years for sanity, but simply gave up during #6408 (review) -- there's only so much one single person can defend. I'm sorry.

[rpardini]

More reports (by @iav ) of trouble with this package -- seems it's missing Conflicts: line and breaks immediately when installed. Phew

[ColorfulRhino]

More reports (by @iav ) of trouble with this package -- seems it's missing Conflicts: line and breaks immediately when installed. Phew

I vote for reverting 22511b3 since it also needlessly clutters the output/debs folder with a bunch of linux-libc-dev*.deb files after building a few times.
But in the end that's not on me to decide.

Maybe instead we can make it an installable package in the Armbian apt repo? So it's not built by default, but one can install it with apt install. Not sure how far the automated systems are built for this scenario though.

[pyavitz]

Could this not be given a flag LIBC_DEV=true or whatever suites everyone and with that @amazingfate can add it to the PPA and base users can move on with their lives and not worry about this failing.