kde-base/system-config-printer-kde-4.3.0 ~alpha ~hppa ~ia64 ~ppc ~ppc64 kde-base/kdeartwork-weatherwallpapers-4.3.0 ~alpha ~hppa ~ia64 ~ppc ~ppc64 kde-base/oxygen-icons-4.3.0 ~alpha ~hppa ~ia64 ~ppc ~ppc64 kde-base/kdebase-menu-icons-4.3.0 ~alpha ~hppa ~ia64 ~ppc ~ppc64 kde-base/kdebase-menu-4.3.0 ~alpha ~hppa ~ia64 ~ppc ~ppc64 kde-base/plasma-runtime-4.3.0 ~alpha ~hppa ~ia64 ~ppc ~ppc64 kde-base/solidautoeject-4.3.0 ~alpha ~hppa ~ia64 ~ppc ~ppc64 kde-base/kdebase-wallpapers-4.3.0 ~alpha ~hppa ~ia64 ~ppc ~ppc64 kde-base/keditfiletype-4.3.0 ~alpha ~hppa ~ia64 ~ppc ~ppc64 kde-base/kglobalaccel-4.3.0 ~alpha ~hppa ~ia64 ~ppc ~ppc64 kde-base/ktron-4.3.0 ~alpha ~hppa ~ia64 ~ppc ~ppc64 kde-base/thumbnailers-4.3.0 ~alpha ~hppa ~ia64 ~ppc ~ppc64 kde-base/mplayerthumbs-4.3.0 ~alpha ~hppa ~ia64 ~ppc ~ppc64 kde-base/printer-applet-4.3.0 ~alpha ~hppa ~ia64 ~ppc ~ppc64 media-libs/libv4l ~hppa app-accessibility/epos ~hppa app-accessibility/flite ~ia64 app-text/djview4 ~ppc sys-power/pm-utils ~alpha ~hppa ~ia64 ~ppc64 sys-auth/policykit-qt-0.9.2 ~alpha ~hppa ~ia64 ~ppc ~ppc64 net-misc/wicd ~alpha ~hppa ~ia64 ~ppc64 Hope I didnt miss something and thakns for cooperation.
Ah also before i forget, if you want us to keyword automaticaly kde-base/ apps with your arch just write it here i will adjust our bump script :]
I don't know if it'll help, but I'll attach the my package.unmask that was created by "autounmask =kde-base/kde-meta-4.3.0". Note that doing this creates a trainwreck of conflicts with KDE 4.2.4. Some apps are slotted, while others are blocked and would cause uninstalls, resulting in massive breakage.
Created attachment 200224 [details] All dependencies of kde-base/kde-meta-4.3.0
Is this "the bug" to be watching for KDE 4.3? Or is there another I should be looking at?
I had to add a few more entries to Timothy's attached package.unmask to install the @kde-4.3 meta set: =sys-auth/policykit-qt-0.9.2 =kde-base/kdelirc-4.3.0 =kde-base/kmousetool-4.3.0 =kde-base/policykit-kde-4.3.0 =kde-base/kttsd-4.3.0 =kde-base/kdeaccessibility-iconthemes-4.3.0 =kde-base/kdeaccessibility-colorschemes-4.3.0 =kde-base/kmag-4.3.0 =kde-base/kmouth-4.3.0
@users: Please let this bug be processed by KDE and arch team members. All currently keyworded 4.2.4 packages will / were already bumped for 4.3.0. What we're requiring here is for arch teams to add keywords for new packages that have thus no keywords for their arches. @ATs: Please ignore users' comments and focus on the list provided by Tomáš.
Readjusting priority following the poke in #gentoo-dev. If you'll allow us to add the mask to each arch profile or if you'll copy it from profiles/package.mask, we'll be able to drop it from profiles/package.mask and allow x86/amd64 users to upgrade to KDE-4.3.0.
kde 4.3.0 is unmasked for amd64
In reply to comment #8: >kde 4.3.0 is unmasked for amd64 Except for: kde-base/printer-applet-4.3.0 which is still masked: /usr/portage/profiles/package.mask: # Jorge Manuel B. S. Vicetto <jmbsvicett@gentoo.org> (07 Aug 2009) # Update the mask to match only system-config-printer-kde-4.2.4 # and not later versions. Mask left as-is for printer-applet for # the moment. # Alexey Shvetsov <alexxy@gentoo.org> (04 Jun 2009) # Mask kde4 printing stuff
HPPA work should be all done except for pm-utils and wicd, which are use.masked now.
Oh wait. kde-base/powerdevil depends on pm-utils too.
We better find a way to (use.)mask pm-utils, because it depends on libx86 which simply doesn't work on anything but amd64 and x86 AFAIK.
*** Bug 280710 has been marked as a duplicate of this bug. ***
(In reply to comment #11) > Oh wait. kde-base/powerdevil depends on pm-utils too. The dependency on pm-utils was made optional through the pm-utils use flag.
Please unmask x86, amd64 users had their fun. Come on.
How should users determine the progress/status of 4.3.0? Or is this the bug to watch? I'm trying to determine how soon x86 will be unmasked. I recognize that this bug should not be used by users, but can not find the best course for determining the status/progress. Thank you for your work, and apologies for posting, Chris (In reply to comment #6) > @users: > Please let this bug be processed by KDE and arch team members. All currently > keyworded 4.2.4 packages will / were already bumped for 4.3.0. > What we're requiring here is for arch teams to add keywords for new packages > that have thus no keywords for their arches. > > @ATs: > Please ignore users' comments and focus on the list provided by Tomáš. >
(In reply to comment #16) > How should users determine the progress/status of 4.3.0? Or is this the bug to > watch? I'm trying to determine how soon x86 will be unmasked. I recognize that > this bug should not be used by users, but can not find the best course for > determining the status/progress. > > Thank you for your work, and apologies for posting, > Hi Chris, kde-4.3.0 is marked testing on both amd64 and x86 (since today), remaining archies will be unmasked as the AT/Devs will keyword the packages. Figuring out that some arch team is done can be easily spotted by watching the CC list and seeing that architecture@gentoo.org alias for that specific arch is gone. Cheers
(In reply to comment #14) > (In reply to comment #11) > > Oh wait. kde-base/powerdevil depends on pm-utils too. > > The dependency on pm-utils was made optional through the pm-utils use flag. > Whats the laptop USE-flag for then? hal uses that USE-flag, and pm-utils = battery = laptop. No need to duplicate it, please...
A desktop or server can also be connected to a UPS. That is also a battery, but those machines are not a laptop. So it isn't a duplicate flag ;). imo offcourse.
IUSE=battery ?
Also, do note pm-utils is working fine on ARM with a package.provided hack (see bug 280477).
How is this going? We would like to purge kde 4.2.4 from tree and we *need* 4.3 keyworded first. Arch teams - please consider this higher priority.
(In reply to comment #14) > (In reply to comment #11) > > Oh wait. kde-base/powerdevil depends on pm-utils too. > > The dependency on pm-utils was made optional through the pm-utils use flag. use.masked for HPPA now.
@KDE: Go ahead and move the masks to the appropriate places so its masked on the archs that you are waiting for, so they can get to this request as time and resources allow.
Created attachment 203007 [details] List of packages to keyword for alpha
Created attachment 203009 [details] List of packages to keyword for hppa List reviewed by Jeroen (rej)
Created attachment 203010 [details] List of packages to keyword for ia64
Created attachment 203011 [details] List of packages to keyword for ppc
Created attachment 203012 [details] List of packages to keyword for ppc64
I've just added individual lists for each arch. Let us know if you need anything else from the KDE team.
@alpha / @ia64: I had to drop your keywords for akonadi-server-1.2.{0,1} as you lack the keywords for the dev-libs/soprano dep. I've restored akonadi-server-1.1.2 to fix the tree breakage.
powerdevil-4.3.1 has an unconditional dep on pm-utils...
Right, but there's kde-base/powerdevil-4.3.1-r1 IUSE="debug +pm-utils" Please use latest revisions available from tree. Thanks
~alpha/~ia64 done, repoman was complaining about 4.3.1, didn't see that there was 4.3.1-r1, still 4.3.1 is now punted
OK, somebody forgot to re-CC... Nice one.
*** Bug 275876 has been marked as a duplicate of this bug. ***
hppa still dont keyworded all packages like libknotification item and so on
Note that net-im/kopete-facebook needs also keywording for kde-base/kopete. It's temporarily p.use.masked pending on this bug.
Marked ~hppa.
(In reply to comment #39) > Marked ~hppa. > You're not realy finish =) # kde-base/kstars/kstars-4.3.1.ebuild: ~hppa(default/linux/hppa/10.0/server) ['>=sci-libs/indilib-0.6[fits]'] # kde-base/kstars/kstars-4.3.1.ebuild: ~hppa(default/linux/hppa/10.0/developer) ['>=sci-libs/indilib-0.6[fits]'] # kde-base/kstars/kstars-4.3.1.ebuild: ~hppa(default/linux/hppa/10.0/desktop) ['>=sci-libs/indilib-0.6[fits]'] # kde-base/kstars/kstars-4.3.2.ebuild: ~hppa(default/linux/hppa/10.0/server) ['>=sci-libs/indilib-0.6[fits]'] # kde-base/kstars/kstars-4.3.2.ebuild: ~hppa(default/linux/hppa/10.0/developer) ['>=sci-libs/indilib-0.6[fits]'] # kde-base/kstars/kstars-4.3.2.ebuild: ~hppa(default/linux/hppa/10.0/desktop) ['>=sci-libs/indilib-0.6[fits]'] # kde-base/printer-applet/printer-applet-4.3.2.ebuild: ~hppa(default/linux/hppa/10.0/server) ['>=app-admin/system-config-printer-common-1.1.12', 'app-misc/hal-cups-utils'] # kde-base/printer-applet/printer-applet-4.3.2.ebuild: ~hppa(default/linux/hppa/10.0/developer) ['>=app-admin/system-config-printer-common-1.1.12', 'app-misc/hal-cups-utils'] # kde-base/printer-applet/printer-applet-4.3.2.ebuild: ~hppa(default/linux/hppa/10.0/desktop) ['>=app-admin/system-config- # kde-base/kstars/kstars-4.3.1.ebuild: ~hppa(default/linux/hppa/10.0) ['>=sci-libs/indilib-0.6[fits]'] # kde-base/kstars/kstars-4.3.2.ebuild: ~hppa(default/linux/hppa/10.0) ['>=sci-libs/indilib-0.6[fits]']
full list of problems affected arches are hppa ppc ppc64 http://pastebin.ca/1645025
ppc/ppc64 are done, removed the mask as well. Please re-add us if I missed something.
Here are the last packages that need to be keyworded ~hppa to close this bug: >=app-admin/system-config-printer-common-1.1.12 app-misc/hal-cups-utils >=dev-python/pycups-1.9.46 >=sci-libs/indilib-0.6 If, for any reason, you do not wish to keyword one of these at this time, then the following package.use.mask entries may be used instead: For app-admin/system-config-printer-common: # add kde-base/printer-applet and kde-base/system-config-printer-kde # to package.mask as well kde-base/kdeadmin-meta cups kde-base/kdeutils-meta cups For app-misc/hal-cups-utils: # add kde-base/printer-applet to package.mask as well kde-base/kdeutils-meta cups For dev-python/pycups: # add kde-base/system-config-printer-kde to package.mask as well kde-base/kdeadmin-meta cups For sci-libs/indilib: kde-base/kstars indi And thanks Joe for finishing ~ppc/~ppc64, as this list was a bit longer until I got in a mid-air collision with you :D
