[MIR] numactl (binary)

Bug #1700824 reported by dann frazier
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
numactl (Ubuntu)
Fix Released
Undecided
Mathieu Trudel-Lapierre

Bug Description

libnuma from the numactl source package was MIR'd in LP: #891232, however the numactl binary is still in universe. I'd like to request that the numactl binary also be considered for main. I work with users of arm64 server platforms, where NUMA is increasingly common, and they find these tools useful for setting scheduling/placement policies.

Per https://wiki.ubuntu.com/MainInclusionProcess:

"If a new source package contains only code which is already in main (e.g., the result of a source package split or rename, or source packages with a version in the name), it may not need a full review. Submitting a bug with an explanation is sufficient."

However, since the numactl binary package was presumably always part of the numactl source package, I'm not sure if the above exception applies. Let me know if more information, such as a full MIR report, is required.

Revision history for this message
dann frazier (dannf) wrote :

Should this request be approved, I'd also like to request that it be considered retroactively for 16.04 so that LTS support is accelerated.

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

I reviewed this anyway, and see nothing wrong with it. MIR approved.

Changed in numactl (Ubuntu):
status: New → Fix Committed
assignee: nobody → Mathieu Trudel-Lapierre (cyphermox)
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

There is bug 1700826 open about seeding this on the images; it would need to be in the metapackage before it remains in main, if it was to get promoted now.

Revision history for this message
Robie Basak (racb) wrote :

Acked for ~ubuntu-server by ~nacc and ~racb (in ~davidpbritton's absence).

Adam Conrad (adconrad)
Changed in numactl (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.