[Gnu-arch-users] possible bug with version number sorting

[Mirian Crzig Lennox]

I have encountered some perplexing behaviour in the way that tla
decides which version on a branch is the most recent.

In a particular category (call it "foo"), I have the following
versions:

        foo--devel--0.1
        foo--devel--0.1.1
        foo--devel--0.1.2
        foo--devel--0.1.3
        foo--devel--0.1.4

The original version was foo--devel--0.1, the others are related as
so:

        tla tag foo--devel--0.1--patch-6 foo--devel--0.1.1
        tla tag foo--devel--0.1.1--patch-2 foo--devel--0.1.2
        tla tag foo--devel--0.1.2--patch-4 foo--devel--0.1.3
        tla tag foo--devel--0.1.3--patch-11 foo--devel--0.1.4

I then wanted to get the latest development sources
(foo--devel--0.1.4--patch-7); I assumed I simply do:

        tla get foo--devel

But, to my surprise, I got moo--cosmic-devel--0.1--patch-6 instead.
This was with (tla--devo--1.1--patch-237).  I'm hoping that this is
not intentional, because it certainly runs counter to the way people
commonly arrange version numbers (e.g., gcc-3.2 < gcc-3.2.1,
FreeBSD-4.6 < FreeBSD-4.6.2, openssh-3.7 < openssh-3.7.1, etc.)

cheers,
Mirian