summaryrefslogtreecommitdiff
path: root/po/apt-all.pot
AgeCommit message (Collapse)Author
2017-07-03Release 1.5~beta11.5_beta1Julian Andres Klode
2017-06-30Upload 1.5~alpha3 to experimental1.5_alpha3Julian Andres Klode
2017-06-29Upload 1.5~alpha2 to experimental1.5_alpha2Julian Andres Klode
2017-06-28Upload 1.5~alpha1 to experimental1.5_alpha1Julian Andres Klode
2017-06-01Release 1.4.61.4.6Julian Andres Klode
2017-05-31Release 1.4.51.4.5Julian Andres Klode
2017-05-16Release 1.4.41.4.4Julian Andres Klode
2017-05-11Release 1.4.31.4.3Julian Andres Klode
2017-05-04Release 1.4.21.4.2Julian Andres Klode
2017-04-24Release 1.4.11.4.1Julian Andres Klode
2017-04-01Release the April Fools' release1.4Julian Andres Klode
2017-02-22Release 1.4~rc21.4_rc2Julian Andres Klode
2017-02-06Release 1.4~rc11.4_rc1Julian Andres Klode
2017-01-17Release 1.4~beta41.4_beta4Julian Andres Klode
We are basically frozen now, but (a) this wildcard thing is a bit "explosive" to call this RC and (b) you never know if you might need to add a new tiny feature and freeze can be long...
2017-01-05Release 1.4~beta31.4_beta3Julian Andres Klode
2016-12-31expand -f to --fix-broken in error messagesDavid Kalnischkies
Users end up believing that this is a --force mode as -f is common for that, but apt doesn't have such a mode and --fix-broken is really not about forcing something but actually trying to fix the breakage which tends to be the result of a user forcing something on its system via low-level forced dpkg calls. Example: The "common" pattern of "dpkg -i ./foo.deb; apt install -f" is nowadays far better dealt with via "apt install ./foo.deb". And while at it the two places handing out this suggestion are changed to use the same strings to avoid needless translation work in the future and the suggestion uses 'apt' instead of 'apt-get' as this will be run interactively by a user, so its a good opportunity to showcase what we can do and will allow us to be more helpful to the user. Closes: #709092 Thanks: Kristian Glass for initial patch!
2016-12-08releasing package apt version 1.4~beta2Julian Andres Klode
2016-11-25Release 1.4~beta11.4_beta1Julian Andres Klode
2016-11-11unfuzzy various strings in manpage po'sDavid Kalnischkies
No need to ask translators to deal with typo fixes in english text, adding new items to long existing lists and 'literals'. Gbp-Dch: Ignore
2016-10-04Release 1.3.11.3.1Julian Andres Klode
2016-09-20Release 1.31.3Julian Andres Klode
2016-09-02Release 1.3~rc41.3_rc4Julian Andres Klode
2016-08-30Release 1.3~rc31.3_rc3Julian Andres Klode
2016-08-17Release 1.3~rc21.3_rc2Julian Andres Klode
2016-08-11Release 1.3~rc11.3_rc1Julian Andres Klode
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.
2016-08-04Release 1.3~pre31.3_pre3Julian Andres Klode
2016-06-23show right binary name in simulation noticeDavid Kalnischkies
Closes: 825216
2016-06-22Release 1.3~exp31.3_exp3Julian Andres Klode
Quite a huge churn of new strings.
2016-06-11Release 1.3~exp21.3_exp2Julian Andres Klode
2016-05-11Release 1.3~exp11.3_exp1Julian Andres Klode
2016-05-01support Signed-By in Release files as a sort of HPKPDavid Kalnischkies
Users have the option since apt >= 1.1 to enforce that a Release file is signed with specific key(s) either via keyring filename or fingerprints. This commit adds an entry with the same name and value (except that it doesn't accept filenames for obvious reasons) to the Release file so that the repository owner can set a default value for this setting effecting the *next* Release file, not the current one, which provides a functionality similar "HTTP Public Key Pinning". The pinning is in effect as long as the (then old) Release file is considered valid, but it is also ignored if the Release file has no Valid-Until at all.
2016-04-25drop empty line from fetch errorDavid Kalnischkies
This is a duplicate of sorts of 0efb29eb36184bbe6de7b1013d1898796d94b171 which is the a lot more frequent case of this error – and also a duplicate of this error message, just without the \n at the end. Git-Dch: Ignore
2016-04-25Release 1.2.111.2.11Julian Andres Klode
2016-03-25drop confusing comma from no strong hash messageDavid Kalnischkies
2016-03-24Release 1.2.81.2.8Julian Andres Klode
2016-03-15Release 1.2.71.2.7Julian Andres Klode
2016-02-10Release 1.2.31.2.3Julian Andres Klode
Build system messed up the 1.2.2 commit by not updating the .po files properly, so they are now.
2016-01-25Release 1.2.11.2.1Julian Andres Klode
2016-01-15Release 1.21.2Julian Andres Klode
2016-01-08Release 1.2~exp11.2_exp1Julian Andres Klode
2015-12-30Release 1.1.101.1.10Julian Andres Klode
2015-12-27Release 1.1.91.1.9Julian Andres Klode
2015-12-241.1.6 Christmas releaseJulian Andres Klode
2015-12-14Release 1.1.51.1.5Julian Andres Klode
2015-12-07Release 1.1.41.1.4Julian Andres Klode
2015-11-30release 1.1.31.1.3Michael Vogt
Git-dch: ignore
2015-11-28Release 1.1.21.1.2Julian Andres Klode
2015-11-25Run ./prepare-release pre-exportMichael Vogt
2015-11-21review of new/changed translatable program stringsJustin B Rye
Reference mail: https://lists.debian.org/debian-l10n-english/2015/11/msg00006.html
2015-11-19more sensible default text in pot filesDavid Kalnischkies
Git-Dch: Ignore
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-05 01:00:54 +0000