Am Montag 04 Juni 2012, 23:10:52 schrieb Sven Burmeister:

So I would suggest to simply create a KR49 repo and mediate via wiki, mailinglist etc. that this repo is (obviously) not stable until upstream releases 4.9.0 and the package names contain 4.9 and not 4.8.85 etc.

Alternatively KUSC could stay as it is. With RC1, packages can be moved to KR49 and everything missing gets added.

If you remember, I in the past advocated for early KR repos to have them ready right on time when the actual release happens. I still think that "Get 4.9 binaries from the KR49 repo" in KDE release announcements is great advertisement for oS. However, the scope of this thread is testing. Personally, I do not have the disk space for a full oS install inside a VM. I think what oS needs is a procedure to test really early DE pre-releases without conflicting with a stable DE release. Doesn't oS ship with patches to change the KDE install directory from /opt to /usr and keep the settings in ~/.kde4 instead of ~/.kde? Why not drop the first patch to install KUSC binaries in /opt and change the second patch to write settings to ~/.kde-unsable or whatever? -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

On Thursday 07 Jun 2012 09:22:08 Křištof Želechovski wrote:

Dnia wtorek, 5 czerwca 2012 01:39:41 Markus pisze:

...

Why not drop the first patch to install KUSC binaries in /opt and change the second patch to write settings to ~/.kde-unsable or whatever?

KDE3 lives in /opt, and we cannot drop KDE3 because the file type database in KDE4 is bro-ken and declares file types that only KDE3 applications (declare to) handle (e.g. Ark and Konsole).

Of course, the right solution would be to make the file type database consistent :-)

Can you explain the problem in more detail? It sounds like eg ark.desktop and konsole.desktop are declaring that they handle mime types that they do not, but to check this I'd like to know which mime type/app combinations cause problems under KDE 4. Or do you mean that KDE apps are registering new types (in /usr/share/mime) that they do not handle? If so, which types? Will -- Will Stephenson, openSUSE Board, Booster, KDE Developer 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-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

On 05/06/12 08:05, C wrote:

On Mon, Jun 4, 2012 at 11:10 PM, Sven Burmeister wrote:

...

Am Montag, 4. Juni 2012, 22:54:51 schrieb Will Stephenson:

...

Do we create KR49 repo in advance and package tarballs there, do we use KUSC snapshots right up until release day, or do we use KDE released tarballs as KUSC sources? This would be my preferred technique, as this provides testing of prerelease milestones, rather than arbitrary snapshots from git. It also does not add additional load to the team or OBS. Last time KUSC was used to prepare a release this caused some confusion and Raymond did not like it since it breaks its actual purpose. I agree with that.

https://bugzilla.novell.com/show_bug.cgi?id=706813#c1

So I would suggest to simply create a KR49 repo and mediate via wiki, mailinglist etc. that this repo is (obviously) not stable until upstream releases 4.9.0 and the package names contain 4.9 and not 4.8.85 etc.

Alternatively KUSC could stay as it is. With RC1, packages can be moved to KR49 and everything missing gets added. My vote is for a KR49 repo that lives alongside the KR48 and 47 etc repos. Treat it the same as any other release. I'll be testing it on a live system as soon as it's available in the repo.

C. I'd like to see continuity and have Release49 also Thanks -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

On Monday, June 04, 2012, Sven Burmeister wrote:

Am Montag, 4. Juni 2012, 22:54:51 schrieb Will Stephenson:

...

Do we create KR49 repo in advance and package tarballs there, do we use KUSC snapshots right up until release day, or do we use KDE released tarballs as KUSC sources? This would be my preferred technique, as this provides testing of prerelease milestones, rather than arbitrary snapshots from git. It also does not add additional load to the team or OBS.

Last time KUSC was used to prepare a release this caused some confusion and Raymond did not like it since it breaks its actual purpose. I agree with that.

It wasn't really me that objected, but we indicate that KUSC contains weekly snapshots and preparing a release based on official tarballs is somehow not consistent with this. However as Martin also indicated we should focus on 12.2 right now and once this gets released we can utilize the spec-files, etc in KUSC to prepare faster the KR49 repo. KUSC contains the spec-files and patches from KDF and I have been keepting them up-to-date. So it should be quite easy to validate them and re-use them. So let's target 12.2 first and after 12.2 we can prepare KR49. Regards Raymond -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

On Friday, June 29, 2012 14:01:23 Markus wrote:

Am Dienstag 05 Juni 2012, 12:59:12 schrieb Raymond Wooninck:

...

So let's target 12.2 first and after 12.2 we can prepare KR49.

So no semi-stable way to install KR49 until September or possibly later? Too bad the once best KDE distribution moves in that direction.

At this moment KDE:Unstable:SC is building a snapshot that is close to KDE 4.9 RC1. So if you enable KDE:Unstable:SC then you would get KDE 4.9 which is in a pretty good shape. Regards Raymond -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

On Fri, Jun 29, 2012 at 3:22 PM, Raymond Wooninck wrote:

On Friday, June 29, 2012 14:01:23 Markus wrote:

...

Am Dienstag 05 Juni 2012, 12:59:12 schrieb Raymond Wooninck:

...

So let's target 12.2 first and after 12.2 we can prepare KR49.

So no semi-stable way to install KR49 until September or possibly later? Too bad the once best KDE distribution moves in that direction.

At this moment KDE:Unstable:SC is building a snapshot that is close to KDE 4.9 RC1. So if you enable KDE:Unstable:SC then you would get KDE 4.9 which is in a pretty good shape.

Regards

Raymond

KDE 4.9 is branched, which means we can no longer count on master being similar to 4.9, and it means that master will likely start getting unstable commits any time now (if it hasn't already). Is the objection to having KDE SC 4.9, or is it merely a lack of volunteers? If the latter, it may take me a few days, but I am willing to help set up a 4.9 repo if someone with access can create it and give me access. -Todd -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

On Tuesday, June 05, 2012, C wrote:

We are at a disadvantage as it stands now. KDE4.8.80 is already available on several other distros. Can we set up the repo and build targets and let it build without any openSUSE specific patching/tweaking?

I assume you are not aware of the KDE:Unstable:SC repository on OBS ? This one contains weekly snapshots and the last one is very close the the official Beta 1 packages (therefore it contains the version number 4.8.80). The packages got build and published for 11.4, 12.1 and Factory. Factory however contained some unresolvable due to the issues around perl. Since that it finished building, I will push a new snapshot in sometime this week so that we can even test the latest improvements on the Beta 1. Regards Raymond -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

On Tuesday 05 Jun 2012 13:30:32 C wrote:

On Tue, Jun 5, 2012 at 1:24 PM, Raymond Wooninck wrote:

...

I assume you are not aware of the KDE:Unstable:SC repository on OBS ? This one contains weekly snapshots and the last one is very close the the official Beta 1 packages (therefore it contains the version number 4.8.80). The packages got build and published for 11.4, 12.1 and Factory. Factory however contained some unresolvable due to the issues around perl.

Since that it finished building, I will push a new snapshot in sometime this week so that we can even test the latest improvements on the Beta 1. Oh.. right :-P I'll just go back to work now :-)

So, what's the issue raised here then? Whether we have a tweaked openSUSE KDE4.9 Beta or not? (I thought.. clearly mistakenly... that for some reason no weekly snapshots would be built... I stand corrected (and I think I need more sleep instead of working 2 full time jobs).

KUSC snapshots are very similar to the betas but are not identical to them. So for people who want to test the betas, they might report bugs that are fixed, or report vs the wrong beta. Which annoys upstream, who are launching a more formal beta testing project. So KUSC is great for us between betas, because we don't get surprised by the volume of changes in the first beta, but not so useful for working with upstream. Will -- Will Stephenson, openSUSE Board, Booster, KDE Developer 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-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org