On Fri, Oct 29, 2021 at 10:01 AM Luya Tshimbalanga
<luya(a)fedoraproject.org> wrote:
On 2021-10-28 17:02, Sérgio Basto wrote:
> On Tue, 2021-10-26 at 16:42 -0700, Luya Tshimbalanga wrote:
>> Hello team,
>>
>> I would like to let you know ImageMagick-6.9.12-26 recently landed
>> upstream.
> Hello , when you update from 6.9.11 to 6.9.12, we need rebuild all
> depended packages because we got one soname bump and packages won't
> will give us rpm broken dependencies on dnf update
>
> I propose do a side-tag to update from 6.9.11 to 6.9.12 on F35 since
> ImageMagick should have been updated a long time ago and it was tested
> on rawhide .
>
> I know is a exception to guidelines , but wait more 6 months for end
> users have ImageMagick update is a bad alternative ...
>
>
Any objection from other maintainers?
Technically, you MUST ask FESCo for approval if you want to push
soname-changing / ABI-breaking updates to a stable branch.
I think ImageMagick should fall into this category for Updates Policy
exceptions:
https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#security-fixes
Since the process for updating ImageMagick in rawhide turned out to be
very bumpy, it would be great if you came up with a solid plan for how
to update it on a stable branch without breaking stuff *before*
starting the process and before asking for that exception - something
like 1) compile a definitive list of packages that need a rebuild, 2)
execute all builds in a side tag in a timely fashion, 3) fix any
breakage fast, 4) create bodhi update from side tag as soon as
possible to reduce possibilities for side-tag merge conflicts.
Fabio