[pkg-firebird-general] Building firebird on etch

[Steffen Heil]

Hi

> > But next version in unstable should then be 
> 2.0.1.12855.ds1-8, which 
> > in my understanding is HIGHER then my version...
> > Anything wrong with this?
> 
> There is no -8 version yet :)

As there is no version more recent than my one, so this should be correct.

> If you want to handle upgrades manually, you may use whatever 
> version suits you. My recommendation was about keeping 
> upgrade paths clean.

I will, if I understand this. Right now, I obviously don't.

Actually, I really would like to do it "correctly", but I also see, that
there will never be firebird2.0 in etch, so this should not be a problem.
What 'should' I use? What's the advantage to use ~something instead of
+something?

> > So, last point, how can I sign those packets?
> 
> Invoke "debsign" from within the build tree (or give it the 
> path to the .changes file).
> 
> > And if I may ask totally off-topic, how can I sign an artibrary 
> > deb-file (even if there is no .dsc or .changes - in the case of 
> > make-jpkg)?
> 
> In Debian-speak, you can "sign" only .changes and .dsc, not .deb's.
> dpkg-genchanges and dpkg-source may be of some help in 
> generating these.

Thanks for these information, however I first found a way to tell make-jpkg
to create a changes file AND I also just figured out, that for my purposes
signing the repository is enough, the enclosed deb's don't have to be
signed.

Regards,
  Steffen
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3109 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-firebird-general/attachments/20070605/ac1df25a/attachment.bin