who write?

Asked by miufullzero

who write this infomation when I build kernel

/home/ubuntu/dev/jammy# fakeroot debian/rules printenv
dh_testdir
src package name = linux
series = jammy
release = 5.15.0
revisions = 0.0 9.9 10.10 11.11 12.12 13.13 14.14 15.15 16.16 17.17 18.18 19.19 20.20 21.21 22.22 23.23 24.24 25.25 26.27 27.28 30.31 33.34 34.35 35.36 37.39 39.42 40.43 41.44 43.46 45.48 46.49 47.51 48.54 49.55 50.56 52.58 53.59 56.62 57.63 58.64 59.65 60.66 65.72 66.73 67.74 68.75 69.76 70.77 71.78 72.79 74.81 75.82 76.83 79.86 81.90 83.92 85.95 86.96 88.98 90.100 91.101 93.103 94.104 100.110 102.112 103.113 105.115 106.116 111.121
revision = 111.121
uploadnum = 121
prev_revisions = 0.0 0.0 9.9 10.10 11.11 12.12 13.13 14.14 15.15 16.16 17.17 18.18 19.19 20.20 21.21 22.22 23.23 24.24 25.25 26.27 27.28 30.31 33.34 34.35 35.36 37.39 39.42 40.43 41.44 43.46 45.48 46.49 47.51 48.54 49.55 50.56 52.58 53.59 56.62 57.63 58.64 59.65 60.66 65.72 66.73 67.74 68.75 69.76 70.77 71.78 72.79 74.81 75.82 76.83 79.86 81.90 83.92 85.95 86.96 88.98 90.100 91.101 93.103 94.104 100.110 102.112 103.113 105.115 106.116
prev_revision = 106.116
abinum = 111
upstream_tag = v5.15
gitver =
variants = --
flavours = generic
skipabi =
skipmodule =
skipdbg = true
ubuntu_log_opts =
CONCURRENCY_LEVEL = 12
ubuntu_selftests = breakpoints cpu-hotplug efivarfs memfd memory-hotplug mount net ptrace seccomp timers powerpc user ftrace
bin package name = linux-image-5.15.0-111
hdr package name = linux-headers-5.15.0-111
doc package name = linux-doc
do_doc_package = true
do_doc_package_content = false
do_source_package = true
do_source_package_content = false
do_libc_dev_package = true
do_flavour_image_package = true
do_flavour_header_package = true
do_common_headers_indep = true
do_full_source = false
do_odm_drivers = true
do_tools = true
do_any_tools = true
do_linux_tools = true
 do_tools_cpupower = true
 do_tools_perf = true
 do_tools_bpftool = true
 do_tools_x86 = true
 do_tools_host = true
do_cloud_tools = true
 do_tools_hyperv = true
any_signed = true
 uefi_signed = true
 opal_signed = true
 sipl_signed = true
full_build = false
libc_dev_version =
DEB_HOST_GNU_TYPE = x86_64-linux-gnu
DEB_BUILD_GNU_TYPE = x86_64-linux-gnu
DEB_HOST_ARCH = amd64
DEB_BUILD_ARCH = amd64
arch = amd64
kmake = make ARCH=x86 CROSS_COMPILE= KERNELVERSION=5.15.0-111- CONFIG_DEBUG_SECTION_MISMATCH=y KBUILD_BUILD_VERSION=121 LOCALVERSION= localver-extra= CFLAGS_MODULE=-DPKG_ABI=111 PYTHON=/usr/bin/python3

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu linux Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
miufullzero (mfz0721) said :
#1

how can I rewrite those varibles? which file can be modify?

Revision history for this message
Manfred Hampl (m-hampl) said :
#2

If you want to build your own *.deb package, you better use the debuild command (which in turn will run "fakeroot debian/rules" after a number of preparatory steps)

Please see the manpages for debuild, dpkg-buildpackage etc.

Revision history for this message
miufullzero (mfz0721) said :
#3

where is manpages for debuild?

Revision history for this message
Manfred Hampl (m-hampl) said :
#4

^The manpages for debuild are in the devscripts package (that is the package that provides debuild). How did you install debuild?

Can you help with this problem?

Provide an answer of your own, or ask miufullzero for more information if necessary.

To post a message you must log in.