Command: cat /mnt/p3/home/build-debian-stuff/dpkg-buildpkg-info ## 2007/05/17 ## SYNOPSIS 'dpkg-buildpackage' , 'dpkg-genchanges' , 'debsign' instructions (and 'debsign' for gpg package signing) working with source (orig.tar.gz) (using/creating .diff.gz, .dsc, .changes files) how to create a diff.gz out of an orig and changed version of a package? dutchfish: you have an unpacked version of the source tree that you've been hacking in? and you have the orig.tar.gz in the parent directory? then just call dpkg-buildpackage -us -uc -S peterS, how to resign it? peterS, with my own gpg dutchfish: well, if you omit the -us -uc then it will sign the source and changes files. alternatively you can use 'debsign' from the devscripts package, after the fact dutchfish: if you want dpkg-buildpackage to know the right key to sign it with, you'll have to change the 'Maintainer' field in debian/control to the same name/address that your gpg key advertises dutchfish: though debsign has an option for signing with any given key peterS, ok, the rest i figure out, thx very much peterS, if i understand it right, i just recreate changes with orig as reference, and sign it myself as package-mantainer, there are no changes on changes? dutchfish: use 'dpkg-buildpackage -S' calls 'dpkg-source' to actually build the .diff.gz and .dsc files, and dpkg-genchanges to generate the .changes file. the .dsc and .changes files need to be gpg-signed if you want to upload to Debian dutchfish: if you want to sign the .dsc and .changes files as they are built, you just call dpkg-buildpackage -S. if you want to sign them separately (for example, with a different key than is mentioned in the Maintainers line of debian/control), you pass -us -uc to dpkg-buildpackage so it doesn't sign, then later you can call debsign with the .changes file peterS, i am not ready for that, because i am not a mantainer, but want a quick fix wich i can distrubute to my own repos, its a sec fix for curent apache in etch