Mailinglist Archive: opensuse-packaging (132 mails)

< Previous Next >
Re: [opensuse-packaging] how to avoid SUSE-Backports-policy-SLE-conflict
On Dienstag, 3. Januar 2017, 13:40:12 CET wrote Olaf Hering:
On Tue, Jan 03, Marcus Meissner wrote:

Olaf, just open a bug describing the change you do in build-compare and
submit an updated build-compare for SLE12.

In case of build-compare just _link to openSUSE:Factory/build-compare.
It is always safe to use the latest version of that package.
If not, give me a call.

But it turned out the whole check is flawed because its not easy to use
the Backports project as a base for other projects.

backports is supposed to be a maintenance project. It is intended
to ship community maintained packages which do not affect the support
status of a SLE installation.

You are using it more as some development playground, so please do not
complain that the check is flawed. It is doing what is supposed to do ;)

If you don't care, just disable it. But the users of your project would
of course not have the same support level as users of the plain Background

I was hoping for a repo stack like this:

If myprj needs 'X-devel' its not possible to rebuild X in myprj because
the checks inherited from Backports cause a build failure, even if X is
_linked from SUSE:SLE-12-SP2:GA/X (or wherever X was initially

So either all the missing devel packages get published, or Backports
rebuilds all of the packages with missing devel packages, or each myprj
has to continue to duplicate these packages.

In the meantime I will stop using the Backports project as base.



Adrian Schroeter
email: adrian@xxxxxxx

SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284
(AG Nürnberg)

Maxfeldstraße 5
90409 Nürnberg

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

< Previous Next >