Mailinglist Archive: opensuse-buildservice (74 mails)

< Previous Next >
Re: [opensuse-buildservice] API query to return all _real_ source packages
  • From: Adrian Schröter <adrian@xxxxxxx>
  • Date: Fri, 10 May 2019 09:17:15 +0200
  • Message-id: <8676663.2XeagXNrg8@linux-ywca>
On Freitag, 10. Mai 2019, 00:38:13 CEST Jimmy Berry wrote:
On Thursday, May 9, 2019 5:20:55 PM CDT Jimmy Berry wrote:
In conclusion, even with a rather complex client-side xpath query it is
possible to get the list of "real packages" without making lots of
queries. Is there a proper way to query the list or can such a method be

Essentially what would be great is the the following.




The definition of real being packages to which one might submit an update
for either my way of maintenance or direct submit request.

I admit that I still struggle a bit of the definition of "real packag es"

In first place I would say these are all packages which actually got build,
no? So the ones below /build/$project. Because beside the listing of source
package containers also the project configuration (_meta and _config) has an
influence what get built and what not.

Yes, it becomes a bit more difficult for maintenance_release projects since
these projects are not supposed to get built, yes getting releases.

Could you explain a bit more what you plan to do with the information
of "real packages" ? We could do that also in a chat later today ....

One should not
be updating a _multibuild psuedo package

Our tooling does not allow you to do that and it should guide you to
the right package automatically .... (you may want to point out to some
example where we could improve :)

, nor a multispec sub-package

mostly not, but there are exceptions so can not forbid that to 100%.

However, I saw that we stopped to set the devel package definition on
these packages. So a "osc branch" is not taking the right packge always
anymore ...

, nor
a maintenance update (submit another for the releasepackage).

yes, but our tooling is supposed to do the right thing here. It recognise
it and creates maintenance requests instead.

Again, there might be cases where we need to improve but some real life
examples would be nice ...


Adrian Schroeter
SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
email: adrian@xxxxxxx

To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-buildservice+owner@xxxxxxxxxxxx

< Previous Next >