msi chokes on empy substitution instance
Bug #1821031 reported by
Ben Franksen
This bug report is a duplicate of:
Bug #1810946: MSI doesn't handle empty substitution patterns correctly.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
EPICS Base |
Confirmed
|
Low
|
Unassigned |
Bug Description
I have this in a substitution file:
file runStatGunDmux.vdb {
{}
}
Used to work with (our heavily patched version of) msi with 3.14.x but the msi in base-3.15.6 doesn't like it:
/srv/csr/
msi: Parse error, unexpected '}'
in substitution file '../runStatGun.
}
I would try and locate where the two versions differ but the msi in 3.15 has diverged so much from the old msi-1.5 (on which our version was based) that diffing is useless.
It works if I add a DUMMY="" definition to the instance.
To post a comment you must log in.
I've noticed this as well, and used the DUMMY trick. I didn't realize that was a regression.