| 1 |
On Sat, Jun 13, 2020, at 11:41 AM, Fabian Groffen wrote: |
| 2 |
> On 13-06-2020 09:58:38 -0500, Sid Spry wrote: |
| 3 |
> > On Sat, Jun 13, 2020, at 8:58 AM, Fabian Groffen wrote: |
| 4 |
> > > Then update your portage? |
| 5 |
> > |
| 6 |
> > ... I can't, it's blocked by EAPI version mistmatch. The stage3 is EAPI6. Most of the packages, and at least the most important ones like postage, are EAPI7. |
| 7 |
> |
| 8 |
> This sounds a lot like the scenario I recently had when I started up an |
| 9 |
> old VM. In the old days, the upgrade path was kept around, but with the |
| 10 |
> current generation of devs, this is considered bloat. |
| 11 |
> |
| 12 |
> I ended up just respinning the VM, reinstalling Gentoo from scratch. Is |
| 13 |
> that something possible for you to do? Your only alternative is (most |
| 14 |
> likely) installing a more recent Portage manually, or by hacking the |
| 15 |
> ebuild to make it EAPI=5 and wading your way through warnings and errors |
| 16 |
> until it manages to install. I would just do |
| 17 |
> ebuild portage... digest clean merge |
| 18 |
> for this, making changes wherever you need to just get the new portage |
| 19 |
> installed. After that, probably --sync to wipe out any modifications |
| 20 |
> you had to make. |
| 21 |
> |
| 22 |
> Thanks, |
| 23 |
> Fabian |
| 24 |
> |
| 25 |
> -- |
| 26 |
> Fabian Groffen |
| 27 |
> Gentoo on a different level |
| 28 |
> |
| 29 |
> Attachments: |
| 30 |
> * signature.asc |
| 31 |
|
| 32 |
I can try this later. Is there no way to trigger the release build machinery? I realize the files are hosted from an experimental dir but doubt their generation was entirely manual. |
| 33 |
|
| 34 |
I would try to build a prefix stage3 myself (via bootstrap-prefix.sh?) but I am not sure I have an arm64 device that will work. |
Archives