On Mar 30, 2015, at 6:50 AM, Cyril Brulebois wrote:

> Meaning ~deb7u1 or +deb7u1 for the first upload to wheezy, ~deb7u2 or
> +deb7u2 for the next one; as for jessie, use ~deb8u1 or +deb8u1 for
> the first upload, etc.


I used to do something like that, but because the 'Dailies' is directly
from the git release, git-buildpackage wouldn't create a tar ball that
worked. It refused to create one because there was [to much] difference
between the '.orig.tar.gz' (which was/is based on the 'Released') one
and the code that's in there (in the source directory) now.

This is because all packages is called '0.6.3' as base.

        0.6.3-1~wheezy vs. 0.6.3-40-0f7d2a-wheezy

Although the latter one is 'almost 0.6.4'… So from this, and from what
is the Debian GNU/Linux packaging standards (what I remember from it :),
it looks like the latter one only have Debian GNU/Linux updates, not
source. Which isn't the case...


In the Dailies this is not a problem (to have the tilde), because that
really is a correct, new source. But I should probably change that to,
just for consistency...

Also, S3 can't handle '+' in the filename, so I have to remember to
make hard links (or copies) of the file, but with a space instead of
a +! And most of the times I forgot about that, so...


Also, because the 'Dailies' for Wheezy and Jessie are _identical_
(down to the last byte - source vise at least, including the debian
directory), I thought it was smarter to use the original suggestion -
'nothing is higher than something'…

So having two different versions (after the ~ or +), doesn't make much
sense - they indicate that there's a difference between the packages.
Which was my first mistake - I started counting from the one for the
first version I created on each platform and that, in part, gave me this
problem in the first place - if I hadn't, maybe I would have discovered
the problem earlier…


The original suggestion takes all that into account - 

        * it makes it easier to see that the packages are identical,
        * there's no plus to screw up S3,
        * there's no tilde to mess with the 'orig.tar.gz' file and
        * the upgrade path works.

The only downside is that I can't easily find only Jessie packages with
a simple find in my repository :). But I can live with that, there's
other ways to find that out (that are only slightly more time consuming :D



But I thank everyone for their suggestion. I really DO appreciate it!
But for me the case is closed :).
--
Life sucks and then you die

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

Reply via email to