Compiler error in 6.7.1 against old scripts that have ignoreversion and replacesameversion [Files] flag set

[Gary Cuthbert]

Hello, we have been using v6.2 for a while now to package a couple of established software applications that we release new versions of a couple of times a year and recently noticed the move to a commercial license which we have bought and so are looking to update our build machine with the latest version of InnoSetup. 

The problem i have encountered is that our existing scripts have both 'ignoreversion' and 'replacesameversion' flags set against our [Files] section entries, the 6.7.1 compiler errors on this.

Looking at the help i can understand why these two flags are incompatible but in 6.2 the scripts compiled fine with these set. If we update our build machine we will need to update our scripts across several source control branches that we build from.

So first of all, if we always want to apply the files we are referencing to our installation is  using the 'ingnoreversion' flag is the correct option to go with (fairly sure it is)?

Secondly, I would be interested to know what the behavior was in 6.2 w.r.t to both flags being set, does 'ingoreversion' override any effect of 'replacesameversion'? if so i would be more comfortable in editing the scripts to remove 'replacesameversion' in our older branches.

Thirdly, i have had a look at the release history of v6 and can't see any mention of this change, i could go through the versions to narrow it down but does anyone know when this change in compiler behavior was introduced? 

Many thanks

Gary

[Martijn Laan]

Hi,

Op 12-3-2026 om 11:45 schreef Gary Cuthbert:

So first of all, if we always want to apply the files we are referencing to our installation is  using the 'ingnoreversion' flag is the correct option to go with (fairly sure it is)?

Yes it is.

Secondly, I would be interested to know what the behavior was in 6.2 w.r.t to both flags being set, does 'ingoreversion' override any effect of 'replacesameversion'?

Yes it does.

Thirdly, i have had a look at the release history of v6 and can't see any mention of this change, i could go through the versions to narrow it down but does anyone know when this change in compiler behavior was introduced?

It was introduced by version 6.5.0 and was considered only a minor tweak.

Greetings,
Martijn Laan

[Gary Cuthbert]

Thanks very much!