On Sun, Dec 11, 2005 at 11:26:43AM +0100, Norbert Preining wrote: > Dear all! > > I have a question concerning packages with epoch: We are preparing a NMU > (maintainer approved) for tipa which currently is of version > 2:1.2-2 > When I get the source package via apt-get source tipa and rebuild the > package with > dpkg-buildpackage -us -uc -rfakeroot > I get a binary package called > tipa_1.2-2_all.deb > and not > tipa_2%3a1.2-2_all.deb > > But the internal version number (in the control file) of the package > is correct, as one can see when calling scanpackages I get a correct > entry: > Package: tipa > Version: 2:1.2-2 > > Any suggestions? What is the correct way to build packages with epoch? That is the correct way. Epochs don't show up in a number of places (when they're deemed to be unimportant). Also note that what a file happens to be called has no bearing whatsoever on it's end utility. You could rename a package winword.exe and then run "dpkg -i winword.exe" and it'll install exactly as per normal. <grin> - Matt
Attachment:
signature.asc
Description: Digital signature