| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
| |
The rest of our documentation files is in apt-docs, but this one is
general and small enough to be in the default install so users have an
easier time finding information like how to reach us and some debug
advice.
|
| |
|
|
|
|
|
|
| |
Our public interface doesn't use zlib for quite a while now so lets drop
the last remnants as hopefully nobody depends on us bringing it in…
Unlike our own private lib for transitive provision of unistd.h.
References: 680b916ce7203a40ebd0a3882b9a71ca77278a67
|
| |
|
|
|
|
| |
Building the library just so we can build the helpers against it is not
only wasteful but as we are supposed to test the system we can use that
as an additional simple smoke test before the real testing starts.
|
| |
|
|
|
|
|
|
|
| |
autopkgtest says:
Tests may not modify the source tree (and may not have write access to it).
We don't really modify the source of course, but we created our build/
directory in the tree, which seems to work just fine (for now), but lets
be nice.
|
| |
|
|
|
|
| |
Reorganising the control file allows this simple test to run first and
be marked as superficial which makes no practical difference, but is
more correct.
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
References: https://wiki.debian.org/BuildProfileSpec#Registered_profile_names
Closes: #1009797
[@donkult: reworded commit message slightly & changed variable name]
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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]
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
This reverts commit 4f89d3629b22255963da3705e4222c71045da58a.
The bugscript uses yesno which is documented to require bash in
/usr/share/doc/reportbug/README.developers.gz.
Closes: #1007121
|
| | |
|
| |
|
|
|
|
|
| |
Without documentation these options will see much less use.
Fixes: commit 1d9e29c9e2a5591b42a99a721b901fc003ed9149
Suggested-by: kibi on #debian-devel
|
| | |
|
| |
|
|
|
| |
With apt-key going away, people need to manage key files, rather
than keys, so they need to know if any keys are in the legacy keyring.
|
| |\
| |
| |
| |
| | |
bugscript: switch to POSIX shell, quoting, other improvements
See merge request apt-team/apt!225
|
| | |
| |
| |
| |
| |
| | |
This means Debian is one step closer to removing bash from essential.
See-also: https://salsa.debian.org/debian/grow-your-ideas/-/issues/20#note_296809
|
| | |
| |
| |
| |
| |
| | |
Otherwise slashes in filenames could be interpreted as newlines etc.
Also makes it portable to shells that don't support `echo -e`.
|
| | |
| |
| |
| |
| |
| |
| | |
The file names could contain spaces and without quoting, the
files would not be found and included in the bug reports.
Suggested-by: shellcheck
|
| | |
| |
| |
| |
| | |
Otherwise the options won't be applied when running the script
directly from a sh command instead of via the shebang.
|
| | |
| |
| |
| |
| |
| | |
See-also: https://bugs.debian.org/169495
Fixed-in: reportbug 2.10
Fixed-on: 2002-12-23
|
| |/
|
|
|
|
|
| |
This directory is intended to provide an alternative to
/usr/share/keyrings for placing keys used with signed-by.
Gbp-Dch: full
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
`which` has been deprecated in debianutils 5.0+. The recommended
replacement, `command -v`, is mandated by Debian policy these days, in
addition to being required by POSIX and its predecessor specs at least
since 1994.
Not found commands cause no output from `command -v` per POSIX, so
remove the redundant 2>&1's while at it.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
If the system tells us that a core dump was created we should try to
display the contained info as that system might not be easily available
when we see the error (like C-I or autopkgtest).
Gbp-Dch: Ignore
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
We use a Breaks for the binary package instead of adding
a versioned depends, as Breaks will cause apt solver to upgrade dpkg,
while depends would make apt try to remove apt as first choice.
|
| | |
|
| | |
|
| | |
|
