Re: OpenPGP certificates with SHA-1 issues in Debian keyrings
Hi Guillem, sorry but I am confused... can you explain at a beginner level what is the difference between a certificate and a "key" in the sense it is used in the Developers Reference? Have a nice day, Charles -- Charles Plessy Nagahama, Yomitan, Okinawa, Japan Debian Med packaging team http://www.debian.org/devel/debian-med Tooting from home https://framapiaf.org/@charles_plessy - You do not have my permission to use this email to train an AI -
Bug#1100885: ITP: obs-draw-dock -- Plugin for OBS Studio to draw on any stream output
Package: wnpp Severity: wishlist Owner: Joao Eriberto Mota Filho X-Debbugs-Cc: debian-devel@lists.debian.org, Exeldro * Package name: obs-draw-dock Version : 0.2.0 Upstream Contact: Exeldro * URL : https://obsproject.com/forum/resources/draw.2081/ * License : GPL-2 Programming Lang: C Description : Plugin for OBS Studio to draw on any stream output This plugin allows anyone to draw on any stream output in a dock. It is useful, in some cases, to make freehand drawings or to write on screen. This plugin makes available some drawing tools: pencil, brush, line, rectangle outline, rectangle fill, ellipse outline, ellipse fill, select rectangle and select ellipse. Also is possible to choose colors and the size of the trace.
Bug#1100886: ITP: decibels -- Audio player for GNOME
Package: wnpp Severity: wishlist Owner: Tianyu Chen X-Debbugs-Cc: debian-devel@lists.debian.org, billchenchina2...@gmail.com * Package name: decibels Version : 48.0 Upstream Contact: The GNOME Project (https://gnome.org) * URL : https://gitlab.gnome.org/GNOME/decibels/ * License : GPL Programming Lang: TypeScript Description : Audio player for GNOME An audio player that just plays audio files. It doesn't require an organized music library and won't overload you with tons of functionality. . Audio Player still offers advanced features such as: . * An elegant waveform of the track * Adjustable playback speed * Easy seek controls * Playing multiple files at the same time Part of the packaging job is done on FOSSASIA 2025, as attendees told me that Decibels is still yet not in Debian. The current packaging job happens in https://salsa.debian.org/billchenchina/decibels, but I would happy to move this package to team packaging.
Re: General Questions about Translations and what a package maintainer has to do
On Wed, 19 Mar 2025 10:46:32 +0100, Julien Plissonneau Duquène wrote: >Don't take it personally: as an established maintainer >of i18nized software did you know about this process? No, I didn't. I am arrogant enough to expect that relevant docs are easy to find and in English. I had four years of French in high school, in practice that is barely enough to navigate public transport in Paris. When I try to speak French, every second word is English and the Grammar anyway. Oh, my, am I going to have fun in Brest? Greetings Marc -- Marc Haber | " Questions are the | Mailadresse im Header Rhein-Neckar, DE | Beginning of Wisdom " | Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 6224 1600402
Documentation for Package Maintainers regarding Translations (was: General Questions about Translations and what a package maintainer has to do)
tl;dr: New Wiki Page https://wiki.debian.org/I18n/ForPackageMaintainers, please review Hi, On Tue, Mar 11, 2025 at 12:03:51PM +0100, Marc Haber wrote: Whenever I am angry about something in Debian, I start writing docs. So I try this here, but here I don't know enough to be really helpful. I hope that this rant will start a positive discussion with actual results that I could pour into a Wiki page that might actually help with the pain I am feeling, assuming that many other maintainers feel as well. Sadly, the disusscion didn't really get traction. But there was valueable advice given. You can read up about this in the archive, beginning with my rant, https://lists.debian.org/debian-devel/2025/03/msg00337.html I have put my knowledge and the result of this discussion in a wiki page, https://wiki.debian.org/I18n/ForPackageMaintainers and have also taken the liberty of putting a link in a prominent place of https://wiki.debian.org/I18n I hope this might be helpful to package maintainers in the presence of the majority of docs that is mainly targeted at translations. Sadly, I haven't fond a comfortable solution about handling merge and rebase conflicts in POT and PO files. Additionally, I think that the widely common practice of creating/updating POT and PO files in the debian/rules clean target is somewhere between suboptimal and wrong. I would like you people, especially you on debian-i18n¹, to review the wiki page and give feedback (resp. direct edit the page) to make it the authoritative documentation for package maintiners. Thanks for helping! Greetings Marc ¹ I initially left out debian-i18n deliberately because I think that the target audience is more on debian-devel, but since there are people who think that debian-i18n can help her as well I am Ccing this to debian-i18n. Reply-To is set to debian-devel though, feel free to ignore. I am reading both lists. -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
Bug#1100830: ITP: jeolib-jiplib -- ISPRA JRC image processing for geospatial data library
Package: wnpp Severity: wishlist Owner: Francesco Paolo Lovergine X-Debbugs-Cc: debian-devel@lists.debian.org, Debian GIS Project * Package name: jeolib-jiplib Version : 1.1.5 Upstream Contact: pieter.kempene...@ec.europa.eu * URL : https://github.com/ec-jrc/jeolib-jiplib * License : GPL-3 Programming Lang: C++ and Python Description : ISPRA JRC image processing for geospatial data library This is an intermediate level library written in C++ with Python binding used by JRC PyJeo and possibly other tools. As such it is mainly a dependency for PyJeo implementation, which is a reimplementation of Pktools for direct C/C++ and Python integration. -- ⢀⣴⠾⠻⢶⣦⠀ Francesco Paolo Lovergine ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ 0579 A97A 2238 EBF9 BE61 ⠈⠳⣄ ED02 0F02 A5E1 1636 86A4
Re: General Questions about Translations and what a package maintainer has to do
Le 2025-03-18 18:19, Marc Haber a écrit : In a few cases there is spurious "fuzzing", e.g. when the source message uses `...' for quoting where it shoud have been using \"...\". In some of these cases it may be possible to fix the issue in the source message, but I believe other cases are actually bugs in msgmerge. Are these what your translators are asking you to deal with? Not directly the translators, but many years ago somebody who helped me with making a package fit for translation mentioned that such changes are unfriendly to translators and that one should handle those manually and unfuzz things (in a manual process that seemed clumsy and error-prone to me even back then). It's hard to tell if this advice is still relevant without more details, but IMO expecting the maintainers to unfuzz translations themselves is not a sound workflow, especially if that has to be done manually. On a merge request I would just post comments to ask the translator to fix the headers metadata and licensing, but may still deal with normalizing/rewrapping myself (e.g. by adding a commit to the MR where possible). If this were exchanged over e-mail I would probably fix most trivial things myself. So you're saying that as package maintainer I can freely edit headers and metadata for translations, putting the PO file into a mixed domain between package maintainer and the respective translator? Yes. They hand you the manuscript but you are the editor and printer. Header and metadata changes where the translator is not expected to have any reason to disagree with your changes are fine. You may also tell the translator that you are going to do these changes and give them a few days to react, to be nicer. ³ I have received translations that were obviously done against the POT file from stable. That's a start, I guess. Maybe in these cases you can keep the .po file as submitted for proposed updates, merge it in unstable and nicely ask the translator to also please work on the upcoming version. But translating a stable package does show a blatant non-understanding of Debian's development mechanisms! How am I supposed to trust people who care THIS little about the project they're contributing to? It's not necessarily that they care little, more probably they don't have enough experience with software development or even engineering in general and don't realize the extent of established processes that could be in place, so they don't even search for them, or if they do they don't know what to look for and where. There is actually a fairly elaborate translation workflow, apparently followed by most translation teams but AFAICT only fully documented here [1] (that is, in french) and more specifically here [2] for Debian native software. Don't take it personally: as an established maintainer of i18nized software did you know about this process? Is there a page in english or in translator's language you could refer them to so you could kindly ask them to have their work reviewed and proofread as part of the process (as you can't yourself check that there isn't, for example, inappropriate language in the submitted translation), even though they missed the initial steps? Cheers, [1]: https://www.debian.org/international/french/ [2]: https://www.debian.org/international/french/po -- Julien Plissonneau Duquène
Re: General Questions about Translations and what a package maintainer has to do
Hey Marc, On 3/11/25 12:03 PM, Marc Haber wrote: Basically the same applies for this step than for the POT generation step, with the additional hardship that the PO files are generated, being written to by a program AND STILL contain a significant part of human work. I never know how much work of other people I am destroying by calling msgmerge out of line. In which stage of package build do I do msgmerge? Do I commit the merged po files, when do I commit them, what do I do with them during git merge when a feature branch is merged? I have a bit played around with `msgmerge` and found a way to display a `diff` which contains the translations which will be destroyed if you merge a .po file from a translator * test-de_DE-transl.po into your maintained one * test-de_DE.po in conjunction with the current generated .pot file * test.pot The essential code snippet looks like this ** * * msgmerge -q -C test-de_DE-transl.po test-de_DE.po test.pot \ * > test-de_DE-maint+transl.po * msgmerge -vv -q -C test-de_DE.po test-de_DE-transl.po test.pot \ * > test-de_DE-transl+maint.po * * # Print out the new merged .po file * cat test-de_DE-transl+maint.po * * # Show the diff of destroyed translations (including comments) * diff -u test-de_DE-maint+transl.po test-de_DE-transl+maint.po * ** The order of the `msgid`s are not necessary in the .po files and will be defined in the .pot file. Also comments and headers diffs will be printed out. For all of my test cases (I could imagine) it works very well. You can try it out: I put an example implementation in a Makefile and put it together with a small test-translation into a tarball attachmented to this email. You just need to run $> make all With `make clean` you can delete the two temporary files. The output of the makefile in the tarball is appended to this email. Hopefully it helps for progression, Dirk =) ** * msgmerge-show-overridden.tar.gz * * Begin of output ** make all msgmerge -q -C test-de_DE-transl.po test-de_DE.po test.pot > test-de_DE-maint+transl.po msgmerge -vv -q -C test-de_DE.po test-de_DE-transl.po test.pot > test-de_DE-transl+maint.po test.pot:11: this message is used but not defined in test-de_DE-transl.po test.pot:32: this message is used but not defined... test-de_DE-transl.po:21: ...but this definition is similar Read 1 old + 1 reference, merged 9, fuzzied 1, missing 1, obsolete 1. New test-de_DE.po cat test-de_DE-transl+maint.po msgid "" msgstr "" "Language: German\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" "X-Generator: PhraseApp (phraseapp.com)\n" msgid "boolean_key" msgstr "" msgid "pluralized_key" msgid_plural "" msgstr[0] "" msgstr[1] "" # Translator: Overridden comment msgid "key_with_description" msgstr "" msgid "empty_string_translation" msgstr "" msgid "nested.key" msgstr "Fuzzy" msgid "null_translation" msgstr "" #, fuzzy msgid "nested.deeply.key" msgstr "Fuzzy" msgid "sample_collection" msgstr "" msgid "unverified_key" msgstr "" msgid "simple_key" msgstr "Einfacher Translator Stirng" Overridden by translator diff -u test-de_DE-maint+transl.po test-de_DE-transl+maint.po || true --- test-de_DE-maint+transl.po 2025-03-19 14:52:18.567974496 +0100 +++ test-de_DE-transl+maint.po 2025-03-19 14:52:18.571974539 +0100 @@ -4,7 +4,7 @@ "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"Plural-Forms: nplurals=3; plural=(n > 2);\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" "X-Generator: PhraseApp (phraseapp.com)\n" msgid "boolean_key" @@ -15,7 +15,7 @@ msgstr[0] "" msgstr[1] "" -# Maintainer: I'm a very important description for this key! +# Translator: Overridden comment msgid "key_with_description" msgstr "" @@ -39,4 +39,4 @@ msgstr "" msgid "simple_key" -msgstr "Einfacher Maintainer Stirng" +msgstr "Einfacher Translator Stirng" ** * End of output * * msgmerge-show-overridden.tar.gz ** msgmerge-show-overridden.tar.gz Description: application/gzip OpenPGP_0xE2A3766F21F02BD5.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
