Script to check Leap 15.3 build status and version
Hi All, Under Leap 15.2 (and tumbleweed) I was using the following API calls to create a gui that allowed me to check my packages were building and compare the version with tumbleweed to check if I wanted to update the package in Leap. https://api.opensuse.org/build/<project>/<repository>/<arch>/<package>/_status https://api.opensuse.org/build/<project>/<repository>/<arch>/<package>/_history During 15.2 development I was using the following values to achieve this "openSUSE:Leap:15.2" "standard" "x86_64" If I change the 15.2 to 15.3 in the repo name for 95% of packages I get "excluded" as the build result. Is there one set of values I an use here for all packages or do I need to know the origin repo, in which case how do I figure that out? -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
Hi, On 05.02.21 05:12, Simon Lees wrote:
Hi All,
Under Leap 15.2 (and tumbleweed) I was using the following API calls to create a gui that allowed me to check my packages were building and compare the version with tumbleweed to check if I wanted to update the package in Leap.
https://api.opensuse.org/build/<project>/<repository>/<arch>/<package>/_status https://api.opensuse.org/build/<project>/<repository>/<arch>/<package>/_history
During 15.2 development I was using the following values to achieve this
"openSUSE:Leap:15.2" "standard" "x86_64"
If I change the 15.2 to 15.3 in the repo name for 95% of packages I get "excluded" as the build result. Is there one set of values I an use here for all packages or do I need to know the origin repo, in which case how do I figure that out?
In future please use the build service mailing list for such posts or file a bugreport if you believe its a bug. Thanks -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman
I'm just thinking whether doing query on openSUSE:Backports:SLE-15-SP3 wouldn't do 90% of what you need. Lubos On Fri, 2021-02-05 at 08:37 +0100, Stefan Seyfried wrote:
Hi,
On 05.02.21 05:12, Simon Lees wrote:
Hi All,
Under Leap 15.2 (and tumbleweed) I was using the following API calls to create a gui that allowed me to check my packages were building and compare the version with tumbleweed to check if I wanted to update the package in Leap.
https://api.opensuse.org/build/<project>/<repository>/<arch>/<packa ge>/_status https://api.opensuse.org/build/<project>/<repository>/<arch>/<packa ge>/_history
During 15.2 development I was using the following values to achieve this
"openSUSE:Leap:15.2" "standard" "x86_64"
If I change the 15.2 to 15.3 in the repo name for 95% of packages I get "excluded" as the build result. Is there one set of values I an use here for all packages or do I need to know the origin repo, in which case how do I figure that out?
In future please use the build service mailing list for such posts or file a bugreport if you believe its a bug.
Thanks
-- Best regards Lubos Kocman Release Manager openSUSE Leap SUSE LINUX, s.r.o. Krizikova 148/34 tel: +49 173 5876850 186 00 Praha 8 http://www.suse.com Czech Republic
On 2/9/21 4:35 AM, Lubos Kocman wrote:
I'm just thinking whether doing query on openSUSE:Backports:SLE-15-SP3 wouldn't do 90% of what you need.
Lubos
It gets me maybe 60% of the way (I have a number of SLE packages), but its the 60% I care about this week given that I hope my SLE stuff for the next release is pretty much done. I guess if I get "unknown_package" back I can then query openSUSE:Step:15-SP3 to at least get the version info but is there a better way of determining that programmatically? https://www.enlightenment.org/ss/display.php?image=e-6023144c9bbf88.87877120... -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
Hello Adrian, would it make sense to track such "user story" as an rfe in OBS JIRA project or openSUSE-release-tools? On Wed, 2021-02-10 at 10:24 +1030, Simon Lees wrote:
On 2/9/21 4:35 AM, Lubos Kocman wrote:
I'm just thinking whether doing query on openSUSE:Backports:SLE-15- SP3 wouldn't do 90% of what you need.
Lubos
It gets me maybe 60% of the way (I have a number of SLE packages), but its the 60% I care about this week given that I hope my SLE stuff for the next release is pretty much done.
I guess if I get "unknown_package" back I can then query openSUSE:Step:15-SP3 to at least get the version info but is there a better way of determining that programmatically?
https://www.enlightenment.org/ss/display.php?image=e-6023144c9bbf88.87877120...
-- Best regards Lubos Kocman Release Manager openSUSE Leap SUSE LINUX, s.r.o. Krizikova 148/34 tel: +49 173 5876850 186 00 Praha 8 http://www.suse.com Czech Republic
Hi On 2/11/21 11:55 PM, Lubos Kocman wrote:
Hello Adrian,
would it make sense to track such "user story" as an rfe in OBS JIRA project or openSUSE-release-tools?
Related to this i've always defined the following (fish shell) function so I can quickly tell where a package has come from. When dealing with a number of packages that probably come from SLE but may have been branched in Leap its been really useful as a quick check. function lookup151 --description 'Where does a leap packages come from' osc -A https://api.opensuse.org cat openSUSE:Leap:15.1:Update 00Meta lookup.yml | grep $argv end
On Wed, 2021-02-10 at 10:24 +1030, Simon Lees wrote:
On 2/9/21 4:35 AM, Lubos Kocman wrote:
I'm just thinking whether doing query on openSUSE:Backports:SLE-15- SP3 wouldn't do 90% of what you need.
Lubos
It gets me maybe 60% of the way (I have a number of SLE packages), but its the 60% I care about this week given that I hope my SLE stuff for the next release is pretty much done.
I guess if I get "unknown_package" back I can then query openSUSE:Step:15-SP3 to at least get the version info but is there a better way of determining that programmatically?
https://www.enlightenment.org/ss/display.php?image=e-6023144c9bbf88.87877120...
-- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
participants (3)
-
Lubos Kocman -
Simon Lees -
Stefan Seyfried