Vesion is too long

[bistack]

v0.6.0+5.3.0-1-ge13ca993e8ccb9ba9847cc330696e02839f328f7

What is the last part?
Is the jemalloc gid? It's not match 5.3.0's gid.

Just v0.6.0+5.3.0 is fine.

[BusyJay]

It's the ref (version and commit hash) of bundled jemalloc. What problem did you meet exactly?

[klensy]

I guess that it's typo in git commit hash, i.e. jemalloc/jemalloc@ge13ca993e8ccb9ba9847cc330696e02839f328f7 not exist, while jemalloc/jemalloc@e13ca99 exist and points to correct commit.

[BusyJay]

The hash points to tikv/jemalloc@e13ca99 , it's generated by git describe.

[reneleonhardt]

I mean this is literally the committed line, 41 chars is not a SHA-1 hash name, thank you @bistack for reporting 👍

jemallocator/jemalloc-sys/Cargo.toml

Line 3 in f260a80

version = "0.6.0+5.3.0-1-ge13ca993e8ccb9ba9847cc330696e02839f328f7"

@BusyJay Would it be possible to use a normal semver or at least the correct hash?

By the way, e13ca99 is outdated, the last one is 09ad115
https://github.com/tikv/jemalloc/commits/5.3.x/