rdesktop-1.4.1 - Bug 94036 sys-libs/db-4.2 - Bug 94219 dev-libs/libusb-0.1.10a - Bug 94220 mDNSResponder - Bug 94222 other dependencies architecture teams may want to look at: app-accessibility/epos app-accessibility/festival app-accessibility/flite app-accessibility/freetts gstreamer-0.8.7 =sys-apps/dbus-0.23* =sys-apps/hal-0.4*
Adding bug 84032: we need to remember to mark kaffeine-0.6-r1 stable before kde-3.4.
are we going to be marking 3.4.1 stable instead of 3.4.0?
(In reply to comment #2) > are we going to be marking 3.4.1 stable instead of 3.4.0? Yes. As I wrote earlier, I think we can mark 3.4.1 stable later today. Opinions?
Just one more before going on: dev-libs/boost, bug 91936.
What do you think about marking 3.4.1 stable except for the two packages which depend on boost (and the packages that depend on those two packages)? If we don't get a response to bug 91936 in a few days, then we can mark it stable and pass the changes on as well. I would think that a majority of ebuild users don't install kdeedu stuff, and this would let the split ebuild users the opportunity to upgrade...
(In reply to comment #5) > What do you think about marking 3.4.1 stable except for the two packages which > depend on boost (and the packages that depend on those two packages)? If we > don't get a response to bug 91936 in a few days, then we can mark it stable and > pass the changes on as well. I would think that a majority of ebuild users > don't install kdeedu stuff, and this would let the split ebuild users the > opportunity to upgrade... I don't think it can be done, it would cause an upgrade downgrade loop for those having kde in world. But I've got an alternative: temporary use.mask'ing kig-scripting until boost-1.32 gets stable, this will only affect very few users. I'm going to do it later, if it's ok.
No feedback... and tomorrow I'm leaving for a week, with limited internet access, so I'm not going to do the unmask just before going away... but please go on and mark 3.4.1 as soon as possible if you think use.masking kig-scripting is ok.
I agree with the use_masking idea. What about the kaffeine issue? (I'm not a kaffeine user...) Other than lost functionality in 0.6 are there reasons not to mark that stable? After all I presume the kaffeine upstream is committed to 0.6 ff anyway... But maybe I simply don't understand the kaffeine situation. Is this really a blocker of kde 3.4 just because kaffeine >0.4 is missing features? Otherwise, I'm OK to unmask 3.4.1. Any objections?
OK, I wrote some nonsense again :-/ We can't use use.mask for this because it would have the same effect as just removing support altogether - how do you mask a flag for ACCEPT_KEYWORDS=x86 but not for ~x86? And changing the base profile(s) is no fun anyway. What I'm doing now is creating a new rev of kig (-r10). r0 will have no kig-scripting support and stable keywords; r10 will have kig-scripting and ~arch keywords. Users will pointlessly upgrade to r10, but I guess we can live with that. That done, I don't think any objections to keywording 3.4.1 stable remain... Please speak out now if you don't want me to do it tomorrow.
Stable on x86 and amd64
