zypper/master — Afrikaans @ openSUSE Weblate: Non-option program arguments:

Translation

English

Afrikaans

Needs editing

Skip

	English	Afrikaans	Actions
	Package manager restart required. (Run this command once again after the update stack got updated)
	%1% is set, otherwise a system reboot would be required.
	System reboot required.
	Consider to cancel:
	PackageKit is blocking zypper. This happens if you have an updater applet or other software management application using PackageKit running.
	We can ask PackageKit to interrupt the current action as soon as possible, but it depends on PackageKit how fast it will respond to this request.
	Ask PackageKit to quit?	Geen nodigheid om %s te installeer nie
	PackageKit is still running (probably busy).
	Try again?	Berei installasie voor ...
	Unexpected exception.	Onverwagte uitsondering.
	Type '%s' to get command-specific help.
	Verbosity: %d	Woordrykheid
	Enforced setting
	The /etc/products.d/baseproduct symlink is dangling or missing! The link must point to your core products .prod file in /etc/products.d.
	The %s option has no effect here, ignoring.
	Non-option program arguments:	Programargumente met geen opsie nie:
	A GPG pubkey is clearly identified by its fingerprint. Do not rely on the key's name. If you are not sure whether the presented key is authentic, ask the repository provider or check their web site. Many providers maintain a web page showing the fingerprints of the GPG keys they are using.
	Signing data enables the recipient to verify that no modifications occurred after the data were signed. Accepting data with no, wrong or unknown signature can lead to a corrupted system and in extreme cases even to a system compromise.
	File '%1%' is the repositories master index file. It ensures the integrity of the whole repo.
	We can't verify that no one meddled with this file, so it might not be trustworthy anymore! You should not continue unless you know it's safe.
	This file was modified after it has been signed. This may have been a malicious change, so it might not be trustworthy anymore! You should not continue unless you know it's safe.
	This might be a transient issue if the server is in the midst of receiving new data. The data file and its signature are two files which must fit together. In case the request hit the server in the midst of updating them, the signature verification might fail. After a few minutes, when the server has updated its data, it should work again.
	Repository:	Woordrykheid
	Key Fingerprint:
	Key Name:	Naam:
	Key Algorithm:
	Key Created:	Naam:
	Key Expires:	Naam:
	Subkey:
	Rpm Name:	Naam:
	The gpg key signing file '%1%' has expired.