Bug#964553: clang-11: Version handling/naming for packages build-from-upstream-git

Sedat Dilek sedat.dilek at gmail.com
Wed Jul 8 16:39:37 BST 2020

Package: clang-11
Version: 1:11~++20200701093119+ffee8040534-1~exp1
Severity: wishlist

Dear Maintainer,

as reported in LLVM bug #38998 "llvm-toolchain: Include Debian version string like for gcc"
the version handling (naming) for packages build-from-upstream-git looks uncommon to me.

In comment #24 I have listed all packages having a "git" on my Debian/testing (sid) AMD64 system:

root# dpkg -l | grep '\~git' | awk '/^ii/ {print $1 " " $2 " " $3}' | column -t

root# dpkg -l | grep '\+git' | awk '/^ii/ {print $1 " " $2 " " $3}' | column -t
ii  crda                        4.14+git20191112.9856751-1
ii  libfakekey0:amd64           0.3+git20170516-2
ii  libmusicbrainz5-2:amd64     5.1.0+git20150707-9
ii  libmusicbrainz5cc2v5:amd64  5.1.0+git20150707-9
ii  libpfm4:amd64               4.10.1+git44-ga2909cd-1
ii  libsox-fmt-alsa:amd64       14.4.2+git20190427-2
ii  libsox-fmt-base:amd64       14.4.2+git20190427-2
ii  libsox3:amd64               14.4.2+git20190427-2
ii  libspatialaudio0:amd64      0.3.0+git20180730+dfsg1-2+b1
ii  libtiff5:amd64              4.1.0+git191117-2
ii  libx264-155:amd64           2:0.155.2917+git0a84d98-2
ii  lua-socket:amd64            3.0~rc1+git+ac3201d-4
ii  sox                         14.4.2+git20190427-2
ii  xserver-xorg-video-intel    2:2.99.917+git20200226-1
ii  xserver-xorg-video-qxl      0.1.5+git20200331-1

I remember when I build myself from git I used to:
'upstream-version' plus '+git' (prefered by Debian see above) or `~git` plus 'posix-date' plus '.commit-hashid' (12 digits) plus 'debian-revision'

Transform for version-string "1:11~++20200701093119+ffee8040534-1~exp1" (latest in Debian/experimental):


To be read:
upstream-version:   11.0.0
"git" version-info: "git" + "posix-date" (here: "20200701" means 01-Jul-2020) + "commit-hashid" (here: "ffee8040534")
debian-revision:    1

We do not need any informations concerning the hh:mm:ss of the commit.
Havin the (POSIX) date and the commit-hashid is clear and obvious enough.
I prefer a "." (dot) between POSIX-date and commit-hashid.

The suffix '~exp1' - if this common or a rule for packages in Debian/experimental - can be kept otherwise you can drop it, too.


- Sedat -

[1] https://bugs.llvm.org/show_bug.cgi?id=38998
[2] https://bugs.llvm.org/show_bug.cgi?id=38998#c24

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing'), (99, 'buildd-unstable'), (99, 'buildd-experimental'), (99, 'experimental'), (99, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.8.0-rc4-4-amd64-llvm11-ias (SMP w/4 CPU cores)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages clang-11 depends on:
ii  binutils      
ii  libc6                   2.30-8
ii  libc6-dev               2.30-8
ii  libclang-common-11-dev  1:11~++20200701093119+ffee8040534-1~exp1
ii  libclang-cpp11          1:11~++20200701093119+ffee8040534-1~exp1
ii  libclang1-11            1:11~++20200701093119+ffee8040534-1~exp1
ii  libgcc-9-dev            9.3.0-14
ii  libgcc-s1               10.1.0-4
ii  libllvm11               1:11~++20200701093119+ffee8040534-1~exp1
ii  libobjc-9-dev           9.3.0-14
ii  libstdc++-9-dev         9.3.0-14
ii  libstdc++6              10.1.0-4

Versions of packages clang-11 recommends:
pn  libomp-11-dev  <none>
pn  llvm-11-dev    <none>
ii  python3        3.8.2-3

Versions of packages clang-11 suggests:
pn  clang-11-doc  <none>

-- no debconf information

More information about the Pkg-llvm-team mailing list