search for: software_version

...irement bump breaks the nbdkit build on RHEL-9.1 -- which provides rustc 1.62. Restrict predicates-{tree,core} to {1.0.7,1.0.5}. (Side commentary: when such things can happen via a *patchlevel* upgrade, that makes a total mockery of "semantic versioning" <https://en.wikipedia.org/wiki/Software_versioning#Semantic_versioning>.) Signed-off-by: Laszlo Ersek <lersek at redhat.com> --- plugins/rust/Cargo.toml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/plugins/rust/Cargo.toml b/plugins/rust/Cargo.toml index 45d8a755e6e3..64ed193a0008 100644 --- a/plugins/rust/Cargo.toml +++ b/plu...

Testing on an 8-node 128-way NUMA machine has exposed a problem with Xen''s nr_cpus calculation. In this case, since Xen cuts off recognized CPUs at 32, the machine appears to have 16 CPUs on the first and second nodes and none on the remaining nodes. Given this asymmetry, the calculation of sockets_per_node (which is later used to calculate nr_cpus) is incorrect:

...", "id"=>"3", "version"=>"3"}>] >> A question: is it normal for the first save without optimistic locking to generate two object versions? % ++++ And the database content ++++ mysql> select * from softwares; select * from software_versions; +----+--------------------+---------+ | id | name | version | +----+--------------------+---------+ | 1 | Name changed again | 4 | +----+--------------------+---------+ 1 row in set (0.00 sec) +----+-------------+---------+--------------------+---...

...llvm-profdata show -metadata foo.profdata customkey: "value1" Total functions: 4 Maximum function count: 866988873 Maximum internal block count: 267914296 Developers could add as much custom context as they find valuable: $ llvm-profdata merge -metadata="mysoft.version,${SOFTWARE_VERSION} (${BUILD_NUMBER})" -metadata="mysoft.exe_md5,`md5 -q foo.exe` foo.profraw -o foo.profdata $ llvm-profdata show -metadata foo.profdata mysoft.version: "0.1.0" mysoft.exe_md5: "337b5c5bc29cbdca090a1921a58465d6" Total functions: 4 Maximum function count: 866988...

...14296 > > > > Developers could add as much custom context as they find valuable: > > I think all meta data should be custom defined -- the profile reader > should not need to understand them. > > > > > > $ llvm-profdata merge -metadata="mysoft.version,${SOFTWARE_VERSION} > > (${BUILD_NUMBER})" -metadata="mysoft.exe_md5,`md5 -q foo.exe` > foo.profraw -o > > foo.profdata > > $ llvm-profdata show -metadata foo.profdata > > mysoft.version: "0.1.0" > > mysoft.exe_md5: "337b5c5bc29cbdca090a1921a58465d6&quot...

I originally meant to post only the "vector.h" patch, but then (independently) nbdkit wouldn't build. Hence the other (rust plugin) patch. Laszlo Laszlo Ersek (2): common/utils: document empty_vector compound literal assignment plugins/rust: restrict predicates-{tree,core} to {1.0.7,1.0.5} common/utils/vector.h | 8 +++++++- plugins/rust/Cargo.toml | 2 ++ 2 files changed,

...ot enough free memory] DCSC-XEN01: Cannot start here [Api_errors.Server_error("VM_HOST_INCOMPATIBLE_VERSION", _)] My question is how do I go about modifying the version and platform information for XAPI? My xensource-inventory file looks fine: BUILD_NUMBER=''61809c'' SOFTWARE_VERSION=''1.6.10'' DOM0_MEM=''752'' MANAGEMENT_INTERFACE=''xenbr0'' INSTALLATION_UUID=''718e7db1-cf3d-46ea-bcc9-cee8c456ed4d'' COMPANY_NAME_SHORT=''xen.org'' PLATFORM_NAME=''XCP'' PLATFORM_VERSION=''1.6....

Bug in cmake (or more likely the makefile?), pure and simple. Version numbers aren't strings, and they aren't floating point numbers, they are a series of integers separated by dots. I can't think of a project where interpreting version numbers that way won't work. On Wed, Jun 15, 2016 at 7:21 AM, Cristianno Martins via llvm-dev < llvm-dev at lists.llvm.org> wrote: >