[opensuse-kde] KDE 4.7 TODO
My meeting action. Overall 1) Sync changes in KDF to KUSC (will) 2) Copy KUSC back to KDF (will) 3) Prepare 4.7rc1 tarballs as copy of KUSC in KDE:Release:47 (just scratch packaging to prove the tarballs) (dirk) 4) Re-run update scripts vs KDF (dirk) 5) setup KR47 properly (javier) Package changes needed in KUSC to sync with KDF: (my TODO, * indicates done, ! indicates looked at, not done yet) KEEP CHANGELOGS INCREMENTAL No change: avogadro phonon polkit-qt-1 strigit (0.7.3.99) OK to copy to KDF: attica kdelibs4 kdea11y4 kdeartwork4 kdebase4 kdemultimedia4 kdepim4 kdepim4-runtime (careful that there may be linked packages like kdebindings kdetoys4 kdeutils4 qhull s-d-o soprano* Need changes in KUSC: * akonadi-runtime * kdebase4-runtime (smi) ! kdebase4-workspace (patches) (some still need rediff) * kdegames4 (old versions) * kdelibs4 (smi) * kdesdk4 (smi, otherwise keep, kate own pkg now) * oxygen-icon-theme (old versions) New in KUSC: kdeedu4: blinken cantor kalgebra kalzium kanagram kbruch kgamma kgeography khangman kig kiten klettres kmplot kstars ktouch kturtle kwordquiz libkdeedu4 libeigen2-devel? libkmap marble rocs sbig sbig-firmware step (kdegraphics): gwenview kamera kcolorchooser kipi-plugins kolourpaint kruler ksaneplugin ksnapshot libkipi libkface libkexiv2 libkdcraw libksane opencv opengtl? liblqr? libprison libqtgtl librcps kate kdebindings-* split kwebkitpart herqq (hupnp) factory backports in KUSC: build-compare KDF -> KUSC: (check whether there are actually _service files in KUSC) cagibi grantlee kde4-filesystem.spec (keep version bump) kdenetwork4 (keep version bump) kdepimlibs4 (version) kdevplatform4 kdevelop4 kdewebdev4 (check kommander subpkg rename direction) phonon-backend-gstreamer plasma-addons (but check and remove old versions) polkit-kde-agent-1 polkit-kde-kcmmodules-1 qalculate (note build changes) substantial changes: kdegraphics4 digikam (1.9 -> 2.0) all bindings find out why not in KUSC: polkit-kde-1 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Thu, Jun 23, 2011 at 9:25 AM, Will Stephenson
My meeting action.
Overall 1) Sync changes in KDF to KUSC (will) 2) Copy KUSC back to KDF (will) 3) Prepare 4.7rc1 tarballs as copy of KUSC in KDE:Release:47 (just scratch packaging to prove the tarballs) (dirk) 4) Re-run update scripts vs KDF (dirk) 5) setup KR47 properly (javier)
Package changes needed in KUSC to sync with KDF: (my TODO, * indicates done, ! indicates looked at, not done yet)
KEEP CHANGELOGS INCREMENTAL
No change: avogadro phonon polkit-qt-1 strigit (0.7.3.99)
OK to copy to KDF: attica kdelibs4 kdea11y4 kdeartwork4 kdebase4 kdemultimedia4 kdepim4 kdepim4-runtime (careful that there may be linked packages like kdebindings kdetoys4 kdeutils4 qhull s-d-o soprano*
Need changes in KUSC: * akonadi-runtime * kdebase4-runtime (smi) ! kdebase4-workspace (patches) (some still need rediff) * kdegames4 (old versions) * kdelibs4 (smi) * kdesdk4 (smi, otherwise keep, kate own pkg now) * oxygen-icon-theme (old versions)
New in KUSC: kdeedu4: blinken cantor kalgebra kalzium kanagram kbruch kgamma kgeography khangman kig kiten klettres kmplot kstars ktouch kturtle kwordquiz libkdeedu4 libeigen2-devel? libkmap marble rocs sbig sbig-firmware step
(kdegraphics): gwenview kamera kcolorchooser kipi-plugins kolourpaint kruler ksaneplugin ksnapshot libkipi libkface libkexiv2 libkdcraw libksane opencv opengtl?
liblqr? libprison libqtgtl librcps
kate
kdebindings-* split
kwebkitpart
herqq (hupnp)
factory backports in KUSC: build-compare
KDF -> KUSC: (check whether there are actually _service files in KUSC)
cagibi grantlee kde4-filesystem.spec (keep version bump) kdenetwork4 (keep version bump) kdepimlibs4 (version) kdevplatform4 kdevelop4 kdewebdev4 (check kommander subpkg rename direction) phonon-backend-gstreamer plasma-addons (but check and remove old versions) polkit-kde-agent-1 polkit-kde-kcmmodules-1 qalculate (note build changes)
substantial changes: kdegraphics4 digikam (1.9 -> 2.0) all bindings
find out why not in KUSC: polkit-kde-1
A couple points: 1. Is this a good opportunity to switch over to the newer stand-alone qtwebkit releases and split that to its own package? 2. I might be able help with checking build dependencies again (depending on the timing), but I don't know what stage I should do that at (after 1 or 2 I would guess). 3. Doing a trunk the build just now, jut off the top of my head it looks like several of packages are looking for QtZeitgeist. It might be good to add that to the list. -Todd -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On 06/23/2011 11:37 AM, todd rme wrote:
A couple points:
1. Is this a good opportunity to switch over to the newer stand-alone qtwebkit releases and split that to its own package?
Dirk is looking into this, we'll switch to QtWebKit 2.2 branch.
2. I might be able help with checking build dependencies again (depending on the timing), but I don't know what stage I should do that at (after 1 or 2 I would guess). 3. Doing a trunk the build just now, jut off the top of my head it looks like several of packages are looking for QtZeitgeist. It might be good to add that to the list.
-Todd
Regards. -- Ismail Dönmez - openSUSE Booster SUSE LINUX Products GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Thu, Jun 23, 2011 at 9:25 AM, Will Stephenson
My meeting action.
Overall 1) Sync changes in KDF to KUSC (will) 2) Copy KUSC back to KDF (will) 3) Prepare 4.7rc1 tarballs as copy of KUSC in KDE:Release:47 (just scratch packaging to prove the tarballs) (dirk) 4) Re-run update scripts vs KDF (dirk) 5) setup KR47 properly (javier)
Package changes needed in KUSC to sync with KDF: (my TODO, * indicates done, ! indicates looked at, not done yet)
KEEP CHANGELOGS INCREMENTAL
No change: avogadro phonon polkit-qt-1 strigit (0.7.3.99)
OK to copy to KDF: attica kdelibs4 kdea11y4 kdeartwork4 kdebase4 kdemultimedia4 kdepim4 kdepim4-runtime (careful that there may be linked packages like kdebindings kdetoys4 kdeutils4 qhull s-d-o soprano*
Need changes in KUSC: * akonadi-runtime * kdebase4-runtime (smi) ! kdebase4-workspace (patches) (some still need rediff) * kdegames4 (old versions) * kdelibs4 (smi) * kdesdk4 (smi, otherwise keep, kate own pkg now) * oxygen-icon-theme (old versions)
New in KUSC: kdeedu4: blinken cantor kalgebra kalzium kanagram kbruch kgamma kgeography khangman kig kiten klettres kmplot kstars ktouch kturtle kwordquiz libkdeedu4 libeigen2-devel? libkmap marble rocs sbig sbig-firmware step
(kdegraphics): gwenview kamera kcolorchooser kipi-plugins kolourpaint kruler ksaneplugin ksnapshot libkipi libkface libkexiv2 libkdcraw libksane opencv opengtl?
liblqr? libprison libqtgtl librcps
kate
kdebindings-* split
kwebkitpart
herqq (hupnp)
factory backports in KUSC: build-compare
KDF -> KUSC: (check whether there are actually _service files in KUSC)
cagibi grantlee kde4-filesystem.spec (keep version bump) kdenetwork4 (keep version bump) kdepimlibs4 (version) kdevplatform4 kdevelop4 kdewebdev4 (check kommander subpkg rename direction) phonon-backend-gstreamer plasma-addons (but check and remove old versions) polkit-kde-agent-1 polkit-kde-kcmmodules-1 qalculate (note build changes)
substantial changes: kdegraphics4 digikam (1.9 -> 2.0) all bindings
find out why not in KUSC: polkit-kde-1
Currently, what repository should we be using if we want the 4.7 rc1 packages? KUSc or KR47? -Todd -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On 07/05/2011 09:54 AM, todd rme wrote:
Currently, what repository should we be using if we want the 4.7 rc1 packages? KUSc or KR47?
KUSC is being worked on, but be careful I only tested Factory so far. -- Ismail Dönmez - openSUSE Booster SUSE LINUX Products GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
Am Dienstag, 5. Juli 2011, 11:36:48 schrieb Ismail Doenmez:
On 07/05/2011 09:54 AM, todd rme wrote:
Currently, what repository should we be using if we want the 4.7 rc1 packages? KUSc or KR47?
KUSC is being worked on, but be careful I only tested Factory so far.
If there is currently nobody working on KR47 to fix it, please remove the published packages from the repos and disable rebuilding in order to save build power, e.g. for KDF etc. Sven -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On 07/05/2011 11:47 AM, Sven Burmeister wrote:
Am Dienstag, 5. Juli 2011, 11:36:48 schrieb Ismail Doenmez:
On 07/05/2011 09:54 AM, todd rme wrote:
Currently, what repository should we be using if we want the 4.7 rc1 packages? KUSc or KR47?
KUSC is being worked on, but be careful I only tested Factory so far.
If there is currently nobody working on KR47 to fix it, please remove the published packages from the repos and disable rebuilding in order to save build power, e.g. for KDF etc.
Dirk works on KR47 but it has some wrong packages AFAIK, its not supposed to be used right now anyhow. Please try KUSC if you want to help testing 4.7rc1. Thanks. -- Ismail Dönmez - openSUSE Booster SUSE LINUX Products GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
Am Dienstag, 5. Juli 2011, 11:50:13 schrieb Ismail Doenmez:
Dirk works on KR47 but it has some wrong packages AFAIK, its not supposed to be used right now anyhow.
Then why are those broken packages published? There are plenty of users which do not ask before they try – more with each day that KDE 4.7 RC1 was announced but is not available for openSUSE. And while it is clearly their risk to do so – why give them the chance if one can easily avoid it by not publishing a repo that is known to be broken – for a week or even longer? I don't get that logic. Sven -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Tuesday 05 July 2011, Sven Burmeister wrote:
Dirk works on KR47 but it has some wrong packages AFAIK, its not supposed to be used right now anyhow. Then why are those broken packages published?
To be able to test them ? :-) I have fixed most of the dependency issues, if there is anything else, please let me know. Thanks, Dirk -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
Am Mittwoch 20 Juli 2011, 11:13:45 schrieb Dirk Müller:
Then why are those broken packages published?
To be able to test them ? I have fixed most of the dependency issues, if there is anything else, please let me know.
Hi, please correct me, but is not: → Unstable → Factory → KR47 the way of testing and releasing? Somehow confusing when tested in: Unstable → 47 RC-2, is somehow in KR47, and distributed in the Factory is KDE SC 4.6.5 .... excuse me, but who is to look there? Would not it be better to focus first to the 4.7 RC-2 is stable enough for factory, and eventually come with Finale 4.7.0 in KR47? Such charges do not proceed straight to participation in tests at! Greetings from the Rainy "Daimler-Country" → Uwe, der Linuxsusefan ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Die SuS(i)E samt KDE sei mit euch, wo immer ihr auch seid .... ;) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ############## openSUSE Member ##############
On 07/20/2011 12:28 PM, Lisufas Linuxfreunde wrote:
Am Mittwoch 20 Juli 2011, 11:13:45 schrieb Dirk Müller:
Then why are those broken packages published?
To be able to test them ? I have fixed most of the dependency issues, if there is anything else, please let me know.
Hi,
please correct me, but is not: → Unstable → Factory → KR47 the way of testing and releasing?
Somehow confusing when tested in: Unstable → 47 RC-2, is somehow in KR47, and distributed in the Factory is KDE SC 4.6.5 .... excuse me, but who is to look there?
Would not it be better to focus first to the 4.7 RC-2 is stable enough for factory, and eventually come with Finale 4.7.0 in KR47?
Such charges do not proceed straight to participation in tests at!
For now please use KDE:Unstable:SC for 4.7 testing. We'll notify the list when this changes.
Greetings from the Rainy "Daimler-Country"
Rain in summer, meh ;( -- Ismail Dönmez - openSUSE Booster SUSE LINUX Products GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On 07/20/2011 12:28 PM, Ismail Doenmez wrote:
On 07/20/2011 12:28 PM, Lisufas Linuxfreunde wrote:
Am Mittwoch 20 Juli 2011, 11:13:45 schrieb Dirk Müller:
Then why are those broken packages published?
To be able to test them ? I have fixed most of the dependency issues, if there is anything else, please let me know.
Hi,
please correct me, but is not: → Unstable → Factory → KR47 the way of testing and releasing?
Somehow confusing when tested in: Unstable → 47 RC-2, is somehow in KR47, and distributed in the Factory is KDE SC 4.6.5 .... excuse me, but who is to look there?
Would not it be better to focus first to the 4.7 RC-2 is stable enough for factory, and eventually come with Finale 4.7.0 in KR47?
Such charges do not proceed straight to participation in tests at!
For now please use KDE:Unstable:SC for 4.7 testing. We'll notify the list when this changes.
Greetings from the Rainy "Daimler-Country"
Rain in summer, meh ;(
But Uwe give on important point, sure it's usefull to have kr47 be mostly ready for end users at release time. But actually having some package build in it, with unpredictable results for end users, will drive to failures. Perharps until real release of 4.7 we should remove the build publish and/or ask admin to remove any pre-published package The pressure of users wanting 4.7 will increase in a short time frame now :D So we can tell them KUSC really unstable, but please test Or wait 4.7 entrance in factory, Then use kr47 when ready no ? -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Ambassador GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
But Uwe give on important point, sure it's usefull to have kr47 be mostly ready for end users at release time. But actually having some package build in it, with unpredictable results for end users, will drive to failures.
I am fully aware that kr47 is unsupported but I use it anyway. It works, it's stable, and it has Kontact 4.4.11 which I consider a plus for the time being. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
Am Mittwoch 20 Juli 2011, 16:07:07 schrieb Bruno Friedmann:
On 07/20/2011 12:28 PM, Ismail Doenmez wrote:
On 07/20/2011 12:28 PM, Lisufas Linuxfreunde wrote:
Am Mittwoch 20 Juli 2011, 11:13:45 schrieb Dirk Müller:
Then why are those broken packages published?
To be able to test them ? I have fixed most of the dependency issues, if there is anything else, please let me know.
Hi,
please correct me, but is not: → Unstable → Factory → KR47 the way of testing and releasing?
Somehow confusing when tested in: Unstable → 47 RC-2, is somehow in KR47, and distributed in the Factory is KDE SC 4.6.5 .... excuse me, but who is to look there?
Would not it be better to focus first to the 4.7 RC-2 is stable enough for factory, and eventually come with Finale 4.7.0 in KR47?
Such charges do not proceed straight to participation in tests at!
For now please use KDE:Unstable:SC for 4.7 testing. We'll notify the list when this changes.
Greetings from the Rainy "Daimler-Country"
Rain in summer, meh ;(
But Uwe give on important point, sure it's usefull to have kr47 be mostly ready for end users at release time. But actually having some package build in it, with unpredictable results for end users, will drive to failures. Perharps until real release of 4.7 we should remove the build publish and/or ask admin to remove any pre-published package
The pressure of users wanting 4.7 will increase in a short time frame now :D
So we can tell them KUSC really unstable, but please test Or wait 4.7 entrance in factory, Then use kr47 when ready
no ?
Hi Bruno, You understand, perhaps incorrectly. I know this may differ, and what packages are in repositories from which my system. I am careful what I get for packages in my system and I can help themselves quite well when problems occur with unstable packages tested. Other user not to use because the naïve view that everything described somewhere and make it their system broken. Then the people running through the forums and then complain about what the KDE project is building for manure. We, yes, I purposely say we (as some users here know I'm probably in the German Wiki a little bit active) should perhaps generally better and more accurately communicate what repos are for that user. If users know the exact date of the KR 47 are only and exclusively be used for tests that can "amateur" the "finger away" and do not use this repo KR47. If the warning is still ignored, the kde team is innocent. But well, let's leave the discussion to be here now, because the topic was probably already discussed often enough. Many greetings from the still rainy, "Daimler-Country" ;-) → Uwe, der Linuxsusefan ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Die SuS(i)E samt KDE sei mit euch, wo immer ihr auch seid .... ;) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ############## openSUSE Member ##############
Am Dienstag, 5. Juli 2011, 09:54:23 schrieb todd rme:
Currently, what repository should we be using if we want the 4.7 rc1 packages? KUSc or KR47?
Last time I checked the status of KR47 was "tell people to stay away" because it contained a wild mix of 4.6 and 4.7 packages, which eventually succeed to build and get published but break your system. So KUSC might be worth a try but check what package versions it tries to install. AFAIK yesterday there were still issues with kdegraphics still being from 4.6. Oh, and if I got the plan right, then 4.7 RC1 will first be in KDF and then KR47. Though currently KDF moved from 4.6.4 to 4.6.5… And which kdepim should one use with KDE 4.7? Officially kdepim 4.7 is part of it yet the repos still build 4.4 and there is no kdepim47_for_KR47/KDF yet. Confused? :) I'd suggest wait until the mess has been sorted out and packages in KR47 or KDF are announced on this list. Sven -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
participants (8)
-
Bruno Friedmann
-
Dirk Müller
-
Ismail Doenmez
-
Lisufas Linuxfreunde
-
Markus Slopianka
-
Sven Burmeister
-
todd rme
-
Will Stephenson