| 1 |
Due to bug 645002 (and possibly others), our stage1 builds are making |
| 2 |
very odd choices on several || ( ) deps, and failing to resolve deps. |
| 3 |
|
| 4 |
One example failure log: |
| 5 |
https://archives.gentoo.org/gentoo-releng-autobuilds/message/19e4086ee421a504c445edafc2e83d88 |
| 6 |
|
| 7 |
This has been fixed in portage-2.3.20 but there is no indication yet |
| 8 |
of if or when this version is going to be stabilized. If the next |
| 9 |
portage stabilization is more than a couple of days out, I propose |
| 10 |
that we add a temporary mask to force portage to make the right |
| 11 |
decisions. Since catalyst now cleans our releng portage configs, |
| 12 |
there would be no visible signs of this workaround in the resulting |
| 13 |
stages. |
| 14 |
|
| 15 |
Proposed masks: |
| 16 |
|
| 17 |
releng/releases/weekly/portage/stages/package.mask/releng/portage-workarounds: |
| 18 |
|
| 19 |
dev-util/pkgconf |
| 20 |
sys-apps/paludis |
| 21 |
sys-fs/static-dev |
| 22 |
|
| 23 |
|
| 24 |
Thoughts? |
| 25 |
|
| 26 |
-Ben |
Archives