[18:48] <Steve132> Hey, so, I found a bug and I've confirmed it, but the process to report a bug has too many steps.  I don't have time to do it right now
[18:48] <Steve132> If I describe it here can someone please file it for me?  Making a launchpad, getting verified, and filling out all the forms will take literally an hour and I have stuff to do.
[18:49] <Steve132> The bug is a simple one for the package maintainer
[18:49] <Steve132> basically, I'm debugging an OpenMP program under clang
[18:49] <Steve132> so I installed the debug symbols package
[18:49] <Steve132> associated with libomp5.so
[18:51] <Steve132> So, steps to reproduce:
[18:51] <Steve132> enable debug symbols repository.
[18:51] <Steve132> Then, do
[18:51] <Steve132> sudo apt update
[18:51] <Steve132> sudo apt install libomp-12-dev libomp-12-dev-dbgsym
[18:51] <Steve132> readelf -n /lib/x86_64-linux-libomp5.so
[18:53] <Steve132> It prints "    Build ID: b522429c30828b8de922bc933054ff333681bade"
[18:53] <Steve132> so then if you do
[18:54] <Steve132> apt content libomp-12-dev-dbgsym
[18:55] <Steve132> It shows /usr/lib/debug/.build-id/96/4fcf0bc474e8420b7ea08d320a89f4926a4f01.debug
[18:56] <Steve132> so the hash is wrong because somehow the debug information for the wrong build ID got uploaded.
[18:56] <Steve132> this breaks the debug information for libomp on clang
[18:57] <Steve132> which is a bug.  The whole point of having the debug symbols is that the build ids should match.
[18:58] <Steve132> so debugging information in the binaries can be found.