| 1 |
On Friday 20 January 2006 23:02, kevin@×××××××××××××.net wrote: |
| 2 |
> I have been running an AMD64 system for a while and was tempted by ~AMD64. |
| 3 |
> I copied my hardrive onto a spare, booted it up, edited make.conf to use |
| 4 |
> ~AMD64 as the default and ran emerge sync && emerge -uavDN world. |
| 5 |
> |
| 6 |
> After a bit of fiddling around with emerge stopping on several occasions |
| 7 |
> for various errors I finally had a fully functional ~AMD64 system with |
| 8 |
> kde3.5. However I noticed several packages had not been upgraded and if I |
| 9 |
> ran emerge -uavDN world again they still were not picked up. Particularly: |
| 10 |
> |
| 11 |
> firefox-bin - stopped at 1.07 and did not upgrade until I specifically ran |
| 12 |
> emerge -uavDN mozilla-firefox-bin |
| 13 |
> |
| 14 |
> kontact/kmail simply did not make it to kde3.5 at all and had to be |
| 15 |
> emerged manually with emerge -uavDN kmail |
| 16 |
|
| 17 |
because kmail was a dependecy of something else, that got not updated, so |
| 18 |
kmail was not updated too? |
| 19 |
|
| 20 |
> amarok did not upgrade.....emerge -uavDN amarok sorted that |
| 21 |
> |
| 22 |
|
| 23 |
don't know |
| 24 |
> There are probably more I haven't found...what is going on here? Why |
| 25 |
> aren't these packages, that should be in my world file, not upgraded? My |
| 26 |
> package.keywords file has nothing in it restricting the upgrades and they |
| 27 |
> work when entered individually. |
| 28 |
|
| 29 |
the magic word is 'should'. If they are dependencies of something else and |
| 30 |
were pulled in that way, they do not get updated. |
| 31 |
-- |
| 32 |
gentoo-amd64@g.o mailing list |
Archives