Your message dated Sun, 10 May 2015 17:17:40 +0200
with message-id <[email protected]>
and subject line done
has caused the Debian Bug report #767752,
regarding kernel-package: '--rootcmd sudo' does not produce workable results
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 [email protected]
immediately.)
--
767752: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767752
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Package: kernel-package
Version: 13.014
Severity: minor
Dear Maintainer,
I looked at the manpage of make-kpkg, and it said, it was not recommended to
build as
root.
> Typically, make-kpkg should be run under fakeroot,
>
>
> make-kpkg --rootcmd fakeroot kernel_image
>
> but instead you run this command as root (this is not recommended), or under
> fakeroot,
> or tell make-kpkg how to become root (not recommended either, fakeroot is
> perhaps the
> safest option), like so:
>
>
> make-kpkg --rootcmd sudo kernel_image
>
> The Debian package file is created in the parent directory of the kernel
> source
> directory where this command is run.
So I tried the '--rootcmd sudo' option and found, that the results are not
workable.
Kernels build and install fine, but booting them fails very early in the
process.
It is probably the case, that using sudo is not significantly more secure than
doing this
as root, so I will have to learn about fakeroot, as it seems. I tried this both
on
testing and on stable, the latter with the latest default 3.2-kernel-source.
So this possibility probably has to be removed from the manpage.
- -- System Information:
Debian Release: jessie/sid
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.3edt (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages kernel-package depends on:
ii bc 1.06.95-9
ii binutils 2.24.90.20141023-1
ii build-essential 11.7
ii bzip2 1.0.6-7
ii dpkg-dev 1.17.13
ii file 1:5.20-1
ii gettext 0.19.2-3
ii kmod 18-3
ii po-debconf 1.0.16+nmu3
ii xmlto 0.0.25-2
ii xz-utils [lzma] 5.1.1alpha+20120614-2
Versions of packages kernel-package recommends:
ii cpio 2.11+dfsg-2
ii docbook-utils 0.6.14-3
ii kernel-common 13.014
pn uboot-mkimage <none>
Versions of packages kernel-package suggests:
pn libncurses-dev <none>
ii linux-source 3.16+62
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAlRWJ84ACgkQ5+rBHyUt5wuXlACcCW0gLGV5VFxXSupQ+p0BIBHY
ahQAoIZV27glgkAZyCNNWFo6fSBPzYup
=xGox
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I was searching online (yes, right not that G-word, no B- there either) because
I found
building i386-kernels on AMD64 is not trivial, it is not sufficient to uncheck
'[ ] 64-bit
kernel' in the configuration.
I found this:
https://stackoverflow.com/questions/16051224/cross-build-i386-linux-kernel-on-amd64-host
, which is in turn pointing there:
https://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-building
They say, make-kpkg is actually deprecated, one shuld use ' $ make deb-pkg'
instead.
While there may be a solution for the initrd:
https://kernel-handbook.alioth.debian.org/ch-initramfs.html
The kernel-handbook does not mention how to build the kernel-headers-package,
so I guess
this is still made with make-kpkg. Some more reading required possibly.
No need to keep this open though.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAlVPdpQACgkQ5+rBHyUt5wsnCgCffEByfWdkiTxFZPpsflNtTCH2
WzUAn3c6YdBgNUfKVUI8d5zb2tbxF74V
=EwQG
-----END PGP SIGNATURE-----
--- End Message ---
