Re: Between a rock and a hard place

2015-12-09 Thread Jamie Nguyen
On 08/12/15 16:07, Jamie Nguyen wrote: > Unfortunately, I don't think this is possible until the Red Hat > maintainer for libunwind bumps the Release. > > RHEL = libunwind-1.1-5 > EPEL = libunwind-1.1-10 > > If I introduce libunwind-1.1-0.5 then it doesn't mess up RHEL but it > *does* mess up EPE

Re: Between a rock and a hard place

2015-12-08 Thread Jamie Nguyen
On 08/12/15 08:58, Paul Howarth wrote: > It's not a different version. It's an exact clone of the RHEL package > except with "0." in front of the release to make sure the RHEL package > "wins" where it is available. It is in fact the official EPEL > limited-arch package policy: > > https://fedorap

Re: Between a rock and a hard place

2015-12-08 Thread Paul Howarth
On 07/12/15 17:40, Kevin Fenzi wrote: FYI, this discussion might be better on the actual epel-devel list... On Mon, 7 Dec 2015 15:17:54 + Paul Howarth wrote: On 07/12/15 14:59, Pierre-Yves Chibon wrote: ...snip... Could make a compat package in EPEL7 be an option? This way you introduce

Re: Between a rock and a hard place

2015-12-07 Thread Jamie Nguyen
On 07/12/15 15:33, Ken Dreyer wrote: > On Mon, Dec 7, 2015 at 6:44 AM, Jamie Nguyen wrote: >> So, in the general case of packages being retired from EPEL7 because >> they have moved to RHEL, how do we avoid missing packages in the future? > > What is the issue with the CR CentOS repository? It's

Re: Between a rock and a hard place

2015-12-07 Thread Kevin Fenzi
FYI, this discussion might be better on the actual epel-devel list... On Mon, 7 Dec 2015 15:17:54 + Paul Howarth wrote: > On 07/12/15 14:59, Pierre-Yves Chibon wrote: ...snip... > > Could make a compat package in EPEL7 be an option? > > This way you introduce back the version that was presen

Re: Between a rock and a hard place

2015-12-07 Thread Jamie Nguyen
On 07/12/15 14:59, Pierre-Yves Chibon wrote: >> So, in the general case of packages being retired from EPEL7 because >> they have moved to RHEL, how do we avoid missing packages in the future? > > Could make a compat package in EPEL7 be an option? > This way you introduce back the version that was

Re: Between a rock and a hard place

2015-12-07 Thread Ken Dreyer
On Mon, Dec 7, 2015 at 6:44 AM, Jamie Nguyen wrote: > So, in the general case of packages being retired from EPEL7 because > they have moved to RHEL, how do we avoid missing packages in the future? What is the issue with the CR CentOS repository? - Ken -- devel mailing list devel@lists.fedorapro

Re: Between a rock and a hard place

2015-12-07 Thread Paul Howarth
On 07/12/15 14:59, Pierre-Yves Chibon wrote: On Mon, Dec 07, 2015 at 01:44:30PM +, Jamie Nguyen wrote: Hi! libunwind package is now part of RHEL 7.2. It got retired from EPEL7 three days ago (and incidentally the Release went backwards so upgrade path is broken): https://bugzilla.redhat

Re: Between a rock and a hard place

2015-12-07 Thread Pierre-Yves Chibon
On Mon, Dec 07, 2015 at 01:44:30PM +, Jamie Nguyen wrote: > Hi! > > libunwind package is now part of RHEL 7.2. It got retired from EPEL7 > three days ago (and incidentally the Release went backwards so upgrade > path is broken): > > https://bugzilla.redhat.com/show_bug.cgi?id=1288313 > > U