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: Mon, 13 May 2019 11:30:59 +0200
  • Message-id: <45825151.MokCKzCfY7@linux-ywca>
On Montag, 13. Mai 2019, 11:14:58 CEST Dominique Leuenberger / DimStar wrote:
On Mon, 2019-05-13 at 08:31 +0200, Adrian Schröter wrote:
Local Links

Same regarding the project local links, you should be fine if all packages
get the devel definition back. Meaning that in the package meta of Mesa-
drivers you add again

<devel package="Mesa"/>

so operations like branch calls get automatically redirected to the right
place. Yes, this is manual work here, but this is basically the main
difference between _multibuild and local links.

Add the info back?! Our staging accept tooling does create the linked
packages as well as the meta info to hae the 'main' set as devel - and
has been doing this for a long time. In case of Mesa-drivers. the meta

<package name="Mesa-drivers" project="openSUSE:Factory">
<title>System for rendering interactive 3-D graphics</title>
<description>Mesa is a 3-D graphics library with an API which[ ..
stripped description, irrelevant here...]</description>
<devel project="openSUSE:Factory" package="Mesa"/>

Any linked package not having this meta was most likely not accepted
using the Staging tooling.

okay, so there should be no problems with the standard workflows, if you have

It may be a problem inside of maintenance_release projects only, where we seem
not to have that information ....


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 >