Before we have an avalanche of "me-too" emails. The way you unsubscribe from an apache mailing list is to send a message to
dev-unsubscr...@mahout.apache.org (or change mahout for whatever list you want to unsubscribe from) Thanks, tg On Fri, Nov 1, 2019 at 2:56 PM Rastin Ken <rastin....@gmail.com> wrote: > Hi > May I unsubscribe from this forum? > > *Regards* > *Rastin* > > > On Tue, Oct 22, 2019 at 1:34 PM Andrew Palumbo <ap....@outlook.com> wrote: > > > Thanks, Tg. > > ________________________________ > > From: Trevor Grant <trevor.d.gr...@gmail.com> > > Sent: Tuesday, October 22, 2019 4:30 PM > > To: Andrew Palumbo <ap....@outlook.com> > > Cc: Mahout Dev List <dev@mahout.apache.org>; Dmitriy Lyubimov < > > dlyubi...@apache.org>; Andrew Musselman <andrew.mussel...@gmail.com>; > Pat > > Ferrel <p...@actionml.com>; Isabel Drost <isa...@apache.org> > > Subject: Re: Build failed in Jenkins: mahout-nightly #2299 > > > > I never got any additional build error notices. I'm +1 to utilizing > > derelict email addresses. > > > > On Tue, Oct 22, 2019 at 3:18 PM Andrew Palumbo <ap....@outlook.com > <mailto: > > ap....@outlook.com>> wrote: > > I'm actually not advocating for this, just bringing it up here. I'd > > actually like to get the distros working. But then Id like to get the > > Dockerfiles polished, and I'd like to get Some Terraform code in > /examples > > to launch on aws, and I'd like to move move some Real-time synthetic data > > runnining through the incubating DataSketches project into Drms to > compare > > their SVD approximation with our DSSVD's. Putting together a > > zepplin/apache everything/mahout AMI for examples... > > > > could keep going.. > > > > IMO it would be worth getting the distros working, so that we could at > > least have examples running. > > > > >>We do have staged binary artifacts, currently for the 14.1 release > > pegged to scala 2.12, spark 2.4.4, java 8 and maven 3.3.9+. We had > > touched on, in slack, the idea of a realease of these binaries, If I/we > > can't get this assembly together in a reasonable amount of time > > > > > > --andy > > > > ________________________________ > > From: Andrew Palumbo <ap....@outlook.com<mailto:ap....@outlook.com>> > > Sent: Tuesday, October 22, 2019 4:09 PM > > To: Mahout Dev List <dev@mahout.apache.org<mailto:dev@mahout.apache.org > >>; > > Dmitriy Lyubimov <dlyubi...@apache.org<mailto:dlyubi...@apache.org>>; > > Trevor Grant <trevor.d.gr...@gmail.com<mailto:trevor.d.gr...@gmail.com > >>; > > Andrew Musselman <andrew.mussel...@gmail.com<mailto: > > andrew.mussel...@gmail.com>>; Pat Ferrel <p...@actionml.com<mailto: > > p...@actionml.com>>; Isabel Drost <isa...@apache.org<mailto: > > isa...@apache.org>> > > Subject: Re: Build failed in Jenkins: mahout-nightly #2299 > > > > Trevor. Yeah- I did. thanks to microsoft. > > > > > > I filed a ticket w INFRA, Gavin McDonald, about it. we must enforce mvn > > 3.3.9.. . > > > > https://issues.apache.org/jira/browse/INFRA-19292 > > > > This email is from last week when i was working on this Thursday > > night/Friday morn. > > > > Have People been getting emails since? > > > > Also What do you guys think- should we change the email ti Issues@? > > rather than dev@? > > > > There is also a builds@ which I was unaware of.. I (we, some of the PMC) > > should to subscribe to it, as Gavin Pointed out on the ticket. > > > > I'm, going to do some mahout work today. Pretty sure I see the release > > error. > > > > also BTW. when I run. PRs from the refactored Branch (mahout-14.1), It is > > in the green... Maybe time I write up a formal PR to Merge that branch, I > > think that we should be able to release soon.. (I'm not sure that there > is > > a reason not to have this on master at this point. > > > > Was looking at the assembly last night again, and I have to do a > rollback, > > and test of what i think may be off in the bin.xml, and root pom. > > > > > > We do have staged binary artifacts, currently for the 14.1 release pegged > > to scala 2.12, spark 2.4.4, java 8 and maven 3.3.9+. We had touched > on, > > in slack, the idea of a realease of these binaries, If I/we can't get > > this assembly together in a reasonable abount of time > > > > > > > > @rawkintrevo, @akm, @pferrel, @Dmitriy Lyubimov<mailto: > > dlyubi...@apache.org> @Isabel Drost<mailto:isa...@apache.org>, @Mahout > > Dev List<mailto:dev@mahout.apache.org> thoughts? > > > > Thanks, > > > > > > Andy > > ________________________________ > > From: Trevor Grant <trevor.d.gr...@gmail.com<mailto: > > trevor.d.gr...@gmail.com>> > > Sent: Thursday, October 17, 2019 7:07 AM > > To: Mahout Dev List <dev@mahout.apache.org<mailto:dev@mahout.apache.org > >> > > Subject: Re: Build failed in Jenkins: mahout-nightly #2299 > > > > Guessing.... Palumbo turned this back on? > > > > Maybe set them to not send messages to dev until we get the Jenkins build > > working right again. > > > > > > On Thu, Oct 17, 2019 at 5:38 AM Apache Jenkins Server < > > jenk...@builds.apache.org<mailto:jenk...@builds.apache.org>> wrote: > > > > > See < > https://builds.apache.org/job/mahout-nightly/2299/display/redirect> > > > > > > Changes: > > > > > > > > > ------------------------------------------ > > > Started by user apalumbo > > > Running as SYSTEM > > > [EnvInject] - Loading node environment variables. > > > Building remotely on H31 (ubuntu) in workspace < > > > https://builds.apache.org/job/mahout-nightly/ws/> > > > ERROR: A Maven installation needs to be available for this project to > be > > > built.Either your server has no Maven installations defined, or the > > > requested Maven version does not exist. > > > Retrying after 10 seconds > > > ERROR: A Maven installation needs to be available for this project to > be > > > built.Either your server has no Maven installations defined, or the > > > requested Maven version does not exist. > > > Retrying after 10 seconds > > > ERROR: A Maven installation needs to be available for this project to > be > > > built.Either your server has no Maven installations defined, or the > > > requested Maven version does not exist. > > > > > >