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?

Adam Lewenberg

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi,
On Tue, Mar 15, 2022 at 05:23:16AM -0700, deb251@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.

BR,
vimer

Adam Lewenberg

[0]: https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#nmu

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From a thread on debian-mentors,

vimer <tsu.yubo@gmail.com> writes:

Hi,
On Tue, Mar 15, 2022 at 05:23:16AM -0700, deb251@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

--=-=-Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQJEBAEBCgAuFiEE4qYmHjkArtfNxmcIWogwR199EGEFAmIzimwQHHN0ZW5AZGVi aWFuLm9yZwAKCRBaiDBHX30QYZAoEACvKdIlIqsFDEXVcdhT6zVBekrvR4cRLELc woyZtAXfdQepCWLczp0q87vYmXscLvqPen1LIYQ2c5m2CerJyNgN7A6qt+KuGGud OaP48URWYwyrUyrhLTXppb/LO09wM0SFk2XwB8N9EA9DTSDBycd34PT0kZ+GBfC6 e8v5jyGDHpTNgKo9IbYd8dKGFyhC1aOU9gVnPf8hNJzmd9kGezvmsxgLwm1FyopC ptXbTzYmacc9fNA3gR9sxdkmMY1z9BBVcGkLaUU3RwlOBgnbz5rta9EPvG1jnkn3 Fd4InHErDTkPcCFHvndtdPiFTqa6UTHl2381YyjEmr/XgZJR8mFjZXodb65FYCI6 Y8eTHWI2j9CAaxv/Prgnsk+m6lIUWzF2RvhkxxGQGDrokSY77z4gftg/ls9k7d6o Hzw0FKGHQAlTtbssK1Q5dTPp7vKTOgWwUHg5NCAYWGmP/Eri3QL17K5Z3+kHEgCn YA2lDOO6Gbse39I6aV4CjrHg3KXAdCl/MtRoc6Vytp6jPbPYraEnbTgiEwCl5wyK X9L1WIeRRYxhfrIbfI0HHbu2f9Q+MGz4yQ4kR+OHC27ofgA4oTis8ZT8V2o85zeF AV+ElwtUsQiAEJ3rv3Kt0gv9Some9emrWS9llo5Dh0rgWF3T/x0ndCRcydCMFKBO 0gqPm3JtqQ==sJj5
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Torsdag den 17 mars 2022, klockan 15:22, skrev Nicholas D Steeves detta:

From a thread on debian-mentors,

vimer <tsu.yubo@gmail.com> writes:

Hi,
On Tue, Mar 15, 2022 at 05:23:16AM -0700, deb251@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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEE5sn+Q4uCja/tn0GrMRvlz3HQeIMFAmIzsKAACgkQMRvlz3HQ eIMc0Q//QL138mJsl5kGD7kUWilqrxHR6gtU1pulcgxTr1qPz/UgrXqgEfqAaw6A lvGKFM1E+t09YBd2TqZBu41WGgiSIl9at7FnT3SUH2yDWtRGwv200iWtfVe1Qeu4 yhCsTGBoJ+OJnj0V+8je23WM4oO1pe16IuMRHmA82dSwvSG3LPbpE8Qh3CQx6j/d aFeYi4Pax/ktfmIeiMOAcBccyLCDRxGQXxIfhztVXybIahv3komdN0eRtl62Tkfx uUH/b0qmFCD145JtccD/FGImcECD3AuJPlvjugBEfPb0QxA5wz3z1LhM9Ie0H4FY +CwA5pGP/xI9/NjDON3cPhNWDiGFM7gJL2KK5DOriCIu9aAg+jUrAhKGrc8EkXOW G+nfcgWoD+tl5m0LBQh5+gbvAQ/Vr/FR6cu+MXRoENb7HoJauT+RzQwyucBVdE86 ZJNjG8kYx3uqcGLIM7bD8roCyyHB6s4qtQG4KSrIiWgdKmjMGZTNDX3RP2K/AAbr I+2ixMT4mZE22Iab7pRYJ/cI2QPyUwtKofe3Dum2njmTVLt1w+a0yYd/YbW5p1nj XFOhAkOSswlnZJjkjPtQat7Eu1vuQ4nBLoeE+PwllulKVGtC2UKJE71gJpNv3q+a rwYIGxzu8u2rKiB75oKwAjLqd2iJWDh0LjF6w4fw+wYL2uLkMvY=
=0zeE
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 3/16/2022 3:53 AM, vimer wrote:

Hi,
On Tue, Mar 15, 2022 at 05:23:16AM -0700, deb251@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.

So is there anything else I can do to expedite this? Or do I just wait
until a Debian Developer picks up the package?

Thank you,
Adam Lewenberg

BR,
vimer

Adam Lewenberg

[0]:
https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#nmu

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi,

On Sun, Mar 20, 2022 at 4:19 AM <deb251@lewenberg.com> wrote:

On 3/16/2022 3:53 AM, vimer wrote:

Hi,
On Tue, Mar 15, 2022 at 05:23:16AM -0700, deb251@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.

So is there anything else I can do to expedite this? Or do I just wait
until a Debian Developer picks up the package?

I think Nicholas's answer is right. We can try to salvage packages for the

rush case.
You can refer to [0][1] to report a bug as ITS(Intend To Salvage).

But there are some situations that are unclean for me:
If you file an ITS bug, that is mean the package's new(co-) packages are
you.

[0]: https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#how-to-salvage-a-package

[1]: https://lists.debian.org/debian-devel/2018/07/msg00453.html

BR,
Bo

Thank you,
Adam Lewenberg

BR,
vimer

Adam Lewenberg

[0]: https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#nmu

<div dir="ltr"><div dir="ltr">Hi,</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Mar 20, 2022 at 4:19 AM &lt;<a href="mailto:deb251@lewenberg.com">deb251@lewenberg.com</a>&gt; wrote:<br></div><blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 3/16/2022 3:53 AM, vimer wrote:<br>
&gt; Hi,<br>
&gt; On Tue, Mar 15, 2022 at 05:23:16AM -0700, <a href="mailto:deb251@lewenberg.com" target="_blank">deb251@lewenberg.com</a> wrote:<br>
&gt;&gt; The Debian package &quot;rush&quot; has not been updated since 2017. The<br>
&gt;&gt; upstream software is actively maintained and has advanced from the 1.x<br>
&gt;&gt; version in Debian to version 2.x (the latest version is 2.2 released<br>
&gt;&gt; Jan 2022). I filed a bug in Dec 2021 to have the upstream changes<br> &gt;&gt; packaged, but no response from the package maintainer was forthcoming.<br>
&gt;&gt;<br>
&gt;&gt; Is there someone who can take over the maintenance of this package?<br>
&gt; In case the maintainer does not mark the package as &#39;O&#39;(Orphaned) package,<br>
&gt; we can do some fix or update with NMU[0].<br>
&gt; <br>
&gt; But it&#39;s would better to do NMU for active Debian Developer.<br>

So is there anything else I can do to expedite this? Or do I just wait <br> until a Debian Developer picks up the package?<br>
<br></blockquote><div>I think Nicholas&#39;s answer is right. We can try to salvage packages for the rush case.</div><div>You can refer to [0][1] to report a bug as ITS(Intend To Salvage). </div><div><br></div><div>But there are some situations that
are unclean for me:</div><div>If you file an  ITS bug, that is mean the package&#39;s new(co-) packages are you.</div><div><br></div><div>[0]: <a href="https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#how-to-salvage-a-package">https:
//www.debian.org/doc/manuals/developers-reference/pkgs.en.html#how-to-salvage-a-package</a> </div><div>[1]: <a href="https://lists.debian.org/debian-devel/2018/07/msg00453.html">https://lists.debian.org/debian-devel/2018/07/msg00453.html</a></div><div><

</div><div>BR,</div><div>Bo</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">

Thank you,<br>
Adam Lewenberg<br>


&gt; <br>
&gt; BR,<br>
&gt; vimer<br>
&gt;&gt;<br>
&gt;&gt; Adam Lewenberg<br>
&gt;&gt;<br>
&gt; [0]: <br>
&gt; <a href="https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#nmu" rel="noreferrer" target="_blank">https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#nmu</a><br>

</blockquote></div></div>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Mon, Mar 21, 2022 at 10:02 AM Bo YU <tsu.yubo@gmail.com> wrote:

Hi,

On Sun, Mar 20, 2022 at 4:19 AM <deb251@lewenberg.com> wrote:

On 3/16/2022 3:53 AM, vimer wrote:

Hi,
On Tue, Mar 15, 2022 at 05:23:16AM -0700, deb251@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.

So is there anything else I can do to expedite this? Or do I just wait
until a Debian Developer picks up the package?

I think Nicholas's answer is right. We can try to salvage packages for

the rush case.
You can refer to [0][1] to report a bug as ITS(Intend To Salvage).

But there are some situations that are unclean for me:
If you file an ITS bug, that is mean the package's new(co-) packages are you.

BTW, I have an ITA package and packaging it. Certainly, there is still some knowledge to learn for me.
That is, I have no confidence in having two or more packages to deal with
at the same time. Once done,
I am glad to salvage the rush package :-)

[0]: https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#how-to-salvage-a-package

[1]: https://lists.debian.org/debian-devel/2018/07/msg00453.html

BR,
Bo

Thank you,
Adam Lewenberg

BR,
vimer

Adam Lewenberg

[0]:

https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#nmu

<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Mar 21, 2022 at 10:02 AM Bo YU &lt;<a href="mailto:tsu.yubo@gmail.com">tsu.yubo@gmail.com</a>&gt; wrote:<br></div><blockquote class="gmail_
quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr">Hi,</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Mar 20, 2022 at 4:19 AM &lt;<a href="mailto:
deb251@lewenberg.com" target="_blank">deb251@lewenberg.com</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 3/16/2022 3:53 AM, vimer wrote:<br>
&gt; Hi,<br>
&gt; On Tue, Mar 15, 2022 at 05:23:16AM -0700, <a href="mailto:deb251@lewenberg.com" target="_blank">deb251@lewenberg.com</a> wrote:<br>
&gt;&gt; The Debian package &quot;rush&quot; has not been updated since 2017. The<br>
&gt;&gt; upstream software is actively maintained and has advanced from the 1.x<br>
&gt;&gt; version in Debian to version 2.x (the latest version is 2.2 released<br>
&gt;&gt; Jan 2022). I filed a bug in Dec 2021 to have the upstream changes<br> &gt;&gt; packaged, but no response from the package maintainer was forthcoming.<br>
&gt;&gt;<br>
&gt;&gt; Is there someone who can take over the maintenance of this package?<br>
&gt; In case the maintainer does not mark the package as &#39;O&#39;(Orphaned) package,<br>
&gt; we can do some fix or update with NMU[0].<br>
&gt; <br>
&gt; But it&#39;s would better to do NMU for active Debian Developer.<br>

So is there anything else I can do to expedite this? Or do I just wait <br> until a Debian Developer picks up the package?<br>
<br></blockquote><div>I think Nicholas&#39;s answer is right. We can try to salvage packages for the rush case.</div><div>You can refer to [0][1] to report a bug as ITS(Intend To Salvage). </div><div><br></div><div>But there are some situations that
are unclean for me:</div><div>If you file an  ITS bug, that is mean the package&#39;s new(co-) packages are you.</div></div></div></blockquote><div>BTW, I have an ITA package and packaging it. Certainly, there is still some knowledge to learn for me.</

<div>That is, I have no confidence in having two or more packages to deal with at the same time. Once done,</div><div>I am glad to salvage the rush package :-)</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px

solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div><br></div><div>[0]: <a href="https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#how-to-salvage-a-package" target="_blank">https://www.debian.org/doc/
manuals/developers-reference/pkgs.en.html#how-to-salvage-a-package</a> </div><div>[1]: <a href="https://lists.debian.org/debian-devel/2018/07/msg00453.html" target="_blank">https://lists.debian.org/debian-devel/2018/07/msg00453.html</a></div><div><br></

<div>BR,</div><div>Bo</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">

Thank you,<br>
Adam Lewenberg<br>


&gt; <br>
&gt; BR,<br>
&gt; vimer<br>
&gt;&gt;<br>
&gt;&gt; Adam Lewenberg<br>
&gt;&gt;<br>
&gt; [0]: <br>
&gt; <a href="https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#nmu" rel="noreferrer" target="_blank">https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#nmu</a><br>

</blockquote></div></div>
</blockquote></div></div>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Mon, Mar 21, 2022 at 10:02:03AM +0800, Bo YU wrote:

But there are some situations that are unclean for me:
If you file an ITS bug, that is mean the package's new(co-) packages are you.

Sure, ITS means you want to maintain the package.
"I want the package to be updated but don't want to maintain it" doesn't
really have a solution. Even NMUing it to a new upstream version is not a solution, and is usually frowned upon.

--
WBR, wRAR

-----BEGIN PGP SIGNATURE-----

iQJhBAABCgBLFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAmI4JqEtFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEDNi9wMaSZLh BVUP/2BqGLT+UZT6bsDfsTpKpxOy5EQVbgghLFsvvXz1J+rmz+jTvxpqbPOio5hv Im2/yCiPzwpdsRaWhmjLGLUyc0Z8rA5JaAfTd3xG1MSWWwl/GuKt+qGsFrS/ff1/ gNcjeoI7rCr1sXhdwTnOqw049wouTds6TyBR2O4hj7sYAe+bj+lASYYtisJX/bl1 40jI8zWToO4Z25zaiKxsf/4Xjq3qMZn6wImDDvAL5eaQ/cZupRZJBvvicLS3hFjE 2AcnbRI7MxX2uaHyj/zRSFo25gz4YDoIDShu5zkPoGDn9ybWc2bPWvyv95AYc/0/ jsQfN3oiUjnx6/r2mCJem2/k0cojIjbhfsAGUJEwFQA1A1Xy1e6dlXJqrIMtMc1W CDk6kYxANP3oOOesV0/1Qvo7rNvECvQ62dubJ5CDYr7TsYjZprc9bpu7CZfc8QVE 3pqWfT1v2sQfVVWuTqz8BU8y3rPW8+qVT9hJUy3z+rtWC+TWYt9Hc2gofwgy0lRW 2XZ0CQxNVaFH8pomrBUznnqSpEdbpA6eb7cdUnzN7/NauXQP+JQ6X8OxILJuOUH3 NLVfzo76H5K9b5Svilpq8GwJ1MMq7EMlDyoMNScvFdnNxhebCzusaHwEvFb9xxjq m0hsneRLzJSVgD/exSgD/SiueVAU8hSpc/w02Scf0X2Upnfa
=dC5y
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Em 17/03/2022 17:19, Mats Erik Andersson escreveu:

Torsdag den 17 mars 2022, klockan 15:22, skrev Nicholas D Steeves detta:

From a thread on debian-mentors,

vimer <tsu.yubo@gmail.com> writes:

Hi,
On Tue, Mar 15, 2022 at 05:23:16AM -0700, deb251@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

Greetings,

Since Mats has expressed his desire to pass the package on to a
new maintainer, I'm guessing it's not necessary to go through
the salvage process. Therefore an ITS would be unnecessary and
one could adopt the package directly.

Maybe orphan the package, then open an ITA.

So I ask, is there anyone working on this package?

If not, I believe I can adopt it.

Cheers

--
⢀⣴⠾⠻⢶⣦
⣾⠁⢠⠒⠀⣿⡁ Fabio Augusto De Muzio Tobich
⢿⡄⠘⠷⠚⠋⠀ 9730 4066 E5AE FAC2 2683 D03D 4FB3 B4D3 7EF6 3B2E ⠈⠳⣄

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Dear Mats, Fabio, and MIA Team,

Mats, would you please skip the "Hi Mats," section below?

MIA Team, It sounds like Mats probably intends to retire, but this
conclusion isn't beyond reasonable doubt--so this Maintainer's packages
are in a limbo state. TLDR; David Kalnischkies recommended contacting
your team 2022-03-17, and Mats has not yet followed up on the
debian-mentors thread. Given that it's almost been a month without
follow-up, I feel that opening a ticket is justified, pending
clarification. Maybe you will interpret the record differently and
understand that Mats expresses a more strong intent to leave than I
understood?

"Fabio A. De Muzio Tobich" <ftobich@debian.org> writes:

Em 17/03/2022 17:19, Mats Erik Andersson escreveu:

Torsdag den 17 mars 2022, klockan 15:22, skrev Nicholas D Steeves detta:

From a thread on debian-mentors,

vimer <tsu.yubo@gmail.com> writes:

Hi,
On Tue, Mar 15, 2022 at 05:23:16AM -0700, deb251@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? [snip]

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:

[snip]

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.

[snip]

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

Hi Mats,

As David Kalnischkies noted, identity verification is not required for sponsored uploads, but only for the "Debian Maintainer" (uploading
rights granted for a select list of packages) role. Given that your
retirement is predicated on "there is no sensible means for me to
achieve [identity verification]", and identity verification is not in
fact required, the conclusion does not follow from the premise,
resulting in an ambiguous state. Are you interested in continuing to
maintain your packages, or would you like to Orphan all of them, or
would you like to orphan only a subset of them?

I noticed that you maintain more than a few packages :-) Thank you for
your work! If it would be too much of a hassle to file Orphan bugs for
all of your packages then would you please reply to at least
mia@qa.debian.org ? I've added them to CC for your convenience, as well
as to tentatively initiate the investigation process.

Let them know that you're retiring from Debian, if that's what you
intent to do. I feel like that's probably what you intend, but Debian
has extensive formal processes in place to prevent people from hijacking
the work of others, and this is one of those processes. That said, I
always hope that Maintainers will resume contributions!

Greetings,

Hi Fabio!

Since Mats has expressed his desire to pass the package on to a
new maintainer, I'm guessing it's not necessary to go through
the salvage process. Therefore an ITS would be unnecessary and
one could adopt the package directly.

Maybe orphan the package, then open an ITA.

I've initiated the MIA process; although, I hope that Mats didn't
actually intent to retire.

So I ask, is there anyone working on this package?

Well, no one filed an ITS, which is too bad because the 21 day wait
would have expired by now.

If not, I believe I can adopt it.

That's great news! :-) As I interpreted the discussion, lots of people
would like to see GNU Rush updated, but no one wanted to maintain it
long-term.


Kind regards,
Nicholas

--=-=-Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQJEBAEBCgAuFiEE4qYmHjkArtfNxmcIWogwR199EGEFAmJbWKkQHHN0ZW5AZGVi aWFuLm9yZwAKCRBaiDBHX30QYbGDD/9GO1g1ORigKvt0yGxA895wEpGkBm2N8MxJ z6lq6WV8kqmzBM1PAPfjq2h7/9zuwlC5Orz1Auxs6/Qv1gCPqPAnzu+iY+LA7+FN i3KZ/XhlDTI/xHCVdxBX2rP5CFzc0WmklQ61XmuqOpGUrA2AYAQ0gv/6ga4SR9WK RV9W9E2dubL3WoRFwWiRYODm4ahOYItNTnHz37/sNeH8SnVB4BgrYiCFV3UvlqnR UP24PMq1xDRi701q6t6tuFPATkQdo07nPeAvLKyXcSKWNL+wbtRco+W9pH50z9tf 97oGzb/Cy/LrqFUFZUp7XVxXSPLri+NFlIq58KjrpDq79Iv0q7dbaYmOV6wrhHar IKM96DpkDJsi1BcOAeCqI9e945y4p88/JdBNe+lUeA6Hp2Yc3CXvEJzkb1KQArxs ewdVJCjsohdQRN8o0FI+EI9ZgnP0C8zYkIxKYkYqQgaOv7dRuWZlnOW3LyWk51QL k6JM95P5GJ3GQvr/u/ziOVyV3qeksPI4eASIen/IJMLcV2v3Usn8mk5VNg9luCNi jveBOfYl3MDcDJR7cqSU4OeLpYVRijAHESTTt5kawKGIeqvyUNjB+evqq0ruX9OS Czl7sUFhldxuVYnVdgIU6ehrhl58G7dh1/KQoSZUurK5ahLcsK9RIu4PFIZs1BZR Ue4qobgAwg==tyx5
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi,
On Fri, Apr 15, 2022 at 09:03:42AM -0300, Fabio A. De Muzio Tobich wrote:

Em 17/03/2022 17:19, Mats Erik Andersson escreveu:

Torsdag den 17 mars 2022, klockan 15:22, skrev Nicholas D Steeves detta:

From a thread on debian-mentors,

vimer <tsu.yubo@gmail.com> writes:

Hi,
On Tue, Mar 15, 2022 at 05:23:16AM -0700, deb251@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

Greetings,

Since Mats has expressed his desire to pass the package on to a
new maintainer, I'm guessing it's not necessary to go through
the salvage process. Therefore an ITS would be unnecessary and
one could adopt the package directly.

Maybe orphan the package, then open an ITA.

So I ask, is there anyone working on this package?

If not, I believe I can adopt it.

Fabio, do you mind I adopt it?
I know this is a little offend to ask the wanted. Because I was umfamiliar
with procedure about such packages that do not submit "ITO" bugs about
several weeks ago.

BR,
Bo

Cheers

--
⢀⣴⠾⠻⢶⣦
⣾⠁⢠⠒⠀⣿⡁ Fabio Augusto De Muzio Tobich
⢿⡄⠘⠷⠚⠋⠀ 9730 4066 E5AE FAC2 2683 D03D 4FB3 B4D3 7EF6 3B2E >⠈⠳⣄

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)