On Tue, Jan 19, 2010 at 01:52:50PM -0500, Jameson Rollins wrote:
> On Mon, Jan 18, 2010 at 09:00:07PM +0000, Olly Betts wrote:
> > For 1.0, I build source packages separately with this script in SVN:
> >
> > xapian-maintainer-tools/debian/make-source-package
>
> Hey, Olly. Thanks so much for the info.
>
> Unfortunately this script doesn't work for me.
>
> It uses an svn+ssh SVNROOT which I can't access. I've included a very
> simple patch below that fixes this issue, though.
Oops, yes - that's just using the write-access URL for SVN, and your fix is
the right one.
> The script also assumes that certain tags exist on the svn repo (for
> instance:
> svn://svn.xapian.org/xapian/tags/debian-1.1.3+svn13834-1/xapian-core).
> I'm not sure I understand this, since it seems to require that the
> repo have a debian-specific tag in order to build a deb, which I
> imagine would be cumpersome for testing purposes.
Yeah, I currently tag the files used for a package version before making
the source package, and retag if I need to iterate. It's a little
cumbersome, but does ensure that the exact versions used get tagged.
> dh_install --sourcedir=debian/tmp --fail-missing
> cp: cannot stat `debian/tmp/usr/include/xapian.h': No such file or directory
> dh_install: cp -a debian/tmp/usr/include/xapian.h
> debian/libxapian-dev//usr/include/ returned exit code 1
Oh, 1.1 installs headers to /usr/include/xapian-1.1 instead of /usr/include
(to permit parallel installation). There may be a few other similar issues.
> Any thoughts on how to streamline this for non-maintainers?
Not really sure. Sorting out whatever was stopping pdebuild in a checkout
working would provide one route. Perhaps svn-buildpackage would provide
a good solution, but I've only used it briefly once.
This is a good time to change such things anyway, as we're close to moving to a
new release branch.
Cheers,
Olly
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
