#606 [modularity]: Exclude platform not respected
Closed: Fixed 3 years ago by praiskup. Opened 5 years ago by dmoluguw.

I was trying to build pki-deps module, which contains all the dependencies for pki module. As you can see, this module has a lot of packages to be built and in certain order.

I triggered a module build as follows:

copr-cli build-module --yaml pki-deps.yaml pki-10.6

I wanted to specifically exclude building this module for f28 and f29. When a module build was triggered, it built across all supported fedora platforms, thus creating a huge array of tasks in COPR.

pki-deps module build in COPR: https://copr.fedorainfracloud.org/coprs/dmoluguw/pki-10.6/module/235787

Source for pki-deps.yaml: https://github.com/SilleBille/pki-deps/blob/master/pki-deps.yaml


Metadata Update from @frostyx:
- Issue assigned to frostyx

5 years ago

Metadata Update from @frostyx:
- Issue tagged with: bug, modularity

5 years ago

Thank you for the feedback @dmoluguw,

I've been researching how MBS resolves the platform and discussed it on #fedora-modularity. My idea what needs to be done is following

  1. Go through all dependencies and get their buildrequires platforms
  2. Combine/intersect/resolve or whatever you want to call it/ them to find out the list of platforms, that are common for all dependencies.
  3. Transform platform names like f28 to chroots

But I was told, that the dependencies resolution in MBS is much more complex. Fortunately, @jkaluza and @mprahl have a plan to document this topic next week, so I am going to revisit the issue then.

Metadata Update from @praiskup:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata