| 1 |
> On Tue, 24 May 2016, at 10:38 am, J. Roeleveld <joost@××××××××.org> wrote: |
| 2 |
> |
| 3 |
> The usual method is to do it in stages. |
| 4 |
> Get portage snapshots about 3 to 6 months apart and do it that way. |
| 5 |
> |
| 6 |
> How long ago did you update that system last? |
| 7 |
|
| 8 |
I did this recently, successfully updating a couple of boxes which hadn't been updated in 2 years. |
| 9 |
|
| 10 |
I think I used snapshots about 4 months apart. |
| 11 |
https://dev.gentoo.org/~swift/snapshots/ |
| 12 |
|
| 13 |
Despite the machines being nearly identical, I had some trouble with setuptools and python_targets on only one of the two. |
| 14 |
|
| 15 |
In its /etc/portage/package.use I have: |
| 16 |
|
| 17 |
>=dev-python/setuptools-18.4 python_targets_python3_3 |
| 18 |
>=dev-python/idna-2.0 python_targets_python3_3 |
| 19 |
>=virtual/python-ipaddress-1.0 python_targets_python3_3 |
| 20 |
>=dev-python/packaging-15.3-r2 python_targets_python3_3 |
| 21 |
>=dev-python/cffi-1.2.1 python_targets_python3_3 |
| 22 |
>=dev-python/six-1.10.0 python_targets_python3_3 |
| 23 |
>=dev-python/enum34-1.0 python_targets_python3_3 |
| 24 |
>=dev-python/pycparser-2.14 python_targets_python3_3 |
| 25 |
>=dev-python/pyasn1-0.1.8 python_targets_python3_3 |
| 26 |
>=dev-python/cryptography-1.0.2 python_targets_python3_3 |
| 27 |
>=dev-python/ply-3.6-r1 python_targets_python3_3 |
| 28 |
>=dev-python/certifi-2015.9.6.2 python_targets_python3_3 |
| 29 |
|
| 30 |
That machine now shows "Last emerge --sync was 124d 13h 44m 35s ago", whereas the other I got fully up-to-date 30 days ago. |
| 31 |
|
| 32 |
I don't know why one updated smoothly, and the other required this python_targets intervention. I seem to recall being quite frustrated by it. |
| 33 |
|
| 34 |
Stroller. |
Archives