chrome://messenger/locale/messengercompose/composeMsgs.properties:
On Tue, Mar 2, 2010 at 1:33 PM, Dale<[email protected]> wrote:
chrome://messenger/locale/messengercompose/composeMsgs.properties:
On Tue, Mar 2, 2010 at 12:03 PM, Dale<[email protected]> wrote:
I read the other day that qt3 is being put to rest. Well, qt3 is not as
dead as the devs want it to be. They buried it in one of those really
old
coffins with the bell and string attached. It sounds like qt3 is ringing
that bell like crazy. Anyway, this is the error I get.
Emerging (6 of 37) kde-misc/kdnssd-avahi-0.1.2-r1 from kde-sunset
Of course if you're using deprecated KDE3 stuff it's going to need
deprecated Qt3 stuff as well, since KDE3 is built atop Qt3. Rid
yourself of KDE3 and Qt3 will almost certainly follow it on the way
out. :)
Well I knew that. Thing is, the kde-sunset maintainers need to know this is
failing because of this. Also, there are quite a few still using KDE 3.
Never assume that just because you have moved on that every one else has
too. KDE 4 has just recently started working well enough for me to start
using. I had to use KDE 3 so that I would have a working desktop. I'm
still not quite ready to get rid of KDE 3 yet.
Sorry, I didn't fully comprehend what you were asking :)
It appears avahi (with requisite qt3 use flag), and Qt3 itself are all
present in the kde-sunset overlay already, and are in the unmask file.
Maybe something is set up wrong on your side. Are you using the sunset
unmask file?
Actually this occurs when doing a preserved-rebuild. It *should* be
rebuilding packages already installed.
I did run autounmask -n kde-base/kde-meta-3.5.10 just to make sure
everything was covered but nothing was changed. As far as I know, the
only thing that has changed is qt3 being removed from portage. I was
thinking maybe qt3 hadn't been moved to the overlay but if it has been
moved, I have no idea why it is failing.
If KDE 4 lasts another week tho, I may be getting rid of KDE 3. I
mostly posted so that the kde-sunset folks would know about the error.
If it was something that could be fixed and needs attention, then they
could work on it.
Me clueless.
Dale
:-) :-)
