Comment # 13 on bug 1162535 from Cliff Zhao

(In reply to Marcus Meissner from comment #11)
> The problem is it does not build, it also cvhanges library major versions.
> This version update request should have better be for SUSE:SLE-15-SP2:GA
> Also %autosetup -S git   fails, which is more annyoing.
> Cliff Zhao,
> can you fix the build issues?

Hi Marcus:
Do you mean request in "https://build.suse.de/request/show/201584"?
Because I saw the building result succeeded in IBS web site and when I local
building against SUSE:SLE-15:Update it also succeeded. I guess maybe it can't
be build from the maintenance side, or there has some information I don't know?

For the library version problem: 
There hass no big API change in so level, everything works as normal, upstream
just use two-step support UEFI logo, so they think they change the so vertion
then, we as the  downstream only can follow up. and there's no other package
linked to plymouth's library. So please don't worry, there is no risk. I
supposed release managers knows all the backgroud, if you have doubt, please
ask me once without any hesitate.

For it's better to release in SUSE:SLE-15-SP2:GA: 
In fact, this version of soure code has already released in SUSE:SLE-15-SP1, so
I think it is not a special point in SUSE:SLE-15-SP2:GA. and I think that the
thing which related to this bug is the Plymouth in Leap 15.2 far behind these 2
maintenance Plymouth sources which inside SLE-15 repos. I think maybe we need
to update Leap or some else actions.

For %autosetup -S git fails,  which is more annyoing.
Where can I find the failures?

> 
> FOR SLES 15 SP1 we would like to have a more minimal submission. 
> The full submission could still be tried for SUSE:SLE-15-SP2:GA, but its
> very very late in the process and might not go in.

Sorry, I'm afraid I haven't mastered the full relationship between your
meanings and my work:
The Plymouth maintenance update is on SUSE:SLE-15:Update. The SUSE:SLE-15-SP1
repo have already had these code in the time point when it released, I mean if
some day, SUSE:SLE-15:Update accept and release plymouth's maintenance
modification, then plymouth's source will be totally the same between
SUSE:SLE-15:Update and SUSE:SLE-15-SP1:GA and SUSE:SLE-15-SP1:Update. Current
situation is the plymouth in SUSE:SLE-15-SP1:GA and SUSE:SLE-15-SP1:Update
don't have the build failures there. Do you mean you want me to fix the
"%autosetup -S git" because it's very annyoing and may have bad depending
effects in the future? Am I understanding correctly? it's ok for me.