Hi,
I have a similar problem (but on a much smaller scale): The certbot stack
comprises ~ a dozen packages which should be updated in lockstep. We push the
same version to all supported Fedora releases + EPEL (mostly).
To do that somewhat efficiently I built/extended some scripts:
https://git
On 11/15/21 14:48, Fabio Valentini wrote:
I don't really have a solution here, but I'd be interested in looking
at this problem.
For example, most* [1] packages in the Rust stack will have (and
should! have) the same versions across all supported Fedora branches.
For any Rust packages that I pus
On Mon, Nov 15, 2021 at 8:42 PM Major Hayden wrote:
>
> Hey there,
>
> As much as I try not to, I sometimes forget to backport a package that I
> manage.
>
> For example, Google's Python SDK updates rather frequently and I usually
> bring those changes into rawhide fairly quickly. The SDK is made
Hey there,
As much as I try not to, I sometimes forget to backport a package that I
manage.
For example, Google's Python SDK updates rather frequently and I usually
bring those changes into rawhide fairly quickly. The SDK is made up of
plenty of different packages that release at different t
