Re: OpenPGP digital signature
On 7/30/24 09:53, imtoas...@mail.com wrote: [Message resent because the year was wrong] Dear all, We are currently considering the following dates as our freeze dates. If you are aware of major clashes of these dates with anything we depend on please let us know. We also like to stress again that we really would like to have a short Hard and Full Freeze (counting in weeks, rather than months), so please plan accordingly. If serious delays turn up during any of the Freeze steps, we rather (partially or completely) thaw bookworm again than staying frozen for a long time. 2023-01-12 - Milestone 1 - Transition and toolchain freeze 2023-02-12 - Milestone 2 - Soft Freeze 2023-03-12 - Milestone 3 - Hard Freeze - for key packages and packages without autopkgtests To be announced - Milestone 4 - Full Freeze On behalf of the Release Team, Paul 2025 I suppose
Re: OpenPGP digital signature
On 30 July 2024 3:35:18 pm GMT+09:00, Yadd wrote: >On 7/30/24 09:53, imtoas...@mail.com wrote: >> >> [Message resent because the year was wrong] >> >> Dear all, >> >> We are currently considering the following dates as our freeze >> dates. If you are aware of major clashes of these dates with anything >> we depend on please let us know. We also like to stress again that we >> really would like to have a short Hard and Full Freeze (counting in >> weeks, rather than months), so please plan accordingly. If serious >> delays turn up during any of the Freeze steps, we rather (partially or >> completely) thaw bookworm again than staying frozen for a long time. >> >> 2023-01-12 - Milestone 1 - Transition and toolchain freeze >> 2023-02-12 - Milestone 2 - Soft Freeze >> 2023-03-12 - Milestone 3 - Hard Freeze - for key packages and >> packages without autopkgtests >> To be announced - Milestone 4 - Full Freeze >> >> On behalf of the Release Team, >> Paul > >2025 I suppose Sounds pretty sus. I doubt if this mail is from the official release team. Doesn't look like Paul's address either.
Re: OpenPGP digital signature
On Tue, 30 Jul 2024 at 10:35:18 +0400, Yadd wrote: > On 7/30/24 09:53, imtoas...@mail.com wrote: > > On behalf of the Release Team, > > Paul Please note that imtoas...@mail.com is (presumably) not Paul, the PGP signature does not validate, the subject line is not what the release team would use, and Paul seems unlikely to send official Debian announcements through a gmx.com mail relay with a (forged?) gmail address as the sender. This appears to be someone attempting to impersonate a release team member, and doing it poorly. Please ignore the message. smcv
Re: OpenPGP digital signature
The original e-mail appears to be this one: https://lists.debian.org/debian-devel/2022/03/msg00251.html It has not been modified. Note that it has an inline and an attached signature. (Both cannot be validated because HTML has broken the signature.) Regards signature.asc Description: This is a digitally signed message part
Bug#1077603: ITP: fcitx5-pinyin-zhwiki -- Fcitx 5 Pinyin Dictionary from zh.wikipedia.org
Package: wnpp Severity: wishlist Owner: Felix Yan X-Debbugs-Cc: debian-devel@lists.debian.org, felixonm...@archlinux.org * Package name: fcitx5-pinyin-zhwiki Version : 0.2.5.20240722 Upstream Contact: Felix Yan * URL : https://github.com/felixonmars/fcitx5-pinyin-zhwiki * License : CC-BY-SA-4.0, Unlicense Programming Lang: Python Description : Fcitx 5 Pinyin Dictionary from zh.wikipedia.org Generated Pinyin dictionary from title and some page content of zh.wikipedia.org, to be used as an additional dictionary for fcitx5 users. I plan to put the package into Debian Input Method Team, and I need a sponsor for this package as well as into the team.
Re: OpenPGP digital signature
Hi, On 30-07-2024 10:21, Simon McVittie wrote: Please note that imtoas...@mail.com is (presumably) not Paul, Correct. the subject line is not what the release team would use, Correct. and Paul seems unlikely to send official Debian announcements through a gmx.com mail relay with a (forged?) gmail address as the sender. Indeed, I wouldn't do that. Please ignore the message. This. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1077623: ITP: google-cloud-cpp -- C++ Client Libraries for Google Cloud Platform
Package: wnpp Severity: wishlist Owner: Darren Bolduc X-Debbugs-Cc: debian-devel@lists.debian.org, dbol...@google.com * Package name: google-cloud-cpp Version : 2.25.0 Upstream Contact: dbolduc * URL : https://cloud.google.com/cpp * License : Apache-2.0 Programming Lang: C++ Description : C++ Client Libraries for Google Cloud Platform A collection of C++ Client Libraries for Google Cloud Platform services, such as Google Cloud Storage and Google Cloud Bigtable. Source code: https://github.com/googleapis/google-cloud-cpp/ I have a package prototype: https://github.com/dbolduc/debian-google-cloud-cpp-prototype g...@debian.org expressed interest in sponsoring this effort. He is helping out with the prototype.
Bug#1077636: ITP: python-changelogd -- Changelogs without conflicts
Package: wnpp Severity: wishlist Owner: Yogeswaran Umasankar X-Debbugs-Cc: debian-devel@lists.debian.org, y...@debian.org * Package name: python-changelogd Version : 0.1.7 Upstream Contact: Andrzej Klajnert * URL : https://gitlab.com/aklajnert/changelogd * License : Expat Programming Lang: Python Description : Changelogs without conflicts Changelogd allows teams to avoid merge conflicts for the changelog files. The ``changelogd`` content is stored within multiple YAML files - one per each changelog entry. Then, during application release, all input files are combined into one release file. The script uses Jinja2 templates to generate one consistent text file out of all input YAML files. The default output format is Markdown, but by modifying the templates it can be changed into any text format you like. Planned to maintain it under DPT.
Bug#1077638: ITP: golang-github-bep-imagemeta -- Go library for reading EXIF, IPTC and XMP image metadata
Package: wnpp Severity: wishlist Owner: Anthony Fok * Package name: golang-github-bep-imagemeta Version : 0.7.4-1 Upstream Author : Bjørn Erik Pedersen * URL : https://github.com/bep/imagemeta * License : Expat Programming Lang: Go Description : Go library for reading EXIF, IPTC and XMP image metadata github.com/bep/imagedata is a Go library for reading EXIF, IPTC and XMP image metadata from JPEG, TIFF, PNG, and WebP files. . This is about READING image metadata Writing is not supported, and never will. . The output of this library is tested against exiftool -n -json. This means, for example, that: . * We use f-numbers and not APEX for aperture values. * We use seconds and not APEX for shutter speed values. * EXIF field definitions are fetched from this table: https://exiftool.org/TagNames/EXIF.html * IPTC field definitions are fetched from this table: https://exiftool.org/TagNames/IPTC.html * The XMP handling is currently very simple, you can supply your own XMP handler (see the HandleXMP option) if you need more. . There are some subtle differences in output: . * Exiftool prints rationale number arrays as space formatted strings with a format/precision that seems unnecessary hard to replicate, so we use strconv.FormatFloat(f, 'f', -1, 64) for these. Reason for packaging: Dependency of hugo (>= 0.130.0)
Bug#1077639: ITP: libcaptcha-recaptcha-v3-perl -- Perl implementation of reCAPTCHA API version v3
Package: wnpp Severity: wishlist Owner: Yadd X-Debbugs-Cc: debian-devel@lists.debian.org, y...@debian.org * Package name: libcaptcha-recaptcha-v3-perl Version : 0.05 Upstream Contact: worthmine * URL : https://metacpan.org/release/Captcha-reCAPTCHA-V3 * License : Artistic or GPL-1+ Programming Lang: Perl Description : Perl implementation of reCAPTCHA API version 3 Perl library for Google's reCAPTCHA version 3. API v2 and v3 are so different, so that this new module is totally distinct than libcaptcha-recaptcha-perl. Will be maintained under Perl Team umbrella
