Ralf Stubner <[EMAIL PROTECTED]> wrote: > Frank Küster wrote: >> Ralf Stubner <[EMAIL PROTECTED]> wrote: >> >>> As one can see, I don't know yet how to build a sarge backport with >>> svn-buildpackage. >> >> Me neither, I generate the source package "by hand" from a copy of the >> tree. What's the problem? Are you trying to build the debs on your >> system, or in a pbuilder?P > > I was only refering to the missing README.sarge. Up to now I have build > the debs directly on my system, but I am investigating whether pbuilder > or a dedicated chroot would be better.
Oh, that one (and the version number and possible patches in the future). You have to run "fakeroot debian/rules sarge" before creating the source package. If we want to do this with svn-buildpackage, we would probably need a branch for sarge that differs only in that one command, but has to be kept synchrone to the main branch continuously. I don't think that this is worth it. > I am not quite sure what the correct format should be. Something like this? > > -------------------------------------- > tetex-bin (3.0-7.1) UNRELEASED; urgency=low > > * install the links to omfonts and clean up the manpage and format links > (closes: #327129) [stubner] > > -- Frank Küster <[EMAIL PROTECTED]> <current date> > -------------------------------------- If you use Emacs, you can simply use the built-in functions; I don't mind if your name and e-mail ends up in the "signature", since for an upload I need to change version and release anyway. Regards, Frank -- Frank Küster Inst. f. Biochemie der Univ. Zürich Debian Developer
