summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Release 2.7.112.7.11Julian Andres Klode2024-02-1359-60/+577
|
* Merge branch 'phasing-api' into 'main'Julian Andres Klode2024-02-1317-122/+227
|\ | | | | | | | | Add public phased update API and separate message list See merge request apt-team/apt!327
| * Show a separate list of upgrades deferred due to phasingJulian Andres Klode2024-02-136-12/+68
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This introduces a new line: The following upgrades have been deferred due to phasing This is any kept back package that is also phasing. This may not be 100% accurate as we have kept it back due to other reasons in an install command, for example, but we don't track for which packages we applied phasing in reality. If additional packages are kept back that are not phasing, show a a notice "N: Some packages may have been kept back due to phasing." LP: #1988819
| * Add the ?security patternJulian Andres Klode2024-02-134-0/+18
| |
| * Add a new ?phasing patternJulian Andres Klode2024-02-134-0/+20
| | | | | | | | | | This selects all packages that are being kept back due to phasing on your system.
| * Add public phased update APIJulian Andres Klode2024-02-138-110/+121
|/ | | | | | | | | | | | | | | | This moves the functions of the PhasedUpgrader class into various other classes so they can be publicly exposed. This introduces three new functions: pkgDepCache::PhasingApplied() tells you whether phasing should be applied to the package. pkgProblemResolver::KeepPhasedUpdates() keeps back updates that have phasing applied. pkgCache::VerIterator::IsSecurityUpdate() determines whether this version contains security fixes.
* For phasing, check if current version is a security update, not just ↵Julian Andres Klode2024-02-132-34/+60
| | | | | | | | | previous ones We only considered an update a security update if a previous update is a security update but not the update in question itself. LP: #2051181
* Support -a for setting host architecture in apt-get source -bDavid Kalnischkies2024-01-191-0/+1
| | | | | | | | | | It is documented and the code supports it, but the command line parsing actually refuses -a/--host-architecture=arch … probably a sign how much "apt-get source -b" is (not) used in practice. Setting via -o APT::Get::Host-Architecture=arch (which -a is just a shorthand for) works as it did before and can be used if backward compatibility is important.
* Remove erroneous -a flag from apt-get synopsis in manpageDavid Kalnischkies2024-01-191-1/+1
| | | | | | | | | | | | | | The -a flag exists for apt-cache (--all-versions) and -a=arch is actually an (also documented) option to set host architecture – as the apt-get manpage documents further below setting a host arch makes sense only for those commands that actually need one set like source and build-dep, so other commands keep refusing the option as unsupported as they should be. So this commit does indeed just remove a single character from documentation with no other practical effect. See: #1061148
* Release 2.7.102.7.10Julian Andres Klode2024-01-195-6/+19
|
* Add Conflicts: apt-verifyJulian Andres Klode2024-01-191-0/+1
| | | | | | | | | | The APT team is very concerned about the encroachement of its namespace and the impact on security of its file verification process. We have expressed those concerns in the ITP bug, but the package was nonetheless uploaded and accepted, so we have to take this extraordinary step to protect our users. Gbp-Dch: full
* Merge branch 'happy-valgrind' into 'main'Julian Andres Klode2024-01-121-1/+1
|\ | | | | | | | | pkgcachegen: Use placement new to construct header See merge request apt-team/apt!320
| * pkgcachegen: Use placement new to construct headerJulian Andres Klode2024-01-121-1/+1
|/ | | | | | | | | | | | | | | | | Avoid copying the header from a stack allocated object as this will copy uninitialized padding bytes into the cache, triggering valgrind errors which people then use as a strawman for unrelated errors on armhf. In an optimal world we should annotate the allocator however such that valgrind actually does treat those bytes as uninitialized and then supress warnings in the harmless places, such that when you then go and try to access it in a place that matters, you do get an error for uninitialized memory. Currently any access within the pool will be considered initialized which is clearly suboptimal. But this is very much a TBD topic and involves annotating the allocator everywhere.
* Release 2.7.92.7.9Julian Andres Klode2024-01-115-6/+16
|
* CI: Pull from testing, unstable broken atmJulian Andres Klode2024-01-101-2/+2
|
* Accept file system disorder in test-ignored-filesDavid Kalnischkies2024-01-101-13/+12
| | | | | | | | Reading the contents of a directory is not deterministic, so if we wanted a fixed order we would need to sort the reported errors, but as we don't need any specific order lets just accept both possibilities. Regression-of: 7b41275b9da31d6c87bbaa0c9115e224e47b15e1
* Release 2.7.82.7.8Julian Andres Klode2024-01-086-7/+29
|
* Revert "Merge branch 'distclean-doc-an-test' into 'main'"Julian Andres Klode2024-01-082-16/+1
| | | | | This reverts commit 86e6eace1d50527b5a2396290acd1db819b13e26, reversing changes made to 6e43eef9ca8250eb561f2c9af2f4890d674f3911.
* test: Disable valgrind on armhf, incompatible with stack clash protectorJulian Andres Klode2024-01-081-1/+6
| | | | Closes: #1059352
* Merge branch 'distclean-doc-an-test' into 'main'Julian Andres Klode2024-01-082-1/+16
|\ | | | | | | | | Document and test 'distclean' See merge request apt-team/apt!312
| * Test and document 'dist-clean'Gábor Németh2023-12-152-1/+16
| |
| * Add 'dist-clean' to 'apt-get' tooGábor Németh2023-12-151-0/+2
| |
* | Merge branch 'fix/dontstorediffindex' into 'main'Julian Andres Klode2024-01-089-92/+106
|\ \ | | | | | | | | | | | | Do not store .diff_Index files in update See merge request apt-team/apt!316
| * | Do not store .diff_Index files in updateDavid Kalnischkies2024-01-033-36/+35
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Nowadays we only download the index file if we have a non-current file on disk which we want to patch. If that is the case, any index file for patches we could have stored is by definition outdated, so storing those files just takes up disk space. At least, that is the case if we have a Release file – if we don't this commit introduces a needless redownload for such repositories but such repositories are an error by default and if they can't be bothered to provide a Release file its very unlikely they actually ship diffs, so adding detection code for this seems pointless at best.
| * | Improve and test distclean implementationDavid Kalnischkies2024-01-037-57/+72
| |/ | | | | | | | | | | | | | | | | | | | | | | | | The implementation as-is as various smaller/esoteric bugs and inconsistencies like apt-get not supporting them, the option -s being supported in code but not accepted on the command line, the regex not escaping the dot before the file extension and exposing more implementation details to public headers than we actually need. Also comes with a small test case to ensure it actually works. References: bd7c126e3fb1b94e76e0e632c657cea854586844
* | Merge branch 'pu/reserved-file-extensions' into 'main'Julian Andres Klode2024-01-082-3/+48
|\ \ | |/ |/| | | | | Do not silently ignore directories for reserved file names See merge request apt-team/apt!311
| * Do not silently ignore directories for reserved file namesJulian Andres Klode2023-12-132-3/+48
|/ | | | | | Files with reserved extensions like .list, .sources, .conf, and .pref should receive notices in their respective directories even if they are directories.
* Merge branch 'fix-959093' into 'main'Julian Andres Klode2023-12-085-18/+86
|\ | | | | | | | | Add 'dist-clean' command to remove packages and list files See merge request apt-team/apt!290
| * Add 'dist-clean' command to remove packages and list filesGábor Németh2023-11-225-18/+86
| | | | | | | | | | | | | | We assume all files in the 'listsdir' are candidates. Keep only files ending with Release, Release.gpg, and InRelease. Closes: #959093
* | Merge branch 'fix/unknownarchconflicts' into 'main'Julian Andres Klode2023-12-083-6/+59
|\ \ | | | | | | | | | | | | Have Grp.FindPreferredPkg return very foreign pkgs as last resort See merge request apt-team/apt!310
| * | Have Grp.FindPreferredPkg return very foreign pkgs as last resortDavid Kalnischkies2023-12-043-6/+59
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Usually this method will return the package in the most preferred architecture (e.g. native) as that is usually what the user talks about and also information wise for our internal usage the most dense. Early on in parsing Packages files through it can happen that we encounter stanzas about packages in architectures we are not even configured to know about – we have to collect them anyhow as we might be requested to show info about them or they could be in the status file and we can't ignore stanzas in the status file… trouble is that this method used to not return anything if only such an architecture was present if we later discover other architectures which causes Provides and Conflicts which are added lazily on discovery of an architecture to not be added correctly. The result is like in the testcase that apt could be instructed to install a package without respecting its negative dependencies, which is bad even if its discovered by dpkg and refused. It does only happen with unknown architectures through which mostly happens if you are unlucky (amd64 users tend to be very lucky as that sorts early) and use flat-style repositories containing multiple architectures. Reported-By: Tianyu Chen (billchenchina) on IRC
* | | Merge branch 'main' into 'main'Julian Andres Klode2023-12-082-0/+24
|\ \ \ | |/ / |/| | | | | | | | apt-pkg/cacheset.cc: set ShowErrors to true when no version matched See merge request apt-team/apt!308
| * | apt-pkg/cacheset.cc: set ShowErrors to true when no version matchedTianyu Chen2023-12-082-0/+24
| | | | | | | | | | | | | | | | | | | | | | | | Enforce helper.canNotGetVersion to show error if no version matched. Regression-of: 572810e9f321237873d1536c88991d7825c6f1db Closes: #1053887
* | | Release 2.7.7Julian Andres Klode2023-11-225-6/+35
| | |
* | | Fix the test suite by adding new "m" flags to debug outputJulian Andres Klode2023-11-225-25/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In "Restore ?garbage by calling MarkAndSweep before parsing" I made install code run MarkAndSweep before parsing arguments such that the "?garbage" pattern works correctly. This caused test suite breakage because packages now ended up with marked flags in the debug output. Hence add "m" to the output we assert where necessary. In a nicer world we might want to just do MarkAndSweep if we actually have a ?garbage pattern to evaluate but that is a bit unpredictable in terms of performance expectations and because a "read-only" construct modifies the depcache, so let's go with the more expected option for now Regression-of: b6f362e8013b03efce54e7381e0e22fac1fa1539
* | | Merge branch 'fix-time-unit-comment' into 'main'Julian Andres Klode2023-11-201-1/+1
|\ \ \ | | | | | | | | | | | | | | | | Fix incorrect time unit comment for PulseInterval See merge request apt-team/apt!304
| * | | Fix incorrect time unit comment for PulseIntervalsid2023-07-271-1/+1
| | | |
* | | | Merge branch 'Peutch-guest-main-patch-29453' into 'main'Julian Andres Klode2023-11-201-1/+1
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | Update fr.po (add a missing dot) See merge request apt-team/apt!306
| * | | | Update fr.po (add a missing dot)Patrice Duroux2023-08-051-1/+1
| | | | |
* | | | | Restore ?garbage by calling MarkAndSweep before parsingJulian Andres Klode2023-11-202-0/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This ensures that things work correctly. LP: #1995790
* | | | | Use different variable name in GTest source path detectionDavid Kalnischkies2023-11-181-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We used GTEST_ROOT, which becomes an issue with 3.27 as that variable would influence find_package behaviour by providing PREFIXES – introduced with potentially mixed-cased name in 3.12. CMake Warning (dev) at test/libapt/CMakeLists.txt:8 (find_package): Policy CMP0144 is not set: find_package uses upper-case <PACKAGENAME>_ROOT variables. Run "cmake --help-policy CMP0144" for policy details. Use the cmake_policy command to set the policy and suppress this warning. CMake variable GTEST_ROOT is set to: /usr/src/googletest/googletest For compatibility, find_package is ignoring the variable, but code in a .cmake module might still use it. As using this new feature isn't what we wanted at all, we just use a different variable name to avoid the warning and potential future problems if we would keep using this name.
* | | | | Raise cmake_minimum_required to 3.13 to avoid warningsDavid Kalnischkies2023-11-181-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | CMake Deprecation Warning at CMakeLists.txt:6 (cmake_minimum_required): Compatibility with CMake < 3.5 will be removed from a future version of CMake. Update the VERSION argument <min> value or use a ...<max> suffix to tell CMake that the project does not need compatibility with older versions. Picking 3.13 here is a semi-random choice to avoid raising the requirement too much needlessly while also hopefully avoiding needing to raise it soon again based on the referenced mail. While we are at it, lets also fix the other spewed warning: CMake Warning (dev) at CMakeLists.txt:5 (project): cmake_minimum_required() should be called prior to this top-level project() call. Please see the cmake-commands(7) manual for usage documentation of both commands. References: https://lists.debian.org/msgid-search/20230617162957.6pklb6632zf4nijc@mail.gaussglocke.de
* | | | | Dutch program translation updateFrans Spiesschaert2023-11-181-5/+6
| | | | | | | | | | | | | | | | | | | | Closes: #1055178
* | | | | Bump Priority to required to match Debian archiveJulian Andres Klode2023-11-151-1/+1
| |_|/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | | s/AlreadDownloaded/AlreadyDownloaded/ in doc/progress-reporting.mdJulian Andres Klode2023-10-111-1/+1
| | | | | | | | | | | | | | | | Thanks: jwilk for suggestion
* | | | Revert "Do not fail on systems running in FIPSmode."Julian Andres Klode2023-10-042-4/+1
| | | | | | | | | | | | | | | | This reverts commit 668451def296afeb0c358a7d80ff39dc546defab.
* | | | Stop calculating Description-md5 if missingJulian Andres Klode2023-10-041-19/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This avoids the rabbit hole of md5 on FIPS systems, and repositories have moved to including the value as well. Also stop validating the field, this can be an arbitrary string as far as we are concerned.
* | | | Release 2.7.62.7.6Julian Andres Klode2023-09-2049-500/+598
| | | | | | | | | | | | | | | | Translation template reordering carnage :D
* | | | Merge branch 'usrmerge-warning' into 'main'Julian Andres Klode2023-09-202-18/+33
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | Downgrade unmerged-usr from error to two warnings See merge request apt-team/apt!307
| * | | | Downgrade unmerged-usr from error to two warningsJulian Andres Klode2023-09-202-18/+33
|/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | One warning will be issued before the Y/n prompt, the other will be issued at the end after package installs have been attempted or if there were other failures, such that the last line you see is warnings about unmerged-usr I do not anticipate this to be the final version either, but there we go. Closes: #1052058
generated by cgit v1.2.3-70-g09d2 (git 2.46.0) at 2026-05-12 15:50:50 +0000