Project

General

Profile

Actions
Copy link

Bug #2786

closed

Upgrade script fail with new Technique not in library before migration.

Added by François ARMAND over 11 years ago. Updated about 9 years ago.

Status:
Released
Priority:
2
Assignee:
Nicolas PERRON
Category:
Packaging
Target version:
2.4.0~beta3
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".

Actions
Copy link

Also available in: Atom PDF