Mailinglist Archive: opensuse-factory (421 mails)

< Previous Next >
Re: [opensuse-factory] About Leap maintenance : bsc not authorized
Hello Bruno,

On 09/15/2017 12:38 PM, Bruno Friedmann wrote:
There's an increase in the number of bsc bnc boo related to Maintenance
from SLE on Leap.

Most of the ticket, which would be the source of informations are hidden
after a login as normal openSUSE user).

That'll be items in SLE development, support/L3 and partner reported bugs.

So we forbid users to have a look at the changes, which is not in favor of
chain of trust and openess attitude.

You make it sound more closed than it really is. The source changes are
public in the build service:
osc rdiff openSUSE:Leap:42.3/squid openSUSE:Leap:42.3:Update/squid.7263

All running incidents:
All binaries and sources:

So would it be possible to have a damn bot, with simple rights which should
reject any submission to Leap if issues are not opened ?

Solution before problem? You seem to drastically underestimate the level
of automation involved when importing updated sources from
SUSE:SLE-12*:Update into openSUSE:Maintenance incidents. That was a
major point of Leap, by the way.

Re-arranging the references in the spec files, patch comments,
changelogs and update descriptions to refer to a cloned bug is
unfeasible. The import is source diff based, so is the harmonization
effort between SLE and openSUSE. The alternative, opening all bugs by
default, including pre-release and enterprise product areas, would be a
massive change to processes. I am not sure that this will be answered in

Having meaningful package changelog entries and maintenance update
descriptions is a good compromise, beyond the available sources and
review team inclusion.


Andreas Stieger <astieger@xxxxxxx>
Project Manager Security
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)

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

< Previous Next >
Follow Ups