Can you provide the logs? The change in SLING-6392 will always log in case it changes something (see https://svn.apache.org/viewvc/sling/trunk/installer/core/src/main/java/org/apache/sling/installer/core/impl/PersistentResourceList.java?r1=1765129&r2=1783196&pathrev=1783196). So I am wondering which package is actually detected as stale? The according log entry should start with "Removing stale resource ..." Thanks, Konrad
> On 17 Feb 2017, at 13:04, Dominik Süß <dominik.su...@gmail.com> wrote: > > Reverting to -1. Subsequential integration testing on product on top of > this did show that SLING-6392 does fail with content-packages that > partially end up uninstalled instead of installed. > > Reverting SLING-6392 only including SLING-5457 succeeds. > > On Fri, Feb 17, 2017 at 1:00 PM, Stefan Seifert <sseif...@pro-vision.de> > wrote: > >> +1 >> >>