Assigning to the registered maintainer.

CC: (none) => marja11
Assignee: bugsquad => doktor5000

A new version has been released:
https://salsa.debian.org/manpages-de-team/manpages-de/-/archive/v2.10/manpages-de-v2.10.tar.bz2

Latest version is 2.11:
https://salsa.debian.org/manpages-de-team/manpages-de/-/archive/v2.11/manpages-de-v2.11.tar.bz2

Summary: Update man-pages-de to the latest upstream version 2.10 => Update man-pages-de to the latest upstream version 2.11

Latest version is 2.12:
https://salsa.debian.org/manpages-de-team/manpages-de/-/archive/v2.12/manpages-de-v2.12.tar.bz2

Summary: Update man-pages-de to the latest upstream version 2.11 => Update man-pages-de to the latest upstream version 2.12

man-pages-de now up-to-date in Cauldron!

CC: (none) => geiger.david68210

Great! But as far as I can see, you are not the assigned package maintainer. Would you be willing to continuously maintain the package and update it within a reasonable time frame? Seems to be you are a »provenpackager« as known to me from Fedora, so you are allowed to change packages which are not owned by you. 

I should mention that I don't use Mageia at all. But I'm an upstream developer of man-pages-de, and as such, of course I'm interested in up-to-date downstream packages.

Currently we support two distributions directly: Debian unstable and Archlinux. This means in terms of our workflow, we download packages from the distributions, extract the contained man pages and merge them into a single translation template. This way all the stuff from Archlinux and Debian packages is present and ready for translation. Distributions which are still not supported directly can have differing package versions, which leads to incompletely translated man pages. And in case of the translation state is under 80%, the man page doesn't get built anymore.

If we add Mageia Cauldron to our list, then things would become easier: The packager can run »./configure--enable-distribution=mageia-cauldron« and the man pages get built from the appropriate Mageia sources. The direct support would even make translations possible for man pages which are not included in Archlinux or Debian, like dnf or something else (currently I use Archlinux, but I was Fedora user and packager for years, that's why dnf came to my mind).

But this makes only sense if someone is willing to maintain this package in the future... It is extra work for us to keep an eye on three distributions instead of two. Actually no problem at all, but it's only worth it if we can be sure that the downstream package will be kept up-to-date.

BTW, is there a Git repo (with a web interface) which contains the sources of Mageia packages, at least the spec files?

Yes I can (me and others packagers) continuously maintain the package and update it within a reasonable time frame.

Yes it would be great if mageia-cauldron can be added in your list and supported distribution.

We have a svn repo with a web interface here:

http://svnweb.mageia.org/packages/cauldron/

e.g. for man-pages-de:

http://svnweb.mageia.org/packages/cauldron/man-pages-de/

http://svnweb.mageia.org/packages/cauldron/man-pages-de/current/SPECS/man-pages-de.spec?revision=1379913&view=markup

http://svnweb.mageia.org/packages/cauldron/man-pages-de/current/SPECS/
http://svnweb.mageia.org/packages/cauldron/man-pages-de/current/SOURCES/

OK, nice to know! Thanks for the links. My websearch was not successful because I was searching only for Git repos, that's why I haven't found the SVN repo.

Some comments about the spec file:

Besides po4a, no one of the BuildRequires is needed anymore. The 2.x versions of man-pages-de changed the behavior. Now we ship the original man pages directly with the tarball. That's why it is urgently needed to keep the package up-to-date, otherwise the translated man pages get outdated soon. In earlier versions, the groff and mdoc file were always taken from the current system, so it was impossible to get outdated stuff. Even when a package ran through mass rebuilds again and again, it was always up-to-date, although some translations went under the 80% threshold for po4a and were not built anymore.


cd po/man1
mv -f ncal.1.po cal.1.po

This refers to the problem that Debian (were the original man pages previously only came from) didn't use cal.1 and comes with ncal.1 from their bsdmainutils package. Now this man page is included. It is based on the cal command from util-linux, which is also shipped with Mageia.

But it's OK for now, leave the spec file as is for the time being. Once Mageia has ben added to our supported distributions and a new tarball is out, you can change these things.

So spec file changes done!

Version 2.13 has been released today.

Summary: Update man-pages-de to the latest upstream version 2.12 => Update man-pages-de to the latest upstream version 2.13

Version 2.14 has been released today.

Note, it's the first tarball which supports Mageia Cauldron directly. Now you should be able to run "./configure --enable-distribution=mageia-cauldron" to get the appropriate translations from Mageia's source files.

Version 2.16 has been released yesterday.

Note the new download location scheme:
https://salsa.debian.org/manpages-l10n-team/manpages-l10n/-/archive/v%{version}/%{srcname}-v%{version}.tar.bz2

This is probably the last version of manpages-de. The projects manpages-de, manpages-fr and manpages-fr-extra have been merged into a new project manpages-l10n [1]. Currently we host the man pages from the mentioned predecessors, and moreover Dutch man pages imported from some old plain text files.

I don't know how to handle this in terms of the packaging policy in Mageia. Maybe the current packages need to be retired, and a new one needs to be added to the distribution? In any case, it would be the best way to split it into manpages-l10n-common (with some files like README, AUTHORS and so on) and subpackages named manpages-de and manpages-fr, containing the respective translated man pages? This way users see the new versions, but with the known names. For the build toolchain, we plan independent Make targets for each language, but as far as I can remember -- as a previous Fedora packager -- in RPM splitting can be done using separate file lists.

Once we have a pre-release tarball, I will inform you.

Summary: Update man-pages-de to the latest upstream version 2.14 => Update man-pages-de to the latest upstream version 2.16

The current Git content [1] is ready for some test installation of manpages-l10n. Note, it supports now six languages, so it would be useful to split the package into language-based subpackages. You can either call »make install« as usual from the base directory, or you can do

cd po/de
make install

and so on for the other languages to get only those files. As long as you use %find_lang --with-man for listing the man pages, this could be useful to keep different languages apart.

Version 4.0.0 of manpages-l10n has been released:

https://salsa.debian.org/manpages-l10n-team/manpages-l10n/-/archive/v4.0.0/manpages-l10n-v4.0.0.tar.bz2

If you have any questions, feel free to ask here.

So ok I have create a new srpm man-pages-l10n-4.0.0-1.mga8 and slpit out in their own sub-packages the following man-pages-de, man-pages-fr, man-pages-nl, man-pages-pl, man-pages-pt_BR and man-pages-ro.

http://svnweb.mageia.org/packages?view=revision&revision=1554826

Great! I'm not familiar with the packaging policies in Mageia; when we may expect the binary packages? Are they rebuilt automatically from time to time?

BTW, the package descriptions say »A large collection of man pages (reference material) from the Linux Documentation Project (LDP)«. First, it is not a large collection in some cases. For Romanian and Brazilian Portuguese, I expect no more than a handful of translated man pages for the time being. The word »large« is a bit exaggerated here. Second, our collection doesn't contain only man pages from LDP. Especially for German, there are many more man pages from other packages than from »man-pages« itself. So I propose the following:

»A collection of man pages (reference material) from the Linux Documentation Project (LDP) and other software, like GNU Coreutils and many more, translated to … «

If you don't like to mention GNU Coreutils explicitely, you can omit it of course. Maybe you can add for better understanding:

»For a complete list of the supported packages, see https://salsa.debian.org/manpages-l10n-team/manpages-l10n/-/raw/master/upstream/mageia-cauldron/packages.txt. Note that not all man pages from the listed packages are already translated into your language.«

And not to forget:

Section 1:  User commands (intro only)

The »intro only« tag refers to the LDP man pages again, you should omit it.

(In reply to Mario Blättermann from comment #17)
> And not to forget:
> 
> Section 1:  User commands (intro only)
> 
> The »intro only« tag refers to the LDP man pages again, you should omit it.

This »intro only« still appears some more times in the summary:

Section 6:  Games (intro only)
Section 7:  Conventions, macro packages, etc. (e.g., nroff, ascii)
Section 8:  System administration (intro only)

For section 6, it could be considered as OK, but the summary also applies to Polish translations, and there is one more translated man page in this section. Simply remove all occurences of »intro only« to be safe.



Still another problem: Recently xz-5.2.5 has been arrived in Cauldron, and this version contains some man pages translated into German:


/usr/share/man/de/man1/lzcat.1.xz
/usr/share/man/de/man1/lzcmp.1.xz
/usr/share/man/de/man1/lzdiff.1.xz
/usr/share/man/de/man1/lzegrep.1.xz
/usr/share/man/de/man1/lzfgrep.1.xz
/usr/share/man/de/man1/lzgrep.1.xz
/usr/share/man/de/man1/lzless.1.xz
/usr/share/man/de/man1/lzma.1.xz
/usr/share/man/de/man1/lzmadec.1.xz
/usr/share/man/de/man1/lzmore.1.xz
/usr/share/man/de/man1/unlzma.1.xz
/usr/share/man/de/man1/unxz.1.xz
/usr/share/man/de/man1/xz.1.xz
/usr/share/man/de/man1/xzcat.1.xz
/usr/share/man/de/man1/xzcmp.1.xz
/usr/share/man/de/man1/xzdec.1.xz
/usr/share/man/de/man1/xzdiff.1.xz
/usr/share/man/de/man1/xzegrep.1.xz
/usr/share/man/de/man1/xzfgrep.1.xz
/usr/share/man/de/man1/xzgrep.1.xz
/usr/share/man/de/man1/xzless.1.xz
/usr/share/man/de/man1/xzmore.1.xz


Because translated man pages shipped from upstream projects should always have priority over those from external projects like manpages-l10n, the mentioned files need to be removed here. The next version of manpages-l10n won't contain the files anymore, but currently there's a file conflict which prevents users from either update to xz-5.2.5 or man-pages-de-4.0.0.

Problem solved. The original package man-pages-de has been merged into manpages-l10n. See also bug #26133.

Resolution: (none) => OLD
Status: NEW => RESOLVED