summaryrefslogtreecommitdiff
path: root/po/sv.po
AgeCommit message (Collapse)Author
2018-02-26Release 1.6~beta11.6_beta1Julian Andres Klode
2018-01-04simplify translating "lists directory missing" msgDavid Kalnischkies
The appended "partial" should not be translated, but some translations got this wrong and now that there is also "auxfiles" we can just fix that problem by hiding these untranslatables from the translators. Gbp-Dch: Ignore
2018-01-03Release 1.6~alpha61.6_alpha6Julian Andres Klode
2018-01-01unfuzzy Progress l10n change due to format modifierDavid Kalnischkies
References: 0b5e329a8ba2461ccb7017d3adfc972f9dccd830 Gbp-Dch: Ignore
2017-10-23Release 1.6~alpha11.6_alpha1Julian Andres Klode
2017-09-24Release 1.51.5Julian Andres Klode
2017-09-09Release 1.5~rc21.5_rc2Julian Andres Klode
2017-08-17Release 1.5~beta21.5_beta2Julian Andres Klode
2017-07-17Merge pull request Debian/apt#44 from willismonroe/patch-1Julian Andres Klode
Minor grammar fix [jak@d.o: Fixed up po/]
2017-07-03Release 1.5~beta11.5_beta1Julian Andres Klode
2017-06-28Upload 1.5~alpha1 to experimental1.5_alpha1Julian Andres Klode
2017-02-06Release 1.4~rc11.4_rc1Julian Andres Klode
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-11-25Release 1.4~beta11.4_beta1Julian 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-04revamp all tools help messagesDavid Kalnischkies
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.
2015-11-04split up help messages for simpler reuseDavid Kalnischkies
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
2015-11-04suggest 'apt autoremove' to get right of unneeded packagesDavid Kalnischkies
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
2015-10-05Run "./prepare-release pre-export"Michael Vogt
Git-dch: ignore
2015-09-14implement apt-get source msg 'Please use: $vcs' for gitDavid Kalnischkies
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.
2015-09-11releasing package apt version 1.1~exp121.1.exp12Michael Vogt
2015-08-27Release 1.11~exp111.1.exp11Julian Andres Klode
2015-08-27Swedish program translation updateAnders Jonsson
Closes: 796059