Mailinglist Archive: opensuse-buildservice (74 mails)

< Previous Next >
[opensuse-buildservice] API query to return all _real_ source packages
  • From: Jimmy Berry <jberry@xxxxxxxx>
  • Date: Thu, 09 May 2019 17:20:55 -0500
  • Message-id: <1865926.ubCnFbbCZv@boomba.local>
Is there a variant of /source/<project> that will return either enough
information in XML to filter client-side or pre-filter server-side to achieve
the following.

A list of _real_ source packages which excludes:
- maintenance updates (revisions of the release source package)
- multi-spec self links (Mesa-drivers to Mesa)
- _multibuild entries (?view=info expands them)

I had same filtering working on top of ?view=info which works well enough for
Leap, but does not work well for maintenance projects and SLE (mix of both) as

Hacks like excluding sourceinfo entries with ':' or '.' end up not working (at
least the '.'). Perhaps ':' is sufficient if no packages are allowed (or
exist) with ':' in name. There are packages with '.' the name that are not
maintenance updates (ex. python-jaraco.base which links python-

The proper way to differentiate a maintenance update package seems to be
<releasename> in the package meta.

<package name="GraphicsMagick.10066" project="openSUSE:Leap:15.0:Update">

The problem is that information is not available in view=info nor does it seem
searchable via /search/package[/id]. The search route also does not expand
project links which is necessary for SLE.

Even playing with checking the filename element does not work since image (ie.
non-spec) packages and product packages end up with special cases.

In conclusion, even with a rather complex client-side xpath query it is not
possible to get the list of "real packages" without making lots of followup
queries. Is there a proper way to query the list or can such a method be


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

< Previous Next >
Follow Ups