| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
This unbreaks mmdebstrap scenarios if you mirror Debian or use
a distro where apt did not get overridden to required.
Reported-By: josch on IRC, following discovery by helmut
Gbp-Dch: full
|
| |
|
|
| |
This reverts commit 668451def296afeb0c358a7d80ff39dc546defab.
|
| |
|
|
| |
Translation template reordering carnage :D
|
| | |
|
| | |
|
| |
|
|
| |
Closes: #1051642
|
| | |
|
| |
|
|
|
|
|
| |
While we are at it fix the mislabeling as (5) in some places and
unfuzzy the translations.
Reported-By: Enrico Zini on IRC
|
| | |
|
| |
|
|
|
| |
Initialize using gcrypt's GCRYCTL_NO_FIPS_MODE, available since
gcrypt version 1.10.0, otherwise apt aborts on FIPS enabled systems.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
lintian-brush only fixed the spare-manual-page ones.
Fixes: lintian: mismatched-override
See-also: https://lintian.debian.org/tags/mismatched-override.html
|
| |\
| |
| |
| |
| | |
Support transition to new non-free-firmware component
See merge request apt-team/apt!282
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Hard coding each and every component is not only boring but given that
everyone is free to add or use more we end up in situations in which apt
behaves differently for the same binary package just because metadata
said it is in different components (e.g. non-free vs. non-free-firmware).
It is also probably not what the casual user would expect.
So we instead treat a value without a component as if it applies for all
of them. The previous behaviour can be restored by prefixing the value
with "<undefined>/" as in the component is not defined.
In an ideal world we would probably use "*/foo" for the new default
instead of changing the behaviour for "foo", but it seems rather
unlikely that the old behaviour is actually desired. All existing values
were duplicated for all (previously) known components in Debian and
Ubuntu.
|
| |/ |
|
| | |
|
| |\
| |
| |
| |
| | |
Do not document path to be repeatable in apt-ftparchive cmds
See merge request apt-team/apt!267
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The manpage for apt-ftparchive {packages,sources} claims that the
path argument can be repeated, but that logically conflicts with having
two optional arguments after that and isn't implemented in code either,
so we just adapt the documentation to reality here.
So, since when is this documentation wrong? The manpage is currently
written in xml (since 2004), but the sgml before that had the same
mistake included all the way back to a time in which time itself is not
stable (the commit is dated in git 2004, but the commit message
says 2001 while including a d/changelog stanza dated 2000) in
my favorite commit "Join with aliencode" which brought in a whole lot
of stuff adding also (quoting said d/changelog entry) "apt-ftparchive
the all dancing all singing FTP archive maintenance program".
In other words: It was documented this way for more than 22 years.
Reported-By: Michael Tokarev on IRC
|
| |/
|
|
|
|
| |
Task packages need to be handled just like metapackages so that users
don't accidentally autoremove half of their system after removing one
of task's dependencies.
|
| | |
|
| |\
| |
| |
| |
| | |
since base-passwd 3.6.1 the _apt user is in the default /etc/passwd, so we can...
See merge request apt-team/apt!260
|
| | |
| |
| |
| |
| |
| |
| | |
- so do not call adduser if the _apt user already exists
- make adduser dependency optional if base-passwd >= 3.6.1
- do not call adduser if $DPKG_ROOT is non-empty as adduser doesn't
support working on a custom root directory
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
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
|