[opensuse-buildservice] SLE: Dependencies failed despite packages are available at repositories at Meta
This must be something stupid, but I can't see what I am doing wrong.
I am trying to build Uyuni Client Tools at: https://build.opensuse.org/ project/show/systemsmanagement:Uyuni:Master:SLE12-Uyuni-Client-Tools
One of the packages (that is able to build internally at build.opensuse.de) fails to build is spacewalk-backend https://build.opensuse.org/package/show/ systemsmanagement:Uyuni:Master:SLE12-Uyuni-Client-Tools/spacewalk-backend
Message is: nothing provides python-debian, nothing provides yum
But I cannot understand why, because at Meta I have SUSE:SLE-12:Update/ standard: https://build.opensuse.org/project/meta/ systemsmanagement:Uyuni:Master:SLE12-Uyuni-Client-Tools
And even SUSE:SLE-12:GA, and both are exactly the same projects I use internally
And packages seems to be there: https://build.opensuse.org/package/show/SUSE:SLE-12:Update/yum https://build.opensuse.org/package/show/SUSE:SLE-12:Update/python-debian
I tried
<path project="SUSE:SLE-12-SP3:Update" repository="standard"/> <path project="SUSE:SLE-12-SP3:GA" repository="standard"/>
But no difference.
To some extent, something similar seems to be happening with: https:// build.opensuse.org/package/show/systemsmanagement:Uyuni:Master:SLE15-Uyuni- Client-Tools/spacewalk-backend as it can't find python-yum for SLE15, while internally it works fine.
What am I doing wrong?
On 23.10.18 16:27, Julio González Gil wrote:
What am I doing wrong?
Well, expecting SLE12 to be complete in OBS :)
SLE12 in OBS contains only what is available to customers, e.g. packages on products and specific addons. The packages you require are not.
What you see in https://build.opensuse.org/package/show/SUSE:SLE-12:Update/yum are just the sources.
Greetings, Stephan
On martes, 23 de octubre de 2018 16:31:39 (CEST) Stephan Kulow wrote:
On 23.10.18 16:27, Julio González Gil wrote:
What am I doing wrong?
Well, expecting SLE12 to be complete in OBS :)
SLE12 in OBS contains only what is available to customers, e.g. packages on products and specific addons. The packages you require are not.
What you see in https://build.opensuse.org/package/show/SUSE:SLE-12:Update/yum are just the sources.
So such packages are basically building dependencies, and if I need them to build, I need to copypac, right?
Greetings, Stephan
Am 23.10.18 um 16:50 schrieb Julio González Gil:
On martes, 23 de octubre de 2018 16:31:39 (CEST) Stephan Kulow wrote:
On 23.10.18 16:27, Julio González Gil wrote:
What am I doing wrong?
Well, expecting SLE12 to be complete in OBS :)
SLE12 in OBS contains only what is available to customers, e.g. packages on products and specific addons. The packages you require are not.
What you see in https://build.opensuse.org/package/show/SUSE:SLE-12:Update/yum are just the sources.
So such packages are basically building dependencies, and if I need them to build, I need to copypac, right?
a linkpac will do - but yes, you're not the first to have this problem and you won' be the last
Greetings, Stephan
I am not sure if this is related, but I am having now problems with
================ hwdata ================ https://build.opensuse.org/package/show/systemsmanagement:Uyuni:Master:SLE12... [ 30s] hwdata-0.314-2.2.noarch.rpm: directories not owned by a package: [ 30s] - /usr/share/licenses
Happens because it installs filesystem-13.1-11.13, while /usr/share/licenses is owned by filesystem-13.1-14.15.x86_64.
I see the change at https://build.opensuse.org/package/view_file/ SUSE:SLE-12:Update/filesystem/filesystem.changes?expand=1 and since filesystem is a package for SLE12 product... should this update be there as binary?
================ mgr-virtualization ================ https://build.opensuse.org/package/show/systemsmanagement:Uyuni:Master:SLE12... nothing provides zypper(updatestack-only) needed by zypp-plugin-spacewalk
Similar case, I can see the SPEC with the provides at https:// build.opensuse.org/package/view_file/SUSE:SLE-12:Update/zypper/zypper.spec? expand=1 but it seems the binary is older
================ spacewalk-backend (aarch64) ================ https://build.opensuse.org/package/show/systemsmanagement:Uyuni:Master:SLE12... nothing provides python-dmidecode needed by python2-spacewalk-client-tools
However the package is available for all other architectures. I am not sure of what's going on.
In theory aarch64 was added with SLE12-SP2, so I am not sure if that is the reason it's not available at SUSE:SLE-12:Update (so far I linked it at Uyuni:Master:SLE12-Uyuni-Client-Tools and that fixes the problem).
PS: I am not sure if I am asking stupid questions that are already documented, but I can't find anything about how SUSE:SLE* works at build.opensuse.org at https://en.opensuse.org/Portal:Packaging :-(
On martes, 23 de octubre de 2018 19:10:08 (CEST) Stephan Kulow wrote:
Am 23.10.18 um 16:50 schrieb Julio González Gil:
On martes, 23 de octubre de 2018 16:31:39 (CEST) Stephan Kulow wrote:
On 23.10.18 16:27, Julio González Gil wrote:
What am I doing wrong?
Well, expecting SLE12 to be complete in OBS :)
SLE12 in OBS contains only what is available to customers, e.g. packages on products and specific addons. The packages you require are not.
What you see in https://build.opensuse.org/package/show/SUSE:SLE-12:Update/yum are just the sources.
So such packages are basically building dependencies, and if I need them to build, I need to copypac, right?
a linkpac will do - but yes, you're not the first to have this problem and you won' be the last
Greetings, Stephan
buildservice@lists.opensuse.org
-
Julio González Gil -
Stephan Kulow