| Summary: | glusterfs new security issue CVE-2017-15096 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | David Walser <luigiwalser> |
| Component: | Security | Assignee: | All Packagers <pkg-bugs> |
| Status: | RESOLVED INVALID | QA Contact: | Sec team <security> |
| Severity: | normal | ||
| Priority: | Normal | CC: | lists.jjorge, mageia, marja11 |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | glusterfs-3.7.9-1.mga6.src.rpm | CVE: | |
| Status comment: | |||
|
Description
David Walser
2017-11-12 20:00:51 CET
Assigning to all packagers collectively, since there is no registered maintainer for this package. Assignee:
bugsquad =>
pkg-bugs glusterfs is already in task-obsoletes (for mga6 and cauldron). The question is, why python-gluster is still present in the repo and why task-obsoletes does not remove it. CC:
(none) =>
mageia If python-gluster has no other dep, it is simply because of human error. It must be added to task-obsoletes and moved in the svn (not removed) according to this : https://wiki.mageia.org/en/Packaging_guidelines#Obsoleting_a_package You are welcome to do so. CC:
(none) =>
lists.jjorge Thanks Marc. I thought we had dropped this package, so I guess I wasn't crazy after all. It was typed incorrectly as python-glusterfs in task-obsolete, so it was still hanging around. glusterfs actually isn't in SVN at all. Status:
NEW =>
RESOLVED |