[EPEL-devel] Re: Current state of dual repository packages.

2017-08-15 Thread Simone Caronni
On Tue, Aug 15, 2017 at 12:01 PM, Simone Caronni wrote: > > If I trigger the rebuild in Koji, we will get again the same version as > the first one. > What will the CentOS folks do for these rebuilds? Regards, --Simone -- You cannot discover new oceans unless you have

[EPEL-devel] Re: Current state of dual repository packages.

2017-08-15 Thread Simone Caronni
On Tue, Aug 15, 2017 at 11:38 AM, Simone Caronni wrote: > On Fri, Aug 11, 2017 at 8:00 PM, Stephen John Smoogen > wrote: >> >> The remaining packages which are not in all architectures BUT are very >> old (and may break other things). These need some sort

[EPEL-devel] Re: Current state of dual repository packages.

2017-08-15 Thread Simone Caronni
On Fri, Aug 11, 2017 at 8:00 PM, Stephen John Smoogen wrote: > > The remaining packages which are not in all architectures BUT are very old > (and may break other things). These need some sort of update/rebuild I > expect. > > libssh > libtomcrypt > libtommath > libvncserver >

[EPEL-devel] Re: Current state of dual repository packages.

2017-08-14 Thread Orion Poplawski
On 08/14/2017 08:31 AM, Paul Howarth wrote: > On 2017-08-11 19:00, Stephen John Smoogen wrote: >> I have opened 2 tickets in RELENG to have these packages >> removed/blocked for EPEL. >> >> Packages which are newer in EPEL than RHEL-7.4 >> >> https://pagure.io/releng/issue/6948 >> >> Packages

[EPEL-devel] Re: Current state of dual repository packages.

2017-08-14 Thread Paul Howarth
On 2017-08-11 19:00, Stephen John Smoogen wrote: I have opened 2 tickets in RELENG to have these packages removed/blocked for EPEL. Packages which are newer in EPEL than RHEL-7.4 https://pagure.io/releng/issue/6948 Packages which are older in EPEL than RHEL-7.4 but exist in aarch64, x86_64,