+1
> On 24. Oct 2017, at 07:33, Ondrej Prazak wrote:
>
> +1
>
>> On Mon, Oct 23, 2017 at 9:49 PM, Marek Hulan wrote:
>> +1, I remember you've helped me many times.
>>
>> --
>> Marek
>>
>>
>>
>> On October 23, 2017 6:16:48 PM Ewoud Kohl van Wijngaarden
>> wrote:
>>
>>> Hello all,
>>>
>>
+1
On Mon, Oct 23, 2017 at 9:49 PM, Marek Hulan wrote:
> +1, I remember you've helped me many times.
>
> --
> Marek
>
>
>
> On October 23, 2017 6:16:48 PM Ewoud Kohl van Wijngaarden <
> ew...@kohlvanwijngaarden.nl> wrote:
>
> Hello all,
>>
>> To get more involved in packaging I'd like to request
+1, I remember you've helped me many times.
--
Marek
On October 23, 2017 6:16:48 PM Ewoud Kohl van Wijngaarden
wrote:
Hello all,
To get more involved in packaging I'd like to request merge access to
foreman-packaging. I've already been monitoring PRs and submitted
various patches[1][2].
Hello all,
To get more involved in packaging I'd like to request merge access to
foreman-packaging. I've already been monitoring PRs and submitted
various patches[1][2].
Regards,
Ewoud Kohl van Wijngaarden
[1]:
https://github.com/theforeman/foreman-packaging/commits/rpm/develop?author=ekohl
In hindsight, I should caught this on the PR. This scratched an itch in the
back of mind and there was the reminder:
https://github.com/Katello/katello/blob/master/lib/katello/tasks/reset.rake#L52
On Mon, Oct 23, 2017 at 11:59 AM, Ewoud Kohl van Wijngaarden <
ew...@kohlvanwijngaarden.nl> wrote:
Hello all,
On Friday a PR was merged[1] that was intended to verify seeding worked.
It turns out that you can't run rake db:migrate db:seed in one command
which resulted in failing tests. An issue has been created[2] and a
workaround implemented[3]. Please rerun tests that failed on
NOT NULL
+1 I guess the foreman and katello config files will still live separately
(i.e. katello_35.yaml and foreman_16.yaml) but in the same repo.
On Mon, Oct 23, 2017 at 5:59 AM, Daniel Lobato Garcia
wrote:
> On 10/20, Eric D Helms wrote:
> > For quite a few releases now, we've been using a little too
puppet-puppet 8.0.3 included a fix for that and RC2 should include that
fix. So when I said 'prepare the installer side' was get everything in
place so we can do a release. That'll mean tagging and building
packages.
On Mon, Oct 23, 2017 at 02:29:41PM +0200, Roger Martensson wrote:
There seem
There seems to be a problem with Puppet 5 with the Foreman-installer.
https://github.com/theforeman/puppet-puppet/issues/549
It seems to be merged in master:
https://github.com/theforeman/puppet-puppet/pull/548/files
Doesn't seem to be installed in 1.16RC.
Would love to see installed in 1.16.
20
On Thu, Oct 12, 2017 at 05:42:19PM +0200, Ewoud Kohl van Wijngaarden wrote:
While Daniel is on PTO I'd like to take over the 1.16 RC2 preparation.
From the installer side I can handle it, but will need help from a
core maintainer and a proxy maintainer to tag releases.
We did prepare the insta
On Mon, Oct 23, 2017 at 5:57 AM, Daniel Lobato Garcia
wrote:
> On 10/20, Eric D Helms wrote:
> > All,
> >
> > One of the items on the Roadmap I've sent out is centralizing packaging
> > into a single repository. The last time I tried this I attempted to go
> > whole hog migrating all things all a
On 10/20, Eric D Helms wrote:
> For quite a few releases now, we've been using a little tool named
> tool_belt as a CLI to perform release tasks such as finding cherry picks,
> or building koji configurations. The larger idea of the repository is you
> define a release via a configuration file and
On 10/20, Eric D Helms wrote:
> All,
>
> One of the items on the Roadmap I've sent out is centralizing packaging
> into a single repository. The last time I tried this I attempted to go
> whole hog migrating all things all at once. In order to make this more
> approachable, and to encourage reviews
On Mon, 2017-10-16 at 14:36 +0100, Greg Sutcliffe wrote:
>
> That said, I've not really been involved with the RPMs, so I'm unsure
> if this causes a bigger headache for Yum users than Apt users. I'm
> also unsure of the work required to create an SCL, but if it's non-
> trivial then I'd be lookin
On Sun, 2017-10-22 at 21:27 -0400, Eric D Helms wrote:
>
> Note that this plan says nothing about changing our actual yum
> repository structure. That would come later. This is just about
> beginning with moving all package management to be centralized in
> foreman-packaging git repository.
So if
On Fri, 2017-10-20 at 16:59 -0400, Eric D Helms wrote:
>
> If there are no objections, I will perform this next Wednesday or
> Thursday.
+1
--
IRC / Twitter: @gwmngilfen
Diaspora: gwmngil...@joindiaspora.com
--
You received this message because you are subscribed to the Google Groups
"foreman
16 matches
Mail list logo