summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Release 2.5.22.5.2Julian Andres Klode2022-07-247-8/+20
|
* Merge branch 'pu/upgrade-other-binaries' into 'main'Julian Andres Klode2022-07-245-7/+108
|\ | | | | | | | | Upgrade all binaries in a source package See merge request apt-team/apt!247
| * Add NEWS entryJulian Andres Klode2022-07-241-0/+8
| |
| * Add flag to disable upgrade by source and test caseJulian Andres Klode2022-07-243-0/+58
| |
| * Avoid recursion by looping of other binaries twiceJulian Andres Klode2022-07-241-1/+7
| | | | | | | | | | | | | | | | First mark them for upgrade without autoInst, so we don't call their "mark other binaries loop"; then call them again with it. Without this change, each binary package would upgrade the next one in the list, recursively.
| * Upgrade all binaries in a source packageJulian Andres Klode2022-07-242-7/+36
|/ | | | | | | | | Schedule all other binaries in the source package for upgrade if the candidate version belongs to the same source version as the package we are upgrading. This will significantly reduce the risk of partial upgrades and should make life a lot easier.
* Merge branch 'pu/upgrade-broken-depends' into 'main'Julian Andres Klode2022-07-245-4/+10891
|\ | | | | | | | | Mark broken reverse depends for upgrade See merge request apt-team/apt!248
| * Add test casesJulian Andres Klode2022-07-112-0/+10856
| |
| * Let the auto installer loose for non-broken packages tooJulian Andres Klode2022-07-111-2/+0
| | | | | | | | | | | | Because the auto installer now also marks other binaries in the package for upgrade, we do need to run it or we don't mark those for upgrade.
| * Mark broken reverse depends for upgradeJulian Andres Klode2022-07-112-2/+35
| | | | | | | | | | | | | | | | | | | | | | | | Currently the solver handles cases where a Breaks b (<< 1) and if we install that a, upgrades b. However, where b Depends a (= 1), b was removed again. This addresses the problem by iterating over installed reverse dependencies of upgrades and upgrading them so that both cases work roughly similarly. LP: #1974196
* | Merge branch 'fix-python-apt-build' into 'main'Julian Andres Klode2022-07-241-1/+1
|\ \ | |/ |/| | | | | apt-pkg: (re)export pkgTagSection::Key to fix FTBFS in python-apt See merge request apt-team/apt!249
| * apt-pkg: (re)export pkgTagSection::Key to fix FTBFS in python-aptMichael Vogt2022-07-221-1/+1
|/ | | | | | | | | | | | | | | | With apt 2.5.1 python-apt fails to build with: ``` ... x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.10 -c python/acquire-item.cc -o build/temp.linux-x86_64-3.10/python/acquire-item.o -std=c++11 -Wno-write-strings -DAPT_8_CLEANER_HEADERS -DAPT_9_CLEANER_HEADERS -DAPT_10_CLEANER_HEADERS -DPY_SSIZE_T_CLEAN In file included from python/python-apt.h:30, from python/apt_pkgmodule.h:211, from python/acquire-item.cc:25: /usr/include/apt-pkg/deblistparser.h:48:65: error: ‘pkgTagSection::Key’ has not been declared 48 | bool ParseDepends(pkgCache::VerIterator &Ver, pkgTagSection::Key Key, | ^~~ ``` This commit adds a small fix by (re)exporting `pkgTagSection::Key`.
* Release 2.5.12.5.1Julian Andres Klode2022-06-305-6/+27
|
* test-phased-updates-upgrade: Tests with argumentsJulian Andres Klode2022-06-301-0/+70
| | | | | | Pass some package names to upgrade to see that that works Gbp-Dch: ignore
* Merge branch 'fix_readme_typos' into 'main'Julian Andres Klode2022-06-291-6/+6
|\ | | | | | | | | Fix readme typos See merge request apt-team/apt!244
| * Some minor tweaks of spelling/grammar for better readability.Roberto C. Sánchez2022-06-171-6/+6
| |
* | Merge branch 'deb.debian.org/debian-security' into 'main'Julian Andres Klode2022-06-292-4/+6
|\ \ | | | | | | | | | | | | Switch from "security.d.o" to "deb.d.o" (matching bullseye release notes) See merge request apt-team/apt!246
| * | Switch from "security.d.o" to "deb.d.o" (matching bullseye release notes)Tianon Gravi2022-06-242-4/+6
| |/ | | | | | | Also, this adds "SUITE-updates", which helps show off one of the smaller benefits of deb822-style sources.list (less duplication).
* | Merge branch 'pu/phasing-better' into 'main'Julian Andres Klode2022-06-295-10/+410
|\ \ | |/ |/| | | | | Rewrite phased updates using a keep-back approach See merge request apt-team/apt!245
| * policy: Do not override negative pins with 1 due to phasingJulian Andres Klode2022-06-282-8/+36
| | | | | | | | | | | | | | | | | | | | | | | | | | If a package is already pinned to a negative value, we should not override this with a positive 1. This causes packages to be installable that were pinned to -1, which is not intended. For this, implement phasing as a ceiling of 1 for the pin instead of a fixed 1 value. An alternative would have been to fix it to NEVER_PIN, but that would mean entirely NEW packages would not be installable while phasing which is not the intention either. LP: #1978125
| * (Temporarily) Rewrite phased updates using a keep-back approachJulian Andres Klode2022-06-285-2/+374
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is a lot closer to the original implementation in update-manager, but still has a couple of differences that might cause bugs: - When checking whether a version is a security update, we only check versions in between and not any later version. This happens mostly because we do not know the suite, so we just check if there is any version between the installed version and our target that is a security update - We only keep already installed packages, as we run before the resolver. update-manager first runs the resolver, and then marks for keep all packages that were upgraded or newly installed that are phasing (afaict). This approach has a significant caveat that if you have version 1 installed from a release pocket, version 2 is in security, and version 3 is phasing in updates, that it installs version 3 rather than 2 from security as the policy based implementation does. It also means that apt install does not respect phasing and would always install version 3 in such a scenario. LP: #1979244
* | Merge branch 'flextension-underflow' into 'main'Julian Andres Klode2022-05-241-1/+1
|\ \ | | | | | | | | | | | | Fix integer underflow in flExtension See merge request apt-team/apt!240
| * | Fix integer underflow in flExtensionRonan Desplanques2022-05-231-1/+1
|/ / | | | | | | | | | | | | | | | | | | | | Before this patch, the expression `Res - File.length()` that was used as the length underflowed. It was very unlikely to cause any problem given the saturating behavior of the std::string constructor that's used. Replacing `Res - File.length()` with `File.length() - Res` would have worked, but omitting the last argument altogether invokes an std::string constructor which does the right thing.
* / Portuguese manpages translation updateAmérico Monteiro2022-05-201-74/+71
|/ | | | Closes: #1011315
* Release 2.5.02.5.0Julian Andres Klode2022-05-175-6/+52
|
* tests: Add g++ dependency to pkg-config testJulian Andres Klode2022-05-171-1/+1
|
* Use temporary file instead of depending on /dev/stdin for triehashDavid Kalnischkies2022-05-111-2/+3
| | | | | | | | /dev might not be populated for example in unshare chroots, so just using a temporary file it is until triehash supports non-file input. Regression-Of: f6438ea9e726a1c13ce8d90ac78cc272346ab0f8 Gbp-Dch: Ignore
* Build examples for arch:any packages again after nodoc branchDavid Kalnischkies2022-05-111-2/+2
| | | | | | | | | | 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
* Merge branch 'ci/nomorelessdocs' into 'main'Julian Andres Klode2022-05-1136-172/+249
|\ | | | | | | | | Support building with no/less docs and use it more in CI See merge request apt-team/apt!238
| * Ship our README.md in apt packageDavid Kalnischkies2022-05-071-0/+1
| | | | | | | | | | | | | | 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.
| * Include our config.h in all C++ files to avoid ODR violationsDavid Kalnischkies2022-05-0711-1/+25
| | | | | | | | | | | | | | Some of our headers use APT_COMPILING_APT trickery to avoid exposing too broadly details we don't want external clients to know and make use of. The flip-side is that this can lead to different compilation units seeing different definitions if they aren't all using the same config.
| * Ignore stty failures in testcasesDavid Kalnischkies2022-05-071-2/+2
| | | | | | | | | | | | | | | | | | | | We use 'stty sane' to combat against stepped output and co caused by (especially) failed tests, but it does so many things that it occasionally fails to reset some bits in the parallel interaction we have with it which fails the tests without a real problem in apt… Ideally we would be better at stitching the output together, but for the time being lets ignore these failures instead to stabilize the tests.
| * Do not build documentation twice in CIDavid Kalnischkies2022-05-071-18/+15
| | | | | | | | | | The documentation will not realistically vary between architectures so building it twice is just wasting time and resources.
| * Run ./prepare-release post-build checks in Gitlab CIDavid Kalnischkies2022-05-072-9/+22
| | | | | | | | | | The checks mostly deal with verifying the syntax of the documentation files and the po4a translations which have no tests otherwise.
| * Remove unused public zlib include from libapt fileutl.hDavid Kalnischkies2022-05-074-4/+2
| | | | | | | | | | | | | | | | 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
| * Link interactive helpers against system libapt for autopkgtestDavid Kalnischkies2022-05-078-43/+57
| | | | | | | | | | | | 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.
| * Avoid building inside the source dir in autopkgtestDavid Kalnischkies2022-05-072-8/+20
| | | | | | | | | | | | | | | | | | 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.
| * Mark pkg-config-test autopkgtest as superficialDavid Kalnischkies2022-05-072-17/+27
| | | | | | | | | | | | 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.
| * Use build-dep & satisfy for our CI dependency resolutionDavid Kalnischkies2022-05-071-29/+6
| | | | | | | | | | | | | | | | As the name suggests the command was introduced for the travis CI which used to be based on a fixed old(er) ubuntu release. The service is no more (at least not like it was) and nowadays the command runs in unstable or equivalent environments, so can depend a bit more on apt features we have implemented years ago instead of duck tapping.
| * Add pkg.apt.nodoxygen build profileDavid Kalnischkies2022-05-072-6/+11
| | | | | | | | | | | | 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 profileDavid Kalnischkies2022-05-0711-49/+67
| | | | | | | | | | | | 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 profileVagrant Cascadian2022-05-072-4/+12
| | | | | | | | | | | | | | 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 overrideVagrant Cascadian2022-05-071-1/+1
|/ | | | | | | | | | | | 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]
* Merge branch 'pu/invalid-dotty-options' into 'main'Julian Andres Klode2022-05-061-1/+1
|\ | | | | | | | | Do not accept arguments for apt-cache dotty, xvcg See merge request apt-team/apt!237
| * Do not accept arguments for apt-cache dotty, xvcgJulian Andres Klode2022-05-061-1/+1
| | | | | | | | | | | | | | These commands do not actually interpret the same arguments as depends, or any own ones for that matter. Gbp-Dch: full
* | Merge branch 'mirror-dequeue-fix' into 'main'Julian Andres Klode2022-05-061-2/+14
|\ \ | | | | | | | | | | | | Fix mirror method dequeuing incorrect items See merge request apt-team/apt!236
| * | Fix mirror method dequeuing incorrect itemsTroy Varney2022-04-281-2/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When the mirror method handles a URI Acquire from apt for a mirror list it already has, it calls the `RedirectItem` function directly. This function assumes that the item being redirected is at the head of the queue, and as such calls `Dequeue` to remove it from the queue. This resulted in incorrect items being removed from the queue when this branch is taken and the queue was already non-empty, as the item to be handled in this case is actually the last item in the queue. This changes `RedirectItem` to properly remove the item passed to it instead of calling Dequeue.
* | | Merge branch 'fix/tagfilekeys' into 'main'Julian Andres Klode2022-05-0626-252/+289
|\ \ \ | | | | | | | | | | | | | | | | Consistently dealing with fields via pkgTagSection::Key See merge request apt-team/apt!233
| * | | Parse Checksum fields via pkgTagSection::Key, tooDavid Kalnischkies2022-04-018-41/+48
| | | | | | | | | | | | | | | | | | | | | | | | | | | | We abstract hashes a fair bit to be able to add new ones eventually, which lead us to building the field names on the fly. We can do better through by keeping a central place for these names, too, which even helps in reducing code as we don't need the MD5 → Files dance anymore.
| * | | Use pkgTagSection::Key in more places in src:aptDavid Kalnischkies2022-04-0112-104/+110
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The speed critical paths were converted earlier, but the remaining could benefit a tiny bit from this as well especially as we have the facility now available and can therefore brush up the code in various places in the process as well. Also takes the time to add the hidden Exists method advertised in the headers, but previously not implemented.
generated by cgit v1.2.3-70-g09d2 (git 2.46.0) at 2026-05-12 18:52:59 +0000