https://bugzilla.redhat.com/show_bug.cgi?id=1255155
Ben Cotton <bcotton(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|MODIFIED |CLOSED
Resolution|--- |EOL
Last Closed| |2020-11-30 15:57:02
--- Comment #5 from Ben Cotton <bcotton(a)redhat.com> ---
EPEL el6 changed to end-of-life (EOL) status on 2020-11-30. EPEL el6 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
EPEL please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.
Thank you for reporting this bug and we are sorry it could not be fixed.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1439748
Bug 1439748 depends on bug 1439752, which changed state.
Bug 1439752 Summary: CVE-2017-3204 golang-googlecode-go-crypto: Go SSH library does not verify host keys by default [epel-6]
https://bugzilla.redhat.com/show_bug.cgi?id=1439752
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CLOSED
Resolution|--- |EOL
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1439752
Ben Cotton <bcotton(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CLOSED
Resolution|--- |EOL
Last Closed|2017-04-06 14:20:07 |2020-11-30 15:26:18
--- Comment #3 from Ben Cotton <bcotton(a)redhat.com> ---
EPEL el6 changed to end-of-life (EOL) status on 2020-11-30. EPEL el6 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
EPEL please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.
Thank you for reporting this bug and we are sorry it could not be fixed.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1346483
Upstream Release Monitoring <upstream-release-monitoring(a)fedoraproject.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|cadvisor-0.38.4 is |cadvisor-0.38.5 is
|available |available
--- Comment #86 from Upstream Release Monitoring <upstream-release-monitoring(a)fedoraproject.org> ---
Latest upstream release: 0.38.5
Current version/release in rawhide: 0.37.0-1.fc34
URL: https://github.com/google/cadvisor
Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
Based on the information from anitya:
https://release-monitoring.org/project/6528/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1443517
--- Comment #24 from Upstream Release Monitoring <upstream-release-monitoring(a)fedoraproject.org> ---
One or more of the new sources for this package are identical to the old
sources. This is most likely caused either by identical source files between
releases, for example service files, or the specfile does not use version macro
in its source URLs. If this is the second case, then please update the specfile
to use version macro in its source URLs.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1443517
Upstream Release Monitoring <upstream-release-monitoring(a)fedoraproject.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|flannel-0.13.0 is available |flannel-0.13.1-rc1 is
| |available
--- Comment #23 from Upstream Release Monitoring <upstream-release-monitoring(a)fedoraproject.org> ---
Latest upstream release: 0.13.1-rc1
Current version/release in rawhide: 0.9.0-8.fc33
URL: https://github.com/coreos/flannel
Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
Based on the information from anitya:
https://release-monitoring.org/project/7421/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1346483
--- Comment #85 from Upstream Release Monitoring <upstream-release-monitoring(a)fedoraproject.org> ---
An unexpected error occurred while creating the scratch build and has been
automatically reported. Sorry!
--
You are receiving this mail because:
You are on the CC list for the bug.