summaryrefslogtreecommitdiff
path: root/debian
Commit message (Collapse)AuthorAgeFilesLines
* add the gpg-classic variant to the gpgv/gnupg or-groupDavid Kalnischkies2016-08-172-3/+4
| | | | | | We need to support partial upgrades anyhow, so we have to deal with the different versions and your tests try to ensure that we do, so we shouldn't make any explicit higher requirements.
* CMake: Install bash completions via cmakeJulian Andres Klode2016-08-151-1/+1
| | | | | | | Having the completions installed only by the packaging was an oversight. Gbp-Dch: ignore
* Change anonscm.d.o links to /git/apt/apt.git and httpsJulian Andres Klode2016-08-131-1/+1
| | | | | | This also fixes Debian/apt#20, but is slightly more complete. I think /git also looks better than /cgit, so let's switch the Vcs entry in control over too.
* ctest: show test output in case of failuresDavid Kalnischkies2016-08-121-0/+2
| | | | | | | | | | ctest as run by cmake by default does not show the output of the tests even if the tests failed. In terms of our tests it could be handy to set it always, but unfortunately it seems like cmake doesn't allow it if the internet is to be believed, so lets enable it at least while building packages and on travis. Gbp-Dch: Ignore
* CMake: Exclude .md5 and .map doxygen files from installJulian Andres Klode2016-08-111-2/+0
| | | | | | This is much better than removing them in debian/rules. Gbp-Dch: ignore
* debian/NEWS: Get rid of 1.3~pre3+cmake1 entryJulian Andres Klode2016-08-111-14/+0
| | | | | | This was only needed temporarily Thanks: Axel Beckert for reporting
* Release 1.3~rc11.3_rc1Julian Andres Klode2016-08-111-0/+43
| | | | | | | | This commit looks heavy. Most of that comes from the fact that the ordering of files in the translations changed with the switch to CMake. I could have gone the extra mile to figure out the original ordering and replicate it, but I have chosen to re-order everything by file and line number, as that's easier.
* CMake: Rewrite existing Documentation support and add doxygenJulian Andres Klode2016-08-101-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | This can now build all documentation. It should also be fairly reusable for other projects, as long as they follow the same naming scheme for the po4a output files and set the PACKAGE_* variables used here. We could have done all translations in a single call to po4a like the makefile based buildsystem does. While that would have made the output slightly nicer, this solution offers a huge performance gain because it can translate the documents in parallel, which also means that the xsltproc stage does not have to wait for all translations to be done first. You might think that the add_custom_command() should list the actual output files as BYPRODUCTS. This is not true however: Because the files are not always generated, Ninja will think missing byproducts mean that the target is out of date - which is not what we want. Finally, also add the missing doxygen support. Note that the packaging script cleans up some md5 and map files created by doxygen, otherwise it is fairly boring.
* CMake: Bump minimum required version to 3.4.0Julian Andres Klode2016-08-101-1/+1
| | | | | The SOURCE_DIR property is used for the translation building and was introduced in cmake 3.4
* debian: make autopkgtest run with CMake build dirJulian Andres Klode2016-08-101-5/+6
|
* releasing package apt version 1.3~pre3+cmake21.3_pre3+cmake2Julian Andres Klode2016-08-061-0/+6
|
* Build-depend on pkg-configJulian Andres Klode2016-08-061-1/+1
|
* releasing package apt version 1.3~pre3+cmake11.3_pre3+cmake1Julian Andres Klode2016-08-062-0/+29
|
* CMake: debian: Switch packaging over to CMake and dh 9Julian Andres Klode2016-08-0622-369/+102
| | | | | | | | | | | This new packaging is much easier to read, although the duplication in the install files is a bit annoying. We should probably also get rid of the movefiles for solvers, planners, and https method; but then we have to keep track of which methods exist in the apt package. Another disadvantage is that building only the documentation packages also requires building the code, as there's no way to turn off code building in the project.
* debian/control: Use versioned provides for same-ver library depsJulian Andres Klode2016-08-061-1/+3
| | | | | | | This simplifies the design a bit, as we do not need to read the major ABI version number from some file / command. Gbp-Dch: ignore
* Release 1.3~pre31.3_pre3Julian Andres Klode2016-08-041-0/+34
|
* Release 1.3~pre21.3_pre2Julian Andres Klode2016-07-081-0/+12
| | | | | Yes, we might still add new features to 1.3 or break some more stuff. Stay tuned!
* Add kernels with "+" in the package name to APT::NeverAutoRemoveAndrew Patterson2016-07-081-1/+1
| | | | | | | | | Escape "+" in kernel package names when generating APT::NeverAutoRemove list so it is not treated as a regular expression meta-character. [Changed by David Kalnischkies: let test actually test the change] Closes: #830159
* Release 1.3~pre11.3_pre1Julian Andres Klode2016-07-071-0/+54
|
* eipp: let apt make a plan, not make stuff planeDavid Kalnischkies2016-06-295-7/+7
| | | | | | | | | | | | | | Julian noticed on IRC that I fall victim to a lovely false friend by calling referring to a 'planer' all the time even through these are machines to e.g. remove splinters from woodwork ("make stuff plane"). The term I meant is written in german in this way (= with a single n) but in english there are two, aka: 'planner'. As that is unreleased code switching all instances without any transitional provisions. Also the reason why its skipped in changelog. Thanks: Julian Andres Klode Gbp-Dch: Ignore
* eipp: provide the internal planer as an external oneDavid Kalnischkies2016-06-275-4/+7
| | | | | | Testing the current implementation can benefit from being able to be feed an EIPP request and produce a fully compliant response. It is also a great test for EIPP in general.
* eipp: implement version 0.1 of the protocolDavid Kalnischkies2016-06-271-0/+1
| | | | | | | | | | | | | | | | | | | | | | | The very first step in introducing the "external installation planer protocol" (short: EIPP) as part of my GSoC2016 project. The description reads: APT-based tools like apt-get, aptitude, synaptic, … work with the user to figure out how their system should look like after they are done installing/removing packages and their dependencies. The actual installation/removal of packages is done by dpkg with the constrain that dependencies must be fulfilled at any point in time (e.g. to run maintainer scripts). Historically APT has a super micro-management approach to this task which hasn't aged that well over the years mostly ignoring changes in dpkg and growing into an unmaintainable mess hardly anyone can debug and everyone fears to touch – especially as more and more requirements are tacked onto it like handling cycles and triggers, dealing with "important" packages first, package sources on removable media, touch minimal groups to be able to interrupt the process if needed (e.g. unattended-upgrades) which not only sky-rocket complexity but also can be mutually exclusive as you e.g. can't have minimal groups and minimal trigger executions at the same time.
* add myself to UploadersDavid Kalnischkies2016-06-271-1/+2
|
* Add a apt suggests powermgmt-baseNicolas Le Cam2016-06-271-1/+1
| | | | debian/apt.apt-compat.cron.daily is using on_ac_power utility
* Use the ConditionACPower feature of systemd in the apt-daily serviceNicolas Le Cam2016-06-273-27/+24
| | | | | | | | | | .. instead of hardcoding the functionnality in the apt.systemd.daily script. Also make the compatibility cron job provide the same functionnality for systems that do not use systemd. Closes: #827930
* Release 1.3~exp31.3_exp3Julian Andres Klode2016-06-221-0/+31
| | | | Quite a huge churn of new strings.
* Release 1.3~exp21.3_exp2Julian Andres Klode2016-06-111-0/+63
|
* move 'dump' solver from apt-utils to apt packageDavid Kalnischkies2016-06-082-3/+3
|
* edsp: use a stanza based interface for solution writingDavid Kalnischkies2016-06-041-1/+1
| | | | | | | | EDSP had a WriteSolution method to write out the entire solution based on the inspection of a given pkgDepCache, but that is rather inflexible both for EDSP itself and for other EDSP like-protocols. It seems better to use a smaller scope in printing just a single stanza based on a given version as there is more reuse potential.
* Pass -fvisibility-inlines-hidden to g++Julian Andres Klode2016-06-012-127/+0
| | | | | | | | | | | | | | This reduces the number of symbols by about 10%. Unfortunately, it does not seem to cover all the weird std::vector and friend template expansions. ABI should not brake due to that change: It was never specified before whether an inline symbol was exported or not; so no library could rely on its presence. Instead, the symbols were exported in each library/program needing it and and then merged into a common one by the dynamic linker. Also update the symbol files to account for the removed symbols.
* Add some more symbols to libapt-pkg5.0.symbolsJulian Andres Klode2016-06-011-0/+4
| | | | | | | David added some more when he changed the output format for numbers. Gbp-Dch: ignore
* use *.docs files instead of hardcoding in debian/rulesDavid Kalnischkies2016-05-255-15/+17
| | | | Git-Dch: Ignore
* remove semi-support for different build-dirsDavid Kalnischkies2016-05-251-16/+2
| | | | | | | | | | | The debian/rules file tries to guess in which directory it is supposed to be building, but that guess is always ./build – if it wasn't it would fail later as not all rules take alternatives into acount. So, as this is clearly not used lets remove this complexity instead of fixing it up. Git-Dch: Ignore
* override lintian on doxygens embedded-javascript-libraryDavid Kalnischkies2016-05-243-2/+6
| | | | | | | The embedding is done completely automatic by doxygen and documented to be that way for reasons: /usr/share/doc/doxygen/README.jquery As we can't do anything about it, it is pointless to keep the warning.
* use https instead of git for Vcs-GitDavid Kalnischkies2016-05-241-1/+1
| | | | | Reported-By: lintian: vcs-field-uses-insecure-uri Git-Dch: Ignore
* remove duplicated 'the' from guides doc-base abstractDavid Kalnischkies2016-05-241-1/+1
| | | | | Reported-By: lintian: spelling-error-in-doc-base-abstract-field Git-Dch: Ignore
* no-change bump of Standards-Version to 3.9.8David Kalnischkies2016-05-241-1/+1
| | | | We don't have no menu file.
* update symbols fileDavid Kalnischkies2016-05-201-1/+14
|
* apt.systemd.daily: Put opening brace of check_power on extra lineJulian Andres Klode2016-05-151-1/+2
| | | | | | | The rest is also on the same line, so let's go consistent here now that we have a bug report about it. LP: #1581985
* Release 1.3~exp11.3_exp1Julian Andres Klode2016-05-111-0/+61
|
* implement Identifier field for IndexTargetsDavid Kalnischkies2016-05-081-0/+1
| | | | | | | | | | | A frontend like apt-file is only interested in a specific set of files and selects those easily via "Created-By". If it supports two locations for those files through it would need to select both and a user would need to know that implementation detail for sources.list configuration. The "Identifier" field is hence introduced which by default has the same value as "Created-By", but can be freely configured – especially it can be used to give two indexes the same identifier.
* move gnupg|gnupg2 from apt Depends to RecommendsDavid Kalnischkies2016-05-011-1/+2
| | | | | | | | | | | | apt doesn't need gnupg in its main execution paths to function, especially the Release file verification is done with gpgv only. It is only used by apt-key for advanced key management functionality most user will never use nor need. The intend is to demote it eventually to Suggests, but we opt here for a staged downgrade as there are still third-party repositories out there which require apt-key functionality without depending on gnupg (or apt for that matter).
* bugscript: include all configuration fragment filesDavid Kalnischkies2016-05-011-1/+1
| | | | Closes: 820861
* Release 1.2.111.2.11Julian Andres Klode2016-04-251-0/+19
|
* releasing package apt version 1.2.101.2.10Michael Vogt2016-04-051-0/+21
|
* Fix `OnCalendar=*-*-* 6,18:00` instead of `OnCalendar=*-*-* 6:00,18:00`Michael Vogt2016-04-041-1/+1
| | | | | | | | See https://github.com/systemd/systemd/issues/2956 - it appears that `OnCalendar=*-*-* 6,18:00` and `OnCalendar=*-*-* 6:00,18:00` are quite different. Git-Dch: ignore
* Use systemd.timer instead of a cron jobMichael Vogt2016-04-019-39/+66
| | | | | | | | | | | | | | | | | | | | | | The rational is that we need to spread the load on the mirrors that apt update and unattended-upgrades cause. To do so, we leverage the RandomizeDelay feature of systemd. The other advantage is that the timer is not run at a fixed daily.daily time but instead every 24h. This also fixes the problem that the randomized deplay in the current apt.cron.daily causes other cron jobs to be deplayed. A compatibility cron job is also provided for systems that do not use systemd. Note that the time is fired two times a day, but the logic inside of apt.systemd.daily will ensure (via stamp files) that the servers are hit at most every 24h. Firing two times a day helps with the worst case update time and it also helps with systems that are not always on. LP: #246381, #727685 Closes: #600262, #709675, #663290
* Release 1.2.91.2.9Julian Andres Klode2016-03-271-0/+12
|
* Release 1.2.81.2.8Julian Andres Klode2016-03-241-0/+27
|
* Update symbols fileJulian Andres Klode2016-03-241-1/+14
|
generated by cgit v1.2.3-70-g09d2 (git 2.46.0) at 2024-11-01 11:32:22 +0000