[arch-dev-public] [draft] KDE 4.3: packaged and split
Hi, This is a draft for a little announcement about the KDE 4.3 packaging changes. If nobody complains I'd like to put this online quite soon. -- The new major release of KDE does not only include exciting upstream improvements and new features but also introduce a new set of packages that makes it possible to only install those applications you like. All important changes in short: * split packages; for more Information see http://wiki.archlinux.org/index.php/KDE_Packages and http://wiki.archlinux.org/index.php/DeveloperWiki:Splitting_KDE * Qt uses the Gstreamer backend for Phonon by default. Other backends like phonon-xine can be installed optionally. * Meta packages ensure a smooth upgrade and emulate the old monolith packages for those who prefer them. Important hints for upgraders: * Check if your mirror is up to date. * pacman will ask you to replace all kde packages with kde-meta packages. * Don't force an update. 'If pacman complains about conflicts please file a bug report. * You can remove the meta packages and the sub packages you don't need after the update. * If you don't like split packages just keep using the kde-meta packages. Information about upstream changes will be available at http://kde.org/announcements/4.3/ -- Pierre Schmitz, http://users.archlinux.de/~pierre
On Mon, Aug 3, 2009 at 3:36 PM, Pierre Schmitz<pierre@archlinux.de> wrote:
This is a draft for a little announcement about the KDE 4.3 packaging changes. If nobody complains I'd like to put this online quite soon.
All seems good from here. I just want to make sure: This is a fairly seemless upgrade path, correct? Users don't have to do any crazy hoop-jumping, do they? Only one issue in your announcement text:
* You can remove the meta packages and the sub packages you don't need after the update.
I'm not sure what this means.... can you clarify / expand on it?
Am Montag 03 August 2009 22:41:51 schrieb Aaron Griffin:
On Mon, Aug 3, 2009 at 3:36 PM, Pierre Schmitz<pierre@archlinux.de> wrote:
This is a draft for a little announcement about the KDE 4.3 packaging changes. If nobody complains I'd like to put this online quite soon.
All seems good from here. I just want to make sure: This is a fairly seemless upgrade path, correct? Users don't have to do any crazy hoop-jumping, do they?
That's right; due to the use of meta packages users just have to hit enter when pacman asks to replace packages. The pacakges themself are more or less well tested.
Only one issue in your announcement text:
* You can remove the meta packages and the sub packages you don't need after the update.
I'm not sure what this means.... can you clarify / expand on it?
I can just remvoe this; I hope this is explained in the wiki article. It just means that during the update the former monolith package will be replaced by several small ones which could be removed selevtively. -- Pierre Schmitz, http://users.archlinux.de/~pierre
On Mon, Aug 3, 2009 at 3:47 PM, Pierre Schmitz<pierre@archlinux.de> wrote:
Am Montag 03 August 2009 22:41:51 schrieb Aaron Griffin:
On Mon, Aug 3, 2009 at 3:36 PM, Pierre Schmitz<pierre@archlinux.de> wrote:
This is a draft for a little announcement about the KDE 4.3 packaging changes. If nobody complains I'd like to put this online quite soon.
All seems good from here. I just want to make sure: This is a fairly seemless upgrade path, correct? Users don't have to do any crazy hoop-jumping, do they?
That's right; due to the use of meta packages users just have to hit enter when pacman asks to replace packages. The pacakges themself are more or less well tested.
Only one issue in your announcement text:
* You can remove the meta packages and the sub packages you don't need after the update.
I'm not sure what this means.... can you clarify / expand on it?
I can just remvoe this; I hope this is explained in the wiki article. It just means that during the update the former monolith package will be replaced by several small ones which could be removed selevtively.
Oh wow, I think my brain parser failed on that one. After re-reading it, it makes total sense. I think I put some extra mental commas in there
On Mon, Aug 3, 2009 at 10:36 PM, Pierre Schmitz <pierre@archlinux.de> wrote: [...]
The new major release of KDE does not only include exciting upstream improvements and new features but also
introduces
a new set of packages that makes it possible to only install those applications you like. [...]
One minor typo, looks fine for the rest. Ronald
Am Montag 03 August 2009 22:55:47 schrieb Ronald van Haren:
On Mon, Aug 3, 2009 at 10:36 PM, Pierre Schmitz <pierre@archlinux.de> wrote: [...]
The new major release of KDE does not only include exciting upstream improvements and new features but also
introduces
a new set of packages that makes it possible to only install those applications you like. [...]
One minor typo, looks fine for the rest.
Ronald
OK, just posted. Packages will move soon...there were just a last-minute minor update by upstream. -- Pierre Schmitz, http://users.archlinux.de/~pierre
On Mon, Aug 3, 2009 at 8:01 PM, Pierre Schmitz<pierre@archlinux.de> wrote:
Am Montag 03 August 2009 22:55:47 schrieb Ronald van Haren:
On Mon, Aug 3, 2009 at 10:36 PM, Pierre Schmitz <pierre@archlinux.de> wrote: [...]
The new major release of KDE does not only include exciting upstream improvements and new features but also
introduces
a new set of packages that makes it possible to only install those applications you like. [...]
One minor typo, looks fine for the rest.
Ronald
OK, just posted. Packages will move soon...there were just a last-minute minor update by upstream.
On x86_64 only, I get this: warning: pyqt: local (4.5.4-1) is newer than extra (4.4.4-3) warning: qscintilla: local (2.4.0-1) is newer than extra (2.3.2-2) warning: qt: local (4.5.2-5) is newer than extra (4.5.2-4) Did you downgraded some packages? If so, you should use the force option.
Am Dienstag 04 August 2009 05:38:45 schrieb Eric Bélanger:
On x86_64 only, I get this: warning: pyqt: local (4.5.4-1) is newer than extra (4.4.4-3) warning: qscintilla: local (2.4.0-1) is newer than extra (2.3.2-2) warning: qt: local (4.5.2-5) is newer than extra (4.5.2-4)
Did you downgraded some packages? If so, you should use the force option.
What the... The db for extra is broken somehow. I see if I am able to fix it. I wonder how that happened. -- Pierre Schmitz, http://users.archlinux.de/~pierre
Am Dienstag 04 August 2009 07:45:48 schrieb Pierre Schmitz:
Am Dienstag 04 August 2009 05:38:45 schrieb Eric Bélanger:
On x86_64 only, I get this: warning: pyqt: local (4.5.4-1) is newer than extra (4.4.4-3) warning: qscintilla: local (2.4.0-1) is newer than extra (2.3.2-2) warning: qt: local (4.5.2-5) is newer than extra (4.5.2-4)
Did you downgraded some packages? If so, you should use the force option.
What the... The db for extra is broken somehow. I see if I am able to fix it. I wonder how that happened.
I hope I fixed it now by manually running repo-add and the cleanup scripts. But its very strange though and I cannot tell if I miss anything. Does the cleanup-cron still run? -- Pierre Schmitz, http://users.archlinux.de/~pierre
On Mon, Aug 3, 2009 at 11:24 PM, Pierre Schmitz<pierre@archlinux.de> wrote:
Am Dienstag 04 August 2009 07:45:48 schrieb Pierre Schmitz:
Am Dienstag 04 August 2009 05:38:45 schrieb Eric Bélanger:
On x86_64 only, I get this: warning: pyqt: local (4.5.4-1) is newer than extra (4.4.4-3) warning: qscintilla: local (2.4.0-1) is newer than extra (2.3.2-2) warning: qt: local (4.5.2-5) is newer than extra (4.5.2-4)
Did you downgraded some packages? If so, you should use the force option.
What the... The db for extra is broken somehow. I see if I am able to fix it. I wonder how that happened.
I hope I fixed it now by manually running repo-add and the cleanup scripts. But its very strange though and I cannot tell if I miss anything.
Does the cleanup-cron still run?
Oh whoops. We were using the one in /arch-new so it didn't cleanup the any packages. Forgot to switch it when I moved then db scripts live
On Tue, Aug 4, 2009 at 09:24, Pierre Schmitz<pierre@archlinux.de> wrote:
Am Dienstag 04 August 2009 07:45:48 schrieb Pierre Schmitz:
Am Dienstag 04 August 2009 05:38:45 schrieb Eric Bélanger:
On x86_64 only, I get this: warning: pyqt: local (4.5.4-1) is newer than extra (4.4.4-3) warning: qscintilla: local (2.4.0-1) is newer than extra (2.3.2-2) warning: qt: local (4.5.2-5) is newer than extra (4.5.2-4)
Did you downgraded some packages? If so, you should use the force option.
What the... The db for extra is broken somehow. I see if I am able to fix it. I wonder how that happened.
I hope I fixed it now by manually running repo-add and the cleanup scripts. But its very strange though and I cannot tell if I miss anything.
The repos dir in SVN still contains testing: http://repos.archlinux.org/viewvc.cgi/kde-meta/repos/ -- Roman Kyrylych (Роман Кирилич)
Am Dienstag 04 August 2009 09:35:37 schrieb Roman Kyrylych:
The repos dir in SVN still contains testing: http://repos.archlinux.org/viewvc.cgi/kde-meta/repos/
fixed -- Pierre Schmitz, http://users.archlinux.de/~pierre
Am Montag 03 August 2009 22:36:47 schrieb Pierre Schmitz:
* Meta packages ensure a smooth upgrade and emulate the old monolith packages for those who prefer them.
Juhu looks like the meta packages made it impossible to install by group because they provided the same name. This is fixed with kde-meta-* 4.3-4. pacman's behaviour with groups is sometimes funky ;-) -- Pierre Schmitz, http://users.archlinux.de/~pierre
On Tue, Aug 4, 2009 at 3:54 AM, Pierre Schmitz<pierre@archlinux.de> wrote:
Am Montag 03 August 2009 22:36:47 schrieb Pierre Schmitz:
* Meta packages ensure a smooth upgrade and emulate the old monolith packages for those who prefer them.
Juhu looks like the meta packages made it impossible to install by group because they provided the same name. This is fixed with kde-meta-* 4.3-4.
pacman's behaviour with groups is sometimes funky ;-)
I don't know what is causing this but kde-l10n-es and kde-l10n-pt_br still show up in /var/abs/kde-unstable.
Am Mittwoch 05 August 2009 02:41:30 schrieb Eric Bélanger:
I don't know what is causing this but kde-l10n-es and kde-l10n-pt_br still show up in /var/abs/kde-unstable.
Should be gone with next abs update. -- Pierre Schmitz, http://users.archlinux.de/~pierre
participants (5)
-
Aaron Griffin
-
Eric Bélanger
-
Pierre Schmitz
-
Roman Kyrylych
-
Ronald van Haren