summaryrefslogtreecommitdiff
path: root/doc
Commit message (Collapse)AuthorAgeFilesLines
* Release 1.3~rc31.3_rc3Julian Andres Klode2016-08-3015-16/+16
|
* Switch documentation from httpredir.d.o to deb.d.oJulian Andres Klode2016-08-2911-154/+154
| | | | | The CDN service deb.d.o is more reliable than the http redirector, so switch to it for our examples.
* Accept --autoremove as alias for --auto-removeJulian Andres Klode2016-08-261-1/+1
| | | | | I probably missed that when I did the usability work. But better late than never.
* CMake: Discover docbook stylesheet in other locationsJulian Andres Klode2016-08-233-3/+3
| | | | | Distributions seem to install this stuff all over the place, so let's add a common list of paths we know about.
* Release 1.3~rc21.3_rc2Julian Andres Klode2016-08-1714-15/+415
|
* add --with-source option and Packages/Sources supportDavid Kalnischkies2016-08-172-1/+22
| | | | | | | | | | | | | We support "./foobar.deb" as a way to install a deb file directly. Recently .changes files were added. This highlights a problem as you can't add the changes file without also trying to install all of them. Now, it could also be handy to add entire Packages/Sources files to perhaps get a bunch of packages in without installing them all implicitly. This commit introduces --with-source which allows to add *.deb, *.changes, *.dsc, source-dirs, Packages & Sources files (the later can also be compressed) without also installing them.
* CMake: Exclude .md5 and .map doxygen files from installJulian Andres Klode2016-08-111-1/+4
| | | | | | This is much better than removing them in debian/rules. Gbp-Dch: ignore
* CMake: Mark Doxygen as required and use DOXYGEN_EXECUTABLEJulian Andres Klode2016-08-111-2/+2
| | | | | | Seems like I missed that when adding doxygen support. Gbp-Dch: ignore
* Release 1.3~rc11.3_rc1Julian Andres Klode2016-08-1112-1678/+1313
| | | | | | | | 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.
* doc/po: Adjust translations for programmatic typo fixJulian Andres Klode2016-08-1110-10/+10
| | | | | | This enhances commit b9e6db821a6ddbc5bf6a90c80c296d4e91283a63. Gbp-Dch: ignore
* Merge branch 'feature/apt-dpkg-comm'David Kalnischkies2016-08-112-78/+10
|\
| * disable explicit configuration of all packages at the endDavid Kalnischkies2016-08-101-77/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | With b4450f1dd6bca537e60406b2383ab154a3e1485f we dropped what we calculated here later on and now that we don't need it in the meantime either we can just skip the busy work by default and expect dpkg to do the right thing dropping also our little "last explicit configures" removal trick introduced in b4450f1dd6bca537e60406b2383ab154a3e1485f. This enables the last of a bunch of previously experimental options, some of them existing still, but are very special and hence not really worth documenting anymore (especially as it would need to be rewritten now entirely) which is why the documentation is nearly completely dropped. The order of configuration stanzas in the simulation code changes slightly as it isn't concerning itself with finding the 'right' order, but any order is valid anyhow as long as the entire set happens in the same call.
| * select remove/purge packages early on for dpkgDavid Kalnischkies2016-08-101-1/+3
| | | | | | | | | | | | | | Telling dpkg early on that we are going to remove these packages later helps it with auto-deconfiguration decisions and its another area where a planner can ignore the nitty gritty details and let dpkg decide the course of action if there are no special requirements.
* | fix programmatic typo in apt-key manpageDavid Kalnischkies2016-08-101-1/+1
|/ | | | | Reported-By: Johannes 'josch' Schauer on IRC Gbp-Dch: Ignore
* Get rid of the old buildsystemJulian Andres Klode2016-08-103-161/+0
| | | | Bye, bye, old friend.
* CMake: Rewrite existing Documentation support and add doxygenJulian Andres Klode2016-08-102-17/+81
| | | | | | | | | | | | | | | | | | | | | | | | 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.
* releasing package apt version 1.3~pre3+cmake21.3_pre3+cmake2Julian Andres Klode2016-08-0616-17/+17
|
* releasing package apt version 1.3~pre3+cmake11.3_pre3+cmake1Julian Andres Klode2016-08-066-6/+6
|
* CMake: Add initial support for documentation buildingJulian Andres Klode2016-08-062-0/+25
| | | | | | | | | | Build HTML docbook guides (untranslated) and manual pages (including translations). Also install the examples in the example subdirectory. Translation of docbook guides has not been implemented yet, but should be easy to do. The code also needs some cleanup to automatically detect the available translations.
* doc: Fix fuzzy string regressionJulian Andres Klode2016-08-0610-42/+44
| | | | | | | | Commit b559d4846018c3adac362c6f1d0d697956586208 updated the documentation to refer to apt.systemd.daily instead of the apt cron job, introducing fuzzy strings in all the translations. Gbp-Dch: ignore
* doc: update path to periodic options scriptJason Travis2016-08-051-1/+1
|
* Release 1.3~pre31.3_pre3Julian Andres Klode2016-08-0416-17/+17
|
* Release 1.3~pre21.3_pre2Julian Andres Klode2016-07-0816-17/+17
| | | | | Yes, we might still add new features to 1.3 or break some more stuff. Stay tuned!
* Release 1.3~pre11.3_pre1Julian Andres Klode2016-07-0717-396/+597
|
* apt-key.8: Put (deprecated) into the term tagJulian Andres Klode2016-07-071-1/+1
| | | | | | Now post-build script should no longer complain... Gbp-Dch: ignore
* use +0000 instead of UTC by default as timezone in outputDavid Kalnischkies2016-07-022-4/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | All apt versions support numeric as well as 3-character timezones just fine and its actually hard to write code which doesn't "accidently" accepts it. So why change? Documenting the Date/Valid-Until fields in the Release file is easy to do in terms of referencing the datetime format used e.g. in the Debian changelogs (policy §4.4). This format specifies only the numeric timezones through, not the nowadays obsolete 3-character ones, so in the interest of least surprise we should use the same format even through it carries a small risk of regression in other clients (which encounter repositories created with apt-ftparchive). In case it is really regressing in practice, the hidden option -o APT::FTPArchive::Release::NumericTimezone=0 can be used to go back to good old UTC as timezone. The EDSP and EIPP protocols use this 'new' format, the text interface used to communicate with the acquire methods does not for compatibility reasons even if none of our methods would be effected and I doubt any other would (in these instances the timezone is 'GMT' as that is what HTTP/1.1 requires). Note that this is only true for apt talking to methods, (libapt-based) methods talking to apt will respond with the 'new' format. It is therefore strongly adviced to support both also in method input.
* deprecate 'apt-key update' and no-op it in DebianDavid Kalnischkies2016-07-021-16/+8
| | | | | | Debian isn't using 'update' anymore for years and the command is in direct conflict with our goal of not requiring gnupg anymore, so it is high time to officially declare this command as deprecated.
* warn if apt-key is used in scripts/its output parsedDavid Kalnischkies2016-07-011-1/+16
| | | | | | | | | apt-key needs gnupg for most of its operations, but depending on it isn't very efficient as apt-key is hardly used by users – and scripts shouldn't use it to begin with as it is just a silly wrapper. To draw more attention on the fact that e.g. 'apt-key add' should not be used in favor of "just" dropping a keyring file into the trusted.gpg.d directory this commit implements the display of warnings.
* alias apt-key list to fingerDavid Kalnischkies2016-07-011-13/+2
| | | | | | | | There is no real point in having two commands which roughly do the same thing, especially if the difference is just in the display of the fingerprint and hence security sensitive information. Closes: 829232
* eipp: let apt make a plan, not make stuff planeDavid Kalnischkies2016-06-291-65/+65
| | | | | | | | | | | | | | 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: rename stanza 'Install' to 'Unpack'David Kalnischkies2016-06-271-1/+40
| | | | | | Freeing 'Install' for future use as an interface for "dpkg --install", which is currently not used by any existent planer, so the implementation of it itself will be delayed until then.
* eipp: add Allow-Temporary-Remove-of-EssentialsDavid Kalnischkies2016-06-271-3/+11
| | | | | | | | A rather special need option, but the internal planer supports this and we have a testcase for it & sometimes it is hit (as a bug through). The option itself mostly serves as a reminder for implementors that they should be careful with removes and especially temporary removes if they perform any.
* eipp: implement Immediate-Configuration flagDavid Kalnischkies2016-06-271-0/+8
| | | | | | | | | APT has 3 modes: no immediate configuration, all packages are configured immediately and its default mode of configuring essentials and pseudo-essentials immediately only. While this seems like a job of different planers at first, it might be handy to have it as an option, too, in case a planer (like apts internal one) supports different modes where the introduction of individual planers would be counter intuitive.
* eipp: implement version 0.1 of the protocolDavid Kalnischkies2016-06-271-0/+243
| | | | | | | | | | | | | | | | | | | | | | | 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.
* Release 1.3~exp31.3_exp3Julian Andres Klode2016-06-2216-336/+1075
| | | | Quite a huge churn of new strings.
* add insecure (and weak) allow-options for sources.listDavid Kalnischkies2016-06-223-6/+26
| | | | | | | | Weak had no dedicated option before and Insecure and Downgrade were both global options, which given the effect they all have on security is rather bad. Setting them for individual repositories only isn't great but at least slightly better and also more consistent with other settings for repositories.
* forbid insecure repositories by default expect in apt-getDavid Kalnischkies2016-06-223-28/+50
| | | | | | | | | | | | | | | With this commit all APT-based clients default to refusing to work with unsigned or otherwise insufficently secured repositories. In terms of apt and apt-get this changes nothing, but it effects all tools using libapt like aptitude, synaptic or packagekit. The exception remains apt-get for stretch for now as this might break too many scripts/usecases too quickly. The documentation is updated and extended to reflect how to opt out or in on this behaviour change. Closes: 808367
* implement and document DIRECT for auto-detect-proxyDavid Kalnischkies2016-06-201-7/+12
| | | | | | | There is a subtile difference between an empty setting and "DIRECT" in the configuration as the later overrides the generic settings while the earlier does not. Also, non-zero exitcodes should really be reported as an error rather than silently discarded.
* Release 1.3~exp21.3_exp2Julian Andres Klode2016-06-1115-482/+1195
|
* edsp: drop privileges before executing solversDavid Kalnischkies2016-06-081-0/+5
| | | | | | | | | | | | | | | Most (if not all) solvers should be able to run perfectly fine without root privileges as they get the entire state they are supposed to work on via stdin and do not perform any action directly, but just pass suggestions on via stdout. The new default is to run them all as _apt hence, but each solver can configure another user if it chooses/must. The security benefits are minimal at best, but it helps preventing silly mistakes (see 35f3ed061f10a25a3fb28bc988fddbb976344c4d) and that is always good. Note that our 'apt' and 'dump' solver already dropped privileges if they had them.
* fix and document on the fly compressor configDavid Kalnischkies2016-05-274-30/+67
| | | | | | | libapt allows to configure compressors to be used by its system via configuration implemented in 03bef78461c6f443187b60799402624326843396, but that was never really documented and also only partly working, which also explains why the tests weren't using it…
* fix two typos in apt.conf & apt-cache manpageDavid Kalnischkies2016-05-2412-33/+33
| | | | | Reported-By: lintian: spelling-error-in-manpage Git-Dch: Ignore
* edsp: add Forbid-{New-Install,Remove} and Upgrade-AllDavid Kalnischkies2016-05-201-5/+22
| | | | | This allows to differentiate properly between 'apt-get upgrade', 'apt upgrade' and 'apt full-upgrade'.
* document --no- as --show-upgraded is the defaultDavid Kalnischkies2016-05-161-3/+2
| | | | | | | | | | | | | --show-upgraded is the default since 906fbf8886926eeb302332d997c9bd861291e155 so documenting it as if it would be an option having an effect as is feels wrong and we do the same for other options like install-recomends, download, …, too. This commit also removes -u from the documentation, but still supports it in the commandline parsing. Eventually we should deprecate the short option, but for now lets just stop documenting it. Closes: 824456
* edsp: warn if unexpected stanzas appear in the solutionDavid Kalnischkies2016-05-121-4/+9
| | | | | | Unexpected are for examples removal requests for versions which aren't installed, installations of already installed versions & requests to install and remove a package at the same time.
* edsp: document unique package identifiersJohannes 'josch' Schauer2016-05-121-5/+10
| | | | | | | | | | Document that package identifiers must be unique (apt only uses the last action for a given identifier) and that install requests do also imply upgrades and downgrades (and thus removal of the old version). This is to prevent that solvers express an upgrade or downgrade instruction as two stanzas: a removal of the old version and an installation of the new version. Instead, a single install stanza is sufficient to express upgrade or downgrade requests.
* Release 1.3~exp11.3_exp1Julian Andres Klode2016-05-1113-146/+308
|
* edsp: support generic and solver-specific configsDavid Kalnischkies2016-05-101-8/+20
| | | | | | | | | | | | | | The spec was slightly inconsistent if the preferences setting is available only as generic or specific setting & the code only supported the specific one, while for the strict-pinning was only generic… As the usual pattern for apt is to have both options we adapt the spec and code to support both as well. This also adds a purely informal "Solver" field so in case the request is saved in a file, we know to which solver the sent preferences apply. Closes: 823918
* implement Identifier field for IndexTargetsDavid Kalnischkies2016-05-084-13/+26
| | | | | | | | | | | 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.
* implement Fallback-Of for IndexTargetsDavid Kalnischkies2016-05-081-2/+7
| | | | | | | | | | | | | | | | Sometimes index files are in different locations in a repository as it is currently the case for Contents files which are per-component in Debian, but aren't in Ubuntu. This has historic reasons and is perhaps changed soon, but such cases of transitions can always happen in the future again, so we should prepare: Introduced is a new field declaring that the current item should only be downloaded if the mentioned item wasn't allowing for transitions without a flagday in clients and archives. This isn't implemented 'simpler' with multiple MetaKeys as items (could) change their descriptions and perhaps also other configuration bits with their location.
generated by cgit v1.2.3-70-g09d2 (git 2.46.0) at 2024-11-01 06:33:14 +0000