We agreed on removing the older versions from Leap-15, but I didn't mean to drop them from Factory/Tumbleweed as well.

Is there any advantage of do so, given that they are going to be maintained in the devel project anyway as long as upstream provides updates for the respective versions?

Andreas Stieger (AndreasStieger) - about 6 years ago

author

Well this is also about postgresql-plr which @bruno_friedmann maintains. It is now a multibuild package, and to drop older version from Leap 15 I sent SR#578908 . Apparently multibuild packages do not support conditionals based on release. Not sure what to do here to get it dropped from Leap 15 only.. make postgresql-plr a fork?

---

Bruno Friedmann (bruno_friedmann) - about 6 years ago

From what I know plr is mutlibuild and done for all version of postgresql we still support (so 9.4 and plus) When Max doesn't support anymore a version I adjust the build for. I've honestly no idea how this can be handle in Leap 15 ? Normally I've sr the new mutlibuild in Factory, and leaper has done the job for Leap alone. If that can help, we can delete it, and resubmit (beside the fact that add to me a bit of load).

---

Reinhard Max (rmax) - about 6 years ago

Maybe there is a way to have different _multibuild files in different projects via the prjconfig? But I am not enough of an OBS expert to know if let alone how it can be done.

---

Dominique Leuenberger (dimstar) - about 6 years ago

Sadly, no.

What CAN be done in the spec file is something like (pseudo code!):

%if %flavor=94 && 0%{?sle_version}
ExclusiveArch: do-not-build
%endif

meaning, on anything where sle_version si defined (so, SLE and Leap) do not build the 94 flavor (and others you want to skip)

---

Max Lin (mlin7442) - about 6 years ago

IMO we can fork it for Leap or(maybe a better way) we disable those FLAVOR build if product is Leap in the specfile, ie. build excluded, like what hdf5 did to decide build openmpi or not https://build.opensuse.org/package/view_file/openSUSE:Factory/hdf5/hdf5.spec?expand=1 , HTH

---

Bruno Friedmann (bruno_friedmann) - about 6 years ago

Max I would prefer to not have %if more than needed. Every condition is a future fail. We should also find a solution which is the lighter burdening tier maintainer.

---

Andreas Stieger (AndreasStieger) - about 6 years ago

author

Okay, proposing the following: Leave devel and Factory alone. FORK postgresql-plr in Leap 15.0 to match the postgresql versions therein

I found all of this quite confusing (don't forget I'm external of SUSE :-) I don't understand why after spending so much effort to finally being able to propose a multi-version of postgresql to openSUSE (which is appreciate, and desirable for end-user). We want to broke everything again ? Why not simply state that any version supported by upstream can still live in openSUSE TW and Leap. When a version has no more support by upstream, then of course the package get retired. Which is simple clear and efficient to explain to manager, maintainer, user, at least this is what I believe.

Bruno Friedmann (bruno_friedmann) - about 6 years ago

So postgresql93 will be retired in September 2018. The rest of the schedule
https://www.postgresql.org/support/versioning/