-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MDEV-32686 Debian: include ELF package notes #3692
base: 10.11
Are you sure you want to change the base?
MDEV-32686 Debian: include ELF package notes #3692
Conversation
6fa05a9
to
25a2be2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! I didn't even know that this exists: https://manpages.debian.org/unstable/dh-package-notes/dh_package_notes.1.en.html
I do spot any issues or have concerns, approving.
Providing build information compiled into the executable provides the ability of core file handlers to access information on the distro and source package version. This information can sometime be lost between the source and an upstream bug report. The Debian dh-package-notes includes the makefile included in debian/rules that sets linking flags to the right values. Add a small bit of safety that if the makefile isn't installed build anyway. ref: https://systemd.io/ELF_PACKAGE_METADATA/
25a2be2
to
8a0a22d
Compare
@@ -131,6 +138,7 @@ in | |||
"focal") | |||
replace_uring_with_aio | |||
disable_libfmt | |||
remove_package_notes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why do you remove package notes in focal and bullseye? too old binutils?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, but more directly not a dh-package-notes
package that would use it.
@@ -155,6 +163,10 @@ in | |||
exit 1 | |||
esac | |||
|
|||
if [ ! -f /usr/share/debhelper/dh_package_notes/package-notes.mk ]; then | |||
remove_package_notes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think it's a good idea. This script builds release packages. They should be consistently built the way we want them to and not depend on whatever we forgot to install on a particular new builder. Better let it fail here — we'll see it and fix the builder — instead of us suddenly releasing the package that doesn't has what we want
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok. Sure.
Bootstrap this package build dependency into the CI images before server PR MariaDB/server#3692 is merged so autobake-deb builders contine to work. Can be removed once server commit merged up to main.
Bootstrap this package build dependency into the CI images before server PR MariaDB/server#3692 is merged so autobake-deb builders contine to work. Can be removed once server commit merged up to main. This excludes Debian 11 and Ubuntu focal
This tests the compile using a spec file. This spec file is defined by environment variables. If the spec file doesn't exist (SLES/OpenSUSE), isn't supported (e.g. clang), or has incorrect environment variables the linker flag won't be used.
a4de93f
to
9651d5d
Compare
|
Bootstrap this package build dependency into the CI images before server PR MariaDB/server#3692 is merged so autobake-deb builders contine to work. Can be removed once server commit merged up to main. This excludes Debian 11 and Ubuntu focal
Description
Providing build information compiled into the executable provides the ability of core file
handlers to access information on the distro and source package version. This information
can sometime be lost between the source and an upstream bug report.
The Debian dh-package-notes includes the makefile included in debian/rules that
sets linking flags to the right values.
ref: https://systemd.io/ELF_PACKAGE_METADATA/
Release Notes
Include OS information compiled into executables.
How can this PR be tested?
As buildbot workers don't have the dh-package-notes package installed yet:
Basing the PR against the correct MariaDB version
main
branch.PR quality check