summaryrefslogtreecommitdiff
path: root/po/ast.po
Commit message (Collapse)AuthorAgeFilesLines
* Release 1.4~beta31.4_beta3Julian Andres Klode2017-01-051-48/+48
|
* expand -f to --fix-broken in error messagesDavid Kalnischkies2016-12-311-22/+19
| | | | | | | | | | | | | | | | | | | | 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!
* Release 1.4~beta11.4_beta1Julian Andres Klode2016-11-251-1/+3
|
* Release 1.3~rc31.3_rc3Julian Andres Klode2016-08-301-1/+2
|
* Release 1.3~rc21.3_rc2Julian Andres Klode2016-08-171-5/+5
|
* Release 1.3~rc11.3_rc1Julian Andres Klode2016-08-111-1915/+1930
| | | | | | | | 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.
* Release 1.3~pre31.3_pre3Julian Andres Klode2016-08-041-11/+48
|
* show right binary name in simulation noticeDavid Kalnischkies2016-06-231-5/+7
| | | | Closes: 825216
* Release 1.3~exp31.3_exp3Julian Andres Klode2016-06-221-28/+36
| | | | Quite a huge churn of new strings.
* Release 1.3~exp21.3_exp2Julian Andres Klode2016-06-111-7/+21
|
* Release 1.3~exp11.3_exp1Julian Andres Klode2016-05-111-25/+30
|
* support Signed-By in Release files as a sort of HPKPDavid Kalnischkies2016-05-011-7/+2
| | | | | | | | | | | | 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.
* drop empty line from fetch errorDavid Kalnischkies2016-04-251-8/+6
| | | | | | | | 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
* Release 1.2.111.2.11Julian Andres Klode2016-04-251-1/+1
|
* drop confusing comma from no strong hash messageDavid Kalnischkies2016-03-251-2/+2
|
* Release 1.2.81.2.8Julian Andres Klode2016-03-241-4/+8
|
* Release 1.2.71.2.7Julian Andres Klode2016-03-151-1/+7
|
* Release 1.2.31.2.3Julian Andres Klode2016-02-101-84/+74
| | | | | Build system messed up the 1.2.2 commit by not updating the .po files properly, so they are now.
* Release 1.2.11.2.1Julian Andres Klode2016-01-251-1/+1
|
* Release 1.21.2Julian Andres Klode2016-01-151-1/+1
|
* Release 1.2~exp11.2_exp1Julian Andres Klode2016-01-081-13/+18
|
* Release 1.1.101.1.10Julian Andres Klode2015-12-301-6/+6
|
* Release 1.1.91.1.9Julian Andres Klode2015-12-271-1/+6
|
* 1.1.6 Christmas releaseJulian Andres Klode2015-12-241-9/+9
|
* Release 1.1.51.1.5Julian Andres Klode2015-12-141-6/+20
|
* Release 1.1.41.1.4Julian Andres Klode2015-12-071-34/+34
|
* release 1.1.31.1.3Michael Vogt2015-11-301-110/+110
| | | | Git-dch: ignore
* Release 1.1.21.1.2Julian Andres Klode2015-11-281-1/+6
|
* Run ./prepare-release pre-exportMichael Vogt2015-11-251-46/+44
|
* review of new/changed translatable program stringsJustin B Rye2015-11-211-10/+10
| | | | | Reference mail: https://lists.debian.org/debian-l10n-english/2015/11/msg00006.html
* revamp all tools help messagesDavid Kalnischkies2015-11-041-420/+394
| | | | | | | | | | | | | | | | The general idea is: A small paragraph on the tool itself as a description, a list of the most used (!= all) commands available in the tool, a remark where to find more information on the tool and its commands (aka: in the manpage) and finally a common block referring to even more manpages. In exchange options are completely omitted from the output as well as deprecated or obscure commands. (Better) Information about them is available in the manpages anyway and the few options which were listed before were also the least interesting ones (-o -c -q and co are hardly of interest for someone totally new looking to find info by asking for help and anyone with a bit of experience doesn't need this short list. Those would need a list of options applying to the command they call, but they are too numerous and command specific to list them sanely in this context.
* split up help messages for simpler reuseDavid Kalnischkies2015-11-041-156/+304
| | | | | | | | | | | | | That is one huge commit with busy work only: Help messages used to be one big translateable string, which is a pain for translators and hard to reuse for us. This change there 'explodes' this single string into new string for each documented string trying hard to split up the translated messages as well. This actually restores many translations as previously adding a single command made all of the bug message fuzzy. The splitup also highlighted that its easy to forget a line, duplicate one and similar stuff. Git-Dch: Ignore
* suggest 'apt autoremove' to get right of unneeded packagesDavid Kalnischkies2015-11-041-4/+4
| | | | | | | | | | The bugreport is more conservative in asking for a conditional, but given that this is a message intended to be read by users to be run by users we should suggest using a command intended to be used by users. And while we are at, add sudo to the message – conditional of course. Closes: 801571
* Run "./prepare-release pre-export"Michael Vogt2015-10-051-2200/+2163
| | | | Git-dch: ignore
* implement apt-get source msg 'Please use: $vcs' for gitDavid Kalnischkies2015-09-141-2/+1
| | | | | A bit unfair that only Bzr had this message. Lets at least print it for git as well with the option of adding more later without string changes.
* releasing package apt version 1.1~exp12Michael Vogt2015-09-111-558/+573
|
* Release 1.11~exp111.1.exp11Julian Andres Klode2015-08-271-655/+657
|
* releasing package apt version 1.1~exp10Michael Vogt2015-08-241-1365/+1470
|
* implement a more generic ShowList methodDavid Kalnischkies2015-08-101-2/+2
| | | | | | | | | | | | | | | apt-get is displaying various lists of package names, which until now it was building as a string before passing it to ShowList, which inserted linebreaks at fitting points and showed a title if needed, but it never really understood what it was working with. With the help of C++11 the new generic knows not only what it works with, but generates the list on the fly rather than asking for it and potentially discarding parts of the input (= the non-default verbose display). It also doubles as a test for how usable the CacheSets are with C++11. (Not all callers are adapted yet.) Git-Dch: Ignore
* show item ID in Hit, Ign and Err lines as wellDavid Kalnischkies2015-06-151-8/+12
| | | | | | | | Again, consistency is the main sellingpoint here, but this way it is now also easier to explain that some files move through different stages and lines are printed for them hence multiple times: That is a bit hard to believe if the number is changing all the time, but now that it keeps consistent.
* properly implement pkgRecord::Parser for *.deb filesDavid Kalnischkies2015-03-161-1325/+1381
| | | | | | | | | Implementing FileName() works for most cases for us, but other frontends might need more and even for us its not very stable as the normal Jump() implementation is pretty bad on a deb file and produce errors on its own at times. So, replacing this makeshift with a complete implementation by mostly just shuffling code around.
* merge debian/sid into debian/experimentalDavid Kalnischkies2015-03-161-1132/+1067
|\
| * prepare 1.0.9.6Michael Vogt2015-01-161-486/+486
| |
| * release 1.0.9.51.0.9.5David Kalnischkies2014-12-231-48/+48
| |
| * release 1.0.9.41.0.9.4David Kalnischkies2014-12-031-1414/+1409
| |
* | Run ./prepare-release pre-exportMichael Vogt2014-11-061-1149/+1204
| | | | | | | | Git-dch: ignore
* | correct the error messages to refer to apt-key instead of gpgvDavid Kalnischkies2014-09-271-4/+4
| | | | | | | | Git-Dch: Ignore
* | fix progress output for (dist-)upgrade calculationDavid Kalnischkies2014-09-271-2/+2
|/ | | | | | | | | | | | | | | | | Previously, we had a start and a done of the calculation printed by higher-level code, but this got intermixed by progress reporting from an external solver or the output of autoremove code… The higherlevel code is now only responsible for instantiating a progress object of its choosing (if it wants progress after all) and the rest will be handled by the upgrade code. Either it is used to show the progress of the external solver or the internal solver will give some hints about its overall progress. The later isn't really a proper progress as it will jump forward after each substep, but that is at least a bit better than before without any progress indication. Fixes also the 'strange' non-display of this progress line in -q=1, while all others are shown, which is reflected by all testcase changes.
* prepare 1.0.8Michael Vogt2014-09-091-1205/+1207
|
* releasing 1.0.7Michael Vogt2014-08-281-1565/+1566
|
generated by cgit v1.2.3-70-g09d2 (git 2.46.0) at 2024-11-01 03:39:40 +0000