| Summary: | sys-apps/portage: glsa-check treats /var/lib/portage/glsa_injected inconsistently | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Evgeny Stambulchik <fnevgeny> |
| Component: | Tools | Assignee: | Portage team <dev-portage> |
| Status: | UNCONFIRMED --- | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
glsa-check is included with >=sys-apps/portage-2.3.72 (bug 463952). |
I have two "injected" entries in /var/lib/portage/glsa_injected: 201406-01 201412-08 (for an old Gtk-based binary package). However, `glsa-check --list` doesn't list them as injected: # glsa-check --list [A] means this GLSA was marked as applied (injected), [U] means the system is not affected and [N] indicates that the system might be affected. # On the other hand, `glsa-check -t` all does show them, while it shouldn't: # glsa-check -t all This system is affected by the following GLSAs: 201412-08 201406-01 This is contrary to what the glsa-check(1) manpage says: FILES /var/lib/portage/glsa_injected List of GLSA ids that have been injected and will _never_ show up as 'affected' on this system.