DevHeads.net

Copr dependency rebuild with circular dependencies

Hi all. Apologies for cross-posting, but I am running out of ideas.

Suppose one updates libmpfr in a copr repository, which bumps the
soname. Both GCC and libmpc depend on libmpfr, and so must be rebuilt,
but neither GCC nor libmpc can be rebuilt without an existing libmpc,
which, in turn, depends on the old soname version of the recently
updated libmpfr. Can somebody please advise the best way to go in cases
like these?

Is a copr mass rebuild even the right solution for this, or should one
really be using a side tag in koji? - though it is unclear to me what
difference that will make.

Happy to provide more info. All the best,
James.

Comments

Re: Copr dependency rebuild with circular dependencies

By Nicolas Mailhot at 01/09/2018 - 15:06

Hi,

Regardless of the build infra, you will need to create a compat package with the old lib version to make it available during bootstraping

Regards,

Re: Copr dependency rebuild with circular dependencies

By James Paul Turner at 01/09/2018 - 15:23

Thanks Nicolas. That makes sense.

Would you advise that the compatibility package remains in rawhide
after the mass rebuild?

Best,
James.

On Tue, 2018-01-09 at 20:06 +0100, <a href="mailto:nicolas. ... at laposte dot net">nicolas. ... at laposte dot net</a> wrote: