I am trying to build a source package with Debian revision -2 and
thus no orig.tar.gz. At first, sbuild complained:

  Automatic build of molly-guard_0.4.4-2 on pulse by sbuild/amd64 0.57.0
  Build started at 20080701-1530
  ******************************************************************************
  /usr/bin/md5sum: ./molly-guard_0.4.4.orig.tar.gz: No such file or directory
  Checking available source versions...
  E: You must put some 'source' URIs in your sources.list
  /usr/bin/apt-cache returned no information about molly-guard source
  Are there any deb-src lines in your /etc/apt/sources.list?

After I put in the line and ran the upgrade, I get

  Automatic build of molly-guard_0.4.4-2 on pulse by sbuild/amd64 0.57.0
  Build started at 20080701-1533
  ******************************************************************************
  /usr/bin/md5sum: ./molly-guard_0.4.4.orig.tar.gz: No such file or directory
  Checking available source versions...
  Checking available source versions...
  Can't find source for molly-guard_0.4.4-2
  (only different version(s) molly-guard 0.4.4-1 found)

It's looking for the wrong thing and thus fails.

  apt-get --tar-only source molly-guard

would have obtained the file...

Sorry for the long delay.

What command did you use to build?  I only see the log output above.

Did you have all of the source files in the working directory (or
whichever directory the .dsc was in)?  If working locally (rather
than from a mirror), you do need to .dsc, .diff.gz and .orig.tar.gz
(or the dpkg-source v3 equivalents); sbuild and/or apt-get aren't
clever enough to get some locally and some remote e.g. .dsc/.diff.gz
locally and the .orig from a mirror).

If it was all on the mirror, is it possible the mirror was out of
sync?

Does "sbuild -A -d unstable molly-guard_0.4.4-2" do the right thing?
It works for me (see attached).



Thanks,
Roger

also sprach Roger Leigh <rleigh@codelibre.net> [2010.10.31.2229 +0100]:

I think this is the problem and shortcoming. If I generate
a *_source.changes file for a -2 package, the orig tarball will not
be included, nor will the .dsc file reference it — *because* it is
assumed to be publicly available.

sbuild can install build-dependencies, so it already interacts with
an APT mirror. Wouldn't it make sense and be possible for it to also
install missing source package components, or at least to try?

Hi,

this could be done but what is your usecase? In which situation would you have
a source-only .changes file but *not* the original source tarball around?

Thanks!

cheers, josch