On 9/23/19 1:42 PM, Petr Pisar wrote:
On 2019-09-22, Till Hofmann <thofmann@xxxxxxxxxxxxxxxxx> wrote:
We have an odd issue with a module build of sway for F30: It looks like
the module was actually built with a F32 buildroot.
BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1754167
Here's the build:
https://koji.fedoraproject.org/koji/buildinfo?buildID=1376355
The modulemd file contains:
dependencies:
- buildrequires:
platform: [f30]
requires:
platform: [f30]
But then, it built packages with f32 in the package version:
artifacts:
rpms:
- mako-0:1.4-1.module_f32+6140+eb754d2b.src
- mako-0:1.4-1.module_f32+6140+eb754d2b.x86_64
- mako-debuginfo-0:1.4-1.module_f32+6140+eb754d2b.x86_64
- mako-debugsource-0:1.4-1.module_f32+6140+eb754d2b.x86_64
There was a bug in Module Build Service that added F32 packages into
non-f32 platform build roots. The bug was fixed and owners of two
affected builds notified that the build will be retired in MBS and they
will have to rebuild them again.
Maybe the sway module slipped through the craks. Or the bug reoccurred.
I cannot find the ticket where this issue was resolved.
Since the build is already in a stable repository, the only option is
probably bumping Release numbers in the spec files and building the
module again.
Thanks for the hint!
Do I really need to bump releases for all the packages in the module or
is it enough to just rebuild the module itself?
Kind regards,
Till
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
