summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Release 2.6.0, the "unhappy bookworm" release2.6.0Julian Andres Klode2023-03-0651-151/+233
|
* Merge branch 'pu/licensing-shenanigans' into 'main'Julian Andres Klode2023-03-0660-28/+398
|\ | | | | | | | | machine-readable version of COPYING See merge request apt-team/apt!287
| * We do not believe rsh was supposed to exclude GPL-3Julian Andres Klode2023-03-062-1/+28
| |
| * COPYING: Address RunScripts()Julian Andres Klode2023-03-061-0/+4
| |
| * Address translation licensing concernsJulian Andres Klode2023-03-0631-1/+105
| |
| * COPYING: Group by licenseJulian Andres Klode2023-03-061-69/+14
| | | | | | | | | | | | | | The concrete copyright holders listed are not really relevant for anything, as they are woefully incomplete anyhow. Grouping by licensing allows us to focus on what matters: Parts that have a different license from the overall project.
| * po/nb.po: Relicensing GPL-2.0 -> GPL-2.0+Julian Andres Klode2023-03-062-2/+4
| | | | | | | | | | Thanks Petter for chasing down the copyright holders and getting consent.
| * Address statements of public domainJulian Andres Klode2023-03-0628-2/+139
| |
| * machine-readable version of COPYINGBastian Germann2023-03-061-17/+169
| | | | | | | | | | | | | | | | The debian/copyright (COPYING) file is missing at least two licenses (Expat, BSD-3-clause) and some copyright statements. A machine-readable version of COPYING is attached that fixes these. Closes: #1019273
| * Update lintian override info format in d/apt.lintian-overridesJulian Andres Klode2023-03-061-7/+6
|/ | | | | | | lintian-brush only fixed the spare-manual-page ones. Fixes: lintian: mismatched-override See-also: https://lintian.debian.org/tags/mismatched-override.html
* Merge branch 'pu/never-sections-matching' into 'main'Julian Andres Klode2023-03-063-5/+5
|\ | | | | | | | | Fix permissions && change section matching in config files to be more gitignore style rightmost match See merge request apt-team/apt!286
| * Use a more gitignore style matchingJulian Andres Klode2023-02-272-4/+4
| | | | | | | | | | | | | | | | Use a rightmost match for / so that if we end up with a Section: a/b/c, a 'c' matcher still matches. If the section does not contain any /, it can be matched using /pattern, e.g. /c only matches Section: c, but not Section: a/b/c.
| * test-apt-get-update-sourceslist-warning: Fix permissionsJulian Andres Klode2023-02-271-1/+1
| | | | | | | | This test did not work with umask 0002
* | Merge branch 'fix/unconditional-trusted' into 'main'Julian Andres Klode2023-03-064-7/+41
|\ \ | | | | | | | | | | | | Do not store trusted=yes Release file unconditionally See merge request apt-team/apt!289
| * | Do not store trusted=yes Release file unconditionallyDavid Kalnischkies2023-03-043-7/+38
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | A source marked with trusted=yes can still fail verification of the Release file, mostly for Date related issues, like being too new or too old, which have other options to force them in. The update code was not using the Release file (which was a InRelease file but failed verification – which was overridden by trusted=yes) as intended, but it marked it for storage, so that this "bad" Release file would end up being moved into lists/, which is bad as the indexes it refers to aren't updated while the next update run assumes that the indexes are in the state the Release file claims them to be in. Fixed simply by making the storage conditional on the usage as intended, which also resolves a second issue: The verification can also detect that a Release file we got is older than what we already have to avoid down- grade attacks. The more likely explanation is a slightly outdated mirror in a rotation/CDN through, so this gets the silent treatment to avoid scaring users by handling it as if we had got the same Release file we already have stored locally, removing the freshly received older file in the process alongside setting some variables. Those variables were already modified in the trusted=yes case though resulting in the stored Release file being removed instead. Not modifying the variables too early resolves this problem as well. Both seem to exist since at least 2015 as traces are visible in 448c38bdcd already, which shuffled lots of code around including the bad ones, but as we are in trusted=yes land, security is of no concern here, this "just" leads to failed pinning, hashsum mismatches and other strange problems in follow-up calls depending on how out of sync the Release file (if its still present) is with the rest of the trusted data. Reported-By: Dima Kogan <dkogan@debian.org> on IRC Tested-By: Dima Kogan <dkogan@debian.org>
| * | Disable retries to speed up failure-propagation testDavid Kalnischkies2023-03-041-0/+3
|/ / | | | | | | Gbp-Dch: Ignore
* | Merge branch 'bookworm/aptchangelog' into 'main'Julian Andres Klode2023-03-032-11/+63
|\ \ | | | | | | | | | | | | Detect trimmed changelogs and pick online instead See merge request apt-team/apt!288
| * | Detect trimmed changelogs and pick online insteadDavid Kalnischkies2023-03-032-11/+63
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We only check the start of these lines to avoid hard coding the exact command and we pick 150 as maximum line length as the longest package name on my system is apparently 75 characters long. We could choose longer or shorter without much issue as over-length just means we mishandle the rest of the line as a new line and it should be really unlikely that a) lines are that long in this file and b) that such long lines contain one of our trigger sequences – but even if, all we do is start a download of an online file. Could be worse. This auto-detection can be avoided by setting Acquire::Changelogs::AlwaysOnline (or Origin specific sub options) to "true" if you always want the changelog from an online source. The reverse – setting it to "false" in the hope it would not get the changelog from an online source – was not and is still not possible. Closes: #1024457
* / Remove incorrectly added unused Debian vendor CMake fileDavid Kalnischkies2023-03-031-2/+0
|/ | | | | | | | | The file is a remnant of the unrelated and closed !145 pull request which tries to generate "apt-vendor.ent" – but that file exists in our sources already while the script that would generate it doesn't. Regression-of: 7e7eb113587230aeb9fe745b2eeac44e634999f5 Gbp-Dch: Ignore
* Merge branch 'pu/lunar' into 'main'Julian Andres Klode2023-02-271-1/+1
|\ | | | | | | | | Update ubuntu-codename to lunar See merge request apt-team/apt!285
| * Update ubuntu-codename to lunarJulian Andres Klode2023-02-271-1/+1
|/
* Merge branch 'feature/non-free-firmware' into 'main'Julian Andres Klode2023-02-2727-543/+677
|\ | | | | | | | | Support transition to new non-free-firmware component See merge request apt-team/apt!282
| * Suggest using non-free-firmware in update for DebianDavid Kalnischkies2023-02-043-50/+193
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In an ideal world everyone would read release notes, but if the last sources.list change is any indication a lot of people wont. This is even more a problem in so far as apt isn't producing errors for invalid repositories, but instead carries on as normal even through it will not be able to install upgrades for the moved packages. This commit implements two scenarios and prints a notice in those cases pointing to the release notes: a) User has 'non-free' but not 'non-free-firmware' b) User has a firmware package which isn't available from anywhere Both only happen if we are talking about a repository which identifies itself as one of Debian and is for a release codenamed bookworm (or sid). Note that as (usually) apt/oldstable is used to upgrade to the new stable release these suggestions only show for users after they have upgraded to bookworm on apt command line usage after that.
| * Bump codenames in docs in preparation for Debian 12David Kalnischkies2023-01-301-7/+7
| |
| * Add non-free-firmware component in documentationDavid Kalnischkies2023-01-3017-450/+380
| | | | | | | | | | | | This changes a lot of lines technically, but its easy enough to unfuzzy the translations as most of the mentions are examples to be copied literally in translations (sadly po4a isn't clever enough for this).
| * Have values in Section config trees refer to them in all componentsDavid Kalnischkies2023-01-305-36/+95
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| * Teach apt-cdrom's scoring system about non-free-firmwareCyril Brulebois2023-01-301-0/+2
| | | | | | | | Closes: #1029751
* | Czech program translation updateMiroslav Kure2023-02-101-108/+66
| | | | | | | | Closes: #1031008
* | Release 2.5.62.5.6Julian Andres Klode2023-02-0815-71/+126
| |
* | Merge branch 'fix/gccwarnings' into 'main'Julian Andres Klode2023-02-078-40/+44
|\ \ | |/ |/| | | | | Build with and fix warnings of gcc-13 See merge request apt-team/apt!280
| * Ignore return of .c_str() in preemptive call for signal handlerDavid Kalnischkies2023-01-293-3/+3
| | | | | | | | | | Reported-By: gcc-13 -Wunused-result Gbp-Dch: Ignore
| * Unhide virtual overloads in some cachefiltersDavid Kalnischkies2023-01-291-0/+2
| | | | | | | | | | | | | | | | | | The matchers are usually called via its base class, but if we would call them via the derivate class we would not be able to call the not explicitly "imported" overloads, which would be strange. Reported-By: gcc-13 -Woverloaded-virtual Gbp-Dch: Ignore
| * Drop redundant 'virtual' on function marked 'override'David Kalnischkies2023-01-291-32/+32
| | | | | | | | | | Reported-By: clang-tidy [cppcoreguidelines-explicit-virtual-functions] Gbp-Dch: Ignore
| * Include cstdint for uint16_t in our mmap wrappingDavid Kalnischkies2023-01-291-0/+1
| | | | | | | | | | | | | | In gcc-13 internal includes were reduced exposing our laziness. Reported-By: gcc-13 Gbp-Dch: Ignore
| * Avoid comparison of integers of different signedness for ETADavid Kalnischkies2023-01-291-1/+2
| | | | | | | | | | Reported-By: gcc -Wsign-compare Gbp-Dch: Ignore
| * Avoid triggering unused parameter warning in staticSIGWINCHDavid Kalnischkies2023-01-291-1/+1
| | | | | | | | | | Reported-By: gcc -Wunused-parameter Gbp-Dch: Ignore
| * Drop unneeded usage of deprecated std::binary_functionDavid Kalnischkies2023-01-291-3/+3
|/ | | | | | | | The code isn't using any of the member types this template provides, so we can just drop it from the code without any practical effect. Reported-By: gcc -Wdeprecated-declarations Gbp-Dch: Ignore
* German program translation updateHelge Kreutzmann2023-01-291-5/+4
| | | | Closes: #1029280
* Merge branch 'allow-insecure-repositories' into 'main'Julian Andres Klode2023-01-251-5/+5
|\ | | | | | | | | Document --allow-insecure-repositories See merge request apt-team/apt!277
| * Document --allow-insecure-repositoriesMichaIng2023-01-251-5/+5
|/ | | | | since --no-allow-insecure-repositories is the default. Signed-off-by: MichaIng <micha@dietpi.com>
* Release 2.5.52.5.5Julian Andres Klode2023-01-1758-207/+552
|
* Merge branch 'pu/installed-matches-version' into 'main'Julian Andres Klode2023-01-133-5/+15
|\ | | | | | | | | make ?installed pattern match installed version only when narrowed See merge request apt-team/apt!275
| * apt-patterns(7): Grouping with () and or using | are supportedJulian Andres Klode2023-01-131-4/+0
| | | | | | | | They have been since 1.9.9, lol
| * make ?installed pattern match installed version only when narrowedJulian Andres Klode2023-01-133-1/+15
|/ | | | | | | | This is the correct behavior, but it was overlooked when aptitude patterns where ported. I remember wondering about this, but I checked the aptitude code and saw a check that CurrentVer != 0 or something and then apparently did not notice another implementation for version matching.
* Merge branch 'fix/doc-ftparchive-path-repeats' into 'main'Julian Andres Klode2023-01-053-9/+10
|\ | | | | | | | | Do not document path to be repeatable in apt-ftparchive cmds See merge request apt-team/apt!267
| * Do not document path to be repeatable in apt-ftparchive cmdsDavid Kalnischkies2022-11-022-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
| * Set our entities as dependencies in manpage generationDavid Kalnischkies2022-11-021-7/+8
| | | | | | | | | | | | | | | | | | Changes in the entities do not lead to a rebuild of the manpages otherwise. We also try to have each lingua have its own (translated) entities as dependencies rather than all as the old code order would have suggested. Gbp-Dch: Ignore
* | Merge branch 'never-markauto-tasks' into 'main'Julian Andres Klode2022-12-301-0/+3
|\ \ | | | | | | | | | | | | Add 'tasks' section to default APT::Never-MarkAuto-Sections list See merge request apt-team/apt!273
| * | Add 'tasks' section to default APT::Never-MarkAuto-Sections listАлексей Шилин2022-12-301-0/+3
|/ / | | | | | | | | | | 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.
* | Dutch manpages translation updateFrans Spiesschaert2022-12-281-8/+8
| | | | | | | | Closes: #1023456, #1025843
generated by cgit v1.2.3-70-g09d2 (git 2.46.0) at 2026-05-12 16:52:44 +0000