Hi Cristian,
thank you for contributing to Fedora :-)
Am 07.01.21 um 13:05 schrieb Cristian Morales Vega:
My failed attempt has left me with some questions.
I think I don't understand what you tried so far and what failed exactly (maybe
I misunderstood your email).
- Can this be done?
I may be able to push to my own fork and create Pull Requests. But to
update a package I am going to need to upload the updated tarball to
the Lookaside Cache, and I guess I need to be in the packager group to
be able to do that (I get a 403 error).
Yes. For a package update don't bother with the lookaside cache. Just fork the
package, create a pull request and the maintainer can do "fedpkg new-sources
..." (assuming "spectool -g *.spec" can download the necessary tarballs).
- How did this happen?
I am not trying to blame the maintainer. Stuff happens, people have a
life outside Fedora. But he probably knows
(https://bugzilla.redhat.com/show_bug.cgi?id=1899163), there is even a
person comment in there asking about the update, and for whatever
reason he has not done it. Two weeks ago I sent him an email but have
got no reply yet.
This was the holiday season and of course there is always real life so people
may be distracted/non-responsive. However I have to say that non-responsive
maintainers are a bit of dark spot in Fedora. Especially when touching more than
a few packages I took me many weeks until all my patches were applied (and there
is at least one pull request for the high-profile mesa package which just open
without any comments for more than a year or so).
But I don't think this should be a problem in your case.
How does Fedora handle this?
For all I know he may have transcended into a pure-energy being and we
will never get more updates from him. If that's the case, when does
Fedora notice and assigns a new maintainer to the package? There is
any defined process?
In terms of policy there is the "Non-responsive maintainer policy":
https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/
However in your case I think you should first submit a pull request and mention
that PR in the bugzilla issue. If you don't get any response within 1-2 weeks
maybe you could send another email to this list. cmake has some well-known
maintainers so I'm sure the version update will be handled somehow.
Also cmake is a pretty important package so there might be the need to
coordinate updating with the rest of Fedora - but the cmake package maintainers
will let you know if that is the case.
- What's wrong with the the-new-hotness?
https://bugzilla.redhat.com/show_bug.cgi?id=1899163 has been
complaining that "An HTTP error occurred downloading the package's new
Source URLs: Getting
https://gitlab.kitware.com/cmake/cmake/-/merge_requests/5482.patch to
./5482.patch" since 18 November. I can open
https://gitlab.kitware.com/cmake/cmake/-/merge_requests/5482.patch in
my browser without any issues, "An HTTP error" is not too helpful
here.
Yes, not sure what is wrong exactly but I'm seeing this quite often. Not
important though...
Felix
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
