On Tue, 2019-05-28 at 17:41 -0400, Dan Čermák wrote:
I just tried to submit an update via `fedpkg update` but got a failure via the cli: $ fedpkg update Could not execute update: Could not generate update request: 'anonymous' A copy of the filled in template is saved as bodhi.template.last
Nevertheless the update got submitted and is available on Bodhi (it's this one: https://bodhi.fedoraproject.org/updates/FEDORA-2019-16433c312e).
Hi Dan!
I presume you are using a Bodhi 2 or 3 client there? This is a known compatibility issue between the Bodhi 3 client and the Bodhi 4 server:
https://bugzilla.redhat.com/show_bug.cgi?id=1714950
There's a FESCo ticket where we are discussing what to do about it. I'm kind of undecided between putting Bodhi 4 into Fedora 29+ (and maybe even EPEL 7, which may be tricky due to dependencies) and making a Bodhi 3.15 that can talk to Bodhi 4 server (downside is that this will require more effort on my part, and I have a lot on my plate ☹). Feel free to voice your opinions on the FESCo ticket!
On Wed, May 29, 2019 at 11:39 AM Randy Barlow bowlofeggs@fedoraproject.org wrote:
On Tue, 2019-05-28 at 17:41 -0400, Dan Čermák wrote:
I just tried to submit an update via `fedpkg update` but got a failure via the cli: $ fedpkg update Could not execute update: Could not generate update request: 'anonymous' A copy of the filled in template is saved as bodhi.template.last
Nevertheless the update got submitted and is available on Bodhi (it's this one: https://bodhi.fedoraproject.org/updates/FEDORA-2019-16433c312e).
Hi Dan!
I presume you are using a Bodhi 2 or 3 client there? This is a known compatibility issue between the Bodhi 3 client and the Bodhi 4 server:
https://bugzilla.redhat.com/show_bug.cgi?id=1714950
There's a FESCo ticket where we are discussing what to do about it. I'm kind of undecided between putting Bodhi 4 into Fedora 29+ (and maybe even EPEL 7, which may be tricky due to dependencies) and making a Bodhi 3.15 that can talk to Bodhi 4 server (downside is that this will require more effort on my part, and I have a lot on my plate ☹). Feel free to voice your opinions on the FESCo ticket!
Could you make a container image based on F30 that can be run on F29/EPEL 7/8? That offers users a way to use the new tool on the OS of their choice and avoids you having to write new code or bring back a bunch of dependencies to the Fedora release itself.
josh
On Wed, 2019-05-29 at 11:58 -0400, Josh Boyer wrote:
Could you make a container image based on F30 that can be run on F29/EPEL 7/8? That offers users a way to use the new tool on the OS of their choice and avoids you having to write new code or bring back a bunch of dependencies to the Fedora release itself.
Yeah anyone could easily do this (just a FROM line [note: it's in Rawhide, not F30] and a RUN dnf install line), but there are also dependencies on bodhi-client in EPEL 7 and F29/30 so it wouldn't fully address the issue. Any end user who wants to work around it could do this though, and I have also provided a Copr[0] that has the new Bodhi client that you can use too.
I also considered modularity, but there's currently a stay on adding new packages to the default stream since RPMs can't currently depend on modules (and things do depend on Bodhi).
Miro and I have proposed on the FESCo ticket to create a bodhi3-client package and upgrade F29/30 to Bodhi 4.
[0] https://copr.fedorainfracloud.org/coprs/bowlofeggs/bodhi
infrastructure@lists.fedoraproject.org