Zen

Translation

Example:
English type: Title ===
Example
10/100 · 7

Sign in to save the translation.

English Finnish Actions
Separate Documentation Packages
 
If building documentation requires many additional dependencies then you MAY elect to not build it in the main package and instead create a separate *-doc source package which builds only the documentation. This separately packaged documentation MUST correspond to the version of the packaged software. In other words, if a new release of the software includes changes to the documentation, then the documentation package MUST also be updated. But if the new version of the software does not include documentation changes, then you MAY choose not to update the documentation package.
 
A comment SHOULD be added near Version tag of the main package to remind maintainers to update the separate *-doc package when needed.
 
Changelogs
 
The changelog describes the changes to the package that are relevant to the users of the package. This includes new upstream versions, important changes to how the package is built, rebuilds, and other changes affecting the outcome. Changes which are only relevant to packagers should not be mentioned in the changelog. This includes spec file cleanups, build error fixes or workarounds, and other changes which don't have an effect on content of the binary packages.
 
The changelog **should** be generated automatically from git commit logs using the `+%autochangelog+` macro:
 
%changelog
%autochangelog
 
The commit subject (the first line of the commit message) and optionally some additional lines are used to generate the changelog text. The commit author name and email address and the commit timestamp are also used in changelog entry.
 
The text in the the commit message which will become part of the changelog should provide a brief summary of the changes relevant for the user. The commit message may contain additional information that is relevant to packagers.
 
If a particular change is related to a Bugzilla bug, include the bug ID in the changelog entry for easy reference, e.g.
 
Add README file (rhbz#1000042)
 
If a particular commit fixes a CVE, this information should be included too.
 
The intent is to give the user a hint as to what changed in a package update without overwhelming them with the technical details. They must never simply contain an entire copy of the source CHANGELOG entries. Links to upstream NEWS files or changelogs can be entered for those who want additional information.
 
See https://docs.pagure.org/fedora-infra.rpmautospec/autochangelog.html[autochangelog documentation] for the details of how the changelog is generated from git commit messages, and how to create multi-line entries or skip entries for certain commits.
 
Packagers **may** alternatively use a manual changelog instead of the `+%autochangelog+` macro. This is described in xref:manual-changelog.adoc[Manual Changelog].
 
Example
Esimerkki:
The packager updates package to version 1.0 and creates a commit
 
$ git show
commit 0000000000001234567890ABCDEF000000000000
Author: Joe Packager <joe@example.com>
Date: Wed Jun 14 2003
 
Version 1.0
 
... (rhbz#1000024)
- Also fixes the slowdown reported in rhbz#1000025
- Upstream changelog: https://example.com/package/NEWS.html#v1.0
 
Whitespace in the spec file has been cleaned up.
 
diff --git package.spec package.spec
index 5c77064c03..efcd53a61c 100644
--- package.spec
+++ package.spec
@@ -1,5 +1,5 @@
Name: package
-Version: 0.1
+Version: 0.2
Release: %autorelease
...
 
When the package is built, an appropriate changelog entry will be generated. It can be previewed with `rpmautospec generate-chagengelog`:
 
$ rpmautospec generate-changelog
* Wed Jun 14 2003 Joe Packager <joe@example.com> - 0.2-1
- Version 1.0 (rhbz#1000024)
- Also fixes the slowdown reported in rhbz#1000025
- Upstream changelog: https://example.com/package/NEWS.html#v1.0
 
Note that the sentence about whitespace is not included in the changelog.
 
Manpages
 
As man pages are the traditional method of getting help on a Unix system, packages SHOULD contain them for all executables. If some man pages are absent, packagers SHOULD work with upstream to add them. It is also occasionally possible to find pages created by other distributions, or to use the output of the `+help2man+` program; those are often useful as a starting point. When installing man pages, note that RPM will re-compress them into its preferred format. So the `+%files+` section MUST reference manpages with a pattern that takes this into account:
 
%files
%{_mandir}/man1/foo.1*
 
Note also that files installed in `+%{_mandir}+` are automatically marked by RPM as documentation. Thus it is not necessary to use `+%doc+`.
 
For localised manpages, use `+%find_lang --with-man+` as described in <<handling_locale_files>>.
 
Compiler
 
User avatar anonymous

Suggestion added

Esimerkki

Suggested change:

Esimerkki:
a year ago

Loading…

User avatar anonymous

Suggestion added
Example
Esimerkki:
a year ago
User avatar None

String updated in the repository
Example
Esimerkki:
a year ago
User avatar None

Source string changed
Example:
a year ago
Browse all string changes

Things to check

Suggestions

There is 1 suggestion for this string.

View

Mismatched colon

Source and translation do not both end with a colon

Reset

Inconsistent

This string has more than one translation in this project or is untranslated in some components.

Reset

Glossary

English Finnish
No related strings found in the glossary.

14620888 String information

Source string description
type: Title ===
Flags
no-wrap
Source string location
pages/index.adoc:1146
String age
a year ago
Last updated
2 months ago
Source string age
a year ago
Translation file
po/fi/master/pages/index.po, string 228