[GitHub] bigtop pull request #188: BIGTOP-2706 Apex package does not run successfully...

Github user chinmaykolhatkar commented on a diff in the pull request: https://github.com/apache/bigtop/pull/188#discussion_r107836097 --- Diff: bigtop-packages/src/common/apex/do-component-build --- @@ -28,6 +28,9 @@ command -v mvn > /dev/null 2>&1 || { # Build apex mvn

[GitHub] bigtop pull request #189: BIGTOP-2712: Juju CI driven updates

GitHub user kwmonroe opened a pull request: https://github.com/apache/bigtop/pull/189 BIGTOP-2712: Juju CI driven updates The original point of this branch was to refresh the hbase charm (readme was out-of-date, needed lint love). However, as soon as ran CI on this and recent

Re: Build failed due to OpenJDK 1.8.0_121 changes

Here is the link for 1.8.0_111 https://launchpad.net/~openjdk-r/+archive/ubuntu/security/+build/11087717 Thanks, Ganesh On Thu, Mar 23, 2017 at 3:28 PM, Olaf Flebbe wrote: > >> > >> So for the incoming 1.2.0 release, to fix this on aarch64/ubuntu-16.04 I > >> see two ways: >

Releasing 1.2 for non-x86 architectures

Hi! recent issues surrounding builds on two of our two non-x86 platforms got me thinking that while it is fun to build on them (to iron out kinds in JDK and what not) we don't actually have to release the packages for most of the projects since all those are arch independent. The only ones that

Re: Build failed due to OpenJDK 1.8.0_121 changes

> Am 23.03.2017 um 21:33 schrieb Roman Shaposhnik : > > There's no 111 :-( Yep, ubuntu seems to have replaced all 111 packages by 121. And yes, our current docker image still has 111. My-o-my. Guess going back is no option, at least not without compiling java ourself or

Re: Build failed due to OpenJDK 1.8.0_121 changes

There's no 111 :-( Jun, Naresh, Ganesh, out of the list available on the URL Olaf provided -- what should we pick? Thanks, Roman. On Thu, Mar 23, 2017 at 1:28 PM, Olaf Flebbe wrote: >>> >>> So for the incoming 1.2.0 release, to fix this on aarch64/ubuntu-16.04 I >>> see two

Re: Build failed due to OpenJDK 1.8.0_121 changes

>> >> So for the incoming 1.2.0 release, to fix this on aarch64/ubuntu-16.04 I >> see two ways: >> 1. Downgrade open-jdk to 1.8.0_111. This needs to change bigtop_toolchain/ >> manifests/jdk.pp > > I'd vote for this option. But I've got to ask: where do I get that exact > version > for ubuntu

Re: Build failed due to OpenJDK 1.8.0_121 changes

On Thu, Mar 23, 2017 at 7:36 AM, Ganesh Raju wrote: > Forwarding to dev mailing list. Any thoughts ? > > Thanks > Ganesh Raju > > > -- Forwarded message -- > From: Jun He > Date: Thu, Mar 23, 2017 at 5:10 AM > Subject: Build failed due

[GitHub] bigtop pull request #188: BIGTOP-2706 Apex package does not run successfully...

Github user c0s commented on a diff in the pull request: https://github.com/apache/bigtop/pull/188#discussion_r107769130 --- Diff: bigtop-packages/src/common/apex/do-component-build --- @@ -28,6 +28,9 @@ command -v mvn > /dev/null 2>&1 || { # Build apex mvn clean package

Re: Build failed due to OpenJDK 1.8.0_121 changes

With any luck we are going to upgrade to Ignite 1.9 which has this issue fixed. -- Take care, Konstantin (Cos) Boudnik 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622 Disclaimer: Opinions expressed in this email are those of the author, and do not necessarily represent the views of any

Fwd: Build failed due to OpenJDK 1.8.0_121 changes

Forwarding to dev mailing list. Any thoughts ? Thanks Ganesh Raju -- Forwarded message -- From: Jun He Date: Thu, Mar 23, 2017 at 5:10 AM Subject: Build failed due to OpenJDK 1.8.0_121 changes To: Roman Shaposhnik , Ganesh Raju

Re: Dockerhub creds

I will answer you privately for the security sake -- Take care, Konstantin (Cos) Boudnik 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622 Disclaimer: Opinions expressed in this email are those of the author, and do not necessarily represent the views of any company the author might be