Your message dated Thu, 19 Jan 2023 14:12:50 +0100
with message-id <2632028.CedTxiVJjX@prancing-pony>
and subject line Re: linux-headers: dpkg-buildpackage -us -uc crashes while
trying to create rt packages
has caused the Debian Bug report #1029159,
regarding linux-headers: dpkg-buildpackage -us -uc crashes while trying to
create rt 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 [email protected]
immediately.)
--
1029159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029159
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: linux-headers-6.2.0-rc4
Version: 6.2.0-rc4-2
Severity: important
File: linux-headers
X-Debbugs-Cc: [email protected]
Dear Maintainer,
I am trying to dpkg-buildpackage -us -uc linux-6.2-rc4.tar.gz
Because I strongly want to learn how to contribute.
problems begin on patches
* Patch debian/dfsg/vs6624-disable.patch does not apply (enforce with -f)
* Patch debian/dfsg/video-remove-nvidiafb-and-rivafb.patch does not apply
(enforce with -f)
* Patch debian/dfsg/video-remove-nvidiafb-and-rivafb.patch does not apply
(enforce with -f)
* Patch debian/ia64-hardcode-arch-script-output.patch does not apply (enforce
with -f)
* Patch debian/tools-perf-perf-read-vdso-in-libexec.patch does not apply
(enforce with -f)
* Patch debian/documentation-drop-sphinx-version-check.patch does not apply
(enforce with -f)
* Patch debian/perf-traceevent-support-asciidoctor-for-documentatio.patch
does not apply (enforce with -f)
* Patch debian/kbuild-look-for-module.lds-under-arch-directory-too.patch does
not apply (enforce with -f)
* Patch
bugfix/all/radeon-amdgpu-firmware-is-required-for-drm-and-kms-on-r600-onward.patch
does not apply (enforce with -f)
* Patch debian/firmware_class-refer-to-debian-wiki-firmware-page.patch does
not apply (enforce with -f)
* Patch
features/x86/intel-iommu-add-kconfig-option-to-exclude-igpu-by-default.patch
does not apply (enforce with -f)
* Patch debian/btrfs-warn-about-raid5-6-being-experimental-at-mount.patch
does not apply (enforce with -f)
* Patch
features/arm64/dt-bindings-rockchip-Add-Hardkernel-ODROID-M1-board.patch does
not apply (enforce with -f)
* Patch
features/arm64/arm64-dts-rockchip-Add-Hardkernel-ODROID-M1-board.patch does not
apply (enforce with -f)
* Patch features/arm64/arm64-dts-rockchip-Add-NOR-flash-to-ODROID-M1.patch
does not apply (enforce with -f)
* Patch
features/arm64/arm64-dts-rockchip-Enable-vop2-and-hdmi-tx-on-ODROID.patch does
not apply (enforce with -f)
* Patch
features/arm64/arm64-dts-rockchip-Enable-HDMI-audio-on-ODROID-M1.patch can be
reverse-applied
* Patch features/arm64/arm64-dts-rockchip-Enable-the-GPU-on-ODROID-M1.patch
can be reverse-applied
* Patch
features/arm64/arm64-dts-rockchip-Enable-the-USB-2.0-ports-on-ODROI.patch does
not apply (enforce with -f)
* Patch
features/arm64/arm64-dts-rockchip-Enable-the-USB-3.0-ports-on-ODROI.patch does
not apply (enforce with -f)
* Patch
features/arm64/arm64-dts-rockchip-Add-PCIEe-v3-nodes-to-ODROID-M1.patch can be
reverse-applied
* Patch
features/arm64/arm64-dts-rockchip-Add-IR-receiver-node-to-ODROID-M1.patch can
be reverse-applied
* Patch features/x86/x86-make-x32-syscall-support-conditional.patch does not
apply (enforce with -f)
* Patch
features/arm64/quartz64/arm64-dts-rockchip-Enable-GPU-on-SOQuartz-CM4.patch
does not apply (enforce with -f)
* Patch
features/arm64/quartz64/arm64-dts-rockchip-Enable-video-output-and-HDMI-on-S.patch
does not apply (enforce with -f)
* Patch
features/arm64/quartz64/arm64-dts-rockchip-Enable-HDMI-sound-on-SOQuartz.patch
can be reverse-applied
* Patch
features/arm64/quartz64/arm64-dts-rockchip-Enable-PCIe-2-on-SOQuartz-CM4IO.patch
can be reverse-applied
* Patch
features/arm64/quartz64/dt-bindings-arm-rockchip-Add-SOQuartz-Blade.patch does
not apply (enforce with -f)
* Patch
features/arm64/quartz64/arm64-dts-rockchip-Add-SOQuartz-blade-board.patch does
not apply (enforce with -f)
* Patch
features/arm64/quartz64/dt-bindings-arm-rockchip-Add-SOQuartz-Model-A.patch can
be reverse-applied
* Patch
features/arm64/quartz64/arm64-dts-rockchip-Add-SOQuartz-Model-A-baseboard.patch
does not apply (enforce with -f)
* Patch 0001-spi-Remove-the-obsolte-u64_stats_fetch_-_irq-users.patch can be
reverse-applied
* Patch 0002-net-Remove-the-obsolte-u64_stats_fetch_-_irq-users-d.patch can
be reverse-applied
* Patch printk-Bring-back-the-RT-bits.patch does not apply (enforce with -f)
* Patch 0016-printk-add-infrastucture-for-atomic-consoles.patch does not
apply (enforce with -f)
* Patch 0018-printk-avoid-preempt_disable-for-PREEMPT_RT.patch does not apply
(enforce with -f)
* Patch x86__Support_for_lazy_preemption.patch does not apply (enforce with
-f)
* Patch ARM__Allow_to_enable_RT.patch does not apply (enforce with -f)
* Patch
powerpc_stackprotector__work_around_stack-guard_init_from_atomic.patch does not
apply (enforce with -f)
* Patch POWERPC__Allow_to_enable_RT.patch does not apply (enforce with -f)
then comes the asciidoctor crash
* asciidoctor 2.0.18 now has unsafe as default and no -f option
asciidoctor --help
Usage: asciidoctor [OPTION]... FILE...
Convert the AsciiDoc input FILE(s) to the backend output format (e.g., HTML 5,
DocBook 5, etc.)
Unless specified otherwise, the output is written to a file whose name is
derived from the input file.
Application log messages are printed to STDERR.
Example: asciidoctor input.adoc
-b, --backend BACKEND set backend output format: [html5, xhtml5,
docbook5, manpage] (default: html5)
additional backends are supported via
extended converters (e.g., pdf, epub3)
-d, --doctype DOCTYPE document type to use when converting
document: [article, book, manpage, inline] (default: article)
-e, --embedded suppress enclosing document structure and
output an embedded document (default: false)
-o, --out-file FILE output file (default: based on path of
input file); use - to output to STDOUT
--safe set safe mode level to safe (default:
unsafe)
enables include directives, but prevents
access to ancestor paths of source file
provided for compatibility with the
asciidoc command
-S, --safe-mode SAFE_MODE set safe mode level explicitly: [unsafe,
safe, server, secure] (default: unsafe)
disables potentially dangerous macros in
source files, such as include::[]
-s, --no-header-footer suppress enclosing document structure and
output an embedded document (default: false)
-n, --section-numbers auto-number section titles in the HTML
backend; disabled by default
--eruby ERUBY specify eRuby implementation to use when
rendering custom ERB templates: [erb, erubi, erubis] (default: erb)
-a, --attribute name[=value] a document attribute to set in the form of
name, name!, or name=value pair
this attribute takes precedence over the
same attribute defined in the source document
unless either the name or value ends in @
(i.e., name@=value or name=value@)
-T, --template-dir DIR a directory containing custom converter
templates that override the built-in converter (requires tilt gem)
may be specified multiple times
-E, --template-engine NAME template engine to use for the custom
converter templates (loads gem on demand)
-B, --base-dir DIR base directory containing the document and
resources (default: directory of source file)
-R, --source-dir DIR source root directory (used for
calculating path in destination directory)
-D, --destination-dir DIR destination output directory (default:
directory of source file)
-I, --load-path DIRECTORY add a directory to the $LOAD_PATH
may be specified more than once
-r, --require LIBRARY require the specified library before
executing the processor (using require)
may be specified more than once
--failure-level LEVEL set minimum log level that yields a
non-zero exit code: [INFO, WARN, ERROR, FATAL] (default: FATAL)
-q, --quiet silence application log messages and
script warnings (default: false)
--trace include backtrace information when
reporting errors (default: false)
-v, --verbose directs application messages logged at
DEBUG or INFO level to STDERR (default: false)
-w, --warnings turn on script warnings (default: false)
-t, --timings print timings report (default: false)
-h, --help [TOPIC] print a help message
show this usage if TOPIC is not specified
or recognized
show an overview of the AsciiDoc syntax if
TOPIC is syntax
dump the Asciidoctor man page (in
troff/groff format) if TOPIC is manpage
-V, --version display the version and runtime
environment (or -v if no other flags or arguments)
then after the linux-headers-6.2.0-0-common-rt_6.2~rc4-1_all.deb generation
make crashes
(nice make -j`nproc` bindeb-pkg works just fine but it doesn't generate the rt
packages
nor includes the source)
I tried patching around but got nothing (apart from the risk of exploding or
starting ww3 by mistake :D )
I am starting to wander if there is some kind of linux/debian archive for the
6.2 kernel series
Can I get a hint here ?
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.2.0-rc4 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
-- no debconf information
--- End Message ---
--- Begin Message ---
On Wed, 18 Jan 2023 17:41:33 +0100 xevilstar <[email protected]> wrote:
> Package: linux-headers-6.2.0-rc4
> Version: 6.2.0-rc4-2
>
> I am trying to dpkg-buildpackage -us -uc linux-6.2-rc4.tar.gz
> Because I strongly want to learn how to contribute.
It's great that you want to learn how to contribute, but please don't abuse
the Debian BTS for that. Only use that to report actual issues in actual
existing packages/versions.
There are various resources that will help you get started, f.e. on
wiki.debian.org and there's also #debian-mentors on IRC where you can ask
questions related to Debian packaging. But the available resources should
already teach you how you can start making contributions and also when it's
appropriate to submit a RFS bug and how to do it.
As for learning how to build a Debian kernel, please read the debian-kernel-
handbook which explains many things on how the Debian kernel gets build.
As for (potential) issues wrt rt packages, you may want to take a look at:
https://salsa.debian.org/kernel-team/linux/-/merge_requests/629
Where the commits should tell you how to deal with that.
Good luck!
signature.asc
Description: This is a digitally signed message part.
--- End Message ---