Opened 8 years ago

Closed 8 years ago

#40 closed defect (fixed)

Vespa 0.3.2 tag in SVN incorrect

Reported by: flip Owned by: flip
Priority: major Milestone:
Component: subversion Version:
Keywords: Cc: bsoher

Description

I screwed up our SVN tags during the release of 0.3.3. (That was the stealth release that we made available but didn't advertise so that we could do a limited release of the Analysis alpha.) Specifically, I released 0.3.3 but tagged it as 0.3.2.

Since the tag 0.3.2 already existed, I overwrote it or combined 0.3.2 with 0.3.3. (I'm not sure what happened since I don't know what happens when one tells SVN to tag two different revisions with the same tag, but I know the result is not what we want.)

I first created the tag 0_3_2 on 24 Jan 2012 with r3004:
http://scion.duhs.duke.edu/vespa/project/timeline?from=2012-01-24T10%3A50%3A11-05%3A00&precision=second

And I re-created 0_3_2 on 15 Feb 2012 with r3102 that should have created 0_3_3 instead:
http://scion.duhs.duke.edu/vespa/project/timeline?from=2012-02-15T09%3A33%3A03-05%3A00&precision=second

Change History (2)

comment:1 Changed 8 years ago by flip

Fixed in r3339 - 3341. I deleted the current 0_3_2 tag and recreated 0_3_2 and 0_3_3 from the correct revisions using the following commands:

svn rm https://scion.duhs.duke.edu/svn/vespa/tags/0_3_2 \
       -m "Removing broken 0_3_2 tag (see http://scion.duhs.duke.edu/vespa/project/ticket/40)"

svn copy -r 3003                                                  \
       https://scion.duhs.duke.edu/svn/vespa/trunk             \
       https://scion.duhs.duke.edu/svn/vespa/tags/0_3_2      \
    -m "Tag for Vespa version 0.3.2."


svn copy -r 3101                                                  \
       https://scion.duhs.duke.edu/svn/vespa/trunk             \
       https://scion.duhs.duke.edu/svn/vespa/tags/0_3_3      \
    -m "Tag for Vespa version 0.3.3."

comment:2 Changed 8 years ago by flip

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.