| 1 |
Nickolas Fortino schrieb: |
| 2 |
> On Tue, Jan 20, 2009 at 12:11 AM, KH <gentoo-user@××××××××××××××××.de |
| 3 |
> <mailto:gentoo-user@××××××××××××××××.de>> wrote: |
| 4 |
> |
| 5 |
> Daniel Pielmeier schrieb: |
| 6 |
> > 2009/1/19 KH <gentoo-user@××××××××××××××××.de |
| 7 |
> <mailto:gentoo-user@××××××××××××××××.de>>: |
| 8 |
> > |
| 9 |
> >> This link was great help for me. Told me everything and how to |
| 10 |
> read the |
| 11 |
> >> blocker. So I did: |
| 12 |
> >> |
| 13 |
> >> #emerge -avC qt-4.3.3 |
| 14 |
> >> #emerge -DuavN world (This installed qt-4.4.2) |
| 15 |
> >> |
| 16 |
> >> But now I do have a problem. When I run |
| 17 |
> >> |
| 18 |
> >> #emerge --depclean -av |
| 19 |
> >> |
| 20 |
> >> I receive the following output: |
| 21 |
> >> [snip] |
| 22 |
> >> |
| 23 |
> >>>>> These are the packages that would be unmerged: |
| 24 |
> >>>>> |
| 25 |
> >> dev-db/sqlite |
| 26 |
> >> selected: 2.8.16-r4 |
| 27 |
> >> protected: none |
| 28 |
> >> omitted: 3.6.6.2 |
| 29 |
> >> |
| 30 |
> >> x11-libs/qt |
| 31 |
> >> selected: 4.4.2 |
| 32 |
> >> protected: none |
| 33 |
> >> omitted: 3.3.8b-r1 |
| 34 |
> >> |
| 35 |
> >> [snip some other qt-split-packages] |
| 36 |
> >> |
| 37 |
> >> What did I miss? This results in an infinite circle of |
| 38 |
> unmerging and |
| 39 |
> >> emerging. |
| 40 |
> >> |
| 41 |
> >> |
| 42 |
> > |
| 43 |
> > I don't think --with-bdeps will solve this issue as qt- packages are |
| 44 |
> > no build-time-dependencies they are needed at runtime too. |
| 45 |
> > Did the affected packages got installed by your previous emerge |
| 46 |
> world |
| 47 |
> > command. My guess is that depclean wants to remove this packages |
| 48 |
> > because they are simply not needed by other packages. Did they |
| 49 |
> really |
| 50 |
> > get pulled in when doing another world update after removing the |
| 51 |
> > packages? |
| 52 |
> > |
| 53 |
> > Maybe checking again your world file or the files in |
| 54 |
> > /etc/portage/package.* for something suspicious is a good idea here. |
| 55 |
> > |
| 56 |
> > |
| 57 |
> |
| 58 |
> Hi, |
| 59 |
> |
| 60 |
> yes I had the blocker when running emerge -DuavN world . I unmerged |
| 61 |
> qt-4.3* and ran emerge -DuavN world again. That brought in the |
| 62 |
> qt-4.4.2. |
| 63 |
> Tho investigate further: |
| 64 |
> |
| 65 |
> equery d x11-libs/qt |
| 66 |
> [ Searching for packages depending on x11-libs/qt... ] |
| 67 |
> app-crypt/pinentry-0.7.5 (qt3? x11-libs/qt:3) |
| 68 |
> app-text/poppler-bindings-0.8.7 (qt3? >=x11-libs/qt-3.3:3) |
| 69 |
> (qt4? >=x11-libs/qt-4.3:4) |
| 70 |
> media-video/vlc-0.9.8a (qt4? =x11-libs/qt-4.3*:4) |
| 71 |
> (skins? =x11-libs/qt-4.3*:4) |
| 72 |
> net-im/skype-2.0.0.63 (x86 & !qt-static? =x11-libs/qt-4.3*:4) |
| 73 |
> |
| 74 |
> Those are still depending on qt-4.3* but non are depending on 4.4.2. |
| 75 |
> |
| 76 |
> I will try an emerge -1av skype to learn what it will depend on |
| 77 |
> afterwards. |
| 78 |
> |
| 79 |
> kh |
| 80 |
> |
| 81 |
> You seem to have missed the point of this upgrade. The qt packages |
| 82 |
> were split, as the single qt package was huge, without good reason. |
| 83 |
> The ideal sequence of events (as I understand it) was: |
| 84 |
> 1. qt-4.3.3 and split packages given mutual exclusion depends. |
| 85 |
> 2. All packages depending on qt-4.3.3 get updated to having an || |
| 86 |
> dependency between qt-4.3.3 and the correct split components. |
| 87 |
> 3. split components stabilized, and qt-4.3.3 simultaneously masked |
| 88 |
> (thus, no blockages, everyone upgrades) |
| 89 |
> 4. qt-4.4.2 kept around for backward compatibility/badly formed |
| 90 |
> e-builds, but is only a virtual package (check it out, it only has |
| 91 |
> dependencies) |
| 92 |
> |
| 93 |
> Somehow, 2 didn't get finished, causing the masking in 3 to get |
| 94 |
> dropped, hence the blocking. |
| 95 |
> Nothing should ever need to depend on qt-4.4, as only needed |
| 96 |
> components should be pulled in. |
| 97 |
> Reference: http://bugs.gentoo.org/show_bug.cgi?id=248038 |
| 98 |
> |
| 99 |
> As has been pointed out, equery d is not a good indicator of |
| 100 |
> dependency. Use emerge -pv --depclean <atom> for a real indication |
| 101 |
> (equery does a grep of the ebuild file, emerge only reports active |
| 102 |
> dependencies, which is what most people care about. I've been tempted |
| 103 |
> to file a bug for a while, but this seems to be the accepted behavior). |
| 104 |
> |
| 105 |
> Nick |
| 106 |
> |
| 107 |
So I just did an new emerge --sync what solved the problem. qt-4.4.2 is |
| 108 |
unmerged by depclean and world is not bringing it in again. |
| 109 |
|
| 110 |
Thanks for all the help |
Archives