On Friday, May 18, 2018 2:06:56 PM CDT Richard Brown wrote:

On 18 May 2018 at 16:56, Manfred Hollstein wrote:

...

Currently, no package can be built in Packman because all are "unresolvable". Andreas Schwab suggested that this should be fixed in 15.0 by the _project maintainer_, but so far this hasn't happened. I'm pretty sure having all (still required) packages from Packman will be appreciated by all users ;)

I believe Andreas' suggestion was that the _Packman_ Project maintainer corrects the problem in the _Packman_ project

He was referring to the maintainer of _Leap 15.0_ (ie lnussel). Referenced configuration difference: - openSUSE:Leap:42.3:Ports

<repository name="ports" rebuild="local" linkedbuild="all"> <path project="openSUSE:Leap:42.3" repository="standard"/>

- openSUSE:Leap:15.0:Ports

<repository name="ports" rebuild="local" block="local" linkedbuild="all"> <path project="openSUSE:Leap:15.0" repository="ports"/>

The repositories on base product project have the same configuration and the :Update repositories are setup the same as before as well. - Packman

<repository name="openSUSE_Leap_42.3"> <path project="openSUSE.org:openSUSE:Leap:42.3:Update" repository="standard"/>

<repository name="openSUSE_Leap_15.0"> <path project="openSUSE.org:openSUSE:Leap:15.0:Update" repository="standard"/>

Summary, Packman has the same config for 15.0 as 42.3. Leap has a different ports config for 15.0 and should be changed to match. Presumably others on OBS will have a similar problem when building against ports on OBS. I don't understand why OBS does not find the x86_64 binaries needed since a path element explicitly includes the standard repo. The ports repository does not have x86_64 available so how it is seemingly "overriding" is bizarre. -- Jimmy -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Mai 18 2018, Jimmy Berry wrote:

- Packman

...

<repository name="openSUSE_Leap_42.3"> <path project="openSUSE.org:openSUSE:Leap:42.3:Update" repository="standard"/>

...

<repository name="openSUSE_Leap_15.0"> <path project="openSUSE.org:openSUSE:Leap:15.0:Update" repository="standard"/>

Summary, Packman has the same config for 15.0 as 42.3. Leap has a different ports config for 15.0 and should be changed to match. Presumably others on OBS will have a similar problem when building against ports on OBS.

A workaround is to use separate repositories for standard and ports architectures.

I don't understand why OBS does not find the x86_64 binaries needed since a path element explicitly includes the standard repo. The ports repository does not have x86_64 available so how it is seemingly "overriding" is bizarre.

Only the last path element is recursively expanded, and openSUSE:Leap:15.0:Update/ports has no connection to openSUSE:Leap:15.0/standard. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Hi,

...

Only the last path element is recursively expanded, and openSUSE:Leap:15.0:Update/ports has no connection to openSUSE:Leap:15.0/standard. Is only looking recursively at the last repo a bug or a feature of obs?

It is a feature. the idea is that this way you can overwrite the result of an expansion of the last element by the earlier elements. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 19 May 2018 at 13:15, AW wrote:

Am Freitag, 18. Mai 2018, 21:06:56 CEST schrieb Richard Brown:

...

On 18 May 2018 at 16:56, Manfred Hollstein wrote:

...

Moin,

On Fri, 18 May 2018, 16:23:02 +0200, Ludwig Nussel wrote:

...

Hi,

openSUSE Leap 15.0 development is done, final build done, no submissions will be accepted anymore. ...

Congratulations! Would it be possible to get the problems with building packages in Packman for Leap 15.0 being addressed? There is a thread starting at

https://lists.opensuse.org/opensuse-factory/2018-05/msg00149.html

Currently, no package can be built in Packman because all are "unresolvable". Andreas Schwab suggested that this should be fixed in 15.0 by the _project maintainer_, but so far this hasn't happened. I'm pretty sure having all (still required) packages from Packman will be appreciated by all users ;)

I believe Andreas' suggestion was that the _Packman_ Project maintainer corrects the problem in the _Packman_ project

The openSUSE Leap 15.0 Ports Project is building just fine - https://build.opensuse.org/project/show/openSUSE:Leap:15.0:Ports

This is an openSUSE Project mailinglist, and as such is most certainly not the appropriate place for _Packman_ questions related to the setup of the Packman projects OBS instance.

I recommend you get in touch with that separate project via their appropriate communication channels.

Hi!

To many users like me Packman is an important part of openSuse, so calling it »that separate project« is from my point of view a bit too technical.

And I wonder what all the journalists will make of a release without a working Packman repo. Here in Germany heise.de examined openSuse critically since some years.

If e.g. VLC no longer could play a movie from a DVD, the verdict of users as well as of the media will be that Leap 15 has an issue.

So yes, this is an openSUSE Project mailinglist and this is an appropriate place for a warning.

Regards,

Alexander

If/when the day comes that the patent encumbered software in Packman is no longer be legally problematic, then openSUSE will happily have that software as part of the project, and there would be no issue discussing it on our formal mailinglists Until that day, if you wish the openSUSE project to continue to operate legally here in Germany, the EU, the US and probably elsewhere, then it's essential that topics solely related to Packman are kept as far away from official openSUSE channels as possible. They have their own mailinglist, if people want to discuss Packman's software, they should use them to discuss them there. Regards, Richard Brown openSUSE Board -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 2018-05-19 15:06, AW wrote:

Am Samstag, 19. Mai 2018, 14:31:13 CEST schrieb Richard Brown:

...

Until that day, if you wish the openSUSE project to continue to operate legally here in Germany, the EU, the US and probably elsewhere, then it's essential that topics solely related to Packman are kept as far away from official openSUSE channels as possible.

Dear Richard,

thank you for your time and effort to answer quickly. I don't buy your legal argument.

Go to forums.opensuse.org and search for »packman«. You'll get thousands of hits, on an official opensuse.org page.

Legal arguments should be discussed in legal circles. If the attorneys of SUSE regarded a discussion about packman as a risk, be sure, they would have told us right on this list.

There is no difference between us discussing it here or there.

By the way, I don't want to discuss packman software here. I'd like to point to the fact that a release of Leap 15 without an existing packman repo might cause lower scores in reviews after release -- and I really would like to see Leap 15 received as good as possible, like you and everybody else here.

Yes, reviews will certainly point that out. Internet will tell people to avoid openSUSE 15. Unless solved in time. I'm tired of explaining outside people why openSUSE doesn't come with multimedia support out of the box (and they nail me as stupid for defending openSUSE). But if I can not point them to the easy solution, I will be out of words. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)

Am 19.05.2018 um 14:31 schrieb Richard Brown:

If/when the day comes that the patent encumbered software in Packman is no longer be legally problematic, then openSUSE will happily have that software as part of the project, and there would be no issue discussing it on our formal mailinglists

Until that day, if you wish the openSUSE project to continue to operate legally here in Germany, the EU, the US and probably elsewhere, then it's essential that topics solely related to Packman are kept as far away from official openSUSE channels as possible.

They have their own mailinglist, if people want to discuss Packman's software, they should use them to discuss them there.

But they cannot change the wrong config on build.o.o (IIUC the problem). -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Am 20.05.2018 um 16:07 schrieb Jan Engelhardt:

On Saturday 2018-05-19 14:31, Richard Brown wrote:

...

...

...

...

...

openSUSE Leap 15.0 development is done, final build done, no submissions will be accepted anymore. ...

Currently, no package can be built in [$EXTERN_REPO] because all are "unresolvable". Andreas Schwab suggested that this should be fixed in 15.0 by the _project maintainer_, but so far this hasn't happened. I'm pretty sure having all (still required) packages from Packman will be appreciated by all users ;)

I believe Andreas' suggestion was that the [$EXTERN_REPO] Project maintainer corrects the problem in the [$EXTERN_REPO] project

[$EXTERN_REPO] have their own mailinglist, if people want to discuss [$EXTERN_REPO]'s software, they should use them to discuss them there.

Come on. It does not affect just that one extern repo everybody is so adamant talking about, it affects all of them, at least those that try to use Ports at the same time.

If only two maintainers can fix/are willing to maybe fix meta prj https://lists.opensuse.org/opensuse-factory/2018-05/msg00151.html and both of them are unavailable, isn't it time to come up with some holiday plan at least?

There are several persons with access as :Ports inherits maintainers via the hierarchy. Nevertheless Dirk is the master of Ports. I would only interfere there in case of emergency which I don't see here. I suppose there is a reason why it chains to ports rather than standard as before. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Hi,

same topic, other direction (Leap 42.3): I just got aware that the one-click installer on software.opensuse.org asks for the ports-repository as well.

From the .ymp file: <repository recommended="true"> <name>openSUSE:Leap:42.3:Ports</name> <summary></summary> <description></description> <url>http://download.opensuse.org/repositories/openSUSE:/Leap:/42.3:/ Ports/ports/</url> </repository>

Paste this into a browser: Resource is no longer available!

Who could fix the settings for the one-click installer?

I am not sure how those files are generated. maybe file a progress.opensuse.org ticket or a bugreport and I'll figure it out together with the OBS team? Thanks, Dirk -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Hi,

There are several persons with access as :Ports inherits maintainers via the hierarchy. Nevertheless Dirk is the master of Ports. I would only interfere there in case of emergency which I don't see here. I suppose there is a reason why it chains to ports rather than standard as before.

I was assuming that Leap:15.0/ports would link Leap:15.0/standard but it seems it doesn't. I've adjusted Leap:15.0:Ports/ports to point to Leap:15.0/standard now to solve this issue. Thanks for letting me know about the problem. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 2018-05-19 13:15, AW wrote:

Am Freitag, 18. Mai 2018, 21:06:56 CEST schrieb Richard Brown:

...

On 18 May 2018 at 16:56, Manfred Hollstein wrote:

...

Moin,

On Fri, 18 May 2018, 16:23:02 +0200, Ludwig Nussel wrote:

...

Hi,

openSUSE Leap 15.0 development is done, final build done, no submissions will be accepted anymore. ...

Congratulations! Would it be possible to get the problems with building packages in Packman for Leap 15.0 being addressed? There is a thread starting at

https://lists.opensuse.org/opensuse-factory/2018-05/msg00149.html

Currently, no package can be built in Packman because all are "unresolvable". Andreas Schwab suggested that this should be fixed in 15.0 by the _project maintainer_, but so far this hasn't happened. I'm pretty sure having all (still required) packages from Packman will be appreciated by all users ;)

I believe Andreas' suggestion was that the _Packman_ Project maintainer corrects the problem in the _Packman_ project

The openSUSE Leap 15.0 Ports Project is building just fine - https://build.opensuse.org/project/show/openSUSE:Leap:15.0:Ports

This is an openSUSE Project mailinglist, and as such is most certainly not the appropriate place for _Packman_ questions related to the setup of the Packman projects OBS instance.

I recommend you get in touch with that separate project via their appropriate communication channels.

Hi!

To many users like me Packman is an important part of openSuse, so calling it »that separate project« is from my point of view a bit too technical.

And I wonder what all the journalists will make of a release without a working Packman repo. Here in Germany heise.de examined openSuse critically since some years.

If e.g. VLC no longer could play a movie from a DVD, the verdict of users as well as of the media will be that Leap 15 has an issue.

So yes, this is an openSUSE Project mailinglist and this is an appropriate place for a warning.

I have to agree. The packman repo has got to work on release day or it will be a disaster for openSUSE. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)

18.05.2018 21:20, Michal Kubecek пишет:

On Friday, 18 May 2018 19:12 Frank Krüger wrote:

...

Regarding the SHIP_STOPPER https://bugzilla.suse.com/show_bug.cgi?id=1092352, is there a solution in sight?

It's not a ship stopper.

It is marked as such.

If it were, we wouldn't have GM now (by definition).

This simply means that SHIP_STOPPER bugs are ignored by release process which makes the very idea of having such indication meaningless.

Michal Kubecek

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

On 18 May 2018 at 20:45, Oliver Kurz wrote:

On Friday, 18 May 2018 20:24:14 CEST Andrei Borzenkov wrote:

...

18.05.2018 21:20, Michal Kubecek пишет:

...

On Friday, 18 May 2018 19:12 Frank Krüger wrote:

...

Regarding the SHIP_STOPPER https://bugzilla.suse.com/show_bug.cgi?id=1092352, is there a solution in sight?

It's not a ship stopper.

It is marked as such.

It's not. From the bug history: lnussel@suse.com 2018-05-14 08:55:27 UTC Flags SHIP_STOPPER+ SHIP_STOPPER-

meaning that lnussel, the project manager for openSUSE Leap 15.0 re-evaluated the bug and denied it as a ship stopper.

Exactly - the full glossary of terms in bugzilla make it very clear that the bug in question has been evaluated and found to NOT be a ship stopper https://bugzilla.suse.com/page.cgi?id=glossary.html#ship_stopper

...

...

If it were, we wouldn't have GM now (by definition).

This simply means that SHIP_STOPPER bugs are ignored by release process which makes the very idea of having such indication meaningless.

From my experience the process works :) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

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