Hi! On Mon, 2022-09-12 at 07:50:51 +0200, Fab Stz wrote: > Package: dpkg > Version: 1.20.12 > Severity: normal
> * What led up to the situation? > > Have a package for which in debian/control there is this: > > Build-Depends: debhelper-compat (= 13), > android-sdk-build-tools > <pkg.qt-android-6.4.armeabi-v7a pkg.qt-android-6.4.systemsdk> > <pkg.qt-android-6.4.arm64-v8a pkg.qt-android-6.4.systemsdk> > <pkg.qt-android-6.4.x86 pkg.qt-android-6.4.systemsdk> > <pkg.qt-android-6.4.x86_64 pkg.qt-android-6.4.systemsdk>, > > Note the fact that the build profiles are on several lines, and not on the > same line as the package name. > * What was the outcome of this action? > > .dsc then contains a faulty profile. Note the "<<" and ">>" in the line. > > Build-Depends: debhelper-compat (= 13), android-sdk-build-tools <<pkg.qt- > android-6.4.armeabi-v7a pkg.qt-android-6.4.systemsdk> <pkg.qt- > android-6.4.arm64-v8a pkg.qt-android-6.4.systemsdk> <pkg.qt-android-6.4.x86 > pkg.qt-android-6.4.systemsdk> <pkg.qt-android-6.4.x86_64 pkg.qt- > android-6.4.systemsdk>> I've fixed this now locally, by converting the field values to a single line before parsing, and will be part of my next push targeting 1.21.10. > This value is not correct and makes other tools fail: > - `dpkg-source -b` will report > E: Problem parsing dependency: Build-Depends That's not an error message from dpkg-source, I'd assume that's apt complaining. Thanks, Guillem
