(In reply to Dr. Werner Fink from comment #3) > Not tested yet > > --- TmpFilesCheck.py > +++ TmpFilesCheck.py 2020-03-12 08:09:38.292286701 +0000 > @@ -34,16 +34,19 @@ class TmpFilesCheck(AbstractCheck.Abstra > > for fn, pkgfile in pkg.files().items(): > if not fn.startswith('/usr/lib/tmpfiles.d/'): > continue > if not stat.S_ISREG(pkgfile.mode): > printWarning(pkg, "tmpfile-not-regular-file", fn) > continue > > + if pkgfile.is_ghost: > + continue > + > basename = os.path.basename(fn) > pattern = re.compile( > r'systemd-tmpfiles --create .*%s' % re.escape(basename)) > if (not postin or not pattern.search(postin)) and \ > (not prein or not pattern.search(prein)): > printWarning(pkg, > 'postin-without-tmpfile-creation', fn) I've local build the rpmlint with this patch and copied the resulting /usr/share/rpmlint/__pycache__/TmpFilesCheck.cpython-38.opt-1.pyc into the build environment for the nvidia package as /opt/testing/share/rpmlint/TmpFilesCheck.pyc to override the rpmlinit-mini and now the pacakge build [ 245s] nvidia-gfxG05-kmp-default.x86_64: W: unstripped-binary-or-object /usr/src/kernel-modules/nvidia-440.64-default/nvidia-modeset/nv-modeset-kernel.o_binary [ 245s] nvidia-gfxG05-kmp-default.x86_64: W: unstripped-binary-or-object /usr/src/kernel-modules/nvidia-440.64-default/nvidia/nv-kernel.o_binary [ 245s] stripping debug info from binaries happens automatically according to global [ 245s] project settings. So there's normally no need to manually strip binaries. Left [ 245s] over unstripped binaries could therefore indicate a bug in the automatic [ 245s] stripping process. [ 245s] [ 245s] nvidia-gfxG05-kmp-default.x86_64: W: useless-provides nvidia-gfxG05-kmp [ 245s] nvidia-gfxG05-kmp-default.x86_64: W: useless-provides nvidia-gfxG05-kmp-default [ 245s] This package provides 2 times the same capacity. It should only provide it [ 245s] once. [ 245s] [ 245s] 2 packages and 0 specfiles checked; 0 errors, 40 warnings. [ 245s]