Package: mdadm Version: 4.1 Mdadm repo ( https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/log/ ) provides EXTRAVERSION as a fourth part of version output. It allows to define unique version string for the mdadm build, e.g. we can add deb number here. It is not used in Debian family and as a result, it makes impossible to determine if correct mdadm is in use (in case of conflict). Here is example for mdadm 4.1:
root@debian:/# dpkg -i mdadm_4.1-1_amd64.deb root@debian:/# mdadm --version mdadm - v4.1 - 2018-10-01 root@debian:/# dpkg -i mdadm_4.1-11_amd64.deb root@debian:/# mdadm --version mdadm - v4.1 - 2018-10-01 Generally it isn't a fix, but it helps to verify if package was installed successfully. >From my point of view change in spec file is missing. We resolved it >internally: Diff: %build -make %{?_smp_mflags} CXFLAGS="$RPM_OPT_FLAGS" SYSCONFDIR="%{_sysconfdir}" -mdadm mdmon +make %{?_smp_mflags} CXFLAGS="$RPM_OPT_FLAGS" SYSCONFDIR="%{_sysconfdir}" +EXTRAVERSION="Intel_Build: %{BUILD_LABEL}" mdadm mdmon This problem occurs for mdadm 4.2 also, should I submit another bug, or it will be resolved globally?