sbuild “Failed to fetch source files”
Howdy all,
I am using ‘sbuild(1)’ successfully for some packages. For one package,
though, I'm getting an error I don't understand: The source package is
not found by Sbuild.
One version finds the source package correctly:
=====
+==============================================================================+
| python-coverage 3.7.1+dfsg.1-1 (amd64) 21 Apr 2016 11:29 |
+==============================================================================+
Package: python-coverage
Version: 3.7.1+dfsg.1-1
Source Version: 3.7.1+dfsg.1-1
[…]
+------------------------------------------------------------------------------+
| Fetch source files |
+------------------------------------------------------------------------------+
Local sources
-------------
/home/bignose/Projects/debian/python-coverage/build-area/python-coverage/python-coverage_3.7.1+dfsg.1-1.dsc exists in /home/bignose/Projects/debian/python-coverage/build-area/python-coverage; copying to chroot
[…]
=====
When I try another version, Sbuild apparently can't find the source package:
=====
+==============================================================================+
| ./python-coverage 4.0.3+dfsg.1-1 (amd64) 21 Apr 2016 11:10 |
+==============================================================================+
Package: ./python-coverage
Version: 4.0.3+dfsg.1-1
Source Version: 4.0.3+dfsg.1-1
[…]
+------------------------------------------------------------------------------+
| Fetch source files |
+------------------------------------------------------------------------------+
Check APT
---------
Checking available source versions...
W: Unable to locate package ./python-coverage
apt-cache returned no information about ./python-coverage source
Are there any deb-src lines in your /etc/apt/sources.list?
[…]
=====
Why does it need to check APT, when the source package is all local to
the source control file?
Both source packages extract just fine:
=====
$ outdir=$(mktemp -t -d)
$ package_name=python-coverage
$ package_version=3.7.1+dfsg.1-1
$ dpkg-source --extract ../build-area/${package_name}/${package_name}_${package_version}.dsc $outdir/${package_name}-${package_version}/
dpkg-source: warning: extracting unsigned source package (../build-area/python-coverage/python-coverage_3.7.1+dfsg.1-1.dsc)
dpkg-source: info: extracting python-coverage in /tmp/tmp.XbUdOVqBzy/python-coverage-3.7.1+dfsg.1-1
dpkg-source: info: unpacking python-coverage_3.7.1+dfsg.1.orig.tar.gz
dpkg-source: info: unpacking python-coverage_3.7.1+dfsg.1-1.debian.tar.xz
dpkg-source: info: applying 01.omit-resource-files-from-distutils-setup.patch
dpkg-source: info: applying 02.rename-public-programs.patch
$ package_version=4.0.3+dfsg.1-1
$ dpkg-source --extract ../build-area/${package_name}/${package_name}_${package_version}.dsc $outdir/${package_name}-${package_version}/
dpkg-source: warning: extracting unsigned source package (../build-area/python-coverage/python-coverage_4.0.3+dfsg.1-1.dsc)
dpkg-source: info: extracting python-coverage in /tmp/tmp.XbUdOVqBzy/python-coverage-4.0.3+dfsg.1-1
dpkg-source: info: unpacking python-coverage_4.0.3+dfsg.1.orig.tar.gz
dpkg-source: info: unpacking python-coverage_4.0.3+dfsg.1-1.debian.tar.xz
dpkg-source: info: applying 01.omit-resource-files-from-distutils-setup.patch
dpkg-source: info: applying 02.rename-public-programs.patch
=====
So if both source packages are readily useable from the same location as
the source control file, why does only one of them work within the
Sbuild run?
--
\ “Compulsory unification of opinion achieves only the unanimity |
`\ of the graveyard.” —Justice Roberts in 319 U.S. 624 (1943) |
_o__) |
Ben Finney
Reply to: