Bug ID | 1058180 |
---|---|
Summary | 42.3 ports build paths pick up 42.2 packages |
Classification | openSUSE |
Product | openSUSE Distribution |
Version | Leap 42.3 |
Hardware | aarch64 |
OS | Other |
Status | NEW |
Severity | Normal |
Priority | P5 - None |
Component | Other |
Assignee | bnc-team-screening@forge.provo.novell.com |
Reporter | astieger@suse.com |
QA Contact | qa-bugs@suse.de |
CC | adrian@suse.com, dmueller@suse.com, gunreben@t-online.de, k0da@opensuse.org |
Found By | --- |
Blocker | --- |
I am investigating dependency issues for ports in openSUSE:Maintenance:7267: nothing provides librdmacm1 = 1.0.19.1 needed by librdmacm-devel That's odd, it is supposed to be using rdma-core-devel which obsoletes that stuff. If I mbranch rdma-core into the incident the package is not picked up. The patch for openSUSE:Leap:42.3:Update/ports is openSUSE:Leap:42.3:Ports/ports, has the following: <repository name="ports" rebuild="local" linkedbuild="all"> <path project="openSUSE:Leap:42.2:Ports" repository="ports"/> <path project="openSUSE:Leap:42.3" repository="standard"/> Why 42.2 here? This makes it pick up 42.2 packages: osc ls -b openSUSE:Leap:42.2:Ports/librdmacm --> 1.0.19.1 rather than the ones from openSUSE:Leap:42.3:Ports/rdma-core Also, the buildconfig looks weird: grep "### from" ### from openSUSE:Leap:42.3 ### from openSUSE:Leap:42.3 ### from openSUSE:Leap:42.2:Ports ### from openSUSE:Leap:42.3 ### from openSUSE:Leap:42.2:Ports ### from openSUSE:Leap:42.3:Ports ### from openSUSE:Leap:42.3:Ports ### from openSUSE:Leap:42.3:Update ### from openSUSE:Leap:42.3:Update ### from openSUSE:Maintenance:7267