On 2020-06-11 23:20, Rich Freeman wrote:
On Thu, Jun 11, 2020 at 4:43 PM n952162 <n952...@web.de> wrote:
On 2020-06-11 22:35, Rich Freeman wrote:
On Thu, Jun 11, 2020 at 4:28 PM n952162 <n952...@web.de> wrote:
On 2020-06-11 22:01, Rich Freeman wrote:
Try:
USE="python_targets_python3_6 -python_targets_python3_7 -rsync-verify"
emerge -p1v =sys-apps/portage-2.3.99-r2
Sorry, try again.
* IMPORTANT: 2 config files in '/etc/portage' need updating.
These are the packages that would be merged, in order:
Calculating dependencies * See the CONFIGURATION FILES and
CONFIGURATION FILES UPDATE TOOLS
* sections of the emerge man page to learn how to update config files.
.... . ... done!
[ebuild U ] sys-apps/portage-2.3.99-r2::gentoo [2.3.13-r1::gentoo]
USE="(ipc) native-extensions xattr -apidoc% -build -doc -gentoo-dev%
-rsync-verify% (-selinux) (-epydoc%)" PYTHON_TARGETS="python3_6*
(-pypy3) -python3_7% (-python3_8) (-pypy%) (-python2_7%*) (-python3_4%)
(-python3_5%*)" 1028 KiB
[blocks B ] <app-portage/gentoolkit-0.4.6
("<app-portage/gentoolkit-0.4.6" is blocking sys-apps/portage-2.3.99-r2)
You're actually pretty close.
I think this will work:
USE="python_targets_python3_6 -python_targets_python3_7 -rsync-verify"
emerge -p1v =sys-apps/portage-2.3.99-r2 app-portage/gentoolkit
!!! All ebuilds that could satisfy "app-portage/gentoolkit" have been
masked.
!!! One of the following masked packages is required to complete your
request:
- app-portage/gentoolkit-9999::gentoo (masked by: EAPI 7)
- app-portage/gentoolkit-0.5.0::gentoo (masked by: EAPI 7)
- app-portage/gentoolkit-0.4.8::gentoo (masked by: EAPI 7)
- app-portage/gentoolkit-0.4.7::gentoo (masked by: EAPI 7)
- app-portage/gentoolkit-0.4.6::gentoo (masked by: EAPI 7)
Yeah, I wasn't thinking and didn't think to check the EAPI on it.
This will break gentoolkit for a short time, but I suggest doing:
quickpkg portage gentoolkit
USE="python_targets_python3_6 -python_targets_python3_7 -rsync-verify"
emerge -p1v --nodeps =sys-apps/portage-2.3.99-r2
USE="python_targets_python3_6 -python_targets_python3_7 -rsync-verify"
emerge -p1uv app-portage/gentoolkit
Check that the first emerge output is sane and JUST wants to update
portage before executing it. The second will immediately update
gentoolkit as the version you currently have is not compatible with
the new portage, so we don't really want to leave that lying around.
Refrain from running anything installed by gentoolkit in-between these
two commands. However, most of the stuff that you would use is
read-only anyway.
The quickpkg command at the start creates a binary package of your
existing portage and gentoolkit packages so that you have a better
chance of recovery if anything goes wrong.
In general ignoring blocks is not something you want to do, and
neither is --nodeps, but I'm pretty sure it is safe in this particular
situation.
Now this is all getting really over my head:
[32;01m * [39;49;00mBuilding package for sys-apps/portage-2.3.13-r1
... [34;01m[ [39;49;00m[32;01mok[39;49;00m[34;01m
][39;49;00m
[33;01m * [39;49;00mExcluded config: '/etc/dispatch-conf.conf'
[33;01m * [39;49;00mExcluded config: '/etc/etc-update.conf'
[33;01m * [39;49;00mExcluded config: '/etc/logrotate.d/elog-save-summary'
[33;01m * [39;49;00mExcluded config:
'/etc/portage/repo.postsync.d/example'
[32;01m * [39;49;00mBuilding package for app-portage/gentoolkit-0.4.0
... [34;01m[ [39;49;00m[32;01mok[39;49;00m[34;01m
][39;49;00m
[33;01m * [39;49;00mExcluded config: '/etc/eclean/distfiles.exclude'
[33;01m * [39;49;00mExcluded config: '/etc/eclean/packages.exclude'
[32;01m * [39;49;00mPackages now in '/usr/portage/packages':
[32;01m * [39;49;00msys-apps/portage-2.3.13-r1: 4.1M
[32;01m * [39;49;00mapp-portage/gentoolkit-0.4.0: 6.5M
[33;01m * [39;49;00mExcluded config files: 6
[33;01m * [39;49;00mSee --help if you would like to include config files.
These are the packages that would be merged, in order:
[ebuild U ] sys-apps/portage-2.3.99-r2::gentoo [2.3.13-r1::gentoo]
USE="(ipc) native-extensions xattr -apidoc% -build -doc -gentoo-dev%
-rsync-verify% (-selinux) (-epydoc%)" PYTHON_TARGETS="python3_6*
(-pypy3) -python3_7% (-python3_8) (-pypy%) (-python2_7%*) (-python3_4%)
(-python3_5%*)" 1028 KiB
Total: 1 package (1 upgrade), Size of downloads: 1028 KiB
* IMPORTANT: 25 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
These are the packages that would be merged, in order:
[ebuild U ] sys-apps/portage-2.3.99-r2::gentoo [2.3.13-r1::gentoo]
USE="(ipc) native-extensions xattr -apidoc% -build -doc -gentoo-dev%
-rsync-verify% (-selinux) (-epydoc%)" PYTHON_TARGETS="python3_6*
(-pypy3) -python3_7% (-python3_8) (-pypy%) (-python2_7%*) (-python3_4%)
(-python3_5%*)" 1028 KiB
Total: 1 package (1 upgrade), Size of downloads: 1028 KiB
>>> Verifying ebuild manifests
* IMPORTANT: 25 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
>>> Running pre-merge checks for sys-apps/portage-2.3.99-r2
* Determining the location of the kernel source code
* Found kernel source directory:
* /usr/src/linux
* Found sources for kernel version:
* 4.9.76-gentoo-r1
* Checking for suitable kernel configuration options...
[ ok ]
>>> Emerging (1 of 1) sys-apps/portage-2.3.99-r2::gentoo
>>> Downloading
'http://distfiles.gentoo.org/distfiles/portage-2.3.99.tar.bz2'
--2020-06-11 21:39:23--
http://distfiles.gentoo.org/distfiles/portage-2.3.99.tar.bz2
Resolving distfiles.gentoo.org... 64.50.236.52, 64.50.233.100,
140.211.166.134, ...
Connecting to distfiles.gentoo.org|64.50.236.52|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1051210 (1.0M) [application/x-bzip2]
Saving to: '/usr/portage/distfiles/portage-2.3.99.tar.bz2'
0K .......... .......... .......... .......... .......... 4%
56.6K 17s
50K .......... .......... .......... .......... .......... 9%
69.9K 15s
100K .......... .......... .......... .......... .......... 14%
60.6K 14s
150K .......... .......... .......... .......... .......... 19%
67.9K 13s
200K .......... .......... .......... .......... .......... 24%
61.9K 12s
250K .......... .......... .......... .......... .......... 29%
48.5K 12s
300K .......... .......... .......... .......... .......... 34%
40.5K 12s
350K .......... .......... .......... .......... .......... 38%
55.6K 11s
400K .......... .......... .......... .......... .......... 43%
69.8K 10s
450K .......... .......... .......... .......... .......... 48% 71.7K 9s
500K .......... .......... .......... .......... .......... 53% 59.1K 8s
550K .......... .......... .......... .......... .......... 58% 68.0K 7s
600K .......... .......... .......... .......... .......... 63% 58.7K 6s
650K .......... .......... .......... .......... .......... 68% 72.2K 5s
700K .......... .......... .......... .......... .......... 73% 52.5K 5s
750K .......... .......... .......... .......... .......... 77% 64.7K 4s
800K .......... .......... .......... .......... .......... 82% 69.4K 3s
850K .......... .......... .......... .......... .......... 87% 68.7K 2s
900K .......... .......... .......... .......... .......... 92% 70.2K 1s
950K .......... .......... .......... .......... .......... 97% 65.9K 0s
1000K .......... .......... ...... 100%
66.3K=17s
2020-06-11 21:39:41 (61.4 KB/s) -
'/usr/portage/distfiles/portage-2.3.99.tar.bz2' saved [1051210/1051210]
* portage-2.3.99.tar.bz2 BLAKE2B SHA512 size ;-)
... [ ok ]
>>> Downloading
'http://distfiles.gentoo.org/distfiles/portage-2.3.89-bug-718578.patch'
--2020-06-11 21:39:41--
http://distfiles.gentoo.org/distfiles/portage-2.3.89-bug-718578.patch
Resolving distfiles.gentoo.org... 64.50.236.52, 64.50.233.100,
140.211.166.134, ...
Connecting to distfiles.gentoo.org|64.50.236.52|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1325 (1.3K) [application/x-troff-man]
Saving to: '/usr/portage/distfiles/portage-2.3.89-bug-718578.patch'
0K . 100% 365K=0.004s
2020-06-11 21:39:42 (365 KB/s) -
'/usr/portage/distfiles/portage-2.3.89-bug-718578.patch' saved [1325/1325]
* portage-2.3.89-bug-718578.patch BLAKE2B SHA512 size ;-)
... [ ok ]
* Please follow the instructions in the news item:
* 2019-06-05-amd64-17-1-profiles-are-now-stable
* or choose the 17.0 profile.
* ERROR: sys-apps/portage-2.3.99-r2::gentoo failed (setup phase):
* ERROR: 17.1 migration has not been performed!!
*
* Call stack:
* ebuild.sh, line 596: Called __source_all_bashrcs
* ebuild.sh, line 415: Called __try_source
'/usr/portage/profiles/default/linux/amd64/17.1/profile.bashrc'
* ebuild.sh, line 470: Called source
'/usr/portage/profiles/default/linux/amd64/17.1/profile.bashrc'
* profile.bashrc, line 6: Called die
* The specific snippet of code:
* die "ERROR: 17.1 migration has not been performed!!"
*
* If you need support, post the output of `emerge --info
'=sys-apps/portage-2.3.99-r2::gentoo'`,
* the complete build log and the output of `emerge -pqv
'=sys-apps/portage-2.3.99-r2::gentoo'`.
* The complete build log is located at
'/var/tmp/portage/sys-apps/portage-2.3.99-r2/temp/build.log'.
* The ebuild environment file is located at
'/var/tmp/portage/sys-apps/portage-2.3.99-r2/temp/die.env'.
* Working directory: '/var/tmp/portage/sys-apps/portage-2.3.99-r2/homedir'
* S: '/var/tmp/portage/sys-apps/portage-2.3.99-r2/work/portage-2.3.99'
>>> Failed to emerge sys-apps/portage-2.3.99-r2, Log file:
>>> '/var/tmp/portage/sys-apps/portage-2.3.99-r2/temp/build.log'
* Messages for package sys-apps/portage-2.3.99-r2:
* Please follow the instructions in the news item:
* 2019-06-05-amd64-17-1-profiles-are-now-stable
* or choose the 17.0 profile.
* ERROR: sys-apps/portage-2.3.99-r2::gentoo failed (setup phase):
* ERROR: 17.1 migration has not been performed!!
*
* Call stack:
* ebuild.sh, line 596: Called __source_all_bashrcs
* ebuild.sh, line 415: Called __try_source
'/usr/portage/profiles/default/linux/amd64/17.1/profile.bashrc'
* ebuild.sh, line 470: Called source
'/usr/portage/profiles/default/linux/amd64/17.1/profile.bashrc'
* profile.bashrc, line 6: Called die
* The specific snippet of code:
* die "ERROR: 17.1 migration has not been performed!!"
*
* If you need support, post the output of `emerge --info
'=sys-apps/portage-2.3.99-r2::gentoo'`,
* the complete build log and the output of `emerge -pqv
'=sys-apps/portage-2.3.99-r2::gentoo'`.
* The complete build log is located at
'/var/tmp/portage/sys-apps/portage-2.3.99-r2/temp/build.log'.
* The ebuild environment file is located at
'/var/tmp/portage/sys-apps/portage-2.3.99-r2/temp/die.env'.
* Working directory: '/var/tmp/portage/sys-apps/portage-2.3.99-r2/homedir'
* S: '/var/tmp/portage/sys-apps/portage-2.3.99-r2/work/portage-2.3.99'
