Hello,
I’m using a branch project to test compilation before pushing to my real project.
My branch project is here : https://build.opensuse.org/package/show/home:VIFIBnexedi:branches:home:VIFIBnexedi/SlapOS-Node
As you can see for example Debian 10 x86_64 is compiling fine but afterward, I can’t see my package in http://download.opensuse.org/repositories/home:/VIFIBnexedi:/branches:/home:/VIFIBnexedi/Debian_10/amd64/
It used to work fine until around 2 weeks ago.
What am I missing ?
Thanks.
Thomas.
Hi and welcome to the Forum
It’s working as designed, by default packages that are ‘branched’ don’t publish (see the repository flags), this is because the workflow expects it’s for an update and don’t want to potentially give out to the end user (via package search).
Normally one is using osc and building locally and install for testing, or manually download if using the web UI. If you really want to publish, then need to adjust the ‘publish’ flag under the repositories tab of the package.
Thank you very much for your answer.
How can I download the package manually after everything compiled in my branch project ? In my project page (https://build.opensuse.org/package/show/home:VIFIBnexedi:branches:home:VIFIBnexedi/SlapOS-Node ) there is a “Download Package” link : https://software.opensuse.org//download.html?project=home%3AVIFIBnexedi%3Abranches%3Ahome%3AVIFIBnexedi&package=SlapOS-Node but this link gives me:
No data for home:VIFIBnexedi:branches:home:VIFIBnexedi / SlapOS-Node
Hi
Click on the successful distribution build, eg https://build.opensuse.org/package/binaries/home:VIFIBnexedi:branches:home:VIFIBnexedi/SlapOS-Node/openSUSE_Leap_15.1 there is a download link here, you need to be logged in. Else build locally with osc, or just grab the binaries you want with osc, eg;
osc getbinaries home:VIFIBnexedi:branches:home:VIFIBnexedi/SlapOS-Node openSUSE_Leap_15.1 x86_64
Creating directory "binaries"
_buildenv: 100%|###############################################################################################################################################| Time: 0:00:00
_statistics: 100%|#############################################################################################################################################| Time: 0:00:00
rpmlint.log: 100%|#############################################################################################################################################| Time: 0:00:00
slapos.node-1.0.174-lp151.19.1.x86_64.rpm: 100%|###############################################################################################################| Time: 0:00:02
Ohhhhhhhhhh thanks. It was right under my nose but didn’t see it. For other people as dumb as me, you need to click on the OS in the “Build Results” tab on the right (e.g. “Debian_10”, “Fedora_29”, …). On those link, you can download the package for all archs of this OS.
malcolmlewis:
Else build locally with osc, or just grab the binaries you want with osc, eg;
osc getbinaries home:VIFIBnexedi:branches:home:VIFIBnexedi/SlapOS-Node openSUSE_Leap_15.1 x86_64
Creating directory "binaries"
_buildenv: 100%|###############################################################################################################################################| Time: 0:00:00
_statistics: 100%|#############################################################################################################################################| Time: 0:00:00
rpmlint.log: 100%|#############################################################################################################################################| Time: 0:00:00
slapos.node-1.0.174-lp151.19.1.x86_64.rpm: 100%|###############################################################################################################| Time: 0:00:02
I didn’t know either. Thanks for the tip.
We can mark this post as “solved”. Thanks again.