Summary: | app-portage/portage-utils-0.96.1: qcheck mtime results not reliable | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Johannes Niess <johannes_niess> |
Component: | Current packages | Assignee: | Fabian Groffen <grobian> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | floppym, genBTC, johannes_niess |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Johannes Niess
2024-05-14 19:58:35 UTC
The MTIME errors for python shouldn't be like that, and indicates something has tampered with them. The other packages are indeed cache files that have dynamic changing MTIMES, and I would agree something might need to be done about those. but the python part means something is changing .pyc files = valid discrepancy I am unable to reproduce the issue you are experiencing with python. % sudo qcheck -v dev-lang/python Checking dev-lang/python-3.12.3 ... * 8236 out of 8236 files are good Checking dev-lang/python-3.11.9 ... * 8421 out of 8421 files are good Checking dev-lang/python-2.7.18_p16-r2 ... * 4565 out of 4565 files are good It seems likely that the file timestamps on your system have been messed with somehow. what filesystem do you use? I can't reproduce the python issues, so "works for me" is OK. Maybe I had an python emerge running at that time. My ext4 fs mounted with noatime,discard,commit=600 P. S.: What's the correct approach for patches regarding the cache file cases like libs/gdk-pixbuf? It is not obvious from typical ebuilds, and mocking with /var/db/pkg/x/y/CONTENTS does not feel correct. |