Re: autotools.mk

[Scott Christley <schristley@mac.com>]

On Apr 24, 2010, at 9:06 PM, Steve M. Robbins wrote:

> On Sat, Apr 24, 2010 at 11:14:31AM -0700, Scott Christley wrote:
> 
>> Then when I use the svn-b alias (svn-buildpackage -us -uc -rfakeroot --svn-ignore) the output is this:
> 
>> chmod a+x /home/scottc/Projects/tools/debian-med/trunk/packages/swarm/build-area/libswarm-2.3.0/./configure
>> chmod: cannot access `/home/scottc/Projects/tools/debian-med/trunk/packages/swarm/build-area/libswarm-2.3.0/./configure': No such file or directory
>> make: *** [config.status] Error 1
>> dpkg-buildpackage: failure: debian/rules build gave error exit status 2
>> Command dpkg-buildpackage -us -uc -rfakeroot failed in <unknown>, how to continue now? [Qri?]: Aborting.
>> 
>> 
>> 
>> I'm still clueless.  Anybody have hints on how to debug?  The build process is still a big black box to me.
>> 
>> I did discover the --dont-purge option for svn-buildpackage, it seems to confirm my idea that the source code is not being copied into the build area.
>> 
> 
> If that's the case, it has nothing to do with autotools.mk.  Likely
> something is wrong with the subversion repository.  Try
> "svn-buildpackage --svn-export" then look in build-area to see what is
> being prepared.
> 
> My guess is that one of two things are missing:
> 
> 1. the .orig.tar.gz file must be in directory "tarballs", sibling to "trunk"


> 2. svn propset mergeWithUpstream 1 trunk/debian

Mystery solved!  Thank you!  Previously I had worked with an already existing package, but this is a new package and was missing that crucial bit to set the svn property.

thanks
Scott