1 |
Hi, |
2 |
|
3 |
$SUBJECT |
4 |
|
5 |
I've updated the portage used on rsync1 and rsync2 from 2.2.28 to 2.3.62 |
6 |
yesterday because I started to see errors about EAPI=7 being unknown. |
7 |
Once I put the newer portage in place I got a lot of errors about the |
8 |
use of versionator.eclass. This was fixed in |
9 |
f5b4e670e0d7a5686f67b5bcfe4c323d6f4fe050 by syncing all the eclasses, |
10 |
some of which depended on versionator. Next were errors about invalid |
11 |
versions due to our usage of interrevisions. I've removed them all in |
12 |
82c2c71837628069aeb9484d295d304b3387d91c, |
13 |
d8c9f4611146c1e16b1aa795b8e599c56386a1a9 and |
14 |
7d3f27a474ff2fc086c95440e29d0319b64f80b0. After this I expect the tree |
15 |
generation to be silent again. I've bumped the latest portage in tree |
16 |
to 2.3.67 in the process, as well as binutils-config to avoid downgrades |
17 |
due to removal of interrevision-versions. |
18 |
|
19 |
Please keep the tree clean from interrevisions (use a .1 extra version |
20 |
or something). Adding them makes egencache unhappy (thus generate no |
21 |
cache for those). |
22 |
|
23 |
Thanks, |
24 |
Fabian |
25 |
|
26 |
-- |
27 |
Fabian Groffen |
28 |
Gentoo on a different level |