On August 1, 2012 06:28:45 PM Carl Fletcher wrote:

On 01/08/12 17:54, Sven Burmeister wrote:

...

Hey everybody!

KDE SC 4.9 was released today and KR49 far from finished building. adrianS was so kind to increase KR49's build prio to get it done. Thanks for that!

Since this is the third upstream release in a row that openSUSE packages are not available on release day, those writing reviews on release day, including internet magazines, cannot use openSUSE. Is that something to care about, missing the chance to get some mentioning on the media publicity-wise?

This time the biggest issue was that the buildservice is very slow to rebuild most packages in the KDE repo since they are not changed but just rebuilt because their dependency changed. Is there anything one can do about that except cheating by changing some bogus files in a package's source to get a higher build prio due to "changed source"? You might have noticed that if you branch a package it starts building almost instantly while building within KRxy can take days even for "scheduled" packages, although KRxy is certainly more important than a home project.

The slow building is also quite tiresome for those working on the packages – I suppose.

Thanks to everybody working on KR49, especially to Todd!

Sven

It really is appreciated. Thanks

Carl

Great job guys! Kudos to Todd! Cheers! Roman -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

On Wednesday 01 August 2012 22:59:47 Will Stephenson wrote:

On Wednesday 01 Aug 2012 18:54:51 Sven Burmeister wrote: Now 12.1 x86_64 is green and could be published - i586 is going to take a few more hours.

seems that the publisher is not publishing the finished packages for i586 so in order for the others to be built... Let's see later today... Nico -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

On 02/08/12 14:16, Will Stephenson wrote:

...

seems that the publisher is not publishing the finished packages for i586 so in order for the others to be built... Yes, that's the way publishing works. The entire set of buildable enabled

On Thursday 02 Aug 2012 00:11:56 Nico Kruber wrote: packages in the repo has to have been attempted to be built, then the whole set of succeeded results are published.

Will

Is this the URL for KDE 49 please?- http://download.opensuse.org/repositories/KDE:/Release:/49/openSUSE_12.2/ BC -- Using openSUSE 12.2 x86_64 KDE 4.8.4 & kernel 3.5.0-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

On 02/08/12 17:12, todd rme wrote:

On Thu, Aug 2, 2012 at 8:48 AM, Basil Chupin wrote:

...

On 02/08/12 14:16, Will Stephenson wrote:

...

...

seems that the publisher is not publishing the finished packages for i586 so in order for the others to be built... Yes, that's the way publishing works. The entire set of buildable enabled

On Thursday 02 Aug 2012 00:11:56 Nico Kruber wrote: packages in the repo has to have been attempted to be built, then the whole set of succeeded results are published.

Will

Is this the URL for KDE 49 please?-

http://download.opensuse.org/repositories/KDE:/Release:/49/openSUSE_12.2/

BC It will be, but right now 12.2 is still on RC2. I am trying to get 12.1 out the door first. It will be ready when its ready, I'm afraid, building is going slow.

-Todd Thank you!

BC -- Using openSUSE 12.2 x86_64 KDE 4.8.4 & kernel 3.5.0-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

On 02/08/12 17:13, Nico Kruber wrote:

On Thursday 02 Aug 2012 16:48:58 Basil Chupin wrote:

...

On 02/08/12 14:16, Will Stephenson wrote:

...

...

seems that the publisher is not publishing the finished packages for i586 so in order for the others to be built... Yes, that's the way publishing works. The entire set of buildable enabled

On Thursday 02 Aug 2012 00:11:56 Nico Kruber wrote: packages in the repo has to have been attempted to be built, then the whole set of succeeded results are published.

Will Is this the URL for KDE 49 please?-

http://download.opensuse.org/repositories/KDE:/Release:/49/openSUSE_12.2/

BC If you are using openSUSE 12.2, then yes - but build for openSUSE 12.2 has not been enabled yet - we're first concentrating on 12.1 and wait for it to finish building the complete repo before enabling others. The published 12.2 repo probably still contains RC2.

Nico

Yep, it's for 12.2. Thank you for the informatin. BC -- Using openSUSE 12.2 x86_64 KDE 4.8.4 & kernel 3.5.0-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

On Thu, Aug 2, 2012 at 9:15 AM, Nico Kruber wrote:

On Thursday 02 Aug 2012 06:16:17 Will Stephenson wrote:

...

On Thursday 02 Aug 2012 00:11:56 Nico Kruber wrote:

...

seems that the publisher is not publishing the finished packages for i586 so in order for the others to be built...

Yes, that's the way publishing works. The entire set of buildable enabled packages in the repo has to have been attempted to be built, then the whole set of succeeded results are published.

-> I just saw the mails on the opensuse-buildservice mailinglist and it seems that the scheduler (that's apparently the right name for the component I meant) is dead...

Looks like the problem is restricted to i586, I have enabled building on 12.2 x86_64 in the meantime. -Todd -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

todd rme wrote:

On Wed, Aug 1, 2012 at 10:59 PM, Will Stephenson wrote:

...

On Wednesday 01 Aug 2012 18:54:51 Sven Burmeister wrote:

...

Since this is the third upstream release in a row that openSUSE packages are not available on release day, those writing reviews on release day, including internet magazines, cannot use openSUSE. Is that something to care about, missing the chance to get some mentioning on the media publicity-wise?

Now 12.1 x86_64 is green and could be published - i586 is going to take a few more hours.

x86_64 has been published. It should be safe to use, only apidocs and oxygen-molecule are i586 only. I will personally begin installation once I send this email. I will build the x86_64 12.2 and then factory packages while I wait for the i586 scheduler to come back on line.

-Todd Hi,

thanks a lot on writing about the progress in building and publishing KR49. It is very much appreciated, but was too often not done in the past for other releases. So, repositories which apparently looked in a good shape from what could be guessed from obs, were still broken. It would be nice to shortly comment about the first experiences after installation, so that we can have a clue when it is relatively save to install the packages ourselves. Thanks to all who contibuted to generating the packages so far! Stefan -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

On Thu, Aug 2, 2012 at 11:02 AM, Basil Chupin wrote:

On 02/08/12 17:28, todd rme wrote:

...

On Wed, Aug 1, 2012 at 10:59 PM, Will Stephenson wrote:

...

On Wednesday 01 Aug 2012 18:54:51 Sven Burmeister wrote:

...

Since this is the third upstream release in a row that openSUSE packages are not available on release day, those writing reviews on release day, including internet magazines, cannot use openSUSE. Is that something to care about, missing the chance to get some mentioning on the media publicity-wise?

Now 12.1 x86_64 is green and could be published - i586 is going to take a few more hours.

x86_64 has been published. It should be safe to use, only apidocs and oxygen-molecule are i586 only. I will personally begin installation once I send this email. I will build the x86_64 12.2 and then factory packages while I wait for the i586 scheduler to come back on line.

-Todd

So very good to hear that the 12.2 is to be built.

Questions: when will the building actually begin

About half an hour ago

and how long does such a build normally take?

Hard to say. It just depends on what state obs is in. Right now, unfortunately, its state is not very good, so it could be a long time. I would be happy if it gets out today, but for all I know it could be out in a couple of hours. I really can't say. Sorry. -Todd -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

Am Donnerstag, 2. August 2012, 19:02:25 schrieb Basil Chupin:

So very good to hear that the 12.2 is to be built.

https://build.opensuse.org/project/monitor?project=KDE%3ARelease%3A49 shows you the status. Sven -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

On Thursday 02 Aug 2012 21:34:25 Basil Chupin wrote:

On 02/08/12 19:27, Sven Burmeister wrote:

...

Am Donnerstag, 2. August 2012, 19:02:25 schrieb Basil Chupin:

...

So very good to hear that the 12.2 is to be built.

https://build.opensuse.org/project/monitor?project=KDE%3ARelease%3A49 shows you the status.

Sven

Thank you! A most interesting graphic! But I don't like the "unresolvable" and the "blocked" bits, especially the former :-) .

BC

don't worry about the former - this is the result of e.g. a 4.9.0 ready-built kdebase4-workspace-devel which is a built-dependency but itself requires kdebase4-runtime which has not yet been built with version 4.9.0 -> this will resolve automatically once everything is built Nico -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

On Thursday 02 Aug 2012 22:32:33 Basil Chupin wrote:

On 02/08/12 22:03, Nico Kruber wrote:

...

On Thursday 02 Aug 2012 21:34:25 Basil Chupin wrote:

...

On 02/08/12 19:27, Sven Burmeister wrote:

...

Am Donnerstag, 2. August 2012, 19:02:25 schrieb Basil Chupin:

...

So very good to hear that the 12.2 is to be built.

https://build.opensuse.org/project/monitor?project=KDE%3ARelease%3A49 shows you the status.

Sven

Thank you! A most interesting graphic! But I don't like the "unresolvable" and the "blocked" bits, especially the former :-) .

BC

don't worry about the former - this is the result of e.g. a 4.9.0 ready-built kdebase4-workspace-devel which is a built-dependency but itself requires kdebase4-runtime which has not yet been built with version 4.9.0 -> this will resolve automatically once everything is built

Nico

Thanks, but I thought that this is what "blocked" is defined as: 'waiting for package(s) to be built'.

it kinda is - but blocked only seems to parse the Build-Depends fields of the spec files. kdebase4-workspace-devel is in the build-depends but succeeded and is thus available -> kdebase4-runtime is just a requirement of kdebase4-workspace-devel when being installed obviously, one could extend the parsing to look further and follow these chains to better present the current state Ultimately this could lead to fewer rebuilds, too. Let's assume kdeartwork4 build-depends on kdebase4-workspace-devel which requires kdebase4-runtime. If the required versions are available and kdebase4-workspace-devel is ready, kdeartwork4 will begin to build. However, once kdebase4-runtime finishes, it will have to build again, will it?

But then "unresolvable" could also be interpreted this way :-) .

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

On 02/08/12 22:05, todd rme wrote:

On Thu, Aug 2, 2012 at 1:34 PM, Basil Chupin wrote:

...

On 02/08/12 19:27, Sven Burmeister wrote:

...

Am Donnerstag, 2. August 2012, 19:02:25 schrieb Basil Chupin:

...

So very good to hear that the 12.2 is to be built. https://build.opensuse.org/project/monitor?project=KDE%3ARelease%3A49 shows you the status.

Sven Thank you! A most interesting graphic! But I don't like the "unresolvable" and the "blocked" bits, especially the former :-) . Those are temporary. What happens is that packages are set to depend on the current KDE SC release. However, the base packages for that release have not been built yet.

So for example kdeartwork4 depends on kdebase4-runtime >= 4.9.0. However, kdebase4-runtime 4.9.0 hasn't been built yet, so kdeartwork4 can't find it. Once kdebase4-runtime is built kdeartwork4 will see it (actually it may change to blocked when kdebase4-runtime starts to build, I can't remember).

Blocked just means that a dependency is currently waiting on something else. So for example kdebase4-runtime is waiting for a bunch of packages, such as nepomuk-core, which in turn is waiting for several other packages, like kactivities, which in turn is waiting in line for its chance to build.

So all of those just mean that that something something else needs is not done yet. You normally shouldn't be worried unless you start seeing "failed" or "broken", or "unresolvable" when everything else is already built.

That being said, there are a couple packages in 12.2 that were failing on RC2, but they aren't critical ones and hopefully fixes are available. I will worry about those, if necessary, once everything is published.

-Todd

Thank you for this clarification. I have already created the repo in YaST (but its not enabled) so I will just wait until all the boxes are marked as "succeeded" :-) . BC -- Using openSUSE 12.2 x86_64 KDE 4.8.4 & kernel 3.5.0-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

On Friday 10 Aug 2012 22:56:21 Basil Chupin wrote:

On 02/08/12 21:34, Basil Chupin wrote:

...

On 02/08/12 19:27, Sven Burmeister wrote:

...

Am Donnerstag, 2. August 2012, 19:02:25 schrieb Basil Chupin:

...

So very good to hear that the 12.2 is to be built.

https://build.opensuse.org/project/monitor?project=KDE%3ARelease%3A49 shows you the status.

Sven

Thank you! A most interesting graphic! But I don't like the "unresolvable" and the "blocked" bits, especially the former :-) .

BC

4.9 has now been building for 8 days and there is still no end in sight. Are there major hassles with finalising the build for 12.2 x86_64, anyone?

BC

I guess there are too many dependencies changing and 12.2 probably does not have the same build priority since it is not released (correct me, if I'm wrong - but since Factory has already been built, I would say that). If you really need 4.9.0 packages on the 12.2 development version, you could probably go for the factory packages instead - they should not differ much at the moment... Nico -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

Am Samstag, 11. August 2012, 16:57:57 schrieb Basil Chupin:

Thanks for the response. But I would have thought that something which is to be tried out in a system which is in the process of being actively developed, and available in the form of a RC2, would have a higher priority than Factory. But that just my idea of things.

Indeed, since KDE 4.9 is not part of 12.2. So trying out 4.9 with 12.2 is of little or none value to the standard 12.2 release. KRxy was always meant to be a repo for released openSUSE and released upstream KDE. So 12.2 does not fall into that category yet, factory neither. The only reason I can imagine why factory is part of KR49 is that KDF is still occupied by 4.8.5. Sven -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

On Wednesday 15 Aug 2012 17:00:01 Basil Chupin wrote:

On 11/08/12 17:50, Sven Burmeister wrote:

...

Am Samstag, 11. August 2012, 16:57:57 schrieb Basil Chupin:

...

Thanks for the response. But I would have thought that something which is to be tried out in a system which is in the process of being actively developed, and available in the form of a RC2, would have a higher priority than Factory. But that just my idea of things.

Indeed, since KDE 4.9 is not part of 12.2. So trying out 4.9 with 12.2 is of little or none value to the standard 12.2 release.

KRxy was always meant to be a repo for released openSUSE and released upstream KDE. So 12.2 does not fall into that category yet, factory neither. The only reason I can imagine why factory is part of KR49 is that KDF is still occupied by 4.8.5.

Sven

Even accepting that KDE 4.9 may not have a high priority, but does it really need to take that long to build the darn thing? It's been building for some 13 days now. Ubuntu already have it up and running with people installing it for several days now I understand.

it has not actually been building the whole repo for 13 days, but constantly rebuilding the repo within the last 13 days. Tonight because of changes in libQtWebkit... Development on all libraries in 12.2 would need to be stopped in order to wait for all repos using 12.2 to finish building - or only the prominent ones. But there are more important issues for 12.2 I think - better to polish 12.2 before release than to allow some repo to finish building software that isn't going to be included in 12.2. I'm sorry (and I know, how frustrating this must be for you) but that's probably the way it is for now... Nico -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

On Wednesday 15 Aug 2012 11:43:59 Will Stephenson wrote:

On Wednesday 15 Aug 2012 09:13:43 Nico Kruber wrote:

...

Development on all libraries in 12.2 would need to be stopped in order to wait for all repos using 12.2 to finish building - or only the prominent ones. But there are more important issues for 12.2 I think - better to polish 12.2 before release than to allow some repo to finish building software that isn't going to be included in 12.2. I'm sorry (and I know, how frustrating this must be for you) but that's probably the way it is for now...

I thought we had rebuild=direct in the prjconf already? This should limit the scope of rebuilds.

I guess this means, that packages are only rebuild if direct dependencies change? Maybe an indirect one changed the package of a direct one - I don't know... Anyway, everything seems to have (tried to) build now. I don't know about the missing dependency for networkmanager-kde4 though: %if 0%{?suse_version} >= 1210 BuildRequires: NetworkManager-devel >= 0.9.0 BuildRequires: openconnect-devel >= 3.99 %else BuildRequires: NetworkManager-devel < 0.8.5 %endif It seems, NetworkManager-devel >= 0.9.0 is available on 12.2, but openconnect- devel >= 3.99 is not... I don't know enough about the real dependencies to fix that... Nico -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

On Sunday 05 Aug 2012 22:41:24 Basil Chupin wrote:

After all the files show up as "succeeded" how long does it take for the files to get into the .../Release/49/12_2 repository, please?

If there are no additional package updates pushed to the repo, the icon at the top of the columns on the build monitor page will change to a lorry with a full load to indicate when repo has been published. If you mouse over the icon the repo status is displayed. https://build.opensuse.org/project/monitor?project=KDE:Release:49 As to how long this will take, well that's too hard to guess. There may be additional fixes or patching required to the packages for 12.2 and I supsect there's already been some updated packages commited that has triggered at least one full rebuild before the previous one had finished. Basil please consider the following problem before you rush to update to KDE49. 12.2 is still only RC2, this means at least one more zypper dup operation to upgrade your installation of 12.2 to GM/Final. KDE 4.9 is *not* released with 12.2 so either you will have to manually lock every package in the K:R:49 repo before you zypper dup to final 12.1 or your zypper dup to 12.2 final will trigger a downgrade of KDE 4.9 back to KDE 4.8.4. I simply cannot know for sure but I would always suggest that a downgrade of a desktop environment is more problematic than an upgrade. Configuration files, database schemas and so on can easily be changed with new settings or formats on upgrade but for such things as desktop environments there's almost always no rollback/downgrade path. This is especially true in this case because the version change is one where there may be backwards incompatible changes. Downgrade from 4.8.4 to 4.8.3 should be no problem, downgrade from 4.9.0 to 4.8.4 is probably asking for trouble. I'm personally looking forward to the improvements and missing features from activites which have been missing for so long and might finally make this concept usable, but 4.8.4 is nice and stable so I'm more than happy to be patient at this time. Cheers the noo, Graham -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

Am Mittwoch 01 August 2012, 22:59:47 schrieb Will Stephenson:

Lesson to learn: the old guard are a bottleneck, and we need to make sure that the new maintainers have all the rights necessary to act independently.

Does that mean that the packagers list will no longer be secret? Never understoof why it's secret in the first place... no other FOSS project I'm aware of does that. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

On Thursday 02 Aug 2012 16:26:10 Graham Anderson wrote:

On Thursday 02 Aug 2012 16:04:45 Markus wrote:

...

Does that mean that the packagers list will no longer be secret? Never understoof why it's secret in the first place... no other FOSS project I'm aware of does that.

You have always been able to see the maintainer list on OBS:

https://build.opensuse.org/project/users?project=KDE:Release:49

osc maintainer KDE:Release:49 kdebase4

He means the (private, but not secret) kde-packager list for coordinating early access to final tarballs. Back in the days when we were the hot new thing, distros and news sites liked to break the agreed release to get users and hits. 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

Am Freitag, 3. August 2012, 02:13:17 schrieb Markus:

So what? Still happens with FreeBSD and Mozilla releases and contrary to these, KDE only releases source code. Most people will rely on distributors anyway and everybody with an KDE Identity gets a "Release tagged" email. Any distributor could build packages off git/svn tags/branches.

If so, what difference does it make to not have the list private? If people would have liked to get around the private mailinglist they could have already. Yet they don't. I think you are debating a non-issue. The reason why e.g. 4.9.0 packages should not appear before the release date is simply that there could be a last minute showstopper. Keeping things private does at least decrease the chance of somebody shipping non-final packages. Sven -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

Am Donnerstag, 2. August 2012, 09:13:11 schrieb todd rme:

...

Hey everybody!

KDE SC 4.9 was released today and KR49 far from finished building. adrianS was so kind to increase KR49's build prio to get it done. Thanks for that! Can anyone confirm that the priority is still increased? A ton of

On Wed, Aug 1, 2012 at 6:54 PM, Sven Burmeister wrote: packages have been stuck at "finished" for almost 12 hours now.

It seems we lost priority again after the i586 scheduler was restarted. :( Sven -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

On Thu, Aug 2, 2012 at 9:41 PM, Marcel Witte wrote:

Am Mittwoch, 1. August 2012 schrieb Sven Burmeister :

...

Hey everybody!

KDE SC 4.9 was released today and KR49 far from finished building. adrianS was so kind to increase KR49's build prio to get it done. Thanks for that!

Since this is the third upstream release in a row that openSUSE packages are not available on release day, those writing reviews on release day, including internet magazines, cannot use openSUSE. Is that something to care about, missing the chance to get some mentioning on the media publicity-wise?

This time the biggest issue was that the buildservice is very slow to rebuild most packages in the KDE repo since they are not changed but just rebuilt because their dependency changed. Is there anything one can do about that except cheating by changing some bogus files in a package's source to get a higher build prio due to "changed source"? You might have noticed that if you branch a package it starts building almost instantly while building within KRxy can take days even for "scheduled" packages, although KRxy is certainly more important than a home project.

The slow building is also quite tiresome for those working on the packages – I suppose.

Thanks to everybody working on KR49, especially to Todd!

Sven

Thanks to everyone who is working on the packages :) One Question: Could KDE:Unstable:Playground:Telepathy be activated for KR49? This is the last missing thing for me to switch to 4.9

Is there something wrong with the stable telepathy packages in KDE:Extra? Personally I am in favor of getting rid of KDE:Unstable:Playground:Telepathy entirely. If people still need bleeding-edge telepathy packages, they should be moved into KDE:Unstable:Playground. But as for your question, someone else would need to do that. KDE:Extra and KDE:Unstable:playground have KR49 enabled because I am a mainainer on those repos and thus have the authory to enable builds on them. I don't have that authority for KDE:Unstable:Playground:Telepathy. -Todd -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

Am Freitag 03 August 2012, 11:27:18 schrieb Marcel Witte:

I never understood why it was be moved from Playground in an own repository

IIRC it was always meant to be an interim solution. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org