Updating Project:KDE:Trunk project on build.pub.meego.com

[Thomas Pfeiffer]

On 17.04.2012 01:02, Lamarque V. Souza wrote:

> The problem with task switcher happens probably because the
> ~/.kde/share/config/kwinrc is configured with a different tabbox layout. The one
> we use now is:
>
> [TabBox]
>
> LayoutName=window_strip

Ah yes, I remember. That thing.

> PA2 uses "LayoutName=thumbnails" in ~/kde/share/config/kwinrc, we need to edit
> that file to fix this problem. I will see if we can use kconf_update for that.

Yes, we definitely need a process to automatically update config files (while 
offering the user a chance to keep her modified version, ideally) if we offer 
updated packages that need changed config files to work correctly. 
Alternatively, we need to provide a working config file (like e.g. pacman does 
with .pacnew files) along with instructions that the user must replace the file 
in order for the system to work correctly. I'd strongly recommend the automatic 
update, though, at least for config files which users shouldn't mess with in PA 
anyways.

> The other problem is still an open issue:
> https://bugs.kde.org/show_bug.cgi?id=292820 . Today I've added a patch to
> kdelibs that seems to workaround the problem (needs more testing).

If this only affects the demo files, it's a minor problem.

> We need more people testing the upgrade process and reporting bugs.

Definitely. And for that, we need a process for testing the upgrade process 
_before_ end-users can gain access to the updated packages.
Would installing the the last stable image, switching to the Testing repository 
and then updating be the correct way?

Cheers,
Thomas