[pkg-nvidia-devel] packaging team

[Randall Donald]

On Mon, 2010-03-29 at 11:00 -0700, Russ Allbery wrote:
> Randall Donald <randy at khensu.org> writes:
> 

> Are there already instructions somewhere about the process used to update
> to a new upstream release?  I know that upstream's packaging is a bit
> weird.
> 

Here are the basic steps from my memory using svn-buildpackage.
- First set up a svn working directory and checkout svn
+ssh://svn.debian.org/svn/pkg-nvidia/packages/nvidia-graphics-drivers/trunk nvidia-graphics-drivers


- Download the pkg0 for i386 and pkg2 for amd64. The pkg2 has the ia32
libs in it. 
- mkdir nvidia-graphics-drivers-190.53.orig 
- place pkg files in nvidia-graphics-drivers-190.53.orig 
- chmod 755 the files
- mkdir tarballs
- tar czvf nvidia-graphics-drivers_190.53.orig.tar.gz
nvidia-graphics-drivers-190.53.orig

- cd nvidia-graphics-drivers
- edit debian/upstream_info
- change RELEASE and NEXTVER variables
- edit the conftest.h file if necessary for kernel compatibility
- fix bugs!
- create a new changelog entry as usual.
- svn ci -m "preparing 190.53-2"  or something suitable
- test build with svn-buildpackage -rfakeroot -us -uc --svn-ignore
--svn-noautodch  ( i have this aliased as svn-b)
- if all ok, run svn-buildpackage -rfakeroot --svn-tag --svn-noautodch
--svn-dont-purge
The dont-purge option is for building the other architecture. E.g. I
have an amd64 system after I have built the amd64 packages I enter the
directory under build-area, run a fakeroot debian/rules clean, then
schroot to do a dpkg-buildpackage -b -rfakeroot
- Then upload!

Something is probably missing or not quite right and it probably could
be simpler but it is the way I learnt to do it.




-- 
--------------------------------------------
Randall Donald             randy at khensu.org
http://www.khensu.org    rdonald at debian.org
Programmer/Debian Developer GnuPG: 6C27DEAB
--------------------------------------------