Missing "kernel-package" in stretch

[Karsten Wemheuer]

Hi *,

I just want to do some tests with kernels in "stretch" and therefore
was looking for packet "kernel-package".

But 
apt install kernel-package
leads to 
E: Package 'kernel-package' has no installation candidate

Is this a bug or is kernel building in stretch different to jessie?

Thanks,

Karsten

[Darac Marjal]

Post by Karsten Wemheuer
Hi *,
I just want to do some tests with kernels in "stretch" and therefore
was looking for packet "kernel-package".
But 
apt install kernel-package
leads to 
E: Package 'kernel-package' has no installation candidate
Is this a bug or is kernel building in stretch different to jessie?

It's a bug. The package tracker page for kernel-package
<https://tracker.debian.org/pkg/kernel-package> states that the package
was removed from strech because the new version introduced a new,
serious-level bug: #848066. The bug was not fixed in time for the
release, so the package was dropped (it's still in unstable, though, so
it may return for buster).

Post by Karsten Wemheuer
Thanks,
Karsten

[Karsten Wemheuer]

Hi Darac,

Post by Darac Marjal
It's a bug. The package tracker page for kernel-package
<https://tracker.debian.org/pkg/kernel-package> states that 
the package was removed from strech because the new version 
introduced a new, serious-level bug: #848066. The bug was not fixed
in time for the release, so the package was dropped (it's still in 
unstable, though, so it may return for buster).

thanks for Your answer. If I understand You correctly, the package
would not be available in "stretch". How should I build a custom kernel
in stretch without this package?

Thanks,

Karsten

[Darac Marjal]

Post by Karsten Wemheuer
Hi Darac,

Post by Darac Marjal
It's a bug. The package tracker page for kernel-package
<https://tracker.debian.org/pkg/kernel-package> states that 
the package was removed from strech because the new version 
introduced a new, serious-level bug: #848066. The bug was not fixed
in time for the release, so the package was dropped (it's still in 
unstable, though, so it may return for buster).

thanks for Your answer. If I understand You correctly, the package
would not be available in "stretch". How should I build a custom kernel
in stretch without this package?

The Debian Hanbook
<https://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official>
appears to recommend using upstream's tools. That is, the kernel now
comes with a "make deb-pkg" target.

[Sven Joachim]

Post by Darac Marjal

Post by Karsten Wemheuer
Hi Darac,

Post by Darac Marjal
It's a bug. The package tracker page for kernel-package
<https://tracker.debian.org/pkg/kernel-package> states that 
the package was removed from strech because the new version 
introduced a new, serious-level bug: #848066. The bug was not fixed
in time for the release, so the package was dropped (it's still in 
unstable, though, so it may return for buster).

thanks for Your answer. If I understand You correctly, the package
would not be available in "stretch". How should I build a custom kernel
in stretch without this package?

The Debian Hanbook
<https://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official>
appears to recommend using upstream's tools. That is, the kernel now
comes with a "make deb-pkg" target.

In current kernels "make deb-pkg" also creates a source package which is
very time-consuming. Unless one wants to distribute the built packages
(and thus has to think about GPL compliance), it's better to use
"make bindeb-pkg" which only creates binary packages.

Cheers,
Sven

[Karsten Wemheuer]

Hi Darac,

thanks again. I wasn't aware of the new target "make deb-pkg".

Best regards,

Karsten

[Eduardo M KALINOWSKI]

Post by Karsten Wemheuer
thanks for Your answer. If I understand You correctly, the package
would not be available in "stretch". How should I build a custom kernel
in stretch without this package?

If you really want to use the package instead of the upstream make
target, you can download the package in unstable and install it. Care
must be taken when mixing distributions, but looking at the
dependencies (https://packages.debian.org/sid/kernel-package) one can
see that there are no specific versions required, and all the
dependencies are for fairly common packages that one probably already
has installed. This should make installation easy and shouldn't cause
any problems.