Bug 1083889

Summary: Upgrade debootstrap on el6 branch
Product: [Fedora] Fedora EPEL Reporter: Adrian Reber <adrian>
Component: debootstrapAssignee: Oron Peled <oron>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: el6CC: jv+fedora, mi, oron, pertusus
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: debootstrap-1.0.59-1.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-04-15 23:29:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Adrian Reber 2014-04-03 08:05:23 UTC
Any chance on getting debootstrap upgraded on the EL6 branch to the latest version?

Comment 1 Jan Včelák 2014-04-06 13:35:34 UTC
I will update the package. The new versions are just adding support for new Debian/Ubuntu releases. There is no need to keep a stable version in the repository, as it qualifies more as old than stable.

Comment 2 Fedora Update System 2014-04-06 13:36:57 UTC
debootstrap-1.0.59-1.el6 has been submitted as an update for Fedora EPEL 6.
https://admin.fedoraproject.org/updates/debootstrap-1.0.59-1.el6

Comment 3 Fedora Update System 2014-04-06 18:53:49 UTC
Package debootstrap-1.0.59-1.el6:
* should fix your issue,
* was pushed to the Fedora EPEL 6 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=epel-testing debootstrap-1.0.59-1.el6'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-1070/debootstrap-1.0.59-1.el6
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2014-04-15 23:29:14 UTC
debootstrap-1.0.59-1.el6 has been pushed to the Fedora EPEL 6 stable repository.  If problems still persist, please make note of it in this bug report.