[jira] [Created] (BIGTOP-3330) oozie and oozie-client deb packages try to install the same jars in the same dir

2020-03-20 Thread Luca Toscano (Jira)
Luca Toscano created BIGTOP-3330:


 Summary: oozie and oozie-client deb packages try to install the 
same jars in the same dir
 Key: BIGTOP-3330
 URL: https://issues.apache.org/jira/browse/BIGTOP-3330
 Project: Bigtop
  Issue Type: Bug
Affects Versions: 1.4.0
Reporter: Luca Toscano


Hi!

While installing oozie I get the following error:
Unpacking oozie (4.3.0-2) ...
dpkg: error processing archive /var/cache/apt/archives/oozie_4.3.0-2_all.deb 
(--unpack):
 trying to overwrite '/usr/lib/oozie/lib/accessors-smart-1.2.jar', which is 
also in package oozie-client 4.3.0-2
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/oozie_4.3.0-2_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


Re: Release-1.4.0

2020-03-20 Thread Luca Toscano
Worked nicely, thanks!

Il giorno mer 18 mar 2020 alle ore 19:30 Evans Ye 
ha scritto:
>
> You just need to change a bit in bigtop.bom:
>
> -  version { base = '2.10.0'; pkg = base; release = 1 }
> +  version { base = '2.10.0'; pkg = base; release = 2 }
>
>
> Luca Toscano  於 2020年3月18日 週三 下午6:29寫道:
>
> > Hi everybody,
> >
> > I have successfully rebuild hadoop/oozie packages via gradlew/docker
> > from branch-1.4, but now I am wondering if there is a way to force a
> > specific version of the packages created. For example, now in my
> > internal apt repo I have the 'hadoop' package with version 2.8.5-1
> > (synced from the bigtop repos) and the same version for the package
> > build by me. I'd like to force the version of the new packages to
> > something like 2.8.5-2 (or similar), but didn't find a quick way yet
> > (usually I modify the changelog debian file but in this case it is
> > autogenerated). Any suggestions?
> >
> > Thanks in advance,
> >
> > Luca
> >
> > Il giorno lun 9 mar 2020 alle ore 08:38 Luca Toscano
> >  ha scritto:
> > >
> > > If possible I'd ask to consider also
> > > https://github.com/apache/bigtop/pull/610 for a branch-1.4 backport
> > > (if the code looks good).
> > >
> > > Thanks!
> > >
> > > Luca
> > >
> > > Il giorno dom 8 mar 2020 alle ore 20:07 Olaf Flebbe  ha
> > scritto:
> > > >
> > > > Thanks Luca, Evans.
> > > >
> > > > Release Tags are pushed and two commits to branch-1.4 as well.
> > > >
> > > > Olaf
> > > >
> > > > Am 08.03.20 um 13:52 schrieb Luca Toscano:
> > > > > Thanks a lot Olaf!
> > > > >
> > > > > Il giorno dom 8 mar 2020 alle ore 10:21 Evans Ye  > >
> > > > > ha scritto:
> > > > >>
> > > > >> It seems that 1.3.0 does not have the final release tag as well.
> > > > >> I think make it consistent by adding 1.4.0 and 1.3.0 release tag
> > would be a
> > > > >> great.
> > > > >> Thanks for discovering this.
> > > > >>
> > > > >> Evans
> > > > >>
> > > > >> Olaf Flebbe  於 2020年3月8日 週日 下午5:08寫道:
> > > > >>
> > > > >>> Hi,
> > > > >>>
> > > > >>> since Luca Toscano asked, I am considering to add two bugfixes to
> > the
> > > > >>> 1.4 branch with BIGTOP-3308.  I was checking tags first:
> > > > >>>
> > > > >>> We have
> > > > >>> release-1.4.0-RC0
> > > > >>> release-1.4.0-RC1
> > > > >>> but no
> > > > >>> release-1.4.0
> > > > >>> tag
> > > > >>>
> > > > >>> Is it ok to push the "release-1.4.0" tag to latest commit on
> > branch-1.4?
> > > > >>>
> > > > >>> Additionally I would add the needed commits to it as well ?
> > > > >>>
> > > > >>> I am not considering a bugfix release, though.
> > > > >>>
> > > > >>> WDYT ?
> > > > >>>
> > > > >>> Best
> > > > >>>   Olaf
> > > > >>>
> > > > >>>
> > > > >>>
> >


[jira] [Created] (BIGTOP-3329) Bump ambari to v2.7.5

2020-03-20 Thread Jun He (Jira)
Jun He created BIGTOP-3329:
--

 Summary: Bump ambari to v2.7.5
 Key: BIGTOP-3329
 URL: https://issues.apache.org/jira/browse/BIGTOP-3329
 Project: Bigtop
  Issue Type: Improvement
  Components: general
Affects Versions: 1.4.0
Reporter: Jun He


Current ambari uses v2.6.1 which was released in Dec 2017.
Bump this to latest v2.7.5



--
This message was sent by Atlassian Jira
(v8.3.4#803005)