After the discovery of the lack of python-celery in EPEL 7 when I
first proposed the rebase update for the "pagure" package a few months
ago, I went back to working out how to bring celery into EPEL 7.
I'm pleased to say that a new update has been proposed that updates
"pagure" and includes "python-celery". It awaits testing now.
If you're running an instance of Pagure using the EPEL 7 package,
please backup everything before attempting to follow through the
documentation on upgrading. For clean installations, please consult
the setup documentation.
Personally, I would recommend exporting everything out, rebuilding
with the new version, and importing your repositories back in. That is
likely to be less risky, given the substantial delta between 2.x and
Going forward, we expect that the "pagure" package will be more
actively maintained, so we will hopefully avoid these problems in the
We're sorry for the inconvenience, but we hope this will be a one-time pain.
真実はいつも一つ！/ Always, there's only one truth!
Good Morning Everyone,
Just a couple of reminders:
- Next week Monday is scheduled the next pagure release: 5.2
From my testing in https://stg.pagure.io it seems to perform fine but the more
eyes on it the better, so if you have some time please poke at it :)
- Next week Tuesday at 13:00 UTC is scheduled the next pagure stakeholder
meeting on #pagure on freenode.
As before everyone interested in pagure is welcome to join.
The basic agenda is:
- State of pagure 5.3
- Planning pagure 5.4
- Open floor
- Ticket triaging
If you would like to add anything to the agenda feel free to reply to this
Have a nice day and a good week-end everyone,