A BA can override that behavior but I agree the default in the Burn engine
doesn't seem quite right in this case. The patch should be removed. I think
Burn should have enough information to know that it should pull out the
superseded patch in this case. Can you open a bug? If you're interested in
Hi all
I'm trying to set up a patching system using burn. We do cumulative
patching and previously had the msp patches set up to supersede one another.
After installing the main bundle, followed by the patch bundles in sequence
v1.1 => v1.2, I can either keep v1.1 displayed in ARPs updates (new
up
2 matches
Mail list logo
