[EPEL-devel] Re: Upgrade to rdiff-backup in EPEL-7

2020-04-20 Thread Frank Crawford
Lance, Just to add a bit more on some of Kevin's comments, this does not break any of your backups and existing backups are both readable and writable with both versions. What is broken is the backup process in some cases, as a Python3 master cannot talk to a Python2 slave, and visa- versa. It

[EPEL-devel] Re: Fedora EPEL 8 updates-testing report

2020-04-20 Thread Leon Fauster
Am 20.04.20 um 22:27 schrieb upda...@fedoraproject.org: The following Fedora EPEL 8 Security updates need testing: Age URL 12 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-8fcf741d7f cacti-1.2.11-1.el8 cacti-spine-1.2.11-1.el8 2

[EPEL-devel] Fedora EPEL 8 updates-testing report

2020-04-20 Thread updates
The following Fedora EPEL 8 Security updates need testing: Age URL 12 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-8fcf741d7f cacti-1.2.11-1.el8 cacti-spine-1.2.11-1.el8 2 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-dfc01a6be3 chromium-81.0.4044.113-1.el8

[EPEL-devel] Re: Trying to find Sponsor to help me get Sensu Go into EPEL7/EPEL8

2020-04-20 Thread Dominik 'Rathann' Mierzejewski
Hello, Devin. Welcome to Fedora (EPEL)! On Monday, 20 April 2020 at 17:54, Devin Acosta wrote: > My name is Devin Acosta, I am a Red Hat Certified Architect, and I > have for the past about month now been trying to get Sensu Go (Open > Source Edition) into EPEL 7 / EPEL 8. I have joined the

[EPEL-devel] Fedora EPEL 7 updates-testing report

2020-04-20 Thread updates
The following Fedora EPEL 7 Security updates need testing: Age URL 614 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-3c9292b62d condor-8.6.11-1.el7 356 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-c499781e80 python-gnupg-0.4.4-1.el7 354

[EPEL-devel] Re: Upgrade to rdiff-backup in EPEL-7

2020-04-20 Thread Kevin Fenzi
On Mon, Apr 20, 2020 at 09:59:17AM -0700, Lance Albertson wrote: > What does the upgrade path look like from if folks are currently creating > backups using 1.x and they suddenly switch to 2.x? Is there an upgrade > path? Is there a way in EPEL to allow for both versions to exist to ease >

[EPEL-devel] Re: Upgrade to rdiff-backup in EPEL-7

2020-04-20 Thread Lance Albertson
What does the upgrade path look like from if folks are currently creating backups using 1.x and they suddenly switch to 2.x? Is there an upgrade path? Is there a way in EPEL to allow for both versions to exist to ease migration? i.e. maybe by creating rdiff-backup2 which supercedes rdiff-backup.

[EPEL-devel] Trying to find Sponsor to help me get Sensu Go into EPEL7/EPEL8

2020-04-20 Thread Devin Acosta
My name is Devin Acosta, I am a Red Hat Certified Architect, and I have for the past about month now been trying to get Sensu Go (Open Source Edition) into EPEL 7 / EPEL 8. I have joined the fedora-devel mailing list and followed the process so far to the best of my ability. I was wondering if

[EPEL-devel] Re: Co-Maintainers wanted for python-lockfile EPEL branches

2020-04-20 Thread Neal Gompa
On Mon, Apr 20, 2020 at 9:51 AM Miro Hrončok wrote: > > On 20. 04. 20 13:45, Fabio Valentini wrote: > > and it seems I > > can't even figure out how to determine which EPEL packages require > > python*-lockfile. > > Take the attached repo files. > > They are good for repoquery, adapted from

[EPEL-devel] Re: Co-Maintainers wanted for python-lockfile EPEL branches

2020-04-20 Thread Miro Hrončok
On 20. 04. 20 13:45, Fabio Valentini wrote: and it seems I can't even figure out how to determine which EPEL packages require python*-lockfile. Take the attached repo files. They are good for repoquery, adapted from epel-release. They don't have -testing repos, but -testingx, so you don't

[EPEL-devel] Upgrade to rdiff-backup in EPEL-7

2020-04-20 Thread Frank Crawford
We have pushed into testing and intend to eventually release a new version of rdiff-backup which has a significant incompatibly with the current distributed version, when used in client-server mode. The current version is v1.2.8 and written in Python2, while the new version is v2.0.0 and written

[EPEL-devel] Re: Co-Maintainers wanted for python-lockfile EPEL branches

2020-04-20 Thread Troy Dawson
On a RHEL8 machine, doing a dnf repoquery --whatrequires python3-lockfile dnf repoquery --whatrequires python2-lockfile Shows that the following depend on it duplicity python3-fedora pungi-legacy I haven't checked EPEL7 yet. On Mon, Apr 20, 2020 at 4:46 AM Fabio Valentini wrote: > >

[EPEL-devel] Re: Cannot retire epel7 package

2020-04-20 Thread Ondrej Nosek
It is a bug, I have already opened a ticket for this. https://pagure.io/fedpkg/issue/395 Thanks, guys for letting me know. ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to

[EPEL-devel] Re: Cannot retire epel7 package

2020-04-20 Thread Miro Hrončok
On 20. 04. 20 12:13, Miro Hrončok wrote: On 20. 04. 20 6:09, Orion Poplawski wrote: zabbix22 (epel7)]$ fedpkg retire 'Zabbix 2.2 is no longer maintained upstream' Fedora release (epel7) is in state 'current' - retire operation is not allowed. Sounds like fedpkg bug. See

[EPEL-devel] Re: Cannot retire epel7 package

2020-04-20 Thread Miro Hrončok
On 20. 04. 20 6:09, Orion Poplawski wrote: zabbix22 (epel7)]$ fedpkg retire 'Zabbix 2.2 is no longer maintained upstream' Fedora release (epel7) is in state 'current' - retire operation is not allowed. Sounds like fedpkg bug. See https://pagure.io/fedpkg/issue/337 -- Miro Hrončok -- Phone: