Bug#1061618: src:haskell-misfortune: unsatisfied build dependency in testing: libghc-regex-pcre-doc
On 07/03/2024 19:43, Peter Green wrote: In raspbian, I removed the reference from misfortune.cabel, removed the build-dependencies on libghc-regex-pcre* and also (for unrelated reasons) removed the build-dependency on ghc-doc. After doing so I was able to successfully build the package. Scratch that, I thought the build had finished, but it hadn't. It did in fact fail. The reference in the code to PCRE was in all caps which is why my grep did not find it.
Bug#1061618: src:haskell-misfortune: unsatisfied build dependency in testing: libghc-regex-pcre-doc
Can you please investigate the situation and figure out how to resolve it? I'm no haskell expert, but to me the dependency looks vestigal. Grepping the source tree for "pcre" finds a mention in the misfortune.cabal file but no mentions in the actual code, and there are no corresponding binary dependencies. In raspbian, I removed the reference from misfortune.cabel, removed the build-dependencies on libghc-regex-pcre* and also (for unrelated reasons) removed the build-dependency on ghc-doc. After doing so I was able to successfully build the package.
Bug#1061618: src:haskell-misfortune: unsatisfied build dependency in testing: libghc-regex-pcre-doc
Source: haskell-misfortune Version: 0.1.2.1-3 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed from testing, but unfortunately there are multiple scenarios where that can happen nevertheless. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. Can you please investigate the situation and figure out how to resolve it? Regularly, if the build dependency is available in unstable, helping the maintainer of your Build-Depends to enable migration to testing is a great way to solve the issue. If your build dependency is gone from unstable and testing, you'll have to fix the build process in some other way. Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html OpenPGP_signature.asc Description: OpenPGP digital signature