I think most folks using vagrant recently have hit this, which is that
"vagrant up" explodes on the dnf upgrade provisioning step.
I've been poking at this off and on, and I have a diff that "fixes" it:
---
$ diff -u Vagrantfile.example Vagrantfile
--- Vagrantfile.example 2016-02-25 10:09:05.084
On Mon, Mar 21, 2016 at 10:06:47AM -0400, Kodiak Firesmith wrote:
> Will there be an "LTS-like" version released periodically for stable
> production use? I mean, I get that it's not a supported product like
> Satellite 6, but since I'm planning to use it in production I'd like to be
> able to sti
On 03/21/2016 10:02 AM, Randy Barlow wrote:
On Mon, Mar 21, 2016 at 09:56:04AM -0400, Bryan Kearney wrote:
you guys are thinking a three month time based cadence?
That is the current proposal. We discussed it during a meeting last week
and it was suggested that something between 3 and 6 months
Will there be an "LTS-like" version released periodically for stable
production use? I mean, I get that it's not a supported product like
Satellite 6, but since I'm planning to use it in production I'd like to be
able to stick with a single version for about 12 months without feeling
like I need t
On Mon, Mar 21, 2016 at 09:56:04AM -0400, Bryan Kearney wrote:
> you guys are thinking a three month time based cadence?
That is the current proposal. We discussed it during a meeting last week
and it was suggested that something between 3 and 6 months would work
well. We can always adjust if we f
On 03/21/2016 09:36 AM, Brian Bouterse wrote:
> Oleg, As I understand it rpm repositories don't support versioning, and
> generally RHEL repos are constant being updated with new/better content.
> Given that, unless there is a feed available for specifically RHEL 6.6 I
> don't know of a way to do t
On 03/21/2016 09:36 AM, Randy Barlow wrote:
Jeremy and I wrote up a quick draft of a 2.9.0 release schedule over the
weekend. We hadn't been using the Redmine Wiki, so we just put it on the
main page for now:
https://pulp.plan.io/projects/pulp/wiki
This is a draft and a Wiki, so feel free to su
Oleg, As I understand it rpm repositories don't support versioning, and
generally RHEL repos are constant being updated with new/better content.
Given that, unless there is a feed available for specifically RHEL 6.6 I
don't know of a way to do this today with Pulp.
One option is to sync a repo and
Jeremy and I wrote up a quick draft of a 2.9.0 release schedule over the
weekend. We hadn't been using the Redmine Wiki, so we just put it on the
main page for now:
https://pulp.plan.io/projects/pulp/wiki
This is a draft and a Wiki, so feel free to suggest changes. We'd like
to get this nailed do
Hi,
I still hitting this bug https://pulp.plan.io/issues/1749 and unable to
use latest version. And seems that it's not critical for anybody else than
me :-)
So I'm a quite curious is there anybody else who use Pulp for Centos6
consumers ? How many users really use Pulp ? is it stable enough to u
10 matches
Mail list logo
