[lsst-dm-stack-users] eups : update a version tag after only a packaging update

[Fabrice Jammes]

Hello K.T.,

Here's what i've runned, in order to tag Andy last version of apr :

fjammes at clrlsstwn02-vm:~/src/qserv-packager/dist/dependencies/ (master) 
$ git clone ssh://git@dev.lsstcorp.org/LSST/external/apr.git
fjammes at clrlsstwn02-vm:~/src/qserv-packager/dist/dependencies/ (master) 
$ cd apr
fjammes at clrlsstwn02-vm:~/src/qserv-packager/dist/dependencies/ (master) 
$ VERSION=1.3.3+1
fjammes at clrlsstwn02-vm:~/src/qserv-packager/dist/dependencies/ (master) 
$ git tag -u fabrice.jammes -f -a -m "Version $VERSION" -s $VERSION; git 
push origin master -f --tags
fjammes at clrlsstwn02-vm:~/src/qserv-packager/dist/dependencies/apr 
(master) $ git tag
1.3.3
1.3.3+1

Same thing has been done for apr_util.

And then on the distribution server :

[fjammes at lsst-dev lsstsw-dev]$ rebuild log4cxx
              log4cxx:  ok (0.8 sec).
                  apr:  ok (0.7 sec).
             apr_util:  ok (0.8 sec).
# BUILD ID: b77
                  apr: 1.3.31 ......ok (25.9 sec).
             apr_util: 1.3.41 ok (8.7 sec).
              log4cxx: 0.10.0+1 ..........ok (36.3 sec).
# BUILD b77 completed.

[fjammes at lsst-dev lsstsw-dev]$ eups list apr
    1.3.31         b77
    master-g3d6a37172a     b71
    u.salnikov.DM-862-g8b50ccce77     b70

As you can see 1.3.3+1 as becomed 1.3.31, is it normal ?

Thanks,

Fabrice

On 07/02/2014 11:27 PM, Kian-Tat Lim wrote:
> Fabrice,
>
>> In order to build apr-1.3.3 as a dynamic library instead of a static
>> one, the build procedure parameters were updated in eupspkg.cfg.sh.
>> Nevertheless, it's always the same apr version which is distributed,
>> and we can't force update the 1.3.3 git tag.
>> Is there a standard LSST way to name tag for this kind of update ?
> 	1.3.3+1.
>