* [gentoo-amd64] Blocking package
@ 2008-10-21 9:18 Sebastian Geiger
2008-10-21 9:56 ` [gentoo-amd64] " Duncan
0 siblings, 1 reply; 4+ messages in thread
From: Sebastian Geiger @ 2008-10-21 9:18 UTC (permalink / raw
To: gentoo-amd64
Hi,
i am getting a blocks package xy error, as you can see from my pastebin:
http://rafb.net/p/tPjaUP71.html and
http://rafb.net/p/G6e9ML21.html
Any ideas what i should do? Im not sure if i should remove qt-4.4.2
since kde4 depends on it, doesnt it?
Best Regards
Sebastian Geiger
^ permalink raw reply [flat|nested] 4+ messages in thread
* [gentoo-amd64] Re: Blocking package
2008-10-21 9:18 [gentoo-amd64] Blocking package Sebastian Geiger
@ 2008-10-21 9:56 ` Duncan
2008-10-23 1:26 ` Sebastian Geiger
0 siblings, 1 reply; 4+ messages in thread
From: Duncan @ 2008-10-21 9:56 UTC (permalink / raw
To: gentoo-amd64
Sebastian Geiger <sbastig@gmx.net> posted 48FD9E6A.6060809@gmx.net,
excerpted below, on Tue, 21 Oct 2008 11:18:34 +0200:
> i am getting a blocks package xy error, as you can see from my pastebin:
>
> http://rafb.net/p/tPjaUP71.html and
>
> http://rafb.net/p/G6e9ML21.html
>
> Any ideas what i should do? Im not sure if i should remove qt-4.4.2
> since kde4 depends on it, doesnt it?
Well, yes and no. As KDE itself, qt-4 (or at least 4.4.2+, I'm not sure
about earlier qt4 versions) is now split packages. kde-4.1.2+ depends on
the various specific split packages, not on the qt-4+ meta-packages
themselves. Thus, removing qt-4.4.2 /should/ be fine, as long as you are
just removing the meta-package, not the components thereof.
FWIW, I have much of kde-4.1.2 (as well as 3.5.10) merged here, and
here's what equery spits out for qt:
~$equery l qt
[ Searching for package 'qt' in all categories among: ]
* installed packages
[I--] [ ] dev-libs/dbus-qt3-old-0.70 (0)
[I--] [ ~] x11-libs/qt-3.3.8b (3)
[I--] [ ~] x11-libs/qt-core-4.4.2 (4)
[I--] [ ~] x11-libs/qt-dbus-4.4.2 (4)
[I--] [ ~] x11-libs/qt-gui-4.4.2 (4)
[I--] [ ~] x11-libs/qt-opengl-4.4.2 (4)
[I--] [ ~] x11-libs/qt-qt3support-4.4.2 (4)
[I--] [ ~] x11-libs/qt-script-4.4.2 (4)
[I--] [ ~] x11-libs/qt-sql-4.4.2 (4)
[I--] [ ~] x11-libs/qt-svg-4.4.2 (4)
[I--] [ ~] x11-libs/qt-test-4.4.2 (4)
[I--] [ ~] x11-libs/qt-webkit-4.4.2 (4)
$
Note that I have a number of the qt-*-4.4.2 components merged, but not
the qt-4.4.2 metapackage itself. If I do a pretend emerge qt, it wants
to install two additional components (qt-xmlpatterns and qt-assistant) of
the metapackage I don't really need, before installing the metapackage
itself.
So unmerging qt-4.4.2 should be fine, as long as all you unmerge is the
metapackage. You'll probably want to do a --depclean after that, and
unmerge the couple of likely unnecessary additional components, too. Of
course, the usual warning before doing a depclean (or before removing the
--pretend) applies. Make sure you've done an emerge update newuse world
first, and that revdep-rebuild doesn't list anything needing rebuilt.
Hopefully that solves the blocker, but I'm not sure. I don't have PyQt4
installed, only PyQt-3.17.4. Obviously, I don't have anything merged
that needs PyQt4. Thus, I don't know its dependencies. Well, let me
look...
From what I see here, you should be fine, tho it's possible you'll need
to remerge PyQt4 as well. An emerge pretend PyQt4 wants to install
-4.4.3 here, and it doesn't throw up any blockers. So hopefully, once
you unmerge the metapackage, you'll be fine. If not, it's likely in your
use flags. Try playing around with them and see if you can avoid the
blocker. I know I had to do that almost a year ago when I was playing
with the kde4 pre-releases, but I gave up when I saw 4.0 wasn't going to
be anywhere close to a 3.5 replacement for me, until 4.1.2 hit the tree
not long ago. Thus, it's likely I already had my USE flags setup not to
conflict this time, due to having worked it out way back then.
Also note that I don't have /all/ of the kde-4.1.2 metapackage merged. I
have most of the first level components (kdebase, kdegames, etc) merged,
but even there, I used set negation to avoid some of the packages I knew
I'd not use. So it's possible you have packages with additional
dependencies merged, thus creating blockages I'm not seeing, even if your
USE flags matched mine 100%, which is unlikely.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [gentoo-amd64] Re: Blocking package
2008-10-21 9:56 ` [gentoo-amd64] " Duncan
@ 2008-10-23 1:26 ` Sebastian Geiger
2008-10-23 5:39 ` Duncan
0 siblings, 1 reply; 4+ messages in thread
From: Sebastian Geiger @ 2008-10-23 1:26 UTC (permalink / raw
To: gentoo-amd64
Hi, thanks for you advice. I follow them and was able to fix the
problem, its seemed that i had to add to unmask PyQt4 to allow
installing 4.4.2
Best Regards Sebastian Geiger
Duncan wrote:
> Sebastian Geiger <sbastig@gmx.net> posted 48FD9E6A.6060809@gmx.net,
> excerpted below, on Tue, 21 Oct 2008 11:18:34 +0200:
>
>> i am getting a blocks package xy error, as you can see from my pastebin:
>>
>> http://rafb.net/p/tPjaUP71.html and
>>
>> http://rafb.net/p/G6e9ML21.html
>>
>> Any ideas what i should do? Im not sure if i should remove qt-4.4.2
>> since kde4 depends on it, doesnt it?
>
> Well, yes and no. As KDE itself, qt-4 (or at least 4.4.2+, I'm not sure
> about earlier qt4 versions) is now split packages. kde-4.1.2+ depends on
> the various specific split packages, not on the qt-4+ meta-packages
> themselves. Thus, removing qt-4.4.2 /should/ be fine, as long as you are
> just removing the meta-package, not the components thereof.
>
> FWIW, I have much of kde-4.1.2 (as well as 3.5.10) merged here, and
> here's what equery spits out for qt:
>
> ~$equery l qt
> [ Searching for package 'qt' in all categories among: ]
> * installed packages
> [I--] [ ] dev-libs/dbus-qt3-old-0.70 (0)
> [I--] [ ~] x11-libs/qt-3.3.8b (3)
> [I--] [ ~] x11-libs/qt-core-4.4.2 (4)
> [I--] [ ~] x11-libs/qt-dbus-4.4.2 (4)
> [I--] [ ~] x11-libs/qt-gui-4.4.2 (4)
> [I--] [ ~] x11-libs/qt-opengl-4.4.2 (4)
> [I--] [ ~] x11-libs/qt-qt3support-4.4.2 (4)
> [I--] [ ~] x11-libs/qt-script-4.4.2 (4)
> [I--] [ ~] x11-libs/qt-sql-4.4.2 (4)
> [I--] [ ~] x11-libs/qt-svg-4.4.2 (4)
> [I--] [ ~] x11-libs/qt-test-4.4.2 (4)
> [I--] [ ~] x11-libs/qt-webkit-4.4.2 (4)
> $
>
> Note that I have a number of the qt-*-4.4.2 components merged, but not
> the qt-4.4.2 metapackage itself. If I do a pretend emerge qt, it wants
> to install two additional components (qt-xmlpatterns and qt-assistant) of
> the metapackage I don't really need, before installing the metapackage
> itself.
>
> So unmerging qt-4.4.2 should be fine, as long as all you unmerge is the
> metapackage. You'll probably want to do a --depclean after that, and
> unmerge the couple of likely unnecessary additional components, too. Of
> course, the usual warning before doing a depclean (or before removing the
> --pretend) applies. Make sure you've done an emerge update newuse world
> first, and that revdep-rebuild doesn't list anything needing rebuilt.
>
> Hopefully that solves the blocker, but I'm not sure. I don't have PyQt4
> installed, only PyQt-3.17.4. Obviously, I don't have anything merged
> that needs PyQt4. Thus, I don't know its dependencies. Well, let me
> look...
>
>>From what I see here, you should be fine, tho it's possible you'll need
> to remerge PyQt4 as well. An emerge pretend PyQt4 wants to install
> -4.4.3 here, and it doesn't throw up any blockers. So hopefully, once
> you unmerge the metapackage, you'll be fine. If not, it's likely in your
> use flags. Try playing around with them and see if you can avoid the
> blocker. I know I had to do that almost a year ago when I was playing
> with the kde4 pre-releases, but I gave up when I saw 4.0 wasn't going to
> be anywhere close to a 3.5 replacement for me, until 4.1.2 hit the tree
> not long ago. Thus, it's likely I already had my USE flags setup not to
> conflict this time, due to having worked it out way back then.
>
> Also note that I don't have /all/ of the kde-4.1.2 metapackage merged. I
> have most of the first level components (kdebase, kdegames, etc) merged,
> but even there, I used set negation to avoid some of the packages I knew
> I'd not use. So it's possible you have packages with additional
> dependencies merged, thus creating blockages I'm not seeing, even if your
> USE flags matched mine 100%, which is unlikely.
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* [gentoo-amd64] Re: Blocking package
2008-10-23 1:26 ` Sebastian Geiger
@ 2008-10-23 5:39 ` Duncan
0 siblings, 0 replies; 4+ messages in thread
From: Duncan @ 2008-10-23 5:39 UTC (permalink / raw
To: gentoo-amd64
Sebastian Geiger <sbastig@gmx.net> posted 48FFD2AE.9060403@gmx.net,
excerpted below, on Thu, 23 Oct 2008 03:26:06 +0200:
> Hi, thanks for you advice. I follow them and was able to fix the
> problem, its seemed that i had to add to unmask PyQt4 to allow
> installing 4.4.2
... And thanks for the fix report and feedback. It's likely to help, me
or someone else, the next time. =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2008-10-23 5:39 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-10-21 9:18 [gentoo-amd64] Blocking package Sebastian Geiger
2008-10-21 9:56 ` [gentoo-amd64] " Duncan
2008-10-23 1:26 ` Sebastian Geiger
2008-10-23 5:39 ` Duncan
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox