package: python-cattrs issues to fix: https://bugzilla.redhat.com/show_bug.cgi?id=1706066 + ~50 others nonresponsive maintainer bug: https://bugzilla.redhat.com/show_bug.cgi?id=1731545 fedora-devel mail: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/NCNDC7AID2DSAA5SQZ3MLASMLJ3NZTFP/ comainainers: N/A additional notes: I don't want to take over the package.
@brouhaha
@brouhaha responded to one of the bugzillas by saying they will just wait until upstream fixes this. I'm not particularly happy but technically, they responded.
Yet all the other problems remain ignored. Not sure how to proceed.
@brouhaha There are multiple FTBFS bugs open against your packages, some for F31, some earlier. None of them have any response from you. Waiting until upstreams magically fix the issues is not a valid answer. Please say if you plan to work on those issues.
The python-cattrs issue is unresolved because upstream does not (yet) support Pyhon 3.8. I am only a packager for the project, not a developer.
I work on packages as I have time available. If someone is dissatisfied with my progress with maintaining a particular package, they are welcome to help by providing patches or taking over maintaining the package.
The python-cattrs issue is unresolved because upstream does not (yet) support Python 3.8. I am only a packager for the project, not a developer.
I'm just worried that upstream might not be even aware of the problem until the Fedora maintainer notifies them. As we roll the Python 3.8 upgrade, we unfortunately cannot talk to all the upstreams ourselves and we strongly rely on help of the package maintainers with doing that.
I work on packages as I have time available.
That is totally fine and I wouldn't even suggest a volunteer maintainer should do more then that. What I worry about is not communication about this and not replying to bugzilla reports at all. An honest answer like: "I don't have time to provide a fix for this until next year, if anybody has one, feel free to push it directly." is always appreciated more than silence. Silence is bad, because then we have no idea if this is on the maintainer's radar, if the maintainer needs help, more information, if they are even aware of the issue.
Either way, Eric has responded.
Metadata Update from @churchyard: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.