| 1 |
On 2019-10-12, Neil Bothwick wrote: |
| 2 |
|
| 3 |
> On Sat, 12 Oct 2019 02:14:51 -0400, Alan Grimes wrote: |
| 4 |
> |
| 5 |
>> right now the next update is looking **BAD**: |
| 6 |
>> |
| 7 |
>> |
| 8 |
>> |
| 9 |
>> tortoise ~ # emerge --update --verbose portage --backtrack=30 |
| 10 |
>> --verbose-conflicts --pretend |
| 11 |
> |
| 12 |
> What are you emerging here, @system or @world? |
| 13 |
|
| 14 |
portage |
| 15 |
|
| 16 |
Alan, what if you try updating gentoolkit and portage at the same time? |
| 17 |
|
| 18 |
>> These are the packages that would be merged, in order: |
| 19 |
>> |
| 20 |
>> Calculating dependencies... done! |
| 21 |
>> [ebuild???????? U?? ] sys-apps/portage-2.3.76::gentoo [2.3.65::gentoo] |
| 22 |
>> USE="(ipc) native-extensions rsync-verify xattr -build -doc -epydoc |
| 23 |
>> -gentoo-dev (-selinux)" PYTHON_TARGETS="python2_7 python3_6 python3_7 |
| 24 |
>> -pypy -python3_5" 1,010 KiB |
| 25 |
>> [blocks B?????????? ] <app-portage/gentoolkit-0.4.6 |
| 26 |
>> ("<app-portage/gentoolkit-0.4.6" is blocking sys-apps/portage-2.3.76) |
| 27 |
> |
| 28 |
> Unmerge gentoolkit, then install the later version after portage if |
| 29 |
> updated. |
| 30 |
|
| 31 |
I don't think it's necessary to unmerge, just to update. I might be |
| 32 |
wrong, but I believe the reason why portage isn't solving this block by |
| 33 |
itself is because it was told to update portage only. |
| 34 |
|
| 35 |
-- |
| 36 |
Nuno Silva |
Archives