[kde-unstable] KDE 4.7

dolby · 2011-06-09 20:04:20

Will the package names change to represent the upstream splitted packages?
For example will kdebase-konsole become plain konsole?
I dont see the reason to keep em like they are now (in 4.6.x).

ilpianista · 2011-06-09 20:12:40

dolby wrote:

Will the package names change to represent the upstream splitted packages?
For example will kdebase-konsole become plain konsole?
I dont see the reason to keep em like they are now (in 4.6.x).

No I'll not change the package names. They are part of some KDE module and is more easy to find an application of a module keeping the module name in the package name.

adee · 2011-06-09 22:56:42

Hmm, Beta 2 release is scheduled to June 8, but still no announcement or anything...

Last edited by adee (2011-06-09 22:57:11)

tavianator · 2011-06-10 01:35:18

bash wrote:

dolby wrote:
Will the package names change to represent the upstream splitted packages?
For example will kdebase-konsole become plain konsole?
I dont see the reason to keep em like they are now (in 4.6.x).
No I'll not change the package names. They are part of some KDE module and is more easy to find an application of a module keeping the module name in the package name.

Really? To me,

$ pacman -Ss konsole
extra/kdebase-konsole 4.6.3-1 ...
$ pacman -S kdebase-konsole

is just an unnecessary -Ss. The use case of finding a module's applications is easily accomplished with "pacman -Sg kdebase".

Are the devs steadfastly against this or is this something that could change? I'm willing to patch the PKGBUILDs myself if you want.

ilpianista · 2011-06-10 08:05:02

adee wrote:

Hmm, Beta 2 release is scheduled to June 8, but still no announcement or anything...

KDE Developer were at Randa and they need a bit of time to write the announcement...also KDE PIM 4.6.0 will be released together with KDE 4.6.4. KDE 4.7beta2 hasn't been tagged yet.

tavianator wrote:

is just an unnecessary -Ss. The use case of finding a module's applications is easily accomplished with "pacman -Sg kdebase".

I'll keep original names in KDE 4.x. To avoid a lot of replaces/conflicts too.

In KDE 5.x the whole KDE structure will change and I'll rename the packages with their original names without the KDE module prefix.

tavianator · 2011-06-10 14:22:45

Cool, thanks!

sumski · 2011-06-10 14:24:57

http://dot.kde.org/2011/06/10/new-konta … and-mobile

ilpianista · 2011-06-10 14:29:51

sumski wrote:

http://dot.kde.org/2011/06/10/new-konta … and-mobile

    Date: Friday, June 10, 2011 @ 14:06:05
  Author: andrea
Revision: 127051

db-move: moved kdelibs from [staging] to [testing] (i686)

sumski · 2011-06-10 14:42:19

This was fast!

syms · 2011-06-10 16:21:03

Why kde 4.6.4 is in testing? usually point releases instantly appear in extra

birdflesh · 2011-06-10 16:22:49

I was wondering the same. Maybe because of newly introduced kdepim 4.6?

venky80 · 2011-06-10 17:06:21

what is changing in kontact? is there an easy way to integrate all your contact now? GMAIL, yahoo etc? can i merge contacts between 2 address resources?

sumski · 2011-06-10 17:26:37

venky80 wrote:

what is changing in kontact? is there an easy way to integrate all your contact now? GMAIL, yahoo etc? can i merge contacts between 2 address resources?

http://steveire.wordpress.com/2011/04/0 … -annoying/
http://steveire.wordpress.com/2011/05/01/it-is-coming/
http://steveire.wordpress.com/2011/05/1 … m-4-6-rc1/
http://steveire.wordpress.com/2011/05/3 … m-4-6-rc2/

ilpianista · 2011-06-10 17:42:43

syms wrote:

Why kde 4.6.4 is in testing? usually point releases instantly appear in extra

Because is built with glibc 2.14, which is bugged and will stay in [testing] until FS#24615 is fixed.

szoasis · 2011-06-11 06:53:42

why should our Kde 4.6.4 build with 2.14?i think we may rebuild it on 2.13.......it is too bleeding edge rely on a just-born-few-days glibc...

Zom · 2011-06-13 16:43:40

Because arch *is* bleeding edge. Why shouldn't it?

Anyway, beta 2 hasn't had a release announcement yet, although the schedule said it was to be released on the 8th. Anybody know why?

vvv⁻⁻⁻ D'oh

Last edited by Zom (2011-06-13 19:24:27)

sumski · 2011-06-13 18:26:41

bash wrote:

KDE Developer were at Randa ... KDE 4.7beta2 hasn't been tagged yet.

spider-mario · 2011-06-16 11:30:44

bash wrote:

syms wrote:
Why kde 4.6.4 is in testing? usually point releases instantly appear in extra
Because is built with glibc 2.14, which is bugged and will stay in [testing] until FS#24615 is fixed.

It seems to have been fixed.

ilpianista · 2011-06-16 11:38:09

spider-mario wrote:

It seems to have been fixed.

http://mailman.archlinux.org/pipermail/ … 20684.html

EDIT:

Zom wrote:

Anyway, beta 2 hasn't had a release announcement yet, although the schedule said it was to be released on the 8th. Anybody know why?

Ok, there is a news: they will skip the beta2; RC1 will be tagged 21th.

Last edited by ilpianista (2011-06-16 14:20:23)

reflexing · 2011-06-17 17:46:15

Experiencing buggy behavior with KWallet. I've set Kopete to store passwords to my IM account in KWallet, and when Kopete starts for the first time it asks for KWallet password. I enter it, but nothing happens — Kopete status becomes "Online" and no account gets connected. Restarting Kopete doesn't solve the issue.

Currently i'm disabling KDE KWallet subsystem in KWalletManager, enabling it again, Kopete asks for password and only then accounts connect for real.

Can somebody confirm whether it is a bug?

I'm using KDE 4.7 beta1.

spctrl · 2011-06-18 04:43:41

I do not have any problems with kwallet and/or kopete with beta1.

ilpianista · 2011-06-23 09:49:31

sorry for the OT (this is about KDE 4.6), but I'm getting a *lot* of mails about 4.6.4 in [testing]

KDE 4.6.4 will never hit the [extra] repository because:
1) is built upon glibc which still has some bug
2) okular, kde-baseapps and maybe others source tarballs are wrong: see http://mail.kde.org/pipermail/release-t … 05003.html and http://mail.kde.org/pipermail/release-t … 05005.html
[/OT]

4.7RC1 has been tagged.

divansantana · 2011-06-23 10:14:43

Thanks for clearing that up, I'm been watching the glibc bug .

Does that mean we have to wait for kde 4.6.5 5 July for kdepim 4.6.0? Just wondering.

ilpianista · 2011-06-23 11:03:22

divansantana wrote:

Does that mean we have to wait for kde 4.6.5 5 July for kdepim 4.6.0? Just wondering.

I've no a plan about that yet. Maybe we should wait kdepim 4.6.1.

divansantana · 2011-06-23 11:53:06

bash wrote:

divansantana wrote:
Does that mean we have to wait for kde 4.6.5 5 July for kdepim 4.6.0? Just wondering.
I've no a plan about that yet. Maybe we should wait kdepim 4.6.1.

Probably a good idea, I think that would come with kde 4.6.5 anyway.

Arch Linux

#51 2011-06-09 20:04:20

Re: [kde-unstable] KDE 4.7

#52 2011-06-09 20:12:40

Re: [kde-unstable] KDE 4.7

#53 2011-06-09 22:56:42

Re: [kde-unstable] KDE 4.7

#54 2011-06-10 01:35:18

Re: [kde-unstable] KDE 4.7

#55 2011-06-10 08:05:02

Re: [kde-unstable] KDE 4.7

#56 2011-06-10 14:22:45

Re: [kde-unstable] KDE 4.7

#57 2011-06-10 14:24:57

Re: [kde-unstable] KDE 4.7

#58 2011-06-10 14:29:51

Re: [kde-unstable] KDE 4.7

#59 2011-06-10 14:42:19

Re: [kde-unstable] KDE 4.7

#60 2011-06-10 16:21:03

Re: [kde-unstable] KDE 4.7

#61 2011-06-10 16:22:49

Re: [kde-unstable] KDE 4.7

#62 2011-06-10 17:06:21

Re: [kde-unstable] KDE 4.7

#63 2011-06-10 17:26:37

Re: [kde-unstable] KDE 4.7

#64 2011-06-10 17:42:43

Re: [kde-unstable] KDE 4.7

#65 2011-06-11 06:53:42

Re: [kde-unstable] KDE 4.7

#66 2011-06-13 16:43:40

Re: [kde-unstable] KDE 4.7

#67 2011-06-13 18:26:41

Re: [kde-unstable] KDE 4.7

#68 2011-06-16 11:30:44

Re: [kde-unstable] KDE 4.7

#69 2011-06-16 11:38:09

Re: [kde-unstable] KDE 4.7

#70 2011-06-17 17:46:15

Re: [kde-unstable] KDE 4.7

#71 2011-06-18 04:43:41

Re: [kde-unstable] KDE 4.7

#72 2011-06-23 09:49:31

Re: [kde-unstable] KDE 4.7

#73 2011-06-23 10:14:43

Re: [kde-unstable] KDE 4.7

#74 2011-06-23 11:03:22

Re: [kde-unstable] KDE 4.7

#75 2011-06-23 11:53:06

Re: [kde-unstable] KDE 4.7

Board footer