Bug 1031736 - push lxc to epel stable
Summary: push lxc to epel stable
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: lxc
Version: el6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Thomas Moschny
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-18 16:31 UTC by Lokesh Mandvekar
Modified: 2014-07-01 22:59 UTC (History)
7 users (show)

Fixed In Version: lxc-0.9.0-2.el6
Clone Of:
Environment:
Last Closed: 2013-12-05 03:23:15 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Lokesh Mandvekar 2013-11-18 16:31:36 UTC 
just wondering if lxc can be pushed to EPEL stable (?), (docker-io Require:'s it)
Comment 1 Thomas Moschny 2013-11-18 21:38:15 UTC 
Hi, lxc is still very unstable, and there's at least one lua issue left with the 0.9.0 version, that's it is still in unstable. I am travelling this week, but hopefully will find some time next week to finally make a version that can be pushed to stable.

That said, we surely want to have the 1.0 version in EPEL 6 once it's released (spring 2014), so I hope people don't mind the update then, as API changes are likely.
Comment 2 Thomas Moschny 2013-11-18 21:39:07 UTC 
I wanted to say: "... that's why it is still in testing."
Comment 3 Lokesh Mandvekar 2013-12-03 15:50:34 UTC 
thomas: ping, is there a bz filed for the lua issue?

/me couldn't find it
Comment 4 Fedora Update System 2013-12-04 18:40:19 UTC 
lxc-0.9.0-2.el6 has been submitted as an update for Fedora EPEL 6.
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11454/lxc-0.9.0-2.el6
Comment 5 Thomas Moschny 2013-12-04 18:43:49 UTC 
Admittedly the lua issue is not relevant for EL6, so I finally pushed the package now.
Comment 6 Fedora Update System 2013-12-05 03:23:15 UTC 
lxc-0.9.0-2.el6 has been pushed to the Fedora EPEL 6 stable repository.  If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.