MJ Ray wrote:
Ow. That does far too much as root for my liking.
I only used it as a guide, to be fair, but even then most was done as root (via sudo). But then it was done in a virtual machine, partly for that reason.
Also, if you give -uc -us flags to dpkg-buildpackage, it won't try to sign things, so won't complain if it can't. Putting stuff like "ignore this message" in a HOWTO makes me think its author hasn't spent much time testing and bugfixing it.
Fair comment - and this is often the case with HowTos. There's a lot in building a Postfix-based mail server that I find hard to understand[*] (I have books on order but they've not arrived yet), and what I really want is a HowAndWhyTo not just a HowTo.
[*] Not because its complicated, but because the documentation is sparse and scattered. It might also turn out to be complicated once I've learnt enough to know :-)
dpkg -i postfix_2.3.8-1_i386.deb perhaps?
Sounds obvious now... but then I'm something of a dpkg virgin so I'm picking things up as I go.
You probably want to call your package 2.3.8-1quarella1 or something, instead of 2, to avoid it conflicting with repository packages. I think some flags to the "dch" command will do that for you, but I forget what they are and I'm rushing, sorry.
Agreed, but I couldn't see where that was set. I guess -2 was just the default? Brett's comments regarding dch (with a sprinkle of Google no doubt) will help me there too.
Returning to your original question: [...]
Well, I'd use cowbuilder and maybe an IP alias to try it in a chroot, instead of building a whole VM. My notes on cowbuilder are http://mjr.towers.org.uk/blog/2007/debian#packaging and I think it's getting pretty common among DDs, so maybe others can offer better tips.
Thanks for that, I'll take a look.
Mark Rogers