| 1 |
On 10/24/2011 02:40 AM, Hartmut Figge wrote: |
| 2 |
> Greetings, |
| 3 |
> |
| 4 |
> emerge --sync was successfull till 'Performing Global Updates' which |
| 5 |
> leaded to an error. After waiting for perhaps 1 to 2 hours i tried |
| 6 |
> another 'emerge --sync' in the hope that would fix the issue. No luck. |
| 7 |
> |
| 8 |
> --------------- |
| 9 |
> i5 hafi # emerge --sync |
| 10 |
> |
| 11 |
> Performing Global Updates: |
| 12 |
> (Could take a couple of minutes if you have a lot of binary packages.) |
| 13 |
> .='update pass' *='binary update' #='/var/db update' @='/var/db move' |
| 14 |
> s='/var/db SLOT move' %='binary move' S='binary SLOT move' |
| 15 |
> p='update /etc/portage/package.*' |
| 16 |
> /usr/portage/profiles/updates/3Q-2011.......................... |
| 17 |
> /usr/portage/profiles/updates/4Q-2011...... |
| 18 |
> ERROR: Malformed update entry 'move dev-php5/dev-php5/pecl-ssh2 dev-php/dev-php5/pecl-ssh2' |
| 19 |
|
| 20 |
For future reference, instead of deleting (which can be a bad idea since |
| 21 |
new ebuilds can depend on renamed/moved packages which means you can |
| 22 |
mess up your installation), you can resync later with: |
| 23 |
|
| 24 |
emerge --sync --package-moves=n |
Archives