[EPEL-devel] Re: Ansible in EL7

2018-04-10 Thread James Hogarth
On Wed, 11 Apr 2018, 01:26 Todd Zullinger,  wrote:

> James Hogarth wrote:
> > On Wed, 11 Apr 2018, 00:59 Todd Zullinger,  wrote:
> >> Red Hat announced today that Ansible was being deprecated
> >> from the extras channel.  Their advice is that those who
> >> have "previously installed Ansible and its dependencies from
> >> the Extras channel are advised to enable and update from the
> >> Ansible Engine channel, or uninstall the packages as future
> >> errata will not be provided from the Extras channel."
> >>
> >> https://access.redhat.com/errata/RHSA-2018:1075
> >>
> >> Given that, I believe it is reasonable to see ansible return
> >> to EPEL.  This was discussed in previous EPEL meetings a
> >> bit, so I'm sure it was known to at least some of the folks
> >> involved.
> >
> > Cheers for the info.
> >
> > It wasn't mentioned on the devel list, I didn't see it in the 7.5 release
> > notes and it was still in extras when I checked a short while ago.
> >
> > In that case yes I agree it makes total sense to return to epel7
> >
> > I wonder why they dropped it when the whole point of them bringing it in
> to
> > begin with was for Satellite and Tower to have it in the standard RHEL
> > repos.
> >
> > Seems so pointless to have only had one release there!
>
> Indeed, it was a bit strange.  Perhaps someone with more
> insight into the rationale can comment.  I have no
> particular knowledge of things, but maybe keeping a fast
> moving project like ansible in even the RHEL extras channel
> was a problem.
>
> Maybe the plan with the move to the "Ansible Engine" channel
> is to work closer with subscribers on migrating from version
> to version.  And non-subscribers can just follow it in EPEL.
>
> I'd be interested in hearing more about the change, though I
> suspect those who know more either aren't on these lists or
> can't say more than Red Hat's advisory has already.
>
>
At this point, no offense to Nirik and the maintenance he does on the
package, I'm actually tempted to just grab it from upstream directly at
https://releases.ansible.com/ansible/rpm/

At least then I can get consistency with selection of stable, preview or
nightly ...



>
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org


[EPEL-devel] Re: Ansible in EL7

2018-04-10 Thread Todd Zullinger
James Hogarth wrote:
> On Wed, 11 Apr 2018, 00:59 Todd Zullinger,  wrote:
>> Red Hat announced today that Ansible was being deprecated
>> from the extras channel.  Their advice is that those who
>> have "previously installed Ansible and its dependencies from
>> the Extras channel are advised to enable and update from the
>> Ansible Engine channel, or uninstall the packages as future
>> errata will not be provided from the Extras channel."
>>
>> https://access.redhat.com/errata/RHSA-2018:1075
>>
>> Given that, I believe it is reasonable to see ansible return
>> to EPEL.  This was discussed in previous EPEL meetings a
>> bit, so I'm sure it was known to at least some of the folks
>> involved.
> 
> Cheers for the info.
> 
> It wasn't mentioned on the devel list, I didn't see it in the 7.5 release
> notes and it was still in extras when I checked a short while ago.
> 
> In that case yes I agree it makes total sense to return to epel7
> 
> I wonder why they dropped it when the whole point of them bringing it in to
> begin with was for Satellite and Tower to have it in the standard RHEL
> repos.
> 
> Seems so pointless to have only had one release there!

Indeed, it was a bit strange.  Perhaps someone with more
insight into the rationale can comment.  I have no
particular knowledge of things, but maybe keeping a fast
moving project like ansible in even the RHEL extras channel
was a problem.

Maybe the plan with the move to the "Ansible Engine" channel
is to work closer with subscribers on migrating from version
to version.  And non-subscribers can just follow it in EPEL.

I'd be interested in hearing more about the change, though I
suspect those who know more either aren't on these lists or
can't say more than Red Hat's advisory has already.

-- 
Todd
~~
I'm not fat. I am a nutritional overachiever.



signature.asc
Description: PGP signature
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org


[EPEL-devel] Re: Ansible in EL7

2018-04-10 Thread James Hogarth
On Wed, 11 Apr 2018, 01:13 James Hogarth,  wrote:

>
>
> On Wed, 11 Apr 2018, 00:59 Todd Zullinger,  wrote:
>
>> James Hogarth wrote:
>> > I was under the impression that as of 2.4.0 in EL7 we removed ansible
>> > from EPEL7 since Red Hat included it in their extras repo, and EPEL
>> > policy is not to conflict.
>> >
>> > I was surprised just now to see ansible 2.5.0 on a test centos system,
>> > when it wasn't in extras, and on a little bit of a search found:
>> >
>> > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-7ef392255b
>> >
>> > Of course this is a bit of an issue for CentOS/RHEL users that have
>> > need for the Red Hat ansible as they have been upgraded, and RH will
>> > need to epoch bump (or release 2.5.1 and we pull this from EPEL7 then)
>> > to ensure they get it from the right repo.
>> >
>> > With a branch retirement shouldn't this have been blocked in koji?
>>
>> Red Hat announced today that Ansible was being deprecated
>> from the extras channel.  Their advice is that those who
>> have "previously installed Ansible and its dependencies from
>> the Extras channel are advised to enable and update from the
>> Ansible Engine channel, or uninstall the packages as future
>> errata will not be provided from the Extras channel."
>>
>> https://access.redhat.com/errata/RHSA-2018:1075
>>
>> Given that, I believe it is reasonable to see ansible return
>> to EPEL.  This was discussed in previous EPEL meetings a
>> bit, so I'm sure it was known to at least some of the folks
>> involved.
>>
>
> Cheers for the info.
>
> It wasn't mentioned on the devel list, I didn't see it in the 7.5 release
> notes and it was still in extras when I checked a short while ago.
>
> In that case yes I agree it makes total sense to return to epel7
>
> I wonder why they dropped it when the whole point of them bringing it in
> to begin with was for Satellite and Tower to have it in the standard RHEL
> repos.
>
> Seems so pointless to have only had one release there!
>
>
And having read the bugzilla entry now... they moved it to its own product
channel that all RHEL subscribers have access to...

Again this feels so very pointless.


>
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org


[EPEL-devel] Re: Ansible in EL7

2018-04-10 Thread Todd Zullinger
James Hogarth wrote:
> I was under the impression that as of 2.4.0 in EL7 we removed ansible
> from EPEL7 since Red Hat included it in their extras repo, and EPEL
> policy is not to conflict.
> 
> I was surprised just now to see ansible 2.5.0 on a test centos system,
> when it wasn't in extras, and on a little bit of a search found:
> 
> https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-7ef392255b
> 
> Of course this is a bit of an issue for CentOS/RHEL users that have
> need for the Red Hat ansible as they have been upgraded, and RH will
> need to epoch bump (or release 2.5.1 and we pull this from EPEL7 then)
> to ensure they get it from the right repo.
> 
> With a branch retirement shouldn't this have been blocked in koji?

Red Hat announced today that Ansible was being deprecated
from the extras channel.  Their advice is that those who
have "previously installed Ansible and its dependencies from
the Extras channel are advised to enable and update from the
Ansible Engine channel, or uninstall the packages as future
errata will not be provided from the Extras channel."

https://access.redhat.com/errata/RHSA-2018:1075

Given that, I believe it is reasonable to see ansible return
to EPEL.  This was discussed in previous EPEL meetings a
bit, so I'm sure it was known to at least some of the folks
involved.

-- 
Todd
~~
Time may be a great healer, but it's a lousy beautician.



signature.asc
Description: PGP signature
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org


[EPEL-devel] Fedora EPEL 7 updates-testing report

2018-04-10 Thread updates
The following Fedora EPEL 7 Security updates need testing:
 Age  URL
 140  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-e64eeb6ece   
nagios-4.3.4-5.el7
  18  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-1fbdf7f103   
chromium-65.0.3325.181-1.el7
  12  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-2074629ed3   
drupal7-7.58-1.el7
  11  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-e12bc7bed5   
nodejs-6.14.0-1.el7 libuv-1.19.2-1.el7
   7  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-7c95e7ac21   
libofx-0.9.9-2.el7
   6  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-13062a4d15   
wordpress-4.9.5-1.el7
   6  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-e56f478565   
koji-1.15.1-1.el7
   4  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-9f8e93d154   
python-jwt-1.6.1-1.el7
   3  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-2c81054303   
remctl-3.14-1.el7


The following builds have been pushed to Fedora EPEL 7 updates-testing

freshmaker-0.0.15-2.el7
jpegoptim-1.4.5-1.el7
libappindicator-sharp-12.10.0-12.el7
nbdkit-1.2.1-1.el7
python-fedmsg-meta-fedora-infrastructure-0.24.0-1.el7

Details about builds:



 freshmaker-0.0.15-2.el7 (FEDORA-EPEL-2018-acd7068bd7)
 Freshmaker is a service scheduling rebuilds of artifacts as new content 
becomes available.

Update Information:

Use Koji build source instead of Koji task source if available.




 jpegoptim-1.4.5-1.el7 (FEDORA-EPEL-2018-11012c2e9d)
 Utility to optimize JPEG files

Update Information:

v1.4.5  - fix `--overwrite` option, - better error reporting for `-d` option -
fix memcmp() potentially reading past end of buffer - some minor fixes

References:

  [ 1 ] Bug #1562503 - jpegoptim-1.4.5 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1562503




 libappindicator-sharp-12.10.0-12.el7 (FEDORA-EPEL-2018-f3e1ef48f4)
 Application indicators library - C#

Update Information:

Mono C# bindings for the libappindicator library. This was split from the
original package when it was moved to RHEL.




 nbdkit-1.2.1-1.el7 (FEDORA-EPEL-2018-1e9e31ed4e)
 NBD server

Update Information:

New stable version 1.2.1.    Move to stable branch version 1.2.0.




 python-fedmsg-meta-fedora-infrastructure-0.24.0-1.el7 
(FEDORA-EPEL-2018-92455aaf1d)
 Metadata providers for Fedora Infrastructure's fedmsg deployment

Update Information:

Update to 0.24.0  Changelog is at: https://github.com/fedora-
infra/fedmsg_meta_fedora_infrastructure/blob/develop/CHANGELOG.rst#0240

___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org


[EPEL-devel] Ansible in EL7

2018-04-10 Thread James Hogarth
Hi all,

I was under the impression that as of 2.4.0 in EL7 we removed ansible
from EPEL7 since Red Hat included it in their extras repo, and EPEL
policy is not to conflict.

I was surprised just now to see ansible 2.5.0 on a test centos system,
when it wasn't in extras, and on a little bit of a search found:

https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-7ef392255b

Of course this is a bit of an issue for CentOS/RHEL users that have
need for the Red Hat ansible as they have been upgraded, and RH will
need to epoch bump (or release 2.5.1 and we pull this from EPEL7 then)
to ensure they get it from the right repo.

With a branch retirement shouldn't this have been blocked in koji?

Cheers,

James
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org


[EPEL-devel] Fedora EPEL 6 updates-testing report

2018-04-10 Thread updates
The following Fedora EPEL 6 Security updates need testing:
 Age  URL
  12  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-e4e96fbf3f   
drupal7-7.58-1.el6
   6  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-b5d9f8f571   
wordpress-4.9.5-1.el6
   6  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-870a92fcc5   
koji-1.15.1-1.el6
   2  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-5aca1d385d   
remctl-3.14-1.el6
   0  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-158680d651   
python-gunicorn-18.0-2.el6


The following builds have been pushed to Fedora EPEL 6 updates-testing

jpegoptim-1.4.5-1.el6
python-fedmsg-meta-fedora-infrastructure-0.24.0-1.el6
python34-3.4.8-1.el6

Details about builds:



 jpegoptim-1.4.5-1.el6 (FEDORA-EPEL-2018-02ca609742)
 Utility to optimize JPEG files

Update Information:

v1.4.5  - fix `--overwrite` option, - better error reporting for `-d` option -
fix memcmp() potentially reading past end of buffer - some minor fixes

References:

  [ 1 ] Bug #1562503 - jpegoptim-1.4.5 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1562503




 python-fedmsg-meta-fedora-infrastructure-0.24.0-1.el6 
(FEDORA-EPEL-2018-e4d78e2e09)
 Metadata providers for Fedora Infrastructure's fedmsg deployment

Update Information:

Update to 0.24.0  Changelog is at: https://github.com/fedora-
infra/fedmsg_meta_fedora_infrastructure/blob/develop/CHANGELOG.rst#0240




 python34-3.4.8-1.el6 (FEDORA-EPEL-2018-dd6e4a3f0b)
 Version 3 of the Python programming language aka Python 3000

Update Information:

Update to 3.4.8 security release

___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org


[EPEL-devel] [Fedocal] Reminder meeting : EPEL Steering Committee

2018-04-10 Thread smooge
Dear all,

You are kindly invited to the meeting:
   EPEL Steering Committee on 2018-04-11 from 18:00:00 to 19:00:00 GMT
   At fedora-meet...@irc.freenode.net

The meeting will be about:
The EPEL Steering Committee will have a weekly meeting to cover current tasks 
and problems needed to keep EPEL going.


Source: https://apps.fedoraproject.org/calendar/meeting/8724/

___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org


[EPEL-devel] No EPSCO meeting 2018-04-11

2018-04-10 Thread Stephen John Smoogen
Kevin, Brian, Jim Perrin and I are at the Fedora Infrastructure
Hackfest and it is wall to wall meetings. I am unable to do anything
towards getting a meeting together.

-- 
Stephen J Smoogen.
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org


[EPEL-devel] Re: RHEL 7.5 fallout

2018-04-10 Thread Stephen John Smoogen
Do you have any information that htis is EPEL packages or just EL7.5 items?

On 10 April 2018 at 09:57, Orion Poplawski  wrote:
> I'm seeing this in the root.log of some packages:
>
> DEBUG util.py:439:  Error: initscripts conflicts with
> 1:redhat-release-server-7.4-1.x86_64
>
> --
> Orion Poplawski
> Manager of NWRA Technical Systems  720-772-5637
> NWRA, Boulder/CoRA Office FAX: 303-415-9702
> 3380 Mitchell Lane   or...@nwra.com
> Boulder, CO 80301 https://www.nwra.com/
> ___
> epel-devel mailing list -- epel-devel@lists.fedoraproject.org
> To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org



-- 
Stephen J Smoogen.
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org


[EPEL-devel] RHEL 7.5 fallout

2018-04-10 Thread Orion Poplawski

I'm seeing this in the root.log of some packages:

DEBUG util.py:439:  Error: initscripts conflicts with 
1:redhat-release-server-7.4-1.x86_64


--
Orion Poplawski
Manager of NWRA Technical Systems  720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane   or...@nwra.com
Boulder, CO 80301 https://www.nwra.com/
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org


[EPEL-devel] Re: CMake 3.11.0 on epel7

2018-04-10 Thread Richard Shaw
On Tue, Apr 10, 2018 at 4:57 AM, Antonio Trande 
wrote:

> Hello everyone.
>
> I wish to update CMake3 to the version 3.11.0 on epel7.
> SRPM: https://sagitter.fedorapeople.org/cmake3-3.11.0-1.fc27.src.rpm
>
> Any objection about?


Not from me.

I support a module upstream (out of necessity because I needed it fixed)
and they seem to have a "fixes forward" culture. I was discouraged from
backporting the fix in a patch because it would create a different behavior
on Fedora from other distros and was instead encouraged to work around the
problem (use a fixed local copy). So we should probably stay on the latest
minor/patch release for the major version of the package, in this case 3.

Thanks,
Richard
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org


[EPEL-devel] CMake 3.11.0 on epel7

2018-04-10 Thread Antonio Trande
Hello everyone.

I wish to update CMake3 to the version 3.11.0 on epel7.
SRPM: https://sagitter.fedorapeople.org/cmake3-3.11.0-1.fc27.src.rpm

Any objection about?

-- 
---
Antonio Trande
Fedora Project
mailto 'sagitter at fedoraproject dot org'
GPG key: 0x5E212EE1D35568BE
GPG key server: https://keys.fedoraproject.org/




signature.asc
Description: OpenPGP digital signature
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org