Hi,

if the Source: field contains a version, then the generated
debian/changelog will contain two versions, the source and the binary
version. This will let dpkg-parsechangelog fail. For an example of a
package with a versioned source dependency look at gfortran for example.

cheers, josch

Hi,

an example consider this control file:

Package: foo
Source: bar (= 1.0)
Version: 1.0
Architecture: amd64

Then you will get:

$ equivs-build control
dh_testdir
dh_testroot
dh_prep
dh_testdir
dh_testroot
dh_install
dh_installdocs
dh_installchangelogs
parsechangelog/debian: warning:     debian/changelog(l1): badly formatted heading line
LINE: bar (= 1.0) (1.0) unstable; urgency=low
parsechangelog/debian: warning:     debian/changelog(l2): found blank line where expected first heading
parsechangelog/debian: warning:     debian/changelog(l3): found change data where expected first heading
LINE:   * First version
parsechangelog/debian: error: Can't call method "as_string" on an undefined value at /usr/share/perl5/Dpkg/Changelog.pm line 250.

dpkg-parsechangelog: error: changelog parser /usr/lib/dpkg/parsechangelog/debian gave error exit status 255
dh_installchangelogs: changelog parse failure
debian/rules:20: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 255
Error in the build process: exit status 2