sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Karl Pauls <karlpa...@gmail.com>
Subject Re: [VOTE][CANCEL] Release Apache Sling Installer Core version 3.8.4
Date Fri, 17 Feb 2017 12:16:56 GMT
Yeah, this is not good. I'll herby cancel this release.

I will rollback the commit in question, reopen the original issue, and
cut a new release candidate without this change for now.

regards,

Karl

On Fri, Feb 17, 2017 at 1:11 PM, Dominik Süß <dominik.suess@gmail.com> wrote:
> @kwin - sorry I cannot add logs as this is confidential information - yet I
> could trace back this to the case where packages contain subpackages which
> within the resource tranformer cause subsequent InstallTasks having the
> same URL. - This migth be a bug but needs to fixed along for this to be
> applicable.
>
> Cheers
> Dominik
>
> On Fri, Feb 17, 2017 at 1:08 PM, Konrad Windszus <konrad_w@gmx.de> wrote:
>
>> 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.suess@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 <sseifert@pro-vision.de>
>> > wrote:
>> >
>> >> +1
>> >>
>> >>
>>
>>



-- 
Karl Pauls
karlpauls@gmail.com

Mime
View raw message