When a .cabal file was essentially unchanged, but contained git
conflict markers then hpack did not write a new .cabal file at
all. To address this hpack now unconditionally writes a new .cabal
file when the existing .cabal file contains any git conflict markers.
When a
.cabal
file was essentially unchanged, but contained git conflict markers thenhpack
did not write a new.cabal
file at all. To address thishpack
now unconditionally writes a new.cabal
file when the existing.cabal
file contains any git conflict markers.