Incomaptible changes in new package for f27

Hello all!

I seek advice how to proceed with following situation.

There is new package for f27 - java-9-openjdk.

It have been first built some two or three months ago. For f27. Before it was available in copr
When it was first built for f27 (and in meantime also for f26, but never left (intentionally)
testing) it was lacking one major promise - to move config files to /etc
This was developed in rawhide in last two weeks, and now backported to f27.

The issue is, RPM do not like change of directory to symlink which is exactly what happened, and
dies with cpio error.

My intention was to let it be. Java9 is techpreview, and was only seen in f26 in testing and in
f27beta. So I was hiding behind "never released before" .
For that reason I wonted to negotiate f27 final blocker before the package with config files in /etc
reach stable for f27.

Anyway, what are general thoughts?



Re: Incomaptible changes in new package for f27

By Michael Schwendt at 10/10/2017 - 07:44

Since you haven't commented on
<a href="" title=""></a>
I wonder whether that would be an option?

Re: Incomaptible changes in new package for f27

By Jiri Vanek at 10/10/2017 - 07:51

On 10/10/2017 01:44 PM, Michael Schwendt wrote:
I'm well aware of this. So am I aware of ways how to script out the above described problem.
As I dont see much more options to do it differently, nor do I wont to scriplet the issue out, I wes
hoping "unreleased software" would be my shield.


Re: Incomaptible changes in new package for f27

By Zbigniew =?utf-... at 10/10/2017 - 11:25

On Tue, Oct 10, 2017 at 01:51:30PM +0200, Jiri Vanek wrote:
I don't think you can get around adding a scriptlet for the upgrade
once the package left testing in branched. Many people (me too ;))
install Fedora around when beta is released, and it is bad to break
the upgrade process for them. Especially that the failure mode for
dir↔file switch is particularly nasty. We push people towards
installing branched early and doing more testing, and the corollary of
that is that breakage must be avoided if possible.

(I really hope that one day rpm will handle this on its own, but
that's a discussion for another time).