The following Fedora EPEL 6 Security updates need testing:
 Age  URL
 797  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-7031   
python-virtualenv-12.0.7-1.el6
 791  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-7168   
rubygem-crack-0.3.2-2.el6
 681  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-e2b4b5b2fb   
mcollective-2.8.4-1.el6
 653  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-35e240edd9   
thttpd-2.25b-24.el6
 263  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-e3e50897ac   
libbsd-0.8.3-2.el6
 159  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-c0d33ae70f   
tnef-1.4.14-1.el6
  61  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-e8124f23c8   
heimdal-7.4.0-1.el6
  23  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-01dbc69547   
exim-4.89-2.el6
  21  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-f14c660f60   
tomcat-7.0.81-1.el6
  12  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-63bdf1b0d8   
libidn2-2.0.4-1.el6
  10  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-225c9fc495   
freexl-1.0.0i-1.el6
   8  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-274b596685   
mimedefang-2.81-1.el6
   1  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-8dca05d55c   
drupal7-views-3.18-1.el6


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

    fedfind-3.6.2-1.el6
    golang-github-pmezard-go-difflib-0-0.9.git792786c.el6
    golang-github-stretchr-objx-0-0.12.git1a9d0bb.el6
    golang-github-stretchr-testify-1.1.4-0.1.git69483b4.el6
    inxi-2.3.38-1.el6
    recap-1.1.0-1.el6

Details about builds:


================================================================================
 fedfind-3.6.2-1.el6 (FEDORA-EPEL-2017-ef03b80a2c)
 Fedora compose and image finder
--------------------------------------------------------------------------------
Update Information:

This update fixes [PDC](https://pdc.fedoraproject.org/) queries to work
correctly again. fedfind has always formed such queries using URLs without
trailing slashes, and this must have worked at some point, or none of the
functions that rely on PDC queries ever would have worked. However, current PDC
[seems not to handle API queries without trailing slashes properly at
all](https://github.com/product-definition-center/product-definition-
center/issues/467), just returning a 404 error for an API endpoint URL that
would be valid with a `/` character added.  So, this new fedfind version ensures
PDC queries use URLs with a trailing `/`. This should resolve [issue
#9](https://pagure.io/fedora-qa/fedfind/issue/9), and any other issue caused by
PDC queries not working correctly. One practical consequence was that the
metadata for composes produced by Pungi 4 but which had their metadata stripped
on release to the mirror system (e.g. Fedora 24, 25 and 26 stable releases) was
not being retrieved from PDC and modified (as was the optimal path in recent
fedfind releases), but was being fully synthesized by fedfind, which results in
much less data.
--------------------------------------------------------------------------------


================================================================================
 golang-github-pmezard-go-difflib-0-0.9.git792786c.el6 
(FEDORA-EPEL-2017-8cd54180b8)
 Partial port of Python difflib package to Go
--------------------------------------------------------------------------------
Update Information:

Bump to upstream 792786c7400a136282c1664665ae0a8db921c6c2
--------------------------------------------------------------------------------
References:

  [ 1 ] Bug #1490448 - Please update to 792786c7400a136282c1664665ae0a8db921c6c2
        https://bugzilla.redhat.com/show_bug.cgi?id=1490448
--------------------------------------------------------------------------------


================================================================================
 golang-github-stretchr-objx-0-0.12.git1a9d0bb.el6 (FEDORA-EPEL-2017-1ced5db8b2)
 Go package for dealing with maps, slices, JSON and other data
--------------------------------------------------------------------------------
Update Information:

update to 1a9d0bb9f541897e62256577b352fdbc1fb4fd94
--------------------------------------------------------------------------------
References:

  [ 1 ] Bug #1490415 - Please update to 1a9d0bb9f541897e62256577b352fdbc1fb4fd94
        https://bugzilla.redhat.com/show_bug.cgi?id=1490415
--------------------------------------------------------------------------------


================================================================================
 golang-github-stretchr-testify-1.1.4-0.1.git69483b4.el6 
(FEDORA-EPEL-2017-f401793750)
 Tools for testifying that your code will behave as you intend
--------------------------------------------------------------------------------
Update Information:

upgrade snapshot to 1.1.4 release
--------------------------------------------------------------------------------
References:

  [ 1 ] Bug #1490397 - Please upgrade snapshot to 1.1.4 release
        https://bugzilla.redhat.com/show_bug.cgi?id=1490397
--------------------------------------------------------------------------------


================================================================================
 inxi-2.3.38-1.el6 (FEDORA-EPEL-2017-97529047c9)
 A full featured system information script
--------------------------------------------------------------------------------
Update Information:

Update to 2.3.38.
--------------------------------------------------------------------------------


================================================================================
 recap-1.1.0-1.el6 (FEDORA-EPEL-2017-281c51739c)
 Generates reports of various system information
--------------------------------------------------------------------------------
Update Information:

https://github.com/rackerlabs/recap/blob/1.1.0/CHANGELOG.md
--------------------------------------------------------------------------------
_______________________________________________
epel-devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to