| Summary: | glsa-check -f new fails with app-portage/gentoolkit-0.3.0_rc7 | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Martin Gerdzhev <mgerdjev> |
| Component: | Tools | Assignee: | Portage Tools Team <tools-portage> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | jakub.januszkiewicz, matt.palermo, pauldv |
| Priority: | High | Keywords: | InVCS |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 237964 | ||
| Attachments: | glsa-check.275105.patch | ||
|
Description
Martin Gerdzhev
2009-06-22 20:20:31 UTC
$ svn commit -m "Fix traceback with glsa-check -f (Bug 275105)" Sending gentoolkit/ChangeLog Sending gentoolkit/bin/glsa-check Transmitting file data .. Committed revision 665. Created attachment 195509 [details, diff]
glsa-check.275105.patch
patch for gentoolkit-0.3.0_rc7
The patch worked fine. Thanks. (In reply to comment #3) > The patch worked fine. Thanks. > If this patch is working (and it does), when is a new _RC going to be released? It is an RC after all. Isn't testing a wider rage of machines what the RC are for? It would be nice to be able to clear out the glsa "db" on my machines. I can't be alone in wishing a "app-portage/gentoolkit-0.3.0_rc8" be released that has this patch in it. M. The patch fixes one problem, failing, but there is still another problem with me. This version of glsa-check does not seem to be able to record or recall the list of applied glsa's. As such a call of "glsa-check -l" returns all glsa's in existence. (In reply to comment #5) > The patch fixes one problem, failing, but there is still another problem with > me. This version of glsa-check does not seem to be able to record or recall the > list of applied glsa's. As such a call of "glsa-check -l" returns all glsa's in > existence. > I confirm this problem. Do you need my emerge --info or anything else? Jakub, Paul: Please open a new bug report if you consider this to be a regression. The behavior of glsa-check has changed in gentoolkit 0.3 (rc8): - there is only two listing modes: "affected" and "all", "new" is gone (i just made "affected" the new default) - fixed GLSAs are no longer stored in a checkfile (injected) It is still possible to inject GLSAs to make them invisible to glsa-check, but it seemed most reasonable to me to check the system for all GLSAs that admins do not manually add to the file instead of caching that "--fix" has been run once and then never bother about that GLSA again. That behavior did not account for: - changes in glsas - re-emerging/downgrading packages And also, /var/cache was not a good place to store the GLSAs admins injected manually. Please let me know if this breaks some workflow you had been using before and we can discuss options to fix this. Thanks for the explanation. Bug #281960 opened by Paul. The change in behavior will be addressed with Bug #281960. The initial issue was fixed a long time ago. |
