[Pkg-alsa-devel] Re: ALSA packager needed

Thomas Hood jdthood at yahoo.co.uk
Sat Dec 17 21:22:52 UTC 2005


Hi.

First, please subscribe to the pkg-alsa-devel mailing list at alioth.

    http://lists.alioth.debian.org/mailman/listinfo/pkg-alsa-devel

OK, let's get right down to details.  :)


Elimar Riesebieter wrote:
> $apt-get source alsa-driver


The Debian packaging for the ALSA packages is in svn at alioth so we can replace
this with

    $ cd ~/src/pkg-alsa/svn-pkg-alsa/trunk
    $ svn up

Originally I did:

    $ cd ~/src/pkg-alsa/
    $ svn co svn+ssh://jdthood-guest@svn.debian.org/svn/pkg-alsa/trunk svn-pkg-alsa/trunk

but this should also work:

    $ svn co svn://anonymous@svn.debian.org/svn/pkg-alsa/trunk svn-pkg-alsa/trunk

I am using the path whither I checked out the sources.  You can use some other
path, of course.


> $wget ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.11rc1.tar.bz2
> $tar -xjf alsa-driver-1.0.11rc1.tar.bz2
> $mv alsa-driver-1.0.11rc1/ alsa-driver-1.0.10+1.0.11rc1
> $tar -czf alsa-driver_1.0.10+1.0.11rc1.orig.tar.gz alsa-driver-1.0.10+1.0.11rc1/


Yes.  Now, since we are using svn we can make use of svn-buildpackage.  So we
put the tarball in the tarballs directory.

    $ mv alsa-driver_1.0.10+1.0.11rc1.orig.tar.gz ~/src/pkg-alsa/svn-pkg-alsa/tarballs

Jordi and I do not check these tarballs into svn.


> $cd alsa-driver-1.0.10+1.0.11rc1
> $cp -a ../alsa-driver-1.0.10/debian .


Instead of this we can do:

   $ cd ~/src/pkg-alsa/svn-pkg-alsa/trunk/alsa-driver


> $dch -i
> $head -7 debian/changelog
> alsa-driver (1.0.10+1.0.11rc1-1) experimental; urgency=low
>
>   * New upstream release candidate
>
>  -- Elimar Riesebieter <riesebie at lxtec.de>  Sat, 17 Dec 2005 18:32:40 +0100


Yes.


> alsa-driver (1.0.10-3) unstable; urgency=low
> $ debuild


Instead of this we can do:

    $ svn-buildpackage -rfakeroot

I have this svn-buildpackage configuration file:

    $ cat .svn-buildpackage.conf
    svn-builder=debuild
    svn-dont-purge

Here is my deb-layout file.  The debs will get built in the buildArea.

    .../svn-pkg-alsa/trunk/alsa-driver$ cat .svn/deb-layout
    buildArea=/home/jdthood/src/pkg-alsa/svn-pkg-alsa/trunk/build-area
    origDir=/home/jdthood/src/pkg-alsa/svn-pkg-alsa/tarballs
    trunkDir=/home/jdthood/src/pkg-alsa/svn-pkg-alsa/trunk/alsa-driver
    trunkUrl=svn+ssh://jdthood-guest@svn.debian.org/svn/pkg-alsa/trunk/alsa-driver

Note that the mergeWithUpstream property has to be set on trunk/alsa-driver/debian
in order for svn-buildpackage to merge the latter with the tarball.


> # Is ther an easy way to check the patches?


I just watch the build and see if dpatch fails.


> # There is no md5sum or similar at ftp://ftp.alsa-project.org/pub/driver/ ?


That would be nice.


> # If debuildrun is ready upload the package to my repos where a DD
> # can pick and load it up


Now the beauty of svn is that you can just make changes to the debian/ tree
and check them in.  Then the DD (Jordi Mallach) can svn-up and build the
package himself when it's ready for uploading.

We still have to talk about what needs to be done to the debian/ tree with
each release.  Please read the NOTES file in alsa-driver/debian.
-- 
Thomas Hood



More information about the Pkg-alsa-devel mailing list