On Thursday 23 October 2008 11:03:12 Daniel Pielmeier wrote:
> I thought he already installed some of the qt split ebuilds so they
> should be unmasked, but let us see :-)
I've found it myself. For some reason I had these two entries in my world
file:
x11-libs/qt
x11-libs/qt:3
Once I'd removed
On Thursday 23 October 2008 11:03:12 Daniel Pielmeier wrote:
> I thought he already installed some of the qt split ebuilds so they
> should be unmasked, but let us see :-)
$ sudo autounmask x11-libs/qt-4.3.3
autounmask version 0.21 (using PortageXS-0.02.07 and portage-2.2_rc12)
* Using reposi
2008/10/23 Alan McKinnon <[EMAIL PROTECTED]>:
> On Thursday 23 October 2008 11:28:49 Peter Humphrey wrote:
>> On Wednesday 22 October 2008 19:32:08 Daniel Pielmeier wrote:
>> > Please post again the output from emerge -pvutND world but attach it in
>> > a file so it doesn't get crippled by the mail
On Thursday 23 October 2008 11:28:49 Peter Humphrey wrote:
> On Wednesday 22 October 2008 19:32:08 Daniel Pielmeier wrote:
> > Please post again the output from emerge -pvutND world but attach it in
> > a file so it doesn't get crippled by the mail program.
>
> Attached.
Finally, we can see what y
On Wednesday 22 October 2008 19:32:08 Daniel Pielmeier wrote:
> Please post again the output from emerge -pvutND world but attach it in
> a file so it doesn't get crippled by the mail program.
Attached.
> Also what I have seen from your previous tree output is that you are
> trying to do many th
Peter Humphrey schrieb am 22.10.2008 18:42:
> Now I'm back on the original system, and putting Alex's package.keywords
> entries in I find I still have the blockers; his solution isn't working for
> me, even after reinstalling PyQt4 and sip. Neither is my own on this
> system. But then I'm getti
On Wednesday 22 October 2008 12:10:15 Daniel Pielmeier wrote:
> 2008/10/22 Alex Schuster <[EMAIL PROTECTED]>:
> > I think I have the same conflict. I just solved it by putting this into
> > package.keywords:
> > ~dev-python/PyQt4-4.4.3
> > ~dev-python/sip-4.7.7
> > [...]
>
> This is maybe the PyQt
2008/10/22 Alex Schuster <[EMAIL PROTECTED]>:
>
> I think I have the same conflict. I just solved it by putting this into
> package.keywords:
> ~dev-python/PyQt4-4.4.3
> ~dev-python/sip-4.7.7
>
> So I upgraded to PyQt4-4.4.3, and this depends on the splitted Qt ebuilds,
> while PyQt4 up to version
Neil Bothwick writes:
> On Wed, 22 Oct 2008 10:15:34 +0100, Peter Humphrey wrote:
> > That was a good idea, one that I ought to have thought of but didn't.
> > Unfortunately, it's made no difference at all. Emerge -upDvN world
> > still gives the same block:
[...]
> > To recap, the only version of
On Wednesday 22 October 2008 11:15:34 Peter Humphrey wrote:
> On Tuesday 21 October 2008 19:46:33 Daniel Pielmeier wrote:
> > One thing I would give a try is to give portage a hand and emerge some of
> > the qt split ebuilds with the oneshot option. In your case the qt split
> > ebuilds which are b
On Wed, 22 Oct 2008 10:15:34 +0100, Peter Humphrey wrote:
> That was a good idea, one that I ought to have thought of but didn't.
> Unfortunately, it's made no difference at all. Emerge -upDvN world
> still gives the same block:
>
> [blocks B ] x11-libs/qt-core ("x11-libs/qt-core" is blockin
On Tuesday 21 October 2008 19:46:33 Daniel Pielmeier wrote:
> One thing I would give a try is to give portage a hand and emerge some of
> the qt split ebuilds with the oneshot option. In your case the qt split
> ebuilds which are blocked:
>
> x11-libs/qt-script-4.4.2, x11-libs/qt-dbus-4.4.2,
> x1
Peter Humphrey schrieb am 21.10.2008 11:07:
> On Monday 20 October 2008 13:08:30 Daniel Pielmeier wrote:
>> Unmerge x11-libs/qt-4.3.3 and try again. If you want to be on the safe
>> side do a quickpkg =x11-libs/qt-4.3.3 before. The new qt-4.4.x split
>> ebuilds can not live alongside the non split
On Monday 20 October 2008 13:08:30 Daniel Pielmeier wrote:
> Unmerge x11-libs/qt-4.3.3 and try again. If you want to be on the safe
> side do a quickpkg =x11-libs/qt-4.3.3 before. The new qt-4.4.x split
> ebuilds can not live alongside the non split ebuild.
I ran quickpkg and emerge -C on qt-4.3.3
Unmerge x11-libs/qt-4.3.3 and try again. If you want to be on the safe
side do a quickpkg =x11-libs/qt-4.3.3 before. The new qt-4.4.x split
ebuilds can not live alongside the non split ebuild.
--
Regards,
Daniel
On Monday 20 October 2008 09:46:56 Peter Humphrey wrote:
> On Sunday 19 October 2008 18:52:49 Alan McKinnon wrote:
> > I main underlying reason seems to be that Qt now comes as split-ebuilds
> > and Peter has some monolithic ones installed. It's similar to migrating
> > KDE to split-ebuilds, but on
On Sunday 19 October 2008 16:28:35 Alan McKinnon wrote:
> Repost the output of your emerge command using the "-t" option.
>
> Tip: tricky blockers often require that you post the output of 'emerge
> -t'. Otherwise all we know is THAT you have a block and no way to
> determine WHY it's happening. I
On Sunday 19 October 2008 18:52:49 Alan McKinnon wrote:
> I main underlying reason seems to be that Qt now comes as split-ebuilds
> and Peter has some monolithic ones installed. It's similar to migrating
> KDE to split-ebuilds, but on a much smaller scale. Unfortunately there's
> no easy way to au
On Sunday 19 October 2008 19:32:42 Alex Schuster wrote:
> Alan McKinnon writes:
> > Repost the output of your emerge command using the "-t" option.
> >
> > Tip: tricky blockers often require that you post the output of 'emerge
> > -t'. Otherwise all we know is THAT you have a block and no way to
>
Alan McKinnon writes:
> Repost the output of your emerge command using the "-t" option.
>
> Tip: tricky blockers often require that you post the output of 'emerge
> -t'. Otherwise all we know is THAT you have a block and no way to
> determine WHY it's happening. If you are going to post emerge out
On Sunday 19 October 2008 16:50:37 Peter Humphrey wrote:
> On Sunday 19 October 2008 15:24:45 Alan McKinnon wrote:
> > From the qt-core-4.4.2 ebuild:
> >
> > RDEPEND="
> > !<=x11-libs/qt-4.4.0_alpha:${SLOT}
> > "
> >
> > [The] first blocker you have does NOT refer to any version less than
> > 4.4.0
Peter Humphrey schrieb am 19.10.2008 16:50:
> On Sunday 19 October 2008 15:24:45 Alan McKinnon wrote:
>
>> From the qt-core-4.4.2 ebuild:
>>
>> RDEPEND="
>> !<=x11-libs/qt-4.4.0_alpha:${SLOT}
>> "
>>
>> [The] first blocker you have does NOT refer to any version less than
>> 4.4.0_alpha, it means a
On Sunday 19 October 2008 15:24:45 Alan McKinnon wrote:
> From the qt-core-4.4.2 ebuild:
>
> RDEPEND="
> !<=x11-libs/qt-4.4.0_alpha:${SLOT}
> "
>
> [The] first blocker you have does NOT refer to any version less than
> 4.4.0_alpha, it means any version less than that which is SLOT=4.
I thought th
On Sunday 19 October 2008 15:54:24 Peter Humphrey wrote:
> Having been inspired by messages here extolling the virtues of KDE-4, I
> tried installing it. I did as Neil B said and autounmasked kde-meta-4.1.2,
> but I still have a couple of show-stoppers.
>
> After running autounmask, I had 81 new en
I think I had the similar blocks while upgrading my kde from 3.5.x to 4.1.2,
I just unmerged x11-libs/qt-core then everything seemed to be fine.
-Weifeng
On Sun, Oct 19, 2008 at 9:54 PM, Peter Humphrey <[EMAIL PROTECTED]>wrote:
> Having been inspired by messages here extolling the virtues of KDE
Having been inspired by messages here extolling the virtues of KDE-4, I
tried installing it. I did as Neil B said and autounmasked kde-meta-4.1.2,
but I still have a couple of show-stoppers.
After running autounmask, I had 81 new entries in package.keywords, but I
had to add another 82 myself a
26 matches
Mail list logo
