Actions
Bug #2786
closed
Upgrade script fail with new Technique not in library before migration.
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
We I tried to upgrade, at some point I got the following error message:
fatal: not under version control, source=techniques/fileDistribution/checkGenericFileContent/3.0/policy.xml, destination=techniques/fileDistribution/checkGenericFileContent/3.0/metadata.xml
That seems to be because techniques/fileDistribution/checkGenericFileContent/3.0/policy.xml exists, but that version of the technique is not in git.
So, what seems to happen is that metada to remane are found with a find (or ls or something alike), looking in the FILESYSTEM, and then for each result, a "git mv" (or alike) is made.
We should do is take the file to move from "git ls-files | grep policy.xml".
Updated by Nicolas PERRON over 11 years ago
- Status changed from 2 to Pending technical review
- % Done changed from 0 to 100
Applied in changeset commit:4940d5e0cef79a9ca4a81785fb35f239b718c32e.
Updated by Matthieu CERDA
Updated by Jonathan CLARKE over 11 years ago
- Status changed from Pending technical review to Released
Nice fix. This looks great.
Updated by Nicolas PERRON about 11 years ago
- Project changed from Rudder to 34
- Category deleted (
11)
Updated by Benoît PECCATTE about 9 years ago
- Project changed from 34 to Rudder
- Category set to Packaging
Actions