Request 649537 (accepted)

This request supersedes: request 648363 (Show diff)

Overview

Request 649537 accepted

- Update to version 2.0.12:
* Release numactl 2.0.12
* Cleanup whitespace from *.c and *.h files
* Add Travis build status to numactl README
* Convert README and INSTALL to Markdown
* Remove `threadtest.c`
* Remove `mkolddemo` script
* Remove file TODO, which has outdated contents
* Remove file DESIGN, which has no contents
* Remove changelogs from the repository
* Revert "make clearcache work on x86/PIC"
* Add "NAME" section to numastat manpage
* Allow building on ARM systems
* Add pkg-config file for NUMA library
* readdir_r(3) is deprecated, use readdir(3) instead
* Avoid filename truncation in numastat
* fix coding style in last change
* Fix: numademo test between sparse nodes
* Fix: allocation of dynamic array
* Fix: numactl distance between sparse nodes
* include sys/sysmacros.h for major/minor
* make clearcache work on x86/PIC
* Fix regress test for invalid hard code of nodenames
* Fix end of line check in distance parsing
* Optimize numa_distance check
* affinity: Include sys/sysmacros.h to fix warning
* numademo: Increase buffer to avoid theoretical buffer overflow
* Check for invalid nodes in numa_distance

Created by a_jaeger over 5 years ago
In state accepted
Supersedes 648363

Submit numactl

Comments for request 649537 0
Comments for request 648363 5

Jan Engelhardt (jengelh) - over 5 years ago

reviewer

Please use real identities, not opensuse-packaging@opensuse.org (who is that, anyway?)

Thomas Renninger (trenn) - over 5 years ago

source maintainer

This is from "obs service run", feature: "*_scm" <param name="changesgenerate">enable</param> parameter. It would be a nice enhancement if the user is put there who run this service, instead the need of adjusting this everytime.

Jan Engelhardt (jengelh) - over 5 years ago

reviewer

That sounds like you should set up a ~/.oscrc if you don't have one yet. After all, the services only run manually (due to mode=disabled) and in full conciousness (so I hope).

Thomas Renninger (trenn) - over 5 years ago

source maintainer

.oscrc does not help. You can explicitly run this service locally (that is what it is for afaik and how I use it as well). You then get a new tarball and latest version set without manual download and fiddling. A nice feature would be to recognize the user from ~/.oscrc when issuing this locally.

Dominique Leuenberger (dimstar) - over 5 years ago

reviewer

if you call osc service locally to produce the changes entries, osc picks up the first 'email=' in .oscrc; so you can configure this to be your own email address instead of a mailing list (giving this as maintainer address means people might want to reach out there about issues - but by far not everybody is on the list and we'd not want that list to become a 'packaging bug list')