Summary: | glsa-check should check that data files are there | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Evgeny Stambulchik <fnevgeny> |
Component: | [OLD] Core system | Assignee: | Marius Mauch (RETIRED) <genone> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | ramereth, security |
Priority: | High | Keywords: | InVCS |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://bugs.gentoo.org/show_bug.cgi?id=81824 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Patch for glsa-check to check for timestamp.chk |
Description
Evgeny Stambulchik
2005-02-13 23:42:30 UTC
What exactly do you want it to do? Just complain that it isn't up to date? Well, in case there is NO directory (or it's empty) it should say the portage tree is corrupted or something like that. Regarding not up-to-date - it could be a nice idea; check that timestamp.chk is not older than x days and if it is, recommend emerge sync or emerge-webrsync. Thanks! Alright, then I'll reassign to dev-portage since its really their baby on changing glsa-check to do that. Created attachment 67838 [details, diff]
Patch for glsa-check to check for timestamp.chk
This patch will warn and sys.exit(0) if there is no timestamp in the
metadata/glsa directory. Depending upon how GLSA_SERVER gets implemented there
may need to be an additional check for that being used but I suppose that will
be obvious. I am also looking at the "too old" request.
existence check done, the "too old" check I'd mark as WONTFIX should have been closed ages ago :/ |