Package: src:fakechroot Version: 2.19-3 Severity: serious Hi,
I uploaded jemalloc 5.1.0-2 to unstable the other day. It involves a new ABI and SONAME and thus a transition from libjemalloc1 -> libjemalloc2. I noticed that your package Build-Depends directly on libjemalloc1, and thus this package will start FTBFSing once libjemalloc1 gets removed from the archive. It seems like the B-D is there because the test suite includes a test for jemalloc (which is great!), and specifically the binary library which it's LD_PRELOADing, hence the dependency on the binary package. Rather than s/libjemalloc1/libjemalloc2/, I would recommend to B-D on "libjemalloc-dev" like a regular source package, and then modify the test suite to search for the symlink "libjemalloc.so" (e.g. /usr/lib/x86_64-linux-gnu/libjemalloc.so). This would make it future proof for future ABI/SONAME bumps. Apologies for filing this after the transition has already started -- as a B-D on the binary package is unsual, it didn't occur to me to grep-dctrl for that beforehand. Regards, Faidon
