fm-orchestrator

Clone
Source Code
GIT

#900 mbs-build submit does not refer the latest rpm package included in module
Closed: Fixed 6 years ago Opened 6 years ago by jaruga.

Closed: Fixed
Reopen Issue

I want to ask you if below situation is intentional or not.

  1. I built modules/ruby by mbs-build submit. modules/ruby includes rpms/ruby, and the latest version is ruby-2.5.0-89 at that time. But the build was failed for an issue.
  2. rpms/ruby fixed the issue. rpms/ruby latest version was ruby-2.5.0-91.
  3. I built modules/ruby by mbs-build submit without updating in modules/ruby itself. Then ruby-2.5.0-89 was used.

I expected rpms/ruby ruby-2.5.0-91 is used.

Reference:
- Actual log: https://koji.fedoraproject.org/koji/taskinfo?taskID=25990404 , Build ruby-2.5.0-89.module_1539+dd658596
- rpms/ruby: https://src.fedoraproject.org/rpms/ruby

You should be using fedpkg module-build instead, but this situation is expected and will happen even with fedpkg module-build.

The "problem" is you are resubmitting the same failed build and when the module build is resubmitted, it uses the same commit hashes of the components as when submitted for first time.

You can just push empty commit to your module dist-git and submit it as new build to get the latest commit hashes.

Metadata Update from @jkaluza:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
6 years ago

@jkaluza Okay, thanks for the response.

Login to comment on this ticket.

Metadata
None
None
None
None
Powered by Pagure 5.13.3
Documentation • File an Issue • About • SSH Hostkey/Fingerprint
© Red Hat, Inc. and others.