releng

#9033 Modular packages missing from updates repo
Closed: Fixed by kevin. Opened by mbooth.

Closed: Fixed
Reopen Issue
  • Describe the issue

There appears to be packages missing from the update repositories. Here's my scenario:

Attempt to install eclipse module dnf module install eclipse:latest/java

$ sudo dnf --enablerepo=updates-testing --enablerepo=updates-testing-modular module install eclipse:latest/java
Last metadata expiration check: 0:11:04 ago on Mon 18 Nov 2019 15:28:35 GMT.
Error: 
 Problem: conflicting requests
  - nothing provides osgi(com.ifedorenko.m2e.sourcelookup) needed by eclipse-m2e-mavendev-0.3.0.201506181201-8.fc30.noarch
(try to add '--skip-broken' to skip uninstallable packages)

This is pretty strange because I fixed this bug a month ago as part of this update:

https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2019-07a48339f0

This is the module build that was pushed to stable: https://koji.fedoraproject.org/koji/buildinfo?buildID=1399247 which you can see was tagged into f31-modular-updates

If you look in the modulemd.txt you can see this segment:

        eclipse-m2e-mavendev:
          ref: 5806c8a374671f6c95f41bf5e253259bb8ad9f50
        eclipse-m2e-workspace:
          ref: df448176641c558fc9803ffd9c988a32105b4bc0

Which corresponds to these two builds:

https://koji.fedoraproject.org/koji/buildinfo?buildID=1398971
-> eclipse-m2e-mavendev-0.5.0-0.2.gitc36928b.module_f31+6793+1c93c38e
https://koji.fedoraproject.org/koji/buildinfo?buildID=1398701
-> eclipse-m2e-workspace-0.4.0-12.module_f31+6793+1c93c38e

You can these comprise modularity build 6793: https://mbs.fedoraproject.org/module-build-service/1/module-builds/6793

Where are these packages on the mirrors? There are not in either of the following two locations:

https://dl.fedoraproject.org/pub/fedora/linux/releases/31/Modular/x86_64/os/Packages/e/
https://dl.fedoraproject.org/pub/fedora/linux/updates/31/Modular/x86_64/Packages/e/

Can anyone help me figure out what's going on here?

What is quite strange to me is that some builds are in both the fedora-modular repo AND the updates-modular repo:

https://dl.fedoraproject.org/pub/fedora/linux/releases/31/Modular/x86_64/os/Packages/e/eclipse-m2e-workspace-0.4.0-11.module_f31+6165+9b01e00c.noarch.rpm
https://dl.fedoraproject.org/pub/fedora/linux/updates/31/Modular/x86_64/Packages/e/eclipse-m2e-workspace-0.4.0-11.module_f31+6165+9b01e00c.noarch.rpm

Should that even be possible?

@lsedlar This seems like a pungi issue, I can see that eclipse-latest-3120191009222626.a5412477 is the latest tagged module build in f31-modular-updates but I dont see it in the latest updates compose in https://kojipkgs.fedoraproject.org/compose/updates/f31-modular-updates/compose/Everything/x86_64/os/Packages/e/

Can you take a look? Thanks.

What is quite strange to me is that some builds are in both the fedora-modular repo AND the updates-modular repo:
https://dl.fedoraproject.org/pub/fedora/linux/releases/31/Modular/x86_64/os/Packages/e/eclipse-m2e-workspace-0.4.0-11.module_f31+6165+9b01e00c.noarch.rpm
https://dl.fedoraproject.org/pub/fedora/linux/updates/31/Modular/x86_64/Packages/e/eclipse-m2e-workspace-0.4.0-11.module_f31+6165+9b01e00c.noarch.rpm
Should that even be possible?

It should not, but for some reason bodhi tagged that module into f31-modular-updates-pending and then moved to f31-modular tag

Sun Sep 22 22:33:10 2019 eclipse-2019_06-3120190902131726.efdece7d tagged into f31-modular-updates-pending by bodhi
Mon Sep 23 21:41:45 2019 eclipse-2019_06-3120190902131726.efdece7d tagged into f31-modular by bodhi [still active]
Mon Sep 23 21:42:00 2019 eclipse-2019_06-3120190902131726.efdece7d untagged from f31-modular-updates-pending by bodhi

The linked compose contains two streams of eclipse module.

2019-11-18 01:53:37 [INFO    ] Module eclipse:latest:3120191009222626:a5412477 in variant Everything will use Koji tag module-eclipse-latest-3120191009222626-a5412477.
2019-11-18 01:53:38 [INFO    ] Module eclipse:2019-06:3120190902131726:efdece7d in variant Everything will use Koji tag module-eclipse-2019-06-3120190902131726-efdece7d.

However the latest stream seems to be empty.
There are no RPM builds tagged in the content tag.

$ koji list-tagged --latest --inherit module-eclipse-latest-3120191009222626-a5412477
Build                                     Tag                   Built by
----------------------------------------  --------------------  ----------------
$

The metadata in https://koji.fedoraproject.org/koji/buildinfo?buildID=1399247 does not list any artifacts.

Is the module built correctly?

Is the module built correctly?

How can I tell? In MBS is looks okay: https://mbs.fedoraproject.org/module-build-service/1/module-builds/6793

And the task IDs correspond with actual builds that exist in koji. Is MBS not tagging something correctly?

Edit: Maybe @jkaluza and @mprahl can give us some insight here?
Edited by mbooth

In the meantime, I guess I just try to rebuild my module and submit another update?

@mbooth , any luck with your rebuild?

Is this still happening?

@kevin I have since exited the modularity game on Fedora.

Winning. Thanks.

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.