#3454 Nonresponsive maintainer: Robert-André Mauchin eclipseo
Closed: Accepted by humaton. Opened by gbcox.

fas username: @
package:
issues to fix: https://bugzilla.redhat.com/show_bug.cgi?id=2380068
issues to fix: https://bugzilla.redhat.com/show_bug.cgi?id=2372324
nonresponsive maintainer bug: https://bugzilla.redhat.com/show_bug.cgi?id=2381934
fedora-devel mail: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/VMSBQKNIWP6XULRI6UCCUHDEW4XQEREN/
comainainers: @
I am interested in comaintaining the package: YES
additional notes
I have upgrade ready go here: https://copr.fedorainfracloud.org/coprs/gbcox/dogfood/build/9342100/
Required for cantata upgrade.
Have requested information from fale, muchy, and kde-sig. No response as of yet. I am going on extended travel August 20th and would to have everything updated several weeks before I leave. I will be still reachable during travel but access to my home server will be limited. Thank you.

This is a ticket for the Fedora's Policy for nonresponsive package maintainers.


Hi all,
Just a quick follow-up on this ticket — it was filed on July 27 and is now in its second week. I understand these requests can take time to process, but I wanted to check in and see if there’s anything else needed from my side.

I’d still really like to get this resolved before I leave on August 20 if possible, as I’ll have reduced access during that time. Thanks for your time and consideration.

@gbcox, I can merge the changes if you want, since I have write access to the repo!

@fale, thank you very very much! That will allow me to get cantata upgraded. Use this COPR:
https://copr.fedorainfracloud.org/coprs/gbcox/dogfood/build/9342100/

Here is the bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2380068

Much appreciated!

+1 here. (which means we can just add you as admin to the package(s) you are willing to maintain).

+1 here. (which means we can just add you as admin to the package(s) you are willing to maintain).

Thanks Kevin that works also! I just would like to get cantata upgraded before I leave on travel, and qtiocompressor is a dependency.

https://bodhi.fedoraproject.org/updates/FEDORA-2025-f511647d20

Open to add you as admin if you want that as well :)

https://bodhi.fedoraproject.org/updates/FEDORA-2025-f511647d20

Open to add you as admin if you want that as well :)

Thanks, yes being a admin will be better. Always good to have multiple maintainers!

https://bodhi.fedoraproject.org/updates/FEDORA-2025-f511647d20

Open to add you as admin if you want that as well :)

Thanks, yes being a admin will be better. Always good to have multiple maintainers!

Permissions are now there :)

+1

Though @eclipseo did some builds in early April (https://koji.fedoraproject.org/koji/builds?userID=eclipseo&order=-build_id). Bugzilla activity cuts off the same time. So I think we should proceed with the ticket. I hope Robert-André comes back.

+1 too.

also refer to https://pagure.io/fesco/issue/2999 where basically the same thing happened.

+1

With +4, 0, -0 this is FESCo-approved.

As for FESCo policy, after 1w for voting the maintainer needs to be pinged.

@eclipseo ping, This is the Week 2 reminder

@eclipseo ping again

Ah, no, I misread the policy. After two weeks, the ticket should be closed.

APPROVED (+4, 0, 0)

This will be announced in the agenda for today.

Metadata Update from @zbyszek:
- Issue close_status updated to: Accepted
- Issue status updated to: Closed (was: Open)

This is approved but not yet implemented. Please file a releng ticket.

Metadata Update from @decathorpe:
- Issue status updated to: Open (was: Closed)

No need for a releng ticket, I'll do it.

Gave qtiocompressor to @gbcox.

I'll try orphaning the rest of the packages tmrw, I keep getting:

requests.exceptions.RetryError: HTTPSConnectionPool(host='src.fedoraproject.org', port=443): Max retries exceeded with url: /api/0/user/eclipseo?per_page=50 (Caused by ResponseError('too many 504 error responses'))

OK, open a releng ticket, the API keeps giving me 504 errors.

I'd like to pick up python-pyahocorasick. I've got a pending request to build it for EPEL10 there.

I'd like to pick up python-pyahocorasick. I've got a pending request to build it for EPEL10 there.

Done.

→ https://pagure.io/releng/issue/12928

pong

got a computer that doesn't turn to flames when plugging in

taking the most urgent requests first

Welcome back ;)

Can I be added as an admin to the packages in the scancode-toolkit stack? I've been maintaining scancode for the past several months as a member of the python-sig, but I'd like to add it to the Software Tools Analysis SIG once I get that started up (see https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/KU2L3C2J2SHP3G2KB4KAZ7DYAMQ3LIA3/). These packages are:

scancode-toolkit
python-commoncode
python-extractcode
python-container-inspector
python-debian-inspector
python-dparse2
python-extractcode-7z
python-extractcode-libarchive
python-fingerprints
python-ftfy
python-gemfileparser2
python-intbitset
python-jsonstreams
python-normality
python-packageurl-python
python-parameter-expansion-patched
python-pygmars
python-pymaven-patch
python-saneyaml
python-spdx-tools
python-typecode
python-typecode-libmagic
python-uritools
python-urlpy

EDIT: I was going to wait for them to be orphaned and then pick up the necessary dependencies based on the orphaned packages report, but that never happened.

@gotmax23

./set-admin-rights-to-gotmax.py "scancode-toolkit" "python-commoncode" "python-extractcode" "python-container-inspector" "python-debian-inspector" "python-dparse2" "python-extractcode-7z" "python-extractcode-libarchive" "python-fingerprints" "python-ftfy" "python-gemfileparser2" "python-intbitset" "python-jsonstreams" "python-normality" "python-packageurl-python" "python-parameter-expansion-patched" "python-pygmars" "python-pymaven-patch" "python-saneyaml" "python-spdx-tools" "python-typecode" "python-typecode-libmagic" "python-uritools" "python-urlpy"

You should be admin everywhere now.

This is on my update radar as I discussed this software with the open source guy of a big French company last week at an event and he is doing such analysis for his company.

This was approved some time ago, closing.

Metadata Update from @humaton:
- Issue close_status updated to: Accepted
- Issue status updated to: Closed (was: Open)

This was approved but never processed. What is the conclusion here? @eclipseo responded, but there was no FESCo reaction to that. The releng ticket is closed, this one is closed, all is good?

In the original report we had two packages (qtiocompressor, cantata), and both have new ownership. Later there was a request for the scancode-toolkit stack, which was handled by @eclipseo. So I think this is indeed done and we can keep the ticket closed.

Metadata