Project

General

Profile

Bug #3431

addpkg_svn detect version

Added by Jan Zirnstein almost 7 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Start date:
02/05/2013
Due date:
% Done:

0%

Estimated time:
1.00 h
Duration:

Description

addpkg_svn has a mode of operation where no version of the package to be added has to be specified and is figured out on the fly. This does not work correctly. For example when I've sourced development at FNAL and done an srt_setup -a in my test release ($SRT_PUBLIC_CONTEXT=/grid/fermiapp/nova/novaart/novasvn/releases/development, $CVSROOT=svn+ssh:///cvs/projects/novaart/pkgs.svn)

addpkg_svn setup

Release development uses setup version lrwxrwxrwx 1 novasoft nova 11 Dec 20 01:56 /grid/fermiapp/nova/novaart/novasvn/releases/development/setup -> ../../setup, will check that out
Adding package "setup" to ".".
svn co svn+ssh:///cvs/projects/novaart/pkgs.svn/tags/lrwxrwxrwx 1 novasoft nova 11 Dec 20 01:56 /grid/fermiapp/nova/novaart/novasvn/releases/development/setup -> ../../setup//setup setup
svn: invalid option character: >
Type 'svn help' for usage.
svn checkout failed.
addpkg failed.

History

#1 Updated by Kanika Sachdev over 5 years ago

  • Status changed from New to Closed

Committed revision 10234 of addpkg_svn, that correctly parses "svn info" on $SRT_DIST/releases/$SRT_BASE_RELEASE/$package and checks that version out.

#2 Updated by Kanika Sachdev over 5 years ago

But obviously this won't work for tags before now since the you'd be using the version of addpkg_svn in $SRT_PUBLIC_CONTEXT, and not the one in head :(

So you would have to specify the tag before this date, so do "addpkg_svn package_name tag_name", whereas, here on, you can just do "addpkg_svn package_name" and it will automatically figure out what to checkout.



Also available in: Atom PDF