Re: [jspaleta/find-inactive-packagers] Inactive packager detected for user ttorcz (Issue #492)

[Tomasz Torcz]

Hey,

where should I reply?  The email below came from fedoraforge-noreply@…

Not to mention this is completely wrong. Recently I've posted here,
prepared update for my package (f44 upgrade is fresh in Bodhi),
written in bugzilla, posted a blog note which got federated to the
planet, etc.

On Mon, Jun 29, 2026 at 03:07:47PM +0000, jspaleta wrote:
> *@jspaleta* mentioned you:
>
> Hello @ttorcz ( https://forge.fedoraproject.org/ttorcz ) ,
>
> during our periodic check as per the " Inactive packagers policy ( https://docs.fedoraproject.org/en-US/fesco/Policy_for_inactive_packagers/ ) "
> we detected no activity from you as a packager, nor in
> other Fedora community places, like Bodhi or mailing lists.
>
> In order to reduce security risks from possible accounts hijacking
> we're trying to contact you to know if you're still reachable and
> if your email set in Fedora Account System ( *ENOEMAIL* ) is still valid.
>
> Please, let us know if you're still intersted in participating
> in Fedora and if you still need your account to be listed in the packager group.
>
> Without any reply from you, in two months the packager group membership will be
> removed from your account and any package for which you are the main admin will
> be orphaned, so that co-maintainers can pick them up.
>
> View it on Fedora Forge ( https://forge.fedoraproject.org/jspaleta/find-inactive-packagers/issues/492 ).

[jspaleta/find-inactive-packagers] Inactive packager detected for user ttorcz (Issue #492)

[José Matos]

On Mon, 2026-06-29 at 17:47 +0200, Tomasz Torcz wrote:
> Hey,
>
> where should I reply?  The email below came from fedoraforge-noreply@…
>
> Not to mention this is completely wrong. Recently I've posted here,
> prepared update for my package (f44 upgrade is fresh in Bodhi),
> written in bugzilla, posted a blog note which got federated to the
> planet, etc.
>
> On Mon, Jun 29, 2026 at 03:07:47PM +0000, jspaleta wrote:
> > *@jspaleta* mentioned you:
> >
> > Hello @ttorcz ( https://forge.fedoraproject.org/ttorcz%C2%A0) ,
> >
> > during our periodic check as per the " Inactive packagers policy (
> > https://docs.fedoraproject.org/en-US/fesco/Policy_for_inactive_packagers/%C2...)
> > "
> > we detected no activity from you as a packager, nor in
> > other Fedora community places, like Bodhi or mailing lists.
> >
> > In order to reduce security risks from possible accounts hijacking
> > we're trying to contact you to know if you're still reachable and
> > if your email set in Fedora Account System ( *ENOEMAIL* ) is still valid.
> >
> > Please, let us know if you're still intersted in participating
> > in Fedora and if you still need your account to be listed in the packager
> > group.
> >
> > Without any reply from you, in two months the packager group membership will
> > be
> > removed from your account and any package for which you are the main admin
> > will
> > be orphaned, so that co-maintainers can pick them up.
> >
> > View it on Fedora Forge (
> > https://forge.fedoraproject.org/jspaleta/find-inactive-packagers/issues/492%...
> > ).
>
> -- 
> Tomasz Torcz                Only gods can safely risk perfection,
> [e-mail]     it’s a dangerous thing for a man.  — Alia

I had the same issue. I also intended to respond, the issue is: where?

No only that but the issue that appears in the title is not available.
"The page you are trying to reach either does not exist, has been removed or you
are not authorized to view it."

Even when I am authenticated. I received not one but 3 of these messages. When changing to the list of issues the numbers do not match.

Best regards,

[jspaleta/find-inactive-packagers] Inactive packager detected for user ttorcz (Issue #492)

[Jef Spaleta]

Sorry for the noise.

i didnt expect my fork of the script repo to end up sending any notifications.

I was working on converting the script to use the forgejo api as part of the transition off of pagure.   It looks like the `AT username` constructions already in use in the ticket text strings was interpreted by the Forge and turned them into notifications.

I've addressed that now by introducing the concept of an official repo in the script, so filing tickets against a non-official repo, like I'm doing in my testing, won't result in notification chatter.  This should also help prevent this from happening again the next time someone does a fork and pull request against the script.

-jef