2013/9/23 Stephan Kulow :

Hi,

We branched the sources of factory into openSUSE:13.1 and from now on I will cherry pick openSUSE:Factory submit requests to copy into 13.1

To ease my work there, it would be great if you document your expectations and the bugs you fixed.

E.g. I agreed to take GNOME 3.10, but that does not mean every update of a package that has GNOME in the group tag is automatically going into 13.1.

The accept message of your submit request will tell you if I copied to 13.1 or not.

When will the dvd iso images available? Thanks, Juan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

On Mon, 23 Sep 2013 11:09:31 +0200 Stephan Kulow wrote:

Hi,

We branched the sources of factory into openSUSE:13.1 and from now on I will cherry pick openSUSE:Factory submit requests to copy into 13.1

Hi Coolo, I wonder what repositories I should set up on my machine if I want to continue testing oS 13.1, including changes made after Beta? Until now I've been using http://download.opensuse.org/factory/repo/oss/ (and friends) But this is going to receive changes that won't appear in oS13.1. Repository publishing for openSUSE:13.1 in OBS is disabled. Description refers me to http://en.opensuse.org/Portal:13.1 but that page doesn't even exist, so I'm lost. :-( Petr T -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Quoting Stephan Kulow :

Well, the portal will exist by the time 13.1 is locked and I won't be able to change the description, so we set the description to be right forever while it's wrong for the next 2 months :)

If you install 13.1 Beta, it will setup http://download.opensuse.org/distribution/13.1/repo/oss as repository and that's the one that will update to RC1. Between Beta and RC1 I don't plan to update the repos.

Stephan, This seems to become an 'issue' with various testers. I had several cases of bug reports against Beta1 where GNOME:Factory (and openSUSE:factory) had the updates in place (but due to timing issues the .92 release was just not available for beta 1.. we always knew that). Most seem to be afraid of adding Factory, as * it is not guaranteed that no other component that does not make it into 13.1 has been updated there, causing different side effects * Addnig a devel project usually gives the same fear: they are built against Factory, not 13.1 (of course I could add this as a built target.. and putting more efforts on OBS). From what I have seen myself, there is likely nothing in Factory which did not make it in 13.1 as well , so of course point 1 is a bit 'weak', but that's only true when you're fully involved in the full process. For most 'beta testers' it is considered 'unsafe' to add Factory on top in order to confirm bugs are gone. If testers can confirm that, then we loose an entire beta1 to RC1 timeframe to confirm and re-evaluate bug reports... which leaves us with less time to fix after (and the same will be in the time RC1 to RC2 and RC2 to GM). Dominique PS: I so far managed to get my results and was always on the safe side.. but the convincing efforts get bigger the closer we get to GM.. and the chance that things are in Factory but not in 13.1 are also increasing at the same time. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Hi, Am 25.09.2013 13:38, schrieb Dominique Leuenberger a.k.a. Dimstar:

Quoting Stephan Kulow :

...

Well, the portal will exist by the time 13.1 is locked and I won't be able to change the description, so we set the description to be right forever while it's wrong for the next 2 months :)

If you install 13.1 Beta, it will setup http://download.opensuse.org/distribution/13.1/repo/oss as repository and that's the one that will update to RC1. Between Beta and RC1 I don't plan to update the repos.

Stephan,

This seems to become an 'issue' with various testers. I had several cases of bug reports against Beta1 where GNOME:Factory (and openSUSE:factory) had the updates in place (but due to timing issues the .92 release was just not available for beta 1.. we always knew that).

I was one of the "complainers" and I can only second what Dominique points out as reasons.

Most seem to be afraid of adding Factory, as * it is not guaranteed that no other component that does not make it into 13.1 has been updated there, causing different side effects * Addnig a devel project usually gives the same fear: they are built against Factory, not 13.1 (of course I could add this as a built target.. and putting more efforts on OBS).

From what I have seen myself, there is likely nothing in Factory which did not make it in 13.1 as well , so of course point 1 is a bit 'weak', but that's only true when you're fully involved in the full process. For most 'beta testers' it is considered 'unsafe' to add Factory on top in order to confirm bugs are gone.

I haven't seen a guarantee that Factory is frozen to only carry updates considered for 13.1 but I might missed it. I saw hints about it in the roadmap but read other statements somewhere else. So I think I'm pretty near to the process (not like the release team) but I'm still scared about using Factory since beta 1 because I would like to end up with 13.1 and not with 13.1.99.

If testers can confirm that, then we loose an entire beta1 to RC1 timeframe to confirm and re-evaluate bug reports... which leaves us with less time to fix after (and the same will be in the time RC1 to RC2 and RC2 to GM).

Dominique

PS: I so far managed to get my results and was always on the safe side.. but the convincing efforts get bigger the closer we get to GM.. and the chance that things are in Factory but not in 13.1 are also increasing at the same time.

My hope and expectations until two days ago was that there will be a 13.1 repo (a bit hidden) which gets updated as packages come in (basically like Factory in normal mode). Not for general consumption (again as Factory) but for people knowing what they are doing. Adding every single devel project where I find issues is not a solution for that problem. So I'm wondering what the reasons are to not have a 13.1 repo published with the current state of things (as long as it builds)? Is it build power? Is it ...? Wolfgang -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Stephan Kulow wrote:

On 25.09.2013 14:51, Wolfgang Rosenauer wrote:

...

So I'm wondering what the reasons are to not have a 13.1 repo published with the current state of things (as long as it builds)? Is it build power? Is it ...?

For factory we have a rather crazy setup to make sure the repo works all the time and we don't have the bandwith and man power to have that duplicated. So I will do as I did in the past: I will reuse factory-snapshot once 13.1 is stable.

Note it's already possible to create maintenance updates for 13.1. So important bugfixes can be released that way. In fact, we even need a few updates to test the update stack already. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

On 25.09.2013 15:20, Greg Freemyer wrote:

Stephan Kulow wrote:

...

On 25.09.2013 14:51, Wolfgang Rosenauer wrote:

...

So I'm wondering what the reasons are to not have a 13.1 repo published with the current state of things (as long as it builds)? Is it build power? Is it ...?

For factory we have a rather crazy setup to make sure the repo works all the time and we don't have the bandwith and man power to have that duplicated. So I will do as I did in the past: I will reuse factory-snapshot once 13.1 is stable.

Greetings, Stephan

Coolo,

Can you clarify the current and short-term freeze status of factory?

I assumed post branch it was unfrozen.

Factory is not frozen, but it makes a lot of sense for the devel projects to stabilize and fix bugs instead of breaking them even more. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Vitezslav Cizek wrote:

* Dne Středa 25. září 2013, 15:15:06 [CEST] Ludwig Nussel napsal:

...

Note it's already possible to create maintenance updates for 13.1. So important bugfixes can be released that way. In fact, we even need a few updates to test the update stack already.

It certainly looks like it'll need some more tweaking. [...] I suppose we can still use the old way and submit to openSUSE:13.1:Update directly.

13.1 is not marked as maintained yet, that's correct. I suppose the submit to openSUSE:13.1:Update will create the correct maintenance request. I haven't tried it myself though. For the update I needed I asked Benjamin :-) cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Am Mittwoch, 25. September 2013, 17:40:38 schrieb Ludwig Nussel:

Vitezslav Cizek wrote:

...

* Dne Středa 25. září 2013, 15:15:06 [CEST] Ludwig Nussel napsal:

...

Note it's already possible to create maintenance updates for 13.1. So important bugfixes can be released that way. In fact, we even need a few updates to test the update stack already.

It certainly looks like it'll need some more tweaking. [...] I suppose we can still use the old way and submit to openSUSE:13.1:Update directly. 13.1 is not marked as maintained yet, that's correct. I suppose the submit to openSUSE:13.1:Update will create the correct maintenance request. I haven't tried it myself though. For the update I needed I asked Benjamin :-)

it will, but it will lead to the exact same error as with creating the maintenance request manualy as Vitezslav did. -- Adrian Schroeter email: adrian@suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Am 25.09.2013 15:23, schrieb Stephan Kulow:

On 25.09.2013 15:20, Greg Freemyer wrote:

...

Can you clarify the current and short-term freeze status of factory?

I assumed post branch it was unfrozen.

Factory is not frozen, but it makes a lot of sense for the devel projects to stabilize and fix bugs instead of breaking them even more.

makes sense but also means we are ahead of time: http://en.opensuse.org/Roadmap 2013-10-01: Start of Maintenance Distro is branched in OBS Maintenance accepts 13.1 updates, Factory packages do not end up in 13.1 automatically anymore Factory unfrozen Factory unfrozen sounds like Factory is frozen until first of October. That's what I found which confused me even more. Wolfgang -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

On 09/25/13 14:39, Jan Engelhardt wrote:

On Monday 2013-09-23 11:09, Stephan Kulow wrote:

...

Hi,

We branched the sources of factory into openSUSE:13.1 and from now on I will cherry pick openSUSE:Factory submit requests to copy into 13.1

I have no idea how to address http://s.kulow.org/bf-iproute2 or http://s.kulow.org/bf-xindy both of which seem to be texlive related.

The xindy build problem is probably because some fonts aren't available. It aborts the creation of a documentation file that shows all alphabets that can be sorted with xindy. The log file shown at http://s.kulow.org/bf-xindy is not sufficient for me to analyze the problem further; I would need to have access to the build directory to be able to check the TeX log file from creation of alphabets-doc.pdf. Short term solution would be --disable-docs at configure... I have no factory/13.1 install available where I can test this assumption. If there's anything I can help nevertheless, contact me. Joachim (xindy's upstream^2 maintainer) -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod, Roedermark, Germany Email: jschrod@acm.org -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Jan Engelhardt writes:

On Monday 2013-09-30 12:32, Joachim Schrod wrote:

...

...

I have no idea how to address http://s.kulow.org/bf-iproute2 or http://s.kulow.org/bf-xindy both of which seem to be texlive related.

The xindy build problem is probably because some fonts aren't available. It aborts the creation of a documentation file that shows all alphabets that can be sorted with xindy. The log file shown at http://s.kulow.org/bf-xindy is not sufficient for me to analyze the problem further; I would need to have access to the build directory to be able to check the TeX log file from creation of alphabets-doc.pdf.

osc co Publishing/xindy; osc build openSUSE_Factory; osc chroot openSUSE_Factory;

in case you run any openSUSE.

I've got 11.4 (on Evergreen) and 12.2 here (12.2 with a nasty problem that rpcbind hangs without any error log message that prevents me from using it regularly). I'll try if I can establish a build environment on one of these systems. If not, I'll install factory or 13.1 in a VM instance.

...

Short term solution would be --disable-docs at configure...

It then falls over in another place, though.

[ 92s] Making all in inputenc [ 92s] make[2]: Entering directory `/home/abuild/rpmbuild/BUILD/xindy-2.4/make-rules/inputenc' [ 92s] /usr/bin/perl ./make-testidx.pl TS1,T2A,T1 cp1250 >cp1250.tex [ 92s] latex -interaction batchmode cp1250.tex [ 92s] This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013/TeX Live for SUSE Linux) [ 92s] restricted \write18 enabled. [ 92s] entering extended mode [ 92s] make[2]: *** [cp1250.xdy] Error 1

That's about as good as Windows's "unknown error" dialog :-(

The error message is probably in cp1250.log. I think it's an issue of build-requires; I will have a look at it. Cheers, Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Joachim Schrod, xindy maintainer. Roedermark, Germany Email: jschrod@acm.org, http://www.xindy.org/ -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Greg Freemyer writes:

On Mon, Sep 30, 2013 at 8:41 AM, Joachim Schrod wrote:

...

...

osc co Publishing/xindy; osc build openSUSE_Factory; osc chroot openSUSE_Factory;

in case you run any openSUSE.

...

I'll try if I can establish a build environment on one of these systems. If not, I'll install factory or 13.1 in a VM instance.

osc will create the build environment inside of a chroot jail. Installing gcc etc. into your main environment has no benefit / detriment as far as osc is concerned. You probably want to get the latest version of osc and not the potentially very old version on 11.4.

You can install from openSUSE:Tools/osc

http://software.opensuse.org/download.html?project=openSUSE%3ATools&package=osc

A current osc is what I meant with `establish a build environment'. Thanks for the link to the OBS repository; now I don't have to search for it. Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Joachim Schrod, xindy maintainer. Roedermark, Germany Email: jschrod@acm.org, http://www.xindy.org/ -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org