| 1 |
gentuxx schreef: |
| 2 |
> Hi all, |
| 3 |
> |
| 4 |
<snip> |
| 5 |
> I went to do an `emerge -Duatv world` tonight, and I get dev-php/php |
| 6 |
> and dev-php/mod_php blocking. So I uninstalled them, and thought |
| 7 |
> that I would re-install later (if necessary). When I run it again, I |
| 8 |
> get dev-lang/php blocking dev-php/php-4.4.0-r4 (which is the one I |
| 9 |
> just unemerged). So, same logical progression, I go to unemerge |
| 10 |
> dev-lang/php, and, lo and behold, it's not installed. |
| 11 |
> |
| 12 |
<snip> |
| 13 |
> |
| 14 |
> So, my questions to the group are these: |
| 15 |
> |
| 16 |
> 1) Why does `emerge -Duatv world` find a package (which blocks |
| 17 |
> another that it wants to update) that `emerge -CDatv world` does NOT |
| 18 |
> find? |
| 19 |
|
| 20 |
As far as I know, emerge -CDatv world is not even a valid command (at |
| 21 |
least I hope it isn't). |
| 22 |
|
| 23 |
This translates to |
| 24 |
|
| 25 |
emerge --unmerge --deep --ask --tree --verbose world, and it seems to me |
| 26 |
would unmerge everything on your system if it was allowed. |
| 27 |
|
| 28 |
The usual use for --unmerge is to tell Portage what you specifically |
| 29 |
want to unmerge; this should not be an automatic function (except in the |
| 30 |
case of repair utilities such as depclean, which even those give you a |
| 31 |
HUGE warning that unmerging "random" --as in "not pre-specified by the |
| 32 |
user, but determined by a script"-- packages automatically can break the |
| 33 |
system). |
| 34 |
|
| 35 |
The actual answer to your question, though, is that the blocking package |
| 36 |
is not a problem unless you want to emerge something that it blocks. So |
| 37 |
of course it's not going to be "noticed" until you attempt to perform |
| 38 |
such an action (emerging a package that is blocked by the installed |
| 39 |
package). |
| 40 |
> |
| 41 |
> 2) How do I rectify this little "version discrepancy" fixed so that |
| 42 |
> I can get things updating normally again? |
| 43 |
|
| 44 |
Iirc from several threads recently, there are one or more packages on |
| 45 |
your system that rely on php which must be updated to ~arch, or else |
| 46 |
they keep trying to bring in PHP4 (only the ~arch version can depend on |
| 47 |
PHP5; the stable versions have a fixed dependency on PHP4). |
| 48 |
|
| 49 |
I don't remember which programs they are, but if you don't feel like |
| 50 |
searching the archives, you can look at your tree view to see what is |
| 51 |
actually pulling in PHP4, upgrading that (or keywording it to unstable, |
| 52 |
rather) and see if you still get the block. |
| 53 |
|
| 54 |
Hope this helps, |
| 55 |
Holly |
| 56 |
-- |
| 57 |
gentoo-user@g.o mailing list |
Archives