>>>>> "Axel" == Axel Beckert <a...@debian.org> writes:
Axel> Control: forcemerge 509100 -1 Hi,
Axel> Yeah, this is a long-standing and known issue in aptitude.
I'd ask the aptitude developers to consider whether this issue should be
reprioritized as important rather than normal.
Here's my rationale.
Last year, we decided that the recommended way to build most packages is
to use debhelper.
The recommended way to describe a debhelper compatibility level is a
dependency of the form
debhelper-compat (= 13)
That is, a dependency on a versioned virtual package.
So, aptitude build-dep is not able to process build dependencies on the
recommended way of describing Debian source packages.
As more and more packages adopt this recommended approach aptitude
build-dep is going to become more and more useless.
Even if you are not able to fix the problem promptly, would it be
possible to detect detect that this situation is happening in the
build-dep path and recommend using a different resolver?
--Sam
