Actually I have a script that does a CVS checkout from the upstreams CVS repository and creates the upstream tarball... Then it creates the package-version directory and copies the tarball and debian/ stuff over runs through dpkg-source to build the package then updates the pbuilder unstable base.tgz and finally builds... Once built I have it upload to people.d.o and update the Packages.gz file so I can test it on my machines by installing through apt-get... Works rather nice and it almost automatically handles upstream revision changes as well... Makes it really easy to upload the official packages once the code is released as a new version as I've been building nitely from CVS... Jeremy On Sun, Sep 29, 2002 at 10:05:49AM +1000, Brian May wrote: > Hello, > > Has anybody created a script that will > automatically do the following? > > 1. build package with pdebuild. > 2. sign it for uploading to Debian. > 3. upload it to Debian. > > ??? > > Currently, I do each step manually, and this > gets tedious after a while. > > What I would like is a process like that I normally > use without pbuilder: > > dpkg-buildpackage: automatically does 1, and 2, and leaves > result in a known location for the next step. > > debrelease: automatically uploads result to Debian. > > This doesn't appear to be immediately possible with pbuilder, > because pdebuild does not sign the package, put it > in the location expected by debrelease, or even set the > privileges correctly, to allow the non-root user write > access. > > Is this possible? Has anyone written code to do this, > or do I need to do it msyelf? > -- > Brian May <bam@snoopy.apana.org.au> > > > -- > To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Attachment:
pgpdkI0LC_gRD.pgp
Description: PGP signature