| Summary: | sys-apps/portage: 'Timestamp of chromium-70.0.3538.45.tar.xz has changed; recreating WORKDIR' makes no sense | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Michał Górny <mgorny> |
| Component: | Core - Ebuild Support | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 671498 | ||
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/proj/portage.git/commit/?id=1fc6cae0b2de181df5ba4c5b3f21b06604555387 commit 1fc6cae0b2de181df5ba4c5b3f21b06604555387 Author: Zac Medico <zmedico@gentoo.org> AuthorDate: 2018-10-10 07:52:10 +0000 Commit: Zac Medico <zmedico@gentoo.org> CommitDate: 2018-10-10 07:57:38 +0000 doebuild: skip timestamp check for deleted distfiles (bug 668206) Avoid behavior like this when a distfile has been removed: >>> Existing ${T}/environment for 'chromium-70.0.3538.45' will be sourced. >>> Run 'clean' to start with a fresh environment. >>> Checking chromium-70.0.3538.45.tar.xz's mtime... >>> Timestamp of chromium-70.0.3538.45.tar.xz has changed; recreating WORKDIR... Bug: https://bugs.gentoo.org/668206 Reported-by: Michał Górny <mgorny@gentoo.org> Signed-off-by: Zac Medico <zmedico@gentoo.org> lib/portage/package/ebuild/doebuild.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) Fixed in portage-2.3.62. |
After removing distfiles that I no longer needed, I can't resume the already-unpacked build of chromium: $ ebuild /var/db/repos/gentoo/www-client/chromium/chromium-70.0.3538.45.ebuild package merge >>> Existing ${T}/environment for 'chromium-70.0.3538.45' will be sourced. >>> Run 'clean' to start with a fresh environment. >>> Checking chromium-70.0.3538.45.tar.xz's mtime... >>> Timestamp of chromium-70.0.3538.45.tar.xz has changed; recreating WORKDIR... This really makes no sense since the ebuild didn't change, neither did the checksum of distfile, so restarting would either mean unpacking the same file unnecessarily or failing due to checksum mismatch.