Bug#1003855: RFS: kotlin-mode/20210917git0-1 [RFP] -- Emacs major mode for kotlin
Hi Joshua, Joshua Peisach writes: > Hi Nicholas, > > The pristine-tar branch is already pushed. And finals won't be happening > until April ish > > https://salsa.debian.org/emacsen-team/kotlin-mode/-/tree/pristine-tar > > > Is something missing? Ah, sorry, I was scanning for a 0.*~ prefixed version and communicated poorly. This is needed to defend against the use of an epoch whenever upstream switches to a tagging stable version, ie 20210917git0 sorts higher than 1.0.0. The cause of this was overriding uscan's "pretty" option in debian/watch. I made the necessary fixups and uploaded. Please review the changes at your leisure :-) Cheers, Nicholas P.S. I chose to enforce xz compression because you're using uscan's git mode, which makes the argument for github release tarballs nonapplicable. For some reason your copy of uscan downloaded an orig.tar.gz instead of an orig.tar.xz, and this gbp.conf will prevent "what is going on?!" moments from emerging. signature.asc Description: PGP signature
Re: Looking for a new maintainer for the "rush" package
On Thu, Mar 17, 2022 at 09:19:54PM +0100, Mats Erik Andersson wrote: > The truth is that I am in no position to verify my identity > to the Debian project, ever since the time it began demanding > three signatures of trust. So even if I desired to commence fwiw you need 2 (not 3) signatures from DDs in the process of becoming a DD (uploading or not) yourself to proof – as you say – your identity to avoid identity theft and other trickery by bad actors. To become a DM you only need one. (And that is only the common case. There is some leeway in the processes if it proves hard, like in the last few years. Your advocates and Application Managers are your friends, not some uptight nitpickers) Neither status nor any signature at all is needed to maintain a package. You can find a sponsor (usually a DD) who reviews your package and can sign it off for you – this very mailing list is one possible place to find such sponsors. (Having worked with sponsors is another corner stone of becoming a DM or DD as they will advocate for your skill both technical and social – something a mere signature on a key does not provide) I am sure you know this already as you had a few sponsors over the years as can be seen on the tracker overview, I am just mentioning it for the rest of the audience here who might not all be as experienced. > for me to achieve that endeavour. Therefore I hereby annonce > my desire for another responsible and devoted person to take > over maintenance of "gnurush". This is a piece of software The standard way of announcing this desire is to either "orphan" (O) or "request an adoption" (RFA) of the package. You can read more about this in the developer reference [0] and the wnpp page [1]: [0] https://debian.org/doc/manuals/developers-reference/pkgs.en.html#orphaning-a-package [1] https://debian.org/devel/wnpp/ You are also noted as the maintainer of 17 other packages. If you do not want to go through this process yourself, you could e.g. notify the MIA team so they can orphan the packages for you as they tend to do for people who have for whatever reason "disappeared". It is much better for everyone if stepping down is done responsibly as it avoids lengthy processes in which people will try to contact you to get permission for "salvaging" (as previously mentioned in the thread), non-maintainer uploads and so on. > I did try my best during a period in time, but now I leave! Thanks for your work & best of luck in your future endeavours, whatever they may be – and who knows, perhaps they lead you back to contributing to Debian again some day! Until then: Best regards David Kalnischkies signature.asc Description: PGP signature
Bug#1003855: convert RFP to ITP and set owner
retitle 922934 ITP: kotlin-mode -- Emacs major mode for editing Kotlin files owner 922934 Joshua Peisach thanks Joshua, please take care to select the *reply to all* function rather than "reply" in the future, because bug_num...@bugs.debian.org should be kept in CC. Debian is developed in the open, and not via private messages.
Re: Looking for a new maintainer for the "rush" package
Torsdag den 17 mars 2022, klockan 15:22, skrev Nicholas D Steeves detta: > > From a thread on debian-mentors, > > vimer writes: > > > Hi, > > On Tue, Mar 15, 2022 at 05:23:16AM -0700, deb...@lewenberg.com wrote: > >>The Debian package "rush" has not been updated since 2017. The > >>upstream software is actively maintained and has advanced from the 1.x > >>version in Debian to version 2.x (the latest version is 2.2 released > >>Jan 2022). I filed a bug in Dec 2021 to have the upstream changes > >>packaged, but no response from the package maintainer was forthcoming. > >> > >>Is there someone who can take over the maintenance of this package? > > In case the maintainer does not mark the package as 'O'(Orphaned) package, > > we can do some fix or update with NMU[0]. > > > > But it's would better to do NMU for active Debian Developer. > > > > Given the OP asked for "someone who can take over the maintenance of > this package", and given the state of the package, salvaging "rush" > would be more appropriate: > > https://wiki.debian.org/PackageSalvaging > > https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging > > #929160 justifies a minimal NMU fixing only that bug. > > I've CCed Mats, because the best solution is for the maintainer to take > care of this :-) > > Anyone interested in pursuing the process may follow the Developers > Reference section "How to salvage a package"; Please note that the > maintainer also has rights, so one must wait 21 days after filing the > ITS before proceeding with the salvage operation. > > > Regards, > Nicholas The truth is that I am in no position to verify my identity to the Debian project, ever since the time it began demanding three signatures of trust. So even if I desired to commence an up-to-date packaging effort, there is no sensible means for me to achieve that endeavour. Therefore I hereby annonce my desire for another responsible and devoted person to take over maintenance of "gnurush". This is a piece of software that deserves continued use under diligent maintainership. I did try my best during a period in time, but now I leave! Best regards, Mats Erik Andersson, dr sci math
Re: Looking for a new maintainer for the "rush" package
From a thread on debian-mentors, vimer writes: > Hi, > On Tue, Mar 15, 2022 at 05:23:16AM -0700, deb...@lewenberg.com wrote: >>The Debian package "rush" has not been updated since 2017. The >>upstream software is actively maintained and has advanced from the 1.x >>version in Debian to version 2.x (the latest version is 2.2 released >>Jan 2022). I filed a bug in Dec 2021 to have the upstream changes >>packaged, but no response from the package maintainer was forthcoming. >> >>Is there someone who can take over the maintenance of this package? > In case the maintainer does not mark the package as 'O'(Orphaned) package, > we can do some fix or update with NMU[0]. > > But it's would better to do NMU for active Debian Developer. > Given the OP asked for "someone who can take over the maintenance of this package", and given the state of the package, salvaging "rush" would be more appropriate: https://wiki.debian.org/PackageSalvaging https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging #929160 justifies a minimal NMU fixing only that bug. I've CCed Mats, because the best solution is for the maintainer to take care of this :-) Anyone interested in pursuing the process may follow the Developers Reference section "How to salvage a package"; Please note that the maintainer also has rights, so one must wait 21 days after filing the ITS before proceeding with the salvage operation. Regards, Nicholas signature.asc Description: PGP signature
Bug#1003855: (everything)
Hi Joshua, So, would you like me to take care of converting the RFP to an ITP, and adding taku0 to the copyright holders? I'm part of the Debian Emacsen Team so also take care of the other nitpicks in git; they're not release critical blockers, so go into the -2 source-only upload. Regards, Nicholas signature.asc Description: PGP signature
Bug#1007807: marked as done (RFS: urlwatch/2.25-1 -- monitors webpages for you)
Your message dated Thu, 17 Mar 2022 12:50:23 +0100 with message-id <6b72afab-fd69-c85f-6e4c-640e99a37...@debian.org> and subject line Re: RFS: urlwatch/2.25-1 -- monitors webpages for you has caused the Debian Bug report #1007807, regarding RFS: urlwatch/2.25-1 -- monitors webpages for you to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1007807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007807 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "urlwatch": * Package name: urlwatch Version : 2.25-1 Upstream Author : Thomas Perl * URL : https://thp.io/2008/urlwatch/ * License : BSD-3-clause * Vcs : https://salsa.debian.org/mwerlen/urlwatch Section : web It builds those binary packages: urlwatch - monitors webpages for you To access further information about this package, please visit the following URL: https://mentors.debian.net/package/urlwatch/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/u/urlwatch/urlwatch_2.25-1.dsc Changes since the last upload: urlwatch (2.25-1) unstable; urgency=medium--- End Message ---
Bug#998046: RFS: fcitx5-table-extra/5.0.7-1 [ITP] -- Flexible Input Method Framework - Zhengma-Pinyin table
Thank you for your reminder, I am processing it locally. Bastian Germann 于2022年3月17日周四 09:27写道： > Control: tags -1 - moreinfo > > On Tue, 30 Nov 2021 06:19:24 + YaNing Lu wrote: > > ok I'll deal with it as soon as possible. > > I have found the package to be updated. Please do not forget to update the > RFS (untag moreinfo) > after that. > >
Bug#998046: marked as done (RFS: fcitx5-table-extra/5.0.7-1 [ITP] -- Flex. Input Method Framework Zhengma-Pinyin)
Your message dated Thu, 17 Mar 2022 11:49:36 +0100 with message-id and subject line Re: RFS: fcitx5-table-extra/5.0.7-1 [ITP] -- Flexible Input Method Framework - Zhengma-Pinyin table has caused the Debian Bug report #998046, regarding RFS: fcitx5-table-extra/5.0.7-1 [ITP] -- Flex. Input Method Framework Zhengma-Pinyin to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 998046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998046 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "fcitx5-table-extra": * Package name: fcitx5-table-extra Version : 5.0.5+git20211025.35e5217-1 Upstream Author : 2012 Xuetian Weng * URL : https://github.com/fcitx/fcitx5-table-extra * License : GPL-3, GPL-2+ * Vcs : https://salsa.debian.org/Dami/fcitx5-table-extra Section : utils It builds those binary packages: fcitx5-table - Flexible Input Method Framework fcitx5-table-array30 - Flexible Input Method Framework - Array30 table fcitx5-table-array30-large - Flexible Input Method Framework - Array30-Large table fcitx5-table-boshiamy - Flexible Input Method Framework - Boshiamy table fcitx5-table-cangjie-large - Flexible Input Method Framework - Cangjie-Large table fcitx5-table-cangjie3 - Flexible Input Method Framework - Cangjie3 table fcitx5-table-cangjie5 - Flexible Input Method Framework - Cangjie5 table fcitx5-table-cantonese - Flexible Input Method Framework - Cantonese table fcitx5-table-cantonhk - Flexible Input Method Framework - Cantonhk table fcitx5-table-easy-large - Flexible Input Method Framework - Easy-Large table fcitx5-table-jyutping - Flexible Input Method Framework - Jyutping table fcitx5-table-quick-classic - Flexible Input Method Framework - Quick-Classic table fcitx5-table-quick3 - Flexible Input Method Framework - Quick3 table fcitx5-table-quick5 - Flexible Input Method Framework - Quick5 table fcitx5-table-scj6 - Flexible Input Method Framework - Scj6 table fcitx5-table-stroke5 - Flexible Input Method Framework - Stroke5 table fcitx5-table-t9 - Flexible Input Method Framework - T9 table fcitx5-table-wu - Flexible Input Method Framework - Wu table fcitx5-table-wubi-large - Flexible Input Method Framework - Wubi-Large table fcitx5-table-zhengma - Flexible Input Method Framework - Zhengma table fcitx5-table-zhengma-large - Flexible Input Method Framework - Zhengma-Large table fcitx5-table-zhengma-pinyin - Flexible Input Method Framework - Zhengma-Pinyin table To access further information about this package, please visit the following URL: https://mentors.debian.net/package/fcitx5-table-extra/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/f/fcitx5-table-extra/fcitx5-table-extra_5.0.5+git20211025.35e5217-1.dsc Changes for the initial release: fcitx5-table-extra (5.0.5+git20211025.35e5217-1) unstable; urgency=low . * Initial release. (Closes: #997975) Regards, -- Lu YaNing --- End Message --- --- Begin Message --- Thanks for your contribution.--- End Message ---
Bug#998046: RFS: fcitx5-table-extra/5.0.7-1 [ITP] -- Flexible Input Method Framework - Zhengma-Pinyin table
Control: tags -1 - moreinfo On Tue, 30 Nov 2021 06:19:24 + YaNing Lu wrote: ok I'll deal with it as soon as possible. I have found the package to be updated. Please do not forget to update the RFS (untag moreinfo) after that.
Bug#1007807: RFS: urlwatch/2.25-1 -- monitors webpages for you
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "urlwatch": * Package name: urlwatch Version : 2.25-1 Upstream Author : Thomas Perl * URL : https://thp.io/2008/urlwatch/ * License : BSD-3-clause * Vcs : https://salsa.debian.org/mwerlen/urlwatch Section : web It builds those binary packages: urlwatch - monitors webpages for you To access further information about this package, please visit the following URL: https://mentors.debian.net/package/urlwatch/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/u/urlwatch/urlwatch_2.25-1.dsc Changes since the last upload: urlwatch (2.25-1) unstable; urgency=medium
