apt/debian/rules, branch mainDebians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=main2026-03-02T21:53:49ZCopyright changes2026-03-02T21:53:49ZJulian Andres Klodejak@debian.org2026-03-02T21:53:49Zurn:sha1:140e4e2f84813c85d96488031e6d3e0359f7b6d5sqv: Warn about signatures that will be rejected by policy within a year2025-04-25T21:07:07ZJulian Andres Klodejulian.klode@canonical.com2025-04-25T18:53:45Zurn:sha1:85c435f23718e168345ea60270b24a57061b54f4
This implements a simple check where we first run `sqv` with
`--policy-as-of` 1 year in the future. If the file is validly
signed one year in the future, it is validly signed now.
If the file is not validly signed 1 year in the future, we check
if it is validly signed now, and otherwise print an error message.
The --policy-as-of feature was added in sqv 1.3.0, hence we add a
version requirement to the dependency.
debian: Plug sqv into the package build2024-12-22T22:52:05ZJulian Andres Klodejulian.klode@canonical.com2024-12-20T11:03:26Zurn:sha1:f5a24acea31248f98db51d7a2fd1d7b2198bb177
Our goal is for each platform to have one blessed OpenPGP verification
system: Platforms that support sqv get sqv, platforms that don't get
gpgv. To do so we hardcode the architecture list at build time.
At build time we check if /usr/bin/sqv exists, which is the condition
that apt uses to see if it should build with sqv support.
We use a slight hack here to build with sqv on the official Debian
buildds but use gpgv on Ubuntu by abusing the fact that Ubuntu
resolves alternative build dependencies, and gpgv is installed
in the buildd image.
Build examples for arch:any packages again after nodoc branch2022-05-11T15:45:49ZDavid Kalnischkiesdavid@kalnischkies.de2022-05-11T15:45:49Zurn:sha1:09f0342ff2a56f8ce8fb9a96648d370f9e21dd01
Who does arch:any builds, right?
Ignoring for changelog as this would just confuse readers as the
effected version was never released.
Regression-of: cd92098caa64b7fd30cdc6b5d56bf7e9e17a449e
Gbp-Dch: Ignore
Add pkg.apt.nodoxygen build profile2022-05-07T08:45:44ZDavid Kalnischkiesdavid@kalnischkies.de2022-04-20T11:18:20Zurn:sha1:c5b22c3dabd0cc8d0ce87576cded2594c2cd7ca1
The documentation generated by doxygen is currently not reproducible,
but as fixing this seems hard we can at least provide a way to check
more automatically if the rest of src:apt is reproducible or not.
Avoid building all docs in nodoc build profile2022-05-07T08:45:44ZDavid Kalnischkiesdavid@kalnischkies.de2022-04-19T11:06:44Zurn:sha1:cd92098caa64b7fd30cdc6b5d56bf7e9e17a449e
Differentiating between different types of documentation we build helps
in better expressing what needs to be done for our arch:any and arch:all
packages currently as well.
Add support for "nodoc" build profile2022-05-07T08:45:44ZVagrant Cascadianvagrant@reproducible-builds.org2022-04-17T22:11:12Zurn:sha1:725fef5ebf45d03fea75866e9795717bf576d26a
References: https://wiki.debian.org/BuildProfileSpec#Registered_profile_names
Closes: #1009797
[@donkult: reworded commit message slightly & changed variable name]
Pass -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON via dh_auto_configure override2022-05-07T08:45:43ZVagrant Cascadianvagrant@reproducible-builds.org2022-04-17T23:12:47Zurn:sha1:e6cefc7683de4f29be7ebcab004ea0ab80ce49bc
CMake by default sets the RPATH property on executables that link to
shared libraries in the same project with an absolute path, which
triggers BuildId differences.
References: https://tests.reproducible-builds.org/debian/issues/unstable/cmake_rpath_contains_build_path_issue.html
https://gitlab.kitware.com/cmake/cmake/-/issues/18413
Closes: #1009796
[@donkult: reworded commit message slightly and have flag passed first]
Only protect two kernels, not last installed one2022-04-07T11:19:52ZJulian Andres Klodejulian.klode@canonical.com2022-04-06T11:51:08Zurn:sha1:824651ded0bcf8603e9b508860b8fe5a68fc53ff
The kernel autoremoval algorithm was written to accomodate
for Ubuntu's boot partition sizing, which was written to
accomodate 3 kernels - 2 installed ones + a new one being
unpacked.
It seems that when the algorithm was designed, it was overlooked
that it actually kept 3 kernels.
LP: #1968154
Fix debian-rules-uses-deprecated-systemd-override2020-01-16T11:11:35ZJulian Andres Klodejulian.klode@canonical.com2020-01-16T11:10:36Zurn:sha1:11cd71b567639a37b46f5c61f4b790e51aa0a0c4
We accidentally managed to restart apt-daily{,-upgrade}.service
again because our dh_systemd_start override was being ignored
since we switched to debhelper 12. Override dh_installsystemd
instead.
Gbp-Dch: full