Hi, Quoting Ben Finney (2016-04-21 04:17:02) > 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? could you show us the exact sbuild invocation you used in each of the above two cases? Thanks! cheers, josch
Attachment:
signature.asc
Description: signature