Greetings!
Fedora Infrastructure recently deployed Bodhi 4.0.0 to production,
which included quite a few backwards incompatible changes[0]. Some of
the changes have resulted in older Bodhi clients (less than 4.0.0) not
being compatible with the new version of the server.
In Fedora, FESCo decided
On Wed, 2019-05-29 at 14:36 +, Anderson, Charles R wrote:
> I'm getting this error as of last night on all of my CentOS 7 boxes:
>
> /etc/cron.hourly/0yum-hourly.cron:
>
> Updateinfo file is not valid XML: '/var/cache/yum/x86_64/7/epel/92f2e15cad66d79ea1ad327e2af7af89d98e4d1
>
I've filed https://pagure.io/noggin/issue/4 as an RFE to noggin to
support an "I forgot my username" workflow. noggin is the name of the
replacement UI for FAS.
signature.asc
Description: This is a digitally signed message part
___
epel-devel mailing
On Mon, 2016-09-19 at 18:36 +, Randy Barlow wrote:
> As per the EPEL incompatible upgrades policy[0], I am writing you to
> announce a backwards incompatible Bodhi update that I've submitted to
> Bodhi for EPEL 7[1]. Since Bodhi is primarily a Fedora Infrastructure
> tool and
During today's EPEL meeting it was agreed that we would proceed with releasing
a backwards-incompatible update to EPEL 7. See 5a.:
https://meetbot.fedoraproject.org/fedora-meeting/2016-08-10/epel.2016-08-10-18.00.html
___
epel-devel mailing list
On Wed, 2016-07-27 at 17:12 -0400, Neal Gompa wrote:
> It makes sense to me to go ahead and upgrade it. I don't know of any
> other Bodhi instances out there, and frankly broken software needs to
> be removed from the repos as soon as possible. It puzzles me that
> this
> hasn't been resolved
Hello!
As you may be aware, Bodhi 2.0 is deployed in production[0] while Bodhi
0.9 is packaged in the Fedora and EPEL repositories[1]. The tl;dr of
this post is that we are interested in updating the bodhi package in
EPEL 7 to the newer 2.x release series so that the client will work
with the
