Project

General

Profile

Necessary Maintenance #7009

Repair required to art repository.

Added by Christopher Green about 6 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Immediate
Category:
User Code
Target version:
Start date:
09/15/2014
Due date:
% Done:

100%

Estimated time:
Spent time:
Scope:
Internal
Experiment:
-
SSI Package:
Duration:

Description

On Friday morning, at around 11:14 CDT, an erroneous merge with the master branch was pushed to the development branch of the art repository on cdcvs.fnal.gov. While no code changes were carried with this commit, it has the effect of making the repository's history much harder to read and understand going forward, and for this reason we will be removing this commit from the central repository. If you have a local clone of the repository via any method (e.g. http or ssh), please for each clone:

  1. Make a tarfile backup with (e.g.):
    ( cd .. ; tar jcf <tarfile> <lcoal-repo-name> )
  2. If you have not pulled or fetched origin/develop from cdcvs.fnal.gov, then please refrain from doing so until you have been given the all-clear. This is the only action required of you in this case.
  3. If you have, or you think you may have, any local branches with the bad merge in the tree (including develop), you may check with the following command:
    git rev-list <branch> | grep 76047bbc39d714ac2f99d645ac420ef0c914f63d
  4. For each branch for which the previous command returns success (i.e. has the offending merge):
    1. Commit any local changes you wish to preserve. This includes anything you currently have stashed, since the stash will also be no good after the repair has been made.
    2. Then, execute the following command to preserve your changes:
      git checkout <branch>
      git format-patch --stdout <first-good-sha1>..<last-good-sha1> > <branch>-rescue.txt
      Note the literal .. separating the two SHA1s. git log or gitk can help you decide which commits you need to keep.
  5. Update the metadata for the origin/develop branch in your local repository:
    git fetch origin
  6. For each branch identified by step (2), when and only when you receive the all clear that the repair has been made:
    git checkout master
    git branch -D <branch>
    git checkout -b <branch> origin/develop
    # If you have a saved patch:
    git am <branch>-rescue.txt

As of right now, there are no published feature branches which include the bad merge commit, so no-one should have to deal with that eventuality.

History

#1 Updated by Christopher Green about 6 years ago

  • Description updated (diff)

#2 Updated by Christopher Green about 6 years ago

  • Description updated (diff)
  • Status changed from Assigned to Resolved
  • Target version set to 1.12.00
  • % Done changed from 0 to 100

#3 Updated by Christopher Green about 6 years ago

  • Description updated (diff)

#4 Updated by Christopher Green about 6 years ago

  • Description updated (diff)

#5 Updated by Christopher Green over 5 years ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF