|
Στις 22/5/2018 15:37, ο Vít Ondruch
έγραψε:
Dne 22.5.2018 v 12:21 Georgios
Petasis napsal(a):
Στις 22/5/2018 11:30, ο Dominik
'Rathann' Mierzejewski έγραψε:
On Tuesday, 22 May 2018 at 07:35, Vít Ondruch wrote:
Dne 21.5.2018 v 22:59 Petr Šabata napsal(a):
On Mon, May 21, 2018 at 11:51:59PM +0300, Georgios Petasis wrote:
Hi all,
I am trying to use the package "fossil", but I am having problems because
its version is too old.
Fedora 28 (and thus the fossil package) contains version 2.2, while the
current version of fossil is 2.6 (released 15 days ago).
Version 2.2 included in Fedora, was released on April 2017.
What is the process of triggering an update to fossil package to version
2.6?
If it doesn't exist already, file a bug for the component
requesting an update.
Or better send a PR updating the package in Pagure.
And ask the maintainer to enable the upstream release monitoring
notifications.
The software is already added to https://release-monitoring.org/ and
I've just added the package name mapping for Fedora.
Regards,
Dominik
Thank you all for the feedback. I have created a new bug (1581180):
https://bugzilla.redhat.com/show_bug.cgi?id=1581180
And I think there are two other bugs (from 2017) that will be
solved if fossil's version gets updated.
Regarding Pagure, I have located the package here:
https://src.fedoraproject.org/rpms/fossil
But I am not sure what "send a PR updating the package in
Pagure" means.
https://docs.pagure.org/pagure/usage/pull_requests.html
I have checked the files in there though, it seems that we
have to just change the version number in fossil.spec, and
check if the fossil-setgroups.patch is still needed.
Well, bumping the version is just the first step. You should check
that the content of the updated package is still appropriate for
fedora, e.g. license was not changed or so and that the update is
compatible with other packages in Fedora, i.e. check what depends
on fossil, what the update might break.
V.
It seems that making a PR is not permitted. After trying two days
trying to figuring out why I cannot checkout the forked repository,
I found this bug:
https://pagure.io/fedora-infrastructure/issue/6361
It won't work if you are not a fedora packager.
I have to do a "remote PR"...
George
|
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/I7SAOZ2BCUKGQLRNEDJY3HBJYXJHEUJK/
