manpages-pl-list

Re: [Manpages-pl-list] Przetłumaczone długie opcje w file(1)

[Michał K. <mic...@gm...>]

W dniu 1.07.2025 o 12:55, krkkx--- przez Manpages-pl-list pisze:
> Dzień dobry, polskie tłumaczenie file(1) posiada opcje --files-from, --magic-file i --special-files przetłumaczone na --pliki-od, --plik-magiczny i --pliki-specjalne. Są one błędne – program rozumie tylko po angielsku.

Dzień dobry!

Bardzo dziękuję za zgłoszenie!

Poprawione w repozytorium w 33a74080[1], choć kolejnego wydania 
manpages-l10n spodziewamy się dopiero pod koniec września, więc błędy 
będą jeszcze chwilę kłuły w oczy.

Przy okazji przepraszam za zwłokę, dodałem e-maila do białej listy, więc 
w przypadku kolejnych wiadomości z tego adresu - do czego zachęcam, choć 
mam nadzieję, że powodów do interwencji będzie jak najmniej :) - pojawią 
się na liście od razu.

[1] 
https://salsa.debian.org/manpages-l10n-team/manpages-l10n/-/commit/33a74080aba4c2028666647bfebd0f94dbde3cf6
-- 
Michał Kułach

[Manpages-pl-list] Przetłumaczone długie opcje w file(1)

[<kr...@pr...>]

Dzień dobry, polskie tłumaczenie file(1) posiada opcje --files-from, --magic-file i --special-files przetłumaczone na --pliki-od, --plik-magiczny i --pliki-specjalne. Są one błędne – program rozumie tylko po angielsku.

Re: [Manpages-pl-list] Tłumaczenie man ss

[Michał K. <mic...@gm...>]

W dniu 22.05.2023 o 03:46, Daria D pisze:
> Dzień dobry, chciałabym dodać tłumaczenie podręcznika polecenia ss. Co 
> dalej zrobić?

Dzień dobry!

Wygląda na to, że ss(8) pochodzi z pakietu iproute2 (zob. 
https://manpages.debian.org/bullseye/iproute2/ss.8.en.html), który nie 
posiada jeszcze tłumaczeń podręcznika w żadnym języku. Z tego względu 
przed przystąpieniem do pracy, musimy poprosić opiekunów zespołu 
manpages-l10n o zaimportowanie oryginalnych plików do tłumaczenia - co 
zrobię dziś wieczorem. Wtedy będzie można brać się do roboty :)

Dzięki za wiadomość i pozdrawiam!
-- 
Michał Kułach

[Manpages-pl-list] Tłumaczenie man ss

[Daria D <dar...@gm...>]

Dzień dobry, chciałabym dodać tłumaczenie podręcznika polecenia ss. Co
dalej zrobić?

[Manpages-pl-list] Next release of manpages-l10n

[Mario B. <mar...@gm...>]

Dear translators,

as you might know, the manpages-l10n project releases a new tarball
approximately every three months. The next release will happen around
June 13, 2021.

Have a look at the status pages [1]. There you see some (or even lots
of) .po files marked in red. In many cases, there are only a few
Gettext messages to translate to reach the 80% threshold. This needs
Po4a to create the translated man page. Even if you don't complete the
translation, you make sure that this man page is available for users –
admittedly, still with some English parts, but it is present.

The Git infrastructure is already prepared for including two new
languages into the tarball: Czech and Danish.

Happy translating!

[1] https://manpages-l10n-team.pages.debian.net/manpages-l10n/index.html

Best Regards,
Mario

[Manpages-pl-list] Translated man pages of util-linux will move to the upstream project

[Mario B. <mar...@gm...>]

Dear translators,

the manpages-l10n project [1] hosts man page translations of the
util-linux tools [2] for some years. Because this external approach
has some disadvantages, the .po files will be moved to the GNU
Translation project soon. Besides the conversion of the source files
from *.roff to asciidoc, the localization using po4a [3] has been
enabled in util-linux itself. A translation template is already
available from [4] (will still be moved to another location in the
project tree, probably po-man/, see [5]).

To mention, in manpage-l10n we have .po files for util-linux man pages
in German, French, Spanish and Polish. I'm already working on the
import of the existing files. This will need at least a few weeks,
maybe months. Because util-linux v2.37 will be released soon and the
template will then be available from a newly to be created TP domain:
Please don't start with the translation into the mentioned languages,
to avoid double work! I will send the prepared .po files to you or
your mailing lists once I'm finished with the import. Of course,
translators of other languages can start as usual. The early
publication of the template is only to give translators of other
languages as much time as possible for their work.

A util-linux tarball *including* translated man pages will not be
released before the import has been finished, this means, possibly
during the lifecycle of util-linux 2.37 (in one of the v2.37.x bugfix
releases), or even later, with v2.38 in autumn this year. Otherwise it
would be too difficult to avoid file conflicts in distribution
packages. In manpages-l10n, we need either to keep all affected .po
files or remove them all in once. If we would try to remove only some
files partially, it would be almost impossible to consider all
imaginable file conflicts. That's why we postpone the activation in
util-linux for the time being.

[1] https://salsa.debian.org/manpages-l10n-team/manpages-l10n
[2] https://github.com/karelzak/util-linux
[3] https://po4a.org/
[4] https://raw.githubusercontent.com/karelzak/util-linux/master/man-common/util-linux-man.pot
[5] https://github.com/karelzak/util-linux/pull/1271

Best Regards,
Mario

Re: [Manpages-pl-list] manpages-l10n: Upcoming release 4.9.3

[Michał K. <mic...@gm...>]

W dniu 09.03.2021 o 20:35, Mario Blättermann pisze:

> Doesn't matter if you do your updates methodical or completely chaotic
> ;) Thanks for your recent contributions; due to the long non-activity
> of Polish translators I already thought about to mark the manpages-pl
> part as "unmaintained"… Nevertheless, welcome back.

That's the problem with smaller teams - when one person is gone, there
is nobody to at least maintain an existing status quo. Anyway, after
much needed break, once again I feel a joy of translating, so the future
of po/pl is bright (I hope) :)

> Your changes are
> in the v4.9.3 release and will (hopefully) go into Bullseye soon; the
> package maintainer Helge Kreutzmann is confident that the new version
> will be accepted by the release managers, although it's quite a bit
> late.

Thanks! It's much appreciated!
-- 
Michał Kułach

Re: [Manpages-pl-list] manpages-l10n: Upcoming release 4.9.3

[Mario B. <mar...@gm...>]

Hello Michał,

Am Mo., 8. März 2021 um 23:07 Uhr schrieb Michał Kułach
<mic...@gm...>:
>
> […]
>
> Thank you for a wake-up call! I will try to do some small updates also
> tomorrow, shortly before the deadline. Also sorry for doing commits in a
> little unstructured form, in the future I'll do more methodical updates!
>
Doesn't matter if you do your updates methodical or completely chaotic
;) Thanks for your recent contributions; due to the long non-activity
of Polish translators I already thought about to mark the manpages-pl
part as "unmaintained"… Nevertheless, welcome back. Your changes are
in the v4.9.3 release and will (hopefully) go into Bullseye soon; the
package maintainer Helge Kreutzmann is confident that the new version
will be accepted by the release managers, although it's quite a bit
late.

Best Regards,
Mario

Re: [Manpages-pl-list] manpages-l10n: Upcoming release 4.9.3

[<mic...@gm...>]

W dniu 07.03.2021 o 09:25, Mario Blättermann pisze:
> Dear translators,
> 
> the next release of manpages-l10n [1] will happen 2021/03/09 around
> 19:00 UTC. We need this release to stay in sync with the current
> packages in Debian Bullseye. Our update from upstream packages is
> already done yesterday. The upcoming Debian version is already frozen
> regarding package versions and changes are only possible with the
> agreement of the release managers. Sorry for this small time frame; as
> an Archlinux user, I'm not really familiar with the release management
> policies in Debian. Nevertheless, v4.9.3 will be the final version for
> Bullseye, because it becomes more and more difficult to jusitfy new
> package versions and can end up in long discussions.
> 
> Maybe it's now the time to shift priorities and have a look at the
> status pages [2] (the »Debian Unstable« pages, which are still in sync
> with Bullseye). As you might know, we use Po4a for managing
> translations, and this tool requires that a .po file is at least 80%
> translated to get the localized version. You see many files marked
> red, which means that the corresponding .po file doesn't reach this
> threshold. By working on these, you can easily increase the number of
> localized man pages users will get. In many cases there are only a few
> gettext messages to translate. Example from Polish:
> 
> Name   |Percent |Translations > 80% |Statistics
> make.1 |79%     |1                  |78 translated, 9 fuzzy, 11 untranslated
> 

Thank you for a wake-up call! I will try to do some small updates also
tomorrow, shortly before the deadline. Also sorry for doing commits in a
little unstructured form, in the future I'll do more methodical updates!

Thanks,
-- 
Michał Kułach

[Manpages-pl-list] manpages-l10n: Upcoming release 4.9.3

[Mario B. <mar...@gm...>]

Dear translators,

the next release of manpages-l10n [1] will happen 2021/03/09 around
19:00 UTC. We need this release to stay in sync with the current
packages in Debian Bullseye. Our update from upstream packages is
already done yesterday. The upcoming Debian version is already frozen
regarding package versions and changes are only possible with the
agreement of the release managers. Sorry for this small time frame; as
an Archlinux user, I'm not really familiar with the release management
policies in Debian. Nevertheless, v4.9.3 will be the final version for
Bullseye, because it becomes more and more difficult to jusitfy new
package versions and can end up in long discussions.

Maybe it's now the time to shift priorities and have a look at the
status pages [2] (the »Debian Unstable« pages, which are still in sync
with Bullseye). As you might know, we use Po4a for managing
translations, and this tool requires that a .po file is at least 80%
translated to get the localized version. You see many files marked
red, which means that the corresponding .po file doesn't reach this
threshold. By working on these, you can easily increase the number of
localized man pages users will get. In many cases there are only a few
gettext messages to translate. Example from Polish:

Name   |Percent |Translations > 80% |Statistics
make.1 |79%     |1                  |78 translated, 9 fuzzy, 11 untranslated

This means, even without completing the translation, you decide
whether users get a localized man page - or not - by translating one
(!) message.

After 4.9.3, changes will flow in backport packages, but not all users
are aware of or willing to use backports. So this release will be the
very last localized man page collection which Bullseye users will get.

For those of you who don't have direct write access to our Git
repository: Just send your updated files to me, I will commit them.

Happy translating!

[1] https://salsa.debian.org/manpages-l10n-team/manpages-l10n
[2] https://manpages-l10n-team.pages.debian.net/manpages-l10n/

Best Regards,
Mario

[Manpages-pl-list] Next release of manpages-l10n

[Mario B. <mar...@gm...>]

Dear translators,

as you might know, the manpages-l10n project releases a new tarball
approximately every three months. The next release will happen around
February 6, 2021.

Especially for Debian users it is of particular interest that Bullseye
is almost »frozen« – however, the upcoming release of manpages-l10n is
probably not the final version which gets into Bullseye, but maybe
*now* it would be time to shift personal priorities and point to that
new Debian version, regarding translation efforts.

Have a look at the status pages [1]. There you see some (or even lots
of) .po files marked in red. In many cases, there are only a few
Gettext messages to translate to reach the 80% threshold. This needs
Po4a to create the translated man page. Even if you don't complete the
translation, you make sure that this man page is available for users –
admittedly, still with some English parts, but it is present.

The Git infrastructure is already prepared for including two new
languages into the tarball: Italian and Spanish. Because the current
man-pages-it package in Mageia is v4.08, we will jump from 4.2 to 4.9
to get a proper upgrade path. Note, the Spanish part of manpages-l10n
brings Spanish man pages back to Debian, but will *not* replace the
manpages-es-extra package for the time being. After our v4.9 has been
released, I will start with importing the files from
manpages-es-extra.

Happy translating!

[1] https://manpages-l10n-team.pages.debian.net/manpages-l10n/index.html


Best Regards,
Mario

Re: [Manpages-pl-list] Next release of manpages-l10n

[Jean-Philippe M. <jpm...@de...>]

Le 15/10/2020 à 21:43, Rafael Fontenelle a écrit :
> On Thu, Oct 15, 2020 at 2:51 PM Mario Blättermann
> <mar...@gm...> wrote:
>>
>> Hello all,
>>
>> I've just released v4.2.0, I've succeeded to figure it out how this
>> works. It was simpler than expected, see below.
>>
> 
> Great. Thanks!
> 
>> Preparing a release is quite simple:
>>
>> Search with grep for the current version number. You'll get some
>> occurrences in »configure«, »configure.ac«, »CHANGES.md« etc.
>> (Don't bother with the version numbers in .po file headers)
>> Replace the old version number with the new one.
>> Write an appropriate entry in CHANGES.md.
>> Run »autoreconf« (don't know if this is really needed).
>> Commit and push the changes.
> 
> Instead of editing "configure", just edit "configure.ac" and then run
> "autoreconf" to recreate the "configure". For instance, changing 4.2.0
> version in configure.ac will repopulate all occurrences of version in
> configure.
> 
> For what it is worth, just figured out command lines to find the
> current version in configure.ac and Changes:
> 
> grep '^AC_INIT' configure.ac | sed 's/.*\[\(.*\)\].*/\1/'
> grep '^##' CHANGES.md | head -n1
> 
> Both should return 4.2.0 at this point.
> 
>>
>> Then, use the Gitlab web interface for creating the tag:
>>
>> In the sidebar on the left, click on »Tags«. In the tag overview on
>> the right, click on the »New tag« button.
>> Fill the mask with the values for the new release:
>> Tag name: v4.2.0
>> Create from: master (just leave this entry untouched)
>> Message: Release 4.2.0
> 
> For command line, consider trying the following (using 4.2.0 as example):
> 
> $ git tag -a -m 'Release 4.2.0' v4.2.0
> 
> "-a" for annotation, commonly used for releases
> (https://git-scm.com/docs/git-tag)
> 
> "-m " is the message you mentioned
> 
> "v4.2.0" is the tag name

Should I commit/push after this? Or the tags is added on the repo 
xithout additional commands?

> 
>>
>> That's all. Users and downstream packagers can now download the
>> tarball from the known location. I'll add these steps to
>> CONTRIBUTING.md soon.

Many thanks for these excellent instructions. I added them to 
CONTRIBUTING.md. Could you have a review to ensure they are appropriate 
and add missing ones?

> 
> I'll try to jump in and help you. How about opening an issue or merge

Great! Many thanks!

> request so we can discuss ideas in there?

Bugs are opened, normally. I dont know about merge requests. Perhaps you 
need to be a member of the team to get rights on it?

> 
> Maybe we should start the CONTRIBUTING with these release
> instructions, and then we adjust style and cosmetics, and add more
> info later.

I agree. So far I put the instructions at the end of CONTRIBUTING.md, 
but you can move it if better.

> 
>> Usually I tell then the Mageia, Opensuse and Archlinux packagers about
>> the new release (Fedora has its own notification service for upstream
>> releases). Regarding Debian, someone needs to pick up the package
>> maintenance.
> 
> I believe that how to contact the packagers from each distro is
> something that should be added to configure as well. Something simple,
> like:
> 
> ## Tell package maintainers of new release
> 
> ### Arch Linux:
> 1- Go to https://www.archlinux.org/packages/?sort=&q=man-pages&maintainer=&flagged=
> 2- Choose just one between "man-pages-de", "man-pages-fr", etc.
> 3- Click "Flag as out-of-date"
> 4- Fill the comment box with the newly released version
> 
> (...)
> 
> Best regards,

Best regards,

> Rafael Fontenelle
> 

Re: [Manpages-pl-list] Next release of manpages-l10n

[Rafael F. <raf...@gn...>]

On Thu, Oct 15, 2020 at 2:51 PM Mario Blättermann
<mar...@gm...> wrote:
>
> Hello all,
>
> I've just released v4.2.0, I've succeeded to figure it out how this
> works. It was simpler than expected, see below.
>

Great. Thanks!

> Preparing a release is quite simple:
>
> Search with grep for the current version number. You'll get some
> occurrences in »configure«, »configure.ac«, »CHANGES.md« etc.
> (Don't bother with the version numbers in .po file headers)
> Replace the old version number with the new one.
> Write an appropriate entry in CHANGES.md.
> Run »autoreconf« (don't know if this is really needed).
> Commit and push the changes.

Instead of editing "configure", just edit "configure.ac" and then run
"autoreconf" to recreate the "configure". For instance, changing 4.2.0
version in configure.ac will repopulate all occurrences of version in
configure.

For what it is worth, just figured out command lines to find the
current version in configure.ac and Changes:

grep '^AC_INIT' configure.ac | sed 's/.*\[\(.*\)\].*/\1/'
grep '^##' CHANGES.md | head -n1

Both should return 4.2.0 at this point.

>
> Then, use the Gitlab web interface for creating the tag:
>
> In the sidebar on the left, click on »Tags«. In the tag overview on
> the right, click on the »New tag« button.
> Fill the mask with the values for the new release:
> Tag name: v4.2.0
> Create from: master (just leave this entry untouched)
> Message: Release 4.2.0

For command line, consider trying the following (using 4.2.0 as example):

$ git tag -a -m 'Release 4.2.0' v4.2.0

"-a" for annotation, commonly used for releases
(https://git-scm.com/docs/git-tag)

"-m " is the message you mentioned

"v4.2.0" is the tag name

>
> That's all. Users and downstream packagers can now download the
> tarball from the known location. I'll add these steps to
> CONTRIBUTING.md soon.

I'll try to jump in and help you. How about opening an issue or merge
request so we can discuss ideas in there?

Maybe we should start the CONTRIBUTING with these release
instructions, and then we adjust style and cosmetics, and add more
info later.

> Usually I tell then the Mageia, Opensuse and Archlinux packagers about
> the new release (Fedora has its own notification service for upstream
> releases). Regarding Debian, someone needs to pick up the package
> maintenance.

I believe that how to contact the packagers from each distro is
something that should be added to configure as well. Something simple,
like:

## Tell package maintainers of new release

### Arch Linux:
1- Go to https://www.archlinux.org/packages/?sort=&q=man-pages&maintainer=&flagged=
2- Choose just one between "man-pages-de", "man-pages-fr", etc.
3- Click "Flag as out-of-date"
4- Fill the comment box with the newly released version

(...)

Best regards,
Rafael Fontenelle

Re: [Manpages-pl-list] Next release of manpages-l10n

[Mario B. <mar...@gm...>]

Hello all,

I've just released v4.2.0, I've succeeded to figure it out how this
works. It was simpler than expected, see below.

Am So., 4. Okt. 2020 um 10:29 Uhr schrieb Jean-Philippe MENGUAL
<jpm...@de...>:
>
>
> Le 04/10/2020 à 07:32, Helge Kreutzmann a écrit :
> > Hello Jean-Philippe,
> > On Sat, Oct 03, 2020 at 08:25:36PM +0200, Mario Blättermann wrote:
> >> Am Sa., 3. Okt. 2020 um 20:03 Uhr schrieb Jean-Philippe MENGUAL
> >> <jpm...@de...>:
> >> You don't have to be an »uploading developer« for releasing an
> >> upstream tarball of manpages-l10n. This is only for Debian packaging.
> >> Upstream releasing and downstream packaging do not necessarily have to
> >> be linked to each other. Of course, this can be done by different
> >> persons, although manpages-l10n is still to be considered as a Debian
> >> project, but meanwhile distribution-agnostic.
> >
> > I strongly concour with Mario.
> >
> > manpages-l10n uses Debian infrastructure, but it is not a Debian
> > project, but rather an upstream one.
> >
> > There are various downstreams as Mario gave a nice overview.
> >
> > One of them is Debian, where currently Tobias is the Maintainer.
> > Unfortunately Tobias is not able to maintain both the Debian
> > downstream and the upstream project as he used to be.
> >
> > Mario is very involved in getting the upstream part working again
> > (which I stronly support where I technically can) and we are
> > discussing this (albeit very slowly) with Tobias.
> >
> > I offered to take over the Debian downstream part, which I technically
> > could (though reviewing the steps once more especially for backports
> > could be helpful), but I'm no developer, so Tobias would need to grant
> > me the permission for uploads. This has been proposed to Tobias, so I
> > hope the Debian side gets going properly again as well.
> >
> > But the big issue are the upstream releases.
>
> Can Tobias, Mario and whoever write a step-to-step doc (eg. in
> CONTRIBUTING.md) with administrative commands and actions needed to be a
> release manager? Perhaps I can help if I have the process and the git
> commands written, if I know who announce the next release to, etc. In
> case I have technical issues, I may find help on the mailing lists. But
> this initial doc is absolutely needed to help a non-tech person to do
> the release management I think.
>
Preparing a release is quite simple:

Search with grep for the current version number. You'll get some
occurrences in »configure«, »configure.ac«, »CHANGES.md« etc.
(Don't bother with the version numbers in .po file headers)
Replace the old version number with the new one.
Write an appropriate entry in CHANGES.md.
Run »autoreconf« (don't know if this is really needed).
Commit and push the changes.

Then, use the Gitlab web interface for creating the tag:

In the sidebar on the left, click on »Tags«. In the tag overview on
the right, click on the »New tag« button.
Fill the mask with the values for the new release:
Tag name: v4.2.0
Create from: master (just leave this entry untouched)
Message: Release 4.2.0

That's all. Users and downstream packagers can now download the
tarball from the known location. I'll add these steps to
CONTRIBUTING.md soon.

Usually I tell then the Mageia, Opensuse and Archlinux packagers about
the new release (Fedora has its own notification service for upstream
releases). Regarding Debian, someone needs to pick up the package
maintenance.

Best Regards,
Mario

Re: [Manpages-pl-list] Next release of manpages-l10n

[Helge K. <de...@he...>]

Hello Jean-Philippe,
On Sun, Oct 04, 2020 at 10:28:59AM +0200, Jean-Philippe MENGUAL wrote:
> Le 04/10/2020 à 07:32, Helge Kreutzmann a écrit :
> > On Sat, Oct 03, 2020 at 08:25:36PM +0200, Mario Blättermann wrote:
> > > Am Sa., 3. Okt. 2020 um 20:03 Uhr schrieb Jean-Philippe MENGUAL
> > > <jpm...@de...>:

> Can Tobias, Mario and whoever write a step-to-step doc (eg. in
> CONTRIBUTING.md) with administrative commands and actions needed to be a
> release manager? Perhaps I can help if I have the process and the git
> commands written, if I know who announce the next release to, etc. In case I
> have technical issues, I may find help on the mailing lists. But this
> initial doc is absolutely needed to help a non-tech person to do the release
> management I think.

Yes, this is the missing piece in the puzzle. Once we have this, I
think Mario is able to do the most generic (upstream) parts as well
and I would be able to complete the Debian specific parts.

Greetings

            Helge

-- 
      Dr. Helge Kreutzmann                     de...@he...
           Dipl.-Phys.                   http://www.helgefjell.de/debian.php
        64bit GNU powered                     gpg signed mail preferred
           Help keep free software "libre": http://www.ffii.de/

Re: [Manpages-pl-list] Next release of manpages-l10n

[Jean-Philippe M. <jpm...@de...>]

Le 04/10/2020 à 07:32, Helge Kreutzmann a écrit :
> Hello Jean-Philippe,
> On Sat, Oct 03, 2020 at 08:25:36PM +0200, Mario Blättermann wrote:
>> Am Sa., 3. Okt. 2020 um 20:03 Uhr schrieb Jean-Philippe MENGUAL
>> <jpm...@de...>:
>> You don't have to be an »uploading developer« for releasing an
>> upstream tarball of manpages-l10n. This is only for Debian packaging.
>> Upstream releasing and downstream packaging do not necessarily have to
>> be linked to each other. Of course, this can be done by different
>> persons, although manpages-l10n is still to be considered as a Debian
>> project, but meanwhile distribution-agnostic.
> 
> I strongly concour with Mario.
> 
> manpages-l10n uses Debian infrastructure, but it is not a Debian
> project, but rather an upstream one.
> 
> There are various downstreams as Mario gave a nice overview.
> 
> One of them is Debian, where currently Tobias is the Maintainer.
> Unfortunately Tobias is not able to maintain both the Debian
> downstream and the upstream project as he used to be.
> 
> Mario is very involved in getting the upstream part working again
> (which I stronly support where I technically can) and we are
> discussing this (albeit very slowly) with Tobias.
> 
> I offered to take over the Debian downstream part, which I technically
> could (though reviewing the steps once more especially for backports
> could be helpful), but I'm no developer, so Tobias would need to grant
> me the permission for uploads. This has been proposed to Tobias, so I
> hope the Debian side gets going properly again as well.
> 
> But the big issue are the upstream releases.

Can Tobias, Mario and whoever write a step-to-step doc (eg. in 
CONTRIBUTING.md) with administrative commands and actions needed to be a 
release manager? Perhaps I can help if I have the process and the git 
commands written, if I know who announce the next release to, etc. In 
case I have technical issues, I may find help on the mailing lists. But 
this initial doc is absolutely needed to help a non-tech person to do 
the release management I think.

Regards

> 
> Greetings
> 
>              Helge
> 

Re: [Manpages-pl-list] Next release of manpages-l10n

[Helge K. <de...@he...>]

Hello Jean-Philippe,
On Sat, Oct 03, 2020 at 08:25:36PM +0200, Mario Blättermann wrote:
> Am Sa., 3. Okt. 2020 um 20:03 Uhr schrieb Jean-Philippe MENGUAL
> <jpm...@de...>:
> You don't have to be an »uploading developer« for releasing an
> upstream tarball of manpages-l10n. This is only for Debian packaging.
> Upstream releasing and downstream packaging do not necessarily have to
> be linked to each other. Of course, this can be done by different
> persons, although manpages-l10n is still to be considered as a Debian
> project, but meanwhile distribution-agnostic.

I strongly concour with Mario.

manpages-l10n uses Debian infrastructure, but it is not a Debian
project, but rather an upstream one. 

There are various downstreams as Mario gave a nice overview.

One of them is Debian, where currently Tobias is the Maintainer.
Unfortunately Tobias is not able to maintain both the Debian
downstream and the upstream project as he used to be. 

Mario is very involved in getting the upstream part working again
(which I stronly support where I technically can) and we are
discussing this (albeit very slowly) with Tobias.

I offered to take over the Debian downstream part, which I technically
could (though reviewing the steps once more especially for backports
could be helpful), but I'm no developer, so Tobias would need to grant
me the permission for uploads. This has been proposed to Tobias, so I
hope the Debian side gets going properly again as well.

But the big issue are the upstream releases.

Greetings

            Helge
-- 
      Dr. Helge Kreutzmann                     de...@he...
           Dipl.-Phys.                   http://www.helgefjell.de/debian.php
        64bit GNU powered                     gpg signed mail preferred
           Help keep free software "libre": http://www.ffii.de/

Re: [Manpages-pl-list] Next release of manpages-l10n

[Helge K. <de...@he...>]

Hello Jean-Philippe,
On Sat, Oct 03, 2020 at 08:03:06PM +0200, Jean-Philippe MENGUAL wrote:
> Le 03/10/2020 à 19:52, Mario Blättermann a écrit :
> > Hello,
> > 
> > Am Sa., 3. Okt. 2020 um 16:15 Uhr schrieb Jean-Philippe MENGUAL
> > <jpm...@de...>:
> > > 
> > > Hi,
> > > 
> > > What about the release and a Debian package? I still don't see any
> > > package in the Debian repo.
> > 
> > The manpages-*_4.1.0 packages are present in Sid (but not in Buster backports):
> > https://packages.debian.org/de/source/sid/manpages-l10n
> 
> hmmm. A Google search plus a apt-cache search manpages-l10n (or show) does
> not return anything. Maybe there is not binary yet? Why?

I do have it for German in Testing:
ii  manpages-de    4.1.0-1      all          German manpages

Similarly I could install this version of manpages-fr.

As Mario said, if possible I would try to make a backports upload
later, if Tobias can transfer the necessary knowledge and rights to
me.

Greetings

        Helge
-- 
      Dr. Helge Kreutzmann                     de...@he...
           Dipl.-Phys.                   http://www.helgefjell.de/debian.php
        64bit GNU powered                     gpg signed mail preferred
           Help keep free software "libre": http://www.ffii.de/

Re: [Manpages-pl-list] Next release of manpages-l10n

[Mario B. <mar...@gm...>]

Hello Jean-Philippe,

Am Sa., 3. Okt. 2020 um 20:03 Uhr schrieb Jean-Philippe MENGUAL
<jpm...@de...>:
>
> Hi,
>
> Le 03/10/2020 à 19:52, Mario Blättermann a écrit :
> > Hello,
> >
> > Am Sa., 3. Okt. 2020 um 16:15 Uhr schrieb Jean-Philippe MENGUAL
> > <jpm...@de...>:
> >>
> >> Hi,
> >>
> >> What about the release and a Debian package? I still don't see any
> >> package in the Debian repo.
> >
> > The manpages-*_4.1.0 packages are present in Sid (but not in Buster backports):
> > https://packages.debian.org/de/source/sid/manpages-l10n
>
> hmmm. A Google search plus a apt-cache search manpages-l10n (or show)
> does not return anything. Maybe there is not binary yet? Why?
>
There's no binary package named manpages-l10n. The source package gets
split in the usual packages manpages-fr, manpages-fr-dev, manpages-de,
manpages-de-dev and so on. By choosing the existing names, we get a
proper upgrade path and avoid that users will be forced to install
lots of man pages in other languages – which would happen in an
all-in-one package of manpages-l10n.

> >
> >> We are not yet at freeze time, but probably
> >> we should try to release a package?
> >>
> >
> > Indeed, especially to do justice to the needs of our supported Rolling
> > Releases (Debian Sid, Opensuse Tumbleweed, Archlinux) we should try to
> > release every three months, and the latest release was three months
> > ago.
> >
> > Two weeks ago I wrote to Tobias Quathamer, asking him to tell me the
> > steps of a release, so that I would become able to do releases myself.
> > He didn't respond yet. As I already knew, actually he doesn't have the
> > time anymore to contribute to manpages-l10n, neither for translations
> > and the release management nor for maintaining the Debian packages. In
> > the past months, I took some administrative tasks over, like updates
> > from upstream packages, updating the authors list, testing the
> > committed .po files for formatting issues and so on. But I don't have
> > any Autotools skills, so I haven't tried to roll out a release yet.
> >
> > This means, first we need a new release manager. Someone who's willing
> > and able to handle the Autotools stack, create the release tarball,
> > and if needed, to fix things if something fails. Second, the Debian
> > part needs a new package maintainer. The German translator Helge
> > Kreutzmann already said that he would take this over, at least as a
> > co-maintainer. Packages for the other distributions are actively
> > maintained, except for Archlinux, but I maintain some (Git-based)
> > unofficial packages in the Arch Linux User Repository, this is OK so
> > far.
> >
> > That's why I call for a volunteer for this task! He would probably
> > need to get the »owner« state in the Salsa repo, but this shouldn't be
> > the problem.
>
> hmmm. Thanks for this message, raising very important information. I am
> not an uploading devloper, but I would like to search for an idea. If
> anyone in the l10n teams has an iedea too, welcome!

You don't have to be an »uploading developer« for releasing an
upstream tarball of manpages-l10n. This is only for Debian packaging.
Upstream releasing and downstream packaging do not necessarily have to
be linked to each other. Of course, this can be done by different
persons, although manpages-l10n is still to be considered as a Debian
project, but meanwhile distribution-agnostic.

Best Regards,
Mario


>
> Regards
>
>
> >
> > Thanks in advance,
> > Mario
> >
> >
> >> Regards
> >>
> >>
> >>
> >> Jean-Philippe MENGUAL
> >> Debian Developer non uploading
> >> Community team member
> >> Accessibility team member
> >> debian-l10n-french team member
> >> President of Debian France non-profit organization
> >> Le 30/05/2020 à 08:27, Jean-Philippe MENGUAL a écrit :
> >>> Le 29/05/2020 à 21:12, Helge Kreutzmann a écrit :
> >>>> Hello Tobias,
> >>>> On Sat, Apr 04, 2020 at 09:40:41PM +0200, Dr. Tobias Quathamer wrote:
> >>>>> Am 10.02.20 um 10:10 schrieb Mario Blättermann:
> >>>>>> the manpages-l10n project is now almost ready for a release. The new
> >>>>>> version 4.0 is scheduled for march 1, 2020. All commits prior to this
> >>>>>> date will be included in the tarball.
> >>>>>
> >>>>> Hi all,
> >>>>>
> >>>>> the new package manpages-l10n has just been accepted into Debian
> >>>>> unstable. Thanks for all your work!
> >>>>
> >>>> Thank you very much for your work and the scripts as well.
> >>>>
> >>>> I discussed this with Mario and we think it would be a good time to
> >>>> target the next version, now with some more languages (I guess Mario
> >>>> has a better overview of the stats) maybe in about a week?
> >>>>
> >>>> I just checked with the French team, this release would close also the
> >>>> remaining open Debian bugs for manpages-fr.
> >>>>
> >>>> And afterwards a Debian backport would be nice.
> >>>
> >>> What would bu useful, if possible, is having a schedule of releases, to
> >>> know when will be the latest release before the freeze for Bullseye. We
> >>> still hope to finish the updating work before Bullseye. What is the
> >>> absolute deadline for it?
> >>>
> >>> Regards
> >>>
> >>>>
> >>>> Of course, the other supported (and unsupported) distribution might
> >>>> also use the chance to do the update, e.g. for Fedora for the very
> >>>> first time.
> >>>>
> >>>> Greetings
> >>>>
> >>>>               Helge
> >>>>
> >>>>

Re: [Manpages-pl-list] Next release of manpages-l10n

[Jean-Philippe M. <jpm...@de...>]

Le 03/10/2020 à 20:03, Jean-Philippe MENGUAL a écrit :
> Hi,
> 
> Le 03/10/2020 à 19:52, Mario Blättermann a écrit :
>> Hello,
>>
>> Am Sa., 3. Okt. 2020 um 16:15 Uhr schrieb Jean-Philippe MENGUAL
>> <jpm...@de...>:
>>>
>>> Hi,
>>>
>>> What about the release and a Debian package? I still don't see any
>>> package in the Debian repo.
>>
>> The manpages-*_4.1.0 packages are present in Sid (but not in Buster 
>> backports):
>> https://packages.debian.org/de/source/sid/manpages-l10n
> 
> hmmm. A Google search plus a apt-cache search manpages-l10n (or show) 
> does not return anything. Maybe there is not binary yet? Why?

Oh I understand. I thought we would have a manpages-l10n, but no. The 
choice is to generate, from the source, several binaries for each 
language. It is a good idea to avoid peple having useless binaries as 
not in their language.

So now it is clear for me.

> 
>>
>>> We are not yet at freeze time, but probably
>>> we should try to release a package?
>>>
>>
>> Indeed, especially to do justice to the needs of our supported Rolling
>> Releases (Debian Sid, Opensuse Tumbleweed, Archlinux) we should try to
>> release every three months, and the latest release was three months
>> ago.
>>
>> Two weeks ago I wrote to Tobias Quathamer, asking him to tell me the
>> steps of a release, so that I would become able to do releases myself.
>> He didn't respond yet. As I already knew, actually he doesn't have the
>> time anymore to contribute to manpages-l10n, neither for translations
>> and the release management nor for maintaining the Debian packages. In
>> the past months, I took some administrative tasks over, like updates
>> from upstream packages, updating the authors list, testing the
>> committed .po files for formatting issues and so on. But I don't have
>> any Autotools skills, so I haven't tried to roll out a release yet.
>>
>> This means, first we need a new release manager. Someone who's willing
>> and able to handle the Autotools stack, create the release tarball,
>> and if needed, to fix things if something fails. Second, the Debian
>> part needs a new package maintainer. The German translator Helge
>> Kreutzmann already said that he would take this over, at least as a
>> co-maintainer. Packages for the other distributions are actively
>> maintained, except for Archlinux, but I maintain some (Git-based)
>> unofficial packages in the Arch Linux User Repository, this is OK so
>> far.
>>
>> That's why I call for a volunteer for this task! He would probably
>> need to get the »owner« state in the Salsa repo, but this shouldn't be
>> the problem.
> 
> hmmm. Thanks for this message, raising very important information. I am 
> not an uploading devloper, but I would like to search for an idea. If 
> anyone in the l10n teams has an iedea too, welcome!

ok now things are clear for me, I guess creating a new Debian package 
would be more confortable from a release point upstream. When such 
milestone is exptected? I think from this milestone, I can update the 
Debian source package, then submitting to Helge as uploader.


> 
> Regards
> 
> 
>>
>> Thanks in advance,
>> Mario
>>
>>
>>> Regards
>>>
>>>
>>>
>>> Jean-Philippe MENGUAL
>>> Debian Developer non uploading
>>> Community team member
>>> Accessibility team member
>>> debian-l10n-french team member
>>> President of Debian France non-profit organization
>>> Le 30/05/2020 à 08:27, Jean-Philippe MENGUAL a écrit :
>>>> Le 29/05/2020 à 21:12, Helge Kreutzmann a écrit :
>>>>> Hello Tobias,
>>>>> On Sat, Apr 04, 2020 at 09:40:41PM +0200, Dr. Tobias Quathamer wrote:
>>>>>> Am 10.02.20 um 10:10 schrieb Mario Blättermann:
>>>>>>> the manpages-l10n project is now almost ready for a release. The new
>>>>>>> version 4.0 is scheduled for march 1, 2020. All commits prior to 
>>>>>>> this
>>>>>>> date will be included in the tarball.
>>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> the new package manpages-l10n has just been accepted into Debian
>>>>>> unstable. Thanks for all your work!
>>>>>
>>>>> Thank you very much for your work and the scripts as well.
>>>>>
>>>>> I discussed this with Mario and we think it would be a good time to
>>>>> target the next version, now with some more languages (I guess Mario
>>>>> has a better overview of the stats) maybe in about a week?
>>>>>
>>>>> I just checked with the French team, this release would close also the
>>>>> remaining open Debian bugs for manpages-fr.
>>>>>
>>>>> And afterwards a Debian backport would be nice.
>>>>
>>>> What would bu useful, if possible, is having a schedule of releases, to
>>>> know when will be the latest release before the freeze for Bullseye. We
>>>> still hope to finish the updating work before Bullseye. What is the
>>>> absolute deadline for it?
>>>>
>>>> Regards
>>>>
>>>>>
>>>>> Of course, the other supported (and unsupported) distribution might
>>>>> also use the chance to do the update, e.g. for Fedora for the very
>>>>> first time.
>>>>>
>>>>> Greetings
>>>>>
>>>>>               Helge
>>>>>
>>>>>
> 

Re: [Manpages-pl-list] Next release of manpages-l10n

[Jean-Philippe M. <jpm...@de...>]

Hi,

Le 03/10/2020 à 19:52, Mario Blättermann a écrit :
> Hello,
> 
> Am Sa., 3. Okt. 2020 um 16:15 Uhr schrieb Jean-Philippe MENGUAL
> <jpm...@de...>:
>>
>> Hi,
>>
>> What about the release and a Debian package? I still don't see any
>> package in the Debian repo.
> 
> The manpages-*_4.1.0 packages are present in Sid (but not in Buster backports):
> https://packages.debian.org/de/source/sid/manpages-l10n

hmmm. A Google search plus a apt-cache search manpages-l10n (or show) 
does not return anything. Maybe there is not binary yet? Why?

> 
>> We are not yet at freeze time, but probably
>> we should try to release a package?
>>
> 
> Indeed, especially to do justice to the needs of our supported Rolling
> Releases (Debian Sid, Opensuse Tumbleweed, Archlinux) we should try to
> release every three months, and the latest release was three months
> ago.
> 
> Two weeks ago I wrote to Tobias Quathamer, asking him to tell me the
> steps of a release, so that I would become able to do releases myself.
> He didn't respond yet. As I already knew, actually he doesn't have the
> time anymore to contribute to manpages-l10n, neither for translations
> and the release management nor for maintaining the Debian packages. In
> the past months, I took some administrative tasks over, like updates
> from upstream packages, updating the authors list, testing the
> committed .po files for formatting issues and so on. But I don't have
> any Autotools skills, so I haven't tried to roll out a release yet.
> 
> This means, first we need a new release manager. Someone who's willing
> and able to handle the Autotools stack, create the release tarball,
> and if needed, to fix things if something fails. Second, the Debian
> part needs a new package maintainer. The German translator Helge
> Kreutzmann already said that he would take this over, at least as a
> co-maintainer. Packages for the other distributions are actively
> maintained, except for Archlinux, but I maintain some (Git-based)
> unofficial packages in the Arch Linux User Repository, this is OK so
> far.
> 
> That's why I call for a volunteer for this task! He would probably
> need to get the »owner« state in the Salsa repo, but this shouldn't be
> the problem.

hmmm. Thanks for this message, raising very important information. I am 
not an uploading devloper, but I would like to search for an idea. If 
anyone in the l10n teams has an iedea too, welcome!

Regards


> 
> Thanks in advance,
> Mario
> 
> 
>> Regards
>>
>>
>>
>> Jean-Philippe MENGUAL
>> Debian Developer non uploading
>> Community team member
>> Accessibility team member
>> debian-l10n-french team member
>> President of Debian France non-profit organization
>> Le 30/05/2020 à 08:27, Jean-Philippe MENGUAL a écrit :
>>> Le 29/05/2020 à 21:12, Helge Kreutzmann a écrit :
>>>> Hello Tobias,
>>>> On Sat, Apr 04, 2020 at 09:40:41PM +0200, Dr. Tobias Quathamer wrote:
>>>>> Am 10.02.20 um 10:10 schrieb Mario Blättermann:
>>>>>> the manpages-l10n project is now almost ready for a release. The new
>>>>>> version 4.0 is scheduled for march 1, 2020. All commits prior to this
>>>>>> date will be included in the tarball.
>>>>>
>>>>> Hi all,
>>>>>
>>>>> the new package manpages-l10n has just been accepted into Debian
>>>>> unstable. Thanks for all your work!
>>>>
>>>> Thank you very much for your work and the scripts as well.
>>>>
>>>> I discussed this with Mario and we think it would be a good time to
>>>> target the next version, now with some more languages (I guess Mario
>>>> has a better overview of the stats) maybe in about a week?
>>>>
>>>> I just checked with the French team, this release would close also the
>>>> remaining open Debian bugs for manpages-fr.
>>>>
>>>> And afterwards a Debian backport would be nice.
>>>
>>> What would bu useful, if possible, is having a schedule of releases, to
>>> know when will be the latest release before the freeze for Bullseye. We
>>> still hope to finish the updating work before Bullseye. What is the
>>> absolute deadline for it?
>>>
>>> Regards
>>>
>>>>
>>>> Of course, the other supported (and unsupported) distribution might
>>>> also use the chance to do the update, e.g. for Fedora for the very
>>>> first time.
>>>>
>>>> Greetings
>>>>
>>>>               Helge
>>>>
>>>>

Re: [Manpages-pl-list] Next release of manpages-l10n

[Mario B. <mar...@gm...>]

Hello,

Am Sa., 3. Okt. 2020 um 16:15 Uhr schrieb Jean-Philippe MENGUAL
<jpm...@de...>:
>
> Hi,
>
> What about the release and a Debian package? I still don't see any
> package in the Debian repo.

The manpages-*_4.1.0 packages are present in Sid (but not in Buster backports):
https://packages.debian.org/de/source/sid/manpages-l10n

> We are not yet at freeze time, but probably
> we should try to release a package?
>

Indeed, especially to do justice to the needs of our supported Rolling
Releases (Debian Sid, Opensuse Tumbleweed, Archlinux) we should try to
release every three months, and the latest release was three months
ago.

Two weeks ago I wrote to Tobias Quathamer, asking him to tell me the
steps of a release, so that I would become able to do releases myself.
He didn't respond yet. As I already knew, actually he doesn't have the
time anymore to contribute to manpages-l10n, neither for translations
and the release management nor for maintaining the Debian packages. In
the past months, I took some administrative tasks over, like updates
from upstream packages, updating the authors list, testing the
committed .po files for formatting issues and so on. But I don't have
any Autotools skills, so I haven't tried to roll out a release yet.

This means, first we need a new release manager. Someone who's willing
and able to handle the Autotools stack, create the release tarball,
and if needed, to fix things if something fails. Second, the Debian
part needs a new package maintainer. The German translator Helge
Kreutzmann already said that he would take this over, at least as a
co-maintainer. Packages for the other distributions are actively
maintained, except for Archlinux, but I maintain some (Git-based)
unofficial packages in the Arch Linux User Repository, this is OK so
far.

That's why I call for a volunteer for this task! He would probably
need to get the »owner« state in the Salsa repo, but this shouldn't be
the problem.

Thanks in advance,
Mario


> Regards
>
>
>
> Jean-Philippe MENGUAL
> Debian Developer non uploading
> Community team member
> Accessibility team member
> debian-l10n-french team member
> President of Debian France non-profit organization
> Le 30/05/2020 à 08:27, Jean-Philippe MENGUAL a écrit :
> > Le 29/05/2020 à 21:12, Helge Kreutzmann a écrit :
> >> Hello Tobias,
> >> On Sat, Apr 04, 2020 at 09:40:41PM +0200, Dr. Tobias Quathamer wrote:
> >>> Am 10.02.20 um 10:10 schrieb Mario Blättermann:
> >>>> the manpages-l10n project is now almost ready for a release. The new
> >>>> version 4.0 is scheduled for march 1, 2020. All commits prior to this
> >>>> date will be included in the tarball.
> >>>
> >>> Hi all,
> >>>
> >>> the new package manpages-l10n has just been accepted into Debian
> >>> unstable. Thanks for all your work!
> >>
> >> Thank you very much for your work and the scripts as well.
> >>
> >> I discussed this with Mario and we think it would be a good time to
> >> target the next version, now with some more languages (I guess Mario
> >> has a better overview of the stats) maybe in about a week?
> >>
> >> I just checked with the French team, this release would close also the
> >> remaining open Debian bugs for manpages-fr.
> >>
> >> And afterwards a Debian backport would be nice.
> >
> > What would bu useful, if possible, is having a schedule of releases, to
> > know when will be the latest release before the freeze for Bullseye. We
> > still hope to finish the updating work before Bullseye. What is the
> > absolute deadline for it?
> >
> > Regards
> >
> >>
> >> Of course, the other supported (and unsupported) distribution might
> >> also use the chance to do the update, e.g. for Fedora for the very
> >> first time.
> >>
> >> Greetings
> >>
> >>              Helge
> >>
> >>

Re: [Manpages-pl-list] Next release of manpages-l10n

[Jean-Philippe M. <jpm...@de...>]

Hi,

What about the release and a Debian package? I still dont see any 
package in the Debian repo. We are not yet at freeze time, but probably 
we should try to release a package?

Regards



Jean-Philippe MENGUAL
Debian Developer non uploading
Community team member
Accessibility team member
debian-l10n-french team member
President of Debian France non-profit organization
Le 30/05/2020 à 08:27, Jean-Philippe MENGUAL a écrit :
> Le 29/05/2020 à 21:12, Helge Kreutzmann a écrit :
>> Hello Tobias,
>> On Sat, Apr 04, 2020 at 09:40:41PM +0200, Dr. Tobias Quathamer wrote:
>>> Am 10.02.20 um 10:10 schrieb Mario Blättermann:
>>>> the manpages-l10n project is now almost ready for a release. The new
>>>> version 4.0 is scheduled for march 1, 2020. All commits prior to this
>>>> date will be included in the tarball.
>>>
>>> Hi all,
>>>
>>> the new package manpages-l10n has just been accepted into Debian
>>> unstable. Thanks for all your work!
>>
>> Thank you very much for your work and the scripts as well.
>>
>> I discussed this with Mario and we think it would be a good time to
>> target the next version, now with some more languages (I guess Mario
>> has a better overview of the stats) maybe in about a week?
>>
>> I just checked with the French team, this release would close also the
>> remaining open Debian bugs for manpages-fr.
>>
>> And afterwards a Debian backport would be nice.
> 
> What would bu useful, if possible, is having a schedule of releases, to 
> know when will be the latest release before the freeze for Bullseye. We 
> still hope to finish the updating work before Bullseye. What is the 
> absolute deadline for it?
> 
> Regards
> 
>>
>> Of course, the other supported (and unsupported) distribution might
>> also use the chance to do the update, e.g. for Fedora for the very
>> first time.
>>
>> Greetings
>>
>>              Helge
>>
>>

Re: [Manpages-pl-list] Next release of manpages-l10n

[Jean-Philippe M. <jpm...@de...>]

Le 29/05/2020 à 21:12, Helge Kreutzmann a écrit :
> Hello Tobias,
> On Sat, Apr 04, 2020 at 09:40:41PM +0200, Dr. Tobias Quathamer wrote:
>> Am 10.02.20 um 10:10 schrieb Mario Blättermann:
>>> the manpages-l10n project is now almost ready for a release. The new
>>> version 4.0 is scheduled for march 1, 2020. All commits prior to this
>>> date will be included in the tarball.
>>
>> Hi all,
>>
>> the new package manpages-l10n has just been accepted into Debian
>> unstable. Thanks for all your work!
> 
> Thank you very much for your work and the scripts as well.
> 
> I discussed this with Mario and we think it would be a good time to
> target the next version, now with some more languages (I guess Mario
> has a better overview of the stats) maybe in about a week?
> 
> I just checked with the French team, this release would close also the
> remaining open Debian bugs for manpages-fr.
> 
> And afterwards a Debian backport would be nice.

What would bu useful, if possible, is having a schedule of releases, to 
know when will be the latest release before the freeze for Bullseye. We 
still hope to finish the updating work before Bullseye. What is the 
absolute deadline for it?

Regards

> 
> Of course, the other supported (and unsupported) distribution might
> also use the chance to do the update, e.g. for Fedora for the very
> first time.
> 
> Greetings
> 
>              Helge
> 
> 

Re: [Manpages-pl-list] Next release of manpages-l10n

[Helge K. <de...@he...>]

Hello Tobias,
On Sat, Apr 04, 2020 at 09:40:41PM +0200, Dr. Tobias Quathamer wrote:
> Am 10.02.20 um 10:10 schrieb Mario Blättermann:
> > the manpages-l10n project is now almost ready for a release. The new
> > version 4.0 is scheduled for march 1, 2020. All commits prior to this
> > date will be included in the tarball.
> 
> Hi all,
> 
> the new package manpages-l10n has just been accepted into Debian
> unstable. Thanks for all your work!

Thank you very much for your work and the scripts as well.

I discussed this with Mario and we think it would be a good time to
target the next version, now with some more languages (I guess Mario
has a better overview of the stats) maybe in about a week?

I just checked with the French team, this release would close also the
remaining open Debian bugs for manpages-fr. 

And afterwards a Debian backport would be nice.

Of course, the other supported (and unsupported) distribution might
also use the chance to do the update, e.g. for Fedora for the very
first time.

Greetings

            Helge


-- 
      Dr. Helge Kreutzmann                     de...@he...
           Dipl.-Phys.                   http://www.helgefjell.de/debian.php
        64bit GNU powered                     gpg signed mail preferred
           Help keep free software "libre": http://www.ffii.de/