[MIR] libpfm4
Bug #1521969 reported by
Dimitri John Ledkov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| libpfm4 (Ubuntu) |
Fix Released
|
Undecided
|
Dimitri John Ledkov | ||
Bug Description
[Availability]
Available in universe.
[Rationale]
Needed for s390-tools, to support installer on s390x
[Security]
Shared library with python bindings.
No CVEs.
[Quality assurance]
Simple. There are many patches, but they are well maintained in debian.
[Dependencies]
All in main.
[Standards compliance]
Complaint
[Maintenance]
Foundations & xnox
[Background information]
Needed for s390-tools, to support d-i on s390x.
| affects: | sysconfig (Ubuntu) → libpfm4 (Ubuntu) |
| Changed in libpfm4 (Ubuntu): | |
| assignee: | nobody → Mathieu Trudel-Lapierre (mathieu-tl) |
Revision history for this message
| Mathieu Trudel-Lapierre (cyphermox) wrote | #1 |
| Changed in libpfm4 (Ubuntu): | |
| status: | New → Incomplete |
| Changed in libpfm4 (Ubuntu): | |
| milestone: | none → ubuntu-17.03 |
| assignee: | Mathieu Trudel-Lapierre (cyphermox) → Dimitri John Ledkov (xnox) |
| Changed in libpfm4 (Ubuntu): | |
| status: | Incomplete → Fix Committed |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in libpfm4 (Ubuntu): | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| Matthias Klose (doko) wrote | #3 |
To post a comment you must log in.
It looks to me like the package meets all the main inclusion requirements.
Some nitpicks:
- [QA] I've noticed there are tests available, they are even being built, but are not run as part of the build.
- [Maintenance] Some concerns with the maintenance in Debian, Andreas Beckman is the uploader, and appears to be the only one touching this package (which was previously maintained by Vincent Danjean (still the maintainer)). The number of people actively looking after this package in Debian when it is a dependency of a "bootloader" might be an issue. Still, it doesn't appear to be a direct requirement of zipl (only cpacfstats), so I'm not considering this a blocker.
Once the tests are being run as part of the build if it's possible, I see no objections to promoting to main.