It's interesting that it took us that long to encounter this! s foo → bar/foo s bar → baz f baz/foo
This means that there is no regular file with path bar/foo. From skimming the code, checkpkg looks for packages containing pkgmap entries equal to the target of the symlink, which does not yield a correct result in this case. To fix this, checkpkg needs to follow directory symlinks. If anyone wants to take that on, the place in the code is checkpkg_lib.py:651, and there are existing unit tests you can copy and modify to expose the problem. Maciej
