msi chokes on empy substitution instance

Bug #1821031 reported by Ben Franksen on 2019-03-20
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
EPICS Base
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/Epics/sumo/build/BASE/R3-15-6-bessy1+AUTO-003/bin/linux-x86_64/msi -I. -I.. -o runStatGun.db -S../runStatGun.substitutions
msi: Parse error, unexpected '}'
  in substitution file '../runStatGun.substitutions' at line 4:
  }

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.

mdavidsaver (mdavidsaver) wrote :

I've noticed this as well, and used the DUMMY trick. I didn't realize that was a regression.

Changed in epics-base:
status: New → Confirmed
importance: Undecided → Low
Andrew Johnson (anj) wrote :

This is a duplicate bug report, we even have a PR for fixing it...

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers