Hi,
Lance from osuosl now has time to upgrade our machine.
Shall I give him the green light?
Wim
------
Let us know when you can reboot and we'll schedule downtime for it.
As of now ecf-builds is running Gentoo and is cfengine managed. We'd like to
get ecf-builds to run Centos and Chef, and in the process also upgrade to Java
8. When we migrate, we can also update logrotate among other things.
I can start working on this immediately if this sounds good to you.
On Jan 14, 2016, at 18:48, Scott Lewis < slewis@xxxxxxxxxxxxx> wrote:
Hi Folks,
Given the discussion with David Williams on [1], I think what I'm
going to do is to release the unpacked repo built from
R-HEAD-sdk-feature yesterday for ECF 3.12.1 tomorrow (Friday
pacific time).
This way we can put 3.12.1 in the can and continue to work on
fixing the pack200 for another maintenance release (3.12.2) as
soon as the pack200 can be fixed.
If you have any objections to this plan, please say so now. I
would appreciate it if those with knowledge/expertise WRT the
builder config could continue to work on this until we figure out
what to change in our builder to deal with the pack200 problems
described below.
Thanksinadvance,
Scott
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=448916#c51
On 1/13/2016 7:51 PM, Scott Lewis wrote:
Hi Folks,
Here's the latest:
1) I fooled around with changing the version of java (1.6, 1.7,
1.8) used to run buckminster for the R-HEAD-sdk-feature and that
didn't change things at all (same exception as below)
2) I turned off pack200 by setting: SITE_PACK200=false for the
R-HEAD-sdk-feature, and the build completed successfully [1]
Obviously pack200 is off, however, so I'm not sure that we can
use this for a release. I will check with the powers that be.
But I would appreciate it if Wim and/or Markus could take
another look at the pack200 stuff...and the compatibility across
java versions, etc (as David Williams points to). One problem
I faced in doing this, however, was that the pack200 code was
called from within a Buckminster action (as can be seen from the
stack trace), and I don't know how (or even whether) this can be
configured to use some specific pack200 version.
Thanks,
Scott
[1] https://build.ecf-project.org/jenkins/job/R-HEAD-sdk.feature/185/
On 1/13/2016 9:28 AM, Scott Lewis wrote:
Ok I will ask that as well.
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ecf-dev
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ecf-dev
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ecf-dev
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ecf-dev
|
