Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#1022061: debian-kernel-handbook: improve kernel build steps for newbies
2 views
Skip to first unread message
Diederik de Haas
Oct 19, 2022, 11:50:03 AM10/19/22
to
Package: debian-kernel-handbook
Version: 1.0.20
Severity: normal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
In https://bugs.debian.org/1022025#37 I saw another example of someone
who hadn't built a kernel before, found the proper instructions but
didn't succeed in building a (patched) kernel.
All it took to succeed was some light guidance. And I know that when I
was at that stage, I had similar problems.
This bug is intended to collect the experiences/problems/etc that
newbies run into, which in turn allows us/me to improve the
documentation for everyone.
I do intend to submit a MR to improve it, but first we need to collect
the issues newbies run into, which will be done in this bug.
- -- System Information:
Debian Release: bookworm/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.0.0-1-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
debian-kernel-handbook depends on no packages.
Versions of packages debian-kernel-handbook recommends:
ii firefox [www-browser] 106.0-1
ii firefox-esr [www-browser] 102.4.0esr-1
ii konqueror [www-browser] 4:21.12.3-1
ii qutebrowser [www-browser] 2.5.2-1
ii w3m [www-browser] 0.5.3+git20220429-1+b1
debian-kernel-handbook suggests no packages.
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
iHUEARYIAB0WIQT1sUPBYsyGmi4usy/XblvOeH7bbgUCY1AavAAKCRDXblvOeH7b
bvUZAQCULw272Gb13pivISHTmnfbKEQ9JnSHSgXI+rHwSAVJ7gD/Qucrg6F0eUAO
z81Be4N3hfK+A8eCDWcezzvOZudQvQo=
=MIDA
-----END PGP SIGNATURE-----
Version: 1.0.20
Severity: normal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
In https://bugs.debian.org/1022025#37 I saw another example of someone
who hadn't built a kernel before, found the proper instructions but
didn't succeed in building a (patched) kernel.
All it took to succeed was some light guidance. And I know that when I
was at that stage, I had similar problems.
This bug is intended to collect the experiences/problems/etc that
newbies run into, which in turn allows us/me to improve the
documentation for everyone.
I do intend to submit a MR to improve it, but first we need to collect
the issues newbies run into, which will be done in this bug.
- -- System Information:
Debian Release: bookworm/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.0.0-1-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
debian-kernel-handbook depends on no packages.
Versions of packages debian-kernel-handbook recommends:
ii firefox [www-browser] 106.0-1
ii firefox-esr [www-browser] 102.4.0esr-1
ii konqueror [www-browser] 4:21.12.3-1
ii qutebrowser [www-browser] 2.5.2-1
ii w3m [www-browser] 0.5.3+git20220429-1+b1
debian-kernel-handbook suggests no packages.
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
iHUEARYIAB0WIQT1sUPBYsyGmi4usy/XblvOeH7bbgUCY1AavAAKCRDXblvOeH7b
bvUZAQCULw272Gb13pivISHTmnfbKEQ9JnSHSgXI+rHwSAVJ7gD/Qucrg6F0eUAO
z81Be4N3hfK+A8eCDWcezzvOZudQvQo=
=MIDA
-----END PGP SIGNATURE-----
Dan Coleman
Oct 19, 2022, 6:10:03 PM10/19/22
to
Hi there! This was me, and yes, it was unclear. The short version is that I was sent two patches to test on a kernel, and I had NO idea how to do that.
I first tried installing linux-source (which doesn't have a debian subfolder from what I could tell), but then learned that actually what I needed to do was run `apt source linux`. I didn't know that all I needed to do was go to the root of that directory and use test-patches in debian/bin/test-patches.
When I finally managed to get the test kernel compiled, I couldn't install it, either via apt or dpkg. I was told that apt would take care of removing the dependencies causing the conflict, but it didn't. DKMS wasn't triggered, it was a mess.
I really appreciate the work that goes into making kernel builds painless, but there are some missing steps.
$ apt source linux
$ cd linux-*/
$ debian/bin/test-patches -j14 /path/to/patch
At this point, everything is fine. But try installing the resulting .deb(s) with either apt or dpkg, and you'll get a whole host of errors and not know what to do. Really unclear for end users trying to help by testing.
On Wed, 19 Oct 2022 17:41:55 +0200 Diederik de Haas <didi....@cknow.org> wrote:
> Package: debian-kernel-handbook > Version: 1.0.20 > Severity: normal >
>
> >
I first tried installing linux-source (which doesn't have a debian subfolder from what I could tell), but then learned that actually what I needed to do was run `apt source linux`. I didn't know that all I needed to do was go to the root of that directory and use test-patches in debian/bin/test-patches.
When I finally managed to get the test kernel compiled, I couldn't install it, either via apt or dpkg. I was told that apt would take care of removing the dependencies causing the conflict, but it didn't. DKMS wasn't triggered, it was a mess.
I really appreciate the work that goes into making kernel builds painless, but there are some missing steps.
$ apt source linux
$ cd linux-*/
$ debian/bin/test-patches -j14 /path/to/patch
At this point, everything is fine. But try installing the resulting .deb(s) with either apt or dpkg, and you'll get a whole host of errors and not know what to do. Really unclear for end users trying to help by testing.
On Wed, 19 Oct 2022 17:41:55 +0200 Diederik de Haas <didi....@cknow.org> wrote:
> Package: debian-kernel-handbook > Version: 1.0.20 > Severity: normal >
> In https://bugs.debian.org/1022025#37 I saw another example of someone
> who hadn't built a kernel before, found the proper instructions but
> didn't succeed in building a (patched) kernel.
>
> All it took to succeed was some light guidance. And I know that when I
> was at that stage, I had similar problems.
>
> This bug is intended to collect the experiences/problems/etc that
> newbies run into, which in turn allows us/me to improve the
> documentation for everyone.
>
> I do intend to submit a MR to improve it, but first we need to collect
> the issues newbies run into, which will be done in this bug.
>
>
> who hadn't built a kernel before, found the proper instructions but
> didn't succeed in building a (patched) kernel.
>
> All it took to succeed was some light guidance. And I know that when I
> was at that stage, I had similar problems.
>
> This bug is intended to collect the experiences/problems/etc that
> newbies run into, which in turn allows us/me to improve the
> documentation for everyone.
>
> I do intend to submit a MR to improve it, but first we need to collect
> the issues newbies run into, which will be done in this bug.
>
>
> -- System Information:
> Debian Release: bookworm/sid
> APT prefers unstable-debug
> APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (101, 'experimental')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 6.0.0-1-amd64 (SMP w/16 CPU threads; PREEMPT)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> debian-kernel-handbook depends on no packages.
>
> Versions of packages debian-kernel-handbook recommends:
> ii firefox [www-browser] 106.0-1
> ii firefox-esr [www-browser] 102.4.0esr-1
> ii konqueror [www-browser] 4:21.12.3-1
> ii qutebrowser [www-browser] 2.5.2-1
> ii w3m [www-browser] 0.5.3+git20220429-1+b1
>
> debian-kernel-handbook suggests no packages.
>
> -- no debconf information
> Debian Release: bookworm/sid
> APT prefers unstable-debug
> APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (101, 'experimental')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 6.0.0-1-amd64 (SMP w/16 CPU threads; PREEMPT)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> debian-kernel-handbook depends on no packages.
>
> Versions of packages debian-kernel-handbook recommends:
> ii firefox [www-browser] 106.0-1
> ii firefox-esr [www-browser] 102.4.0esr-1
> ii konqueror [www-browser] 4:21.12.3-1
> ii qutebrowser [www-browser] 2.5.2-1
> ii w3m [www-browser] 0.5.3+git20220429-1+b1
>
> debian-kernel-handbook suggests no packages.
>
>
> >
Diederik de Haas
Oct 23, 2022, 10:20:05 AM10/23/22
to
Hi Dan!
Thanks so much for your description, it already gives me some ideas how to
improve things wrt the documentation :-)
On Wednesday, 19 October 2022 23:56:23 CEST Dan Coleman wrote:
> use test-patches in debian/bin/test-patches.
From bug 1022025:
On Thursday, 20 October 2022 21:48:20 CEST Diederik de Haas wrote:
> On Thursday, 20 October 2022 19:53:22 CEST Dan Coleman wrote:
> > > Apparently "test-patches" does not build a 'headers-common' package and
> > > therefor installing the headers failed which in turn made DKMS fail.
> >
> > That seems like less-than-ideal behavior for test-patches.
> > Is that a bug that would benefit from being reported?
I (now) do think it is useful to file a (wishlist) bug against src:linux in
which you request improvements to the 'test-patches' script:
1) also creates a headers-common package.
> When I finally managed to get the test kernel compiled, I couldn't install
> it, either via apt or dpkg. I was told that apt would take care of removing
> the dependencies causing the conflict, but it didn't. DKMS wasn't
> triggered, it was a mess.
2) make it easy/easier to install the resulting kernel deb, which does not
involve removing an existing kernel (meta) package.
By setting the 'abiname' 'property' you can achieve that, but I don't know if
that idea has been evaluated before and discarded.
But the kernel maintainers should be able to answer that.
Cheers,
Diederik
Thanks so much for your description, it already gives me some ideas how to
improve things wrt the documentation :-)
On Wednesday, 19 October 2022 23:56:23 CEST Dan Coleman wrote:
> use test-patches in debian/bin/test-patches.
From bug 1022025:
On Thursday, 20 October 2022 21:48:20 CEST Diederik de Haas wrote:
> On Thursday, 20 October 2022 19:53:22 CEST Dan Coleman wrote:
> > > Apparently "test-patches" does not build a 'headers-common' package and
> > > therefor installing the headers failed which in turn made DKMS fail.
> >
> > That seems like less-than-ideal behavior for test-patches.
> > Is that a bug that would benefit from being reported?
I (now) do think it is useful to file a (wishlist) bug against src:linux in
which you request improvements to the 'test-patches' script:
1) also creates a headers-common package.
> When I finally managed to get the test kernel compiled, I couldn't install
> it, either via apt or dpkg. I was told that apt would take care of removing
> the dependencies causing the conflict, but it didn't. DKMS wasn't
> triggered, it was a mess.
involve removing an existing kernel (meta) package.
By setting the 'abiname' 'property' you can achieve that, but I don't know if
that idea has been evaluated before and discarded.
But the kernel maintainers should be able to answer that.
Cheers,
Diederik
Geert Stappers
Feb 8, 2023, 3:40:05 PM2/8/23
to
Hi Debian Kernel Team,
Where is develop happening?
Groeten
Geert Stappers
P.S.
At https://salsa.debian.org/kernel-team/kernel-handbook/-/tags
is tag 1.20 missing.
--
Silence is hard to parse
Where is develop happening?
Groeten
Geert Stappers
P.S.
At https://salsa.debian.org/kernel-team/kernel-handbook/-/tags
is tag 1.20 missing.
--
Silence is hard to parse
Geert Stappers
Apr 22, 2023, 10:30:03 AM4/22/23
to
Hi,
> Where is develop happening?
} Where is development happening?
Seems to be at "salsa".
<screenshot>
stappers@juli:~/src
$ debcheckout debian-kernel-handbook
declared git repository at https://salsa.debian.org/kernel-team/kernel-handbook.git
git clone https://salsa.debian.org/kernel-team/kernel-handbook.git debian-kernel-handbook ...
Cloning into 'debian-kernel-handbook'...
remote: Enumerating objects: 1283, done.
remote: Counting objects: 100% (228/228), done.
remote: Compressing objects: 100% (88/88), done.
remote: Total 1283 (delta 169), reused 181 (delta 134), pack-reused 1055
Receiving objects: 100% (1283/1283), 412.97 KiB | 1.10 MiB/s, done.
Resolving deltas: 100% (836/836), done.
stappers@juli:~/src
$ cd debian-kernel-handbook/
stappers@juli:~/src/debian-kernel-handbook
$ ls
chapter-bugs.dbk chapter-scope.dbk kernel-handbook.dbk
chapter-common-tasks.dbk chapter-source.dbk Makefile
chapter-initramfs.dbk chapter-update-hooks.dbk po4a
chapter-modules.dbk chapter-versions.dbk stylesheet.xsl
chapter-packaging.dbk debian
stappers@juli:~/src/debian-kernel-handbook
$
</screenshot>
The silence in this bug report might be transmitting
Yes, your contribution is welcome.
Regards
Geert Stappers
--
What is the last time
you did something for the first time?
> Where is develop happening?
} Where is development happening?
Seems to be at "salsa".
<screenshot>
stappers@juli:~/src
$ debcheckout debian-kernel-handbook
declared git repository at https://salsa.debian.org/kernel-team/kernel-handbook.git
git clone https://salsa.debian.org/kernel-team/kernel-handbook.git debian-kernel-handbook ...
Cloning into 'debian-kernel-handbook'...
remote: Enumerating objects: 1283, done.
remote: Counting objects: 100% (228/228), done.
remote: Compressing objects: 100% (88/88), done.
remote: Total 1283 (delta 169), reused 181 (delta 134), pack-reused 1055
Receiving objects: 100% (1283/1283), 412.97 KiB | 1.10 MiB/s, done.
Resolving deltas: 100% (836/836), done.
stappers@juli:~/src
$ cd debian-kernel-handbook/
stappers@juli:~/src/debian-kernel-handbook
$ ls
chapter-bugs.dbk chapter-scope.dbk kernel-handbook.dbk
chapter-common-tasks.dbk chapter-source.dbk Makefile
chapter-initramfs.dbk chapter-update-hooks.dbk po4a
chapter-modules.dbk chapter-versions.dbk stylesheet.xsl
chapter-packaging.dbk debian
stappers@juli:~/src/debian-kernel-handbook
$
</screenshot>
The silence in this bug report might be transmitting
Yes, your contribution is welcome.
Regards
Geert Stappers
--
What is the last time
you did something for the first time?
Debian Bug Tracking System
May 8, 2023, 6:00:04 PM5/8/23
to
Your message dated Mon, 08 May 2023 21:49:06 +0000
with message-id <E1pw8jC-...@fasolo.debian.org>
and subject line Bug#1022061: fixed in kernel-handbook 1.0.21
has caused the Debian Bug report #1022061,
regarding debian-kernel-handbook: improve kernel build steps for newbies
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1022061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022061
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
with message-id <E1pw8jC-...@fasolo.debian.org>
and subject line Bug#1022061: fixed in kernel-handbook 1.0.21
has caused the Debian Bug report #1022061,
regarding debian-kernel-handbook: improve kernel build steps for newbies
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1022061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022061
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Debian Bug Tracking System
Jul 1, 2023, 7:11:48 PM7/1/23
to
Your message dated Sat, 01 Jul 2023 23:00:26 +0000
with message-id <E1qFjZq-...@fasolo.debian.org>
and subject line Bug#1035359: fixed in linux 6.3.11-1
has caused the Debian Bug report #1035359,
regarding linux: test-patches script produces uninstallable packages
with message-id <E1qFjZq-...@fasolo.debian.org>
and subject line Bug#1035359: fixed in linux 6.3.11-1
has caused the Debian Bug report #1035359,
regarding linux: test-patches script produces uninstallable packages
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1035359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035359
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
0 new messages