Re: [foreman-dev] Moving foreman-tasks to the core: the plan

2017-01-04 Thread Marek Hulán
+1 -- Marek On středa 4. ledna 2017 10:29:19 CET Ivan Necas wrote: > Hello friends, > > You've might noticed we started using foreman-tasks inside the > foreman-core since [1] was merged. Unfortunately, we hit issues in the > packaging phase and the proposed workarounds were not accepted ([2] >

Re: [foreman-dev] Moving foreman-tasks to the core: the plan

2017-01-04 Thread Eric D Helms
On Wed, Jan 4, 2017 at 4:29 AM, Ivan Necas wrote: > Hello friends, > > You've might noticed we started using foreman-tasks inside the > foreman-core since [1] was merged. Unfortunately, we hit issues in the > packaging phase and the proposed workarounds were not accepted ([2]

[foreman-dev] 1.14.0 inclusion request

2017-01-04 Thread Justin Sherrill
The following issue was just moved to 1.14.1: http://projects.theforeman.org/issues/17894 and I'd like to request for it to be moved back to 1.14.0. Its currently preventing katello from being built for 1.14.0 and the only other workaround would be to partially revert a commit and hope that the

[foreman-dev] Moving foreman-tasks to the core: the plan

2017-01-04 Thread Ivan Necas
Hello friends, You've might noticed we started using foreman-tasks inside the foreman-core since [1] was merged. Unfortunately, we hit issues in the packaging phase and the proposed workarounds were not accepted ([2] [3]). Based on various discussions, as well as on the fact that foreman-tasks

Re: [foreman-dev] Moving foreman-tasks to the core: the plan

2017-01-04 Thread Michael Moll
Hi, On Wed, Jan 04, 2017 at 10:29:19AM +0100, Ivan Necas wrote: > In the mean time, I would like to kindly ask for trying to > find an acceptable workaround in [2] and [3] until this is done. > > [...] > > [2] - https://github.com/theforeman/foreman-packaging/pull/1436 > [3] -