It looks like the two packages truly(libressl-devel and libopenssl-devel)
can't co-exist on opensuse:

---------------------------------------------------------------------------------------------------------
$ docker pull opensuse:13.2
13.2: Pulling from opensuse
717905e6e6af: Pull complete
5b8dd08af89b: Already exists
Digest:
sha256:325785de46c5c706fc529f28d4f6f70db1b7d57f82a9d328ab945425959741e7
Status: Downloaded newer image for opensuse:13.2
$ docker run -ti --rm opensuse:13.2 bash
bash-4.2# zypper install libressl-devel libopenssl-devel
Retrieving repository 'NON-OSS' metadata
..............................................................................................................[done]
Building repository 'NON-OSS' cache
...................................................................................................................[done]
Retrieving repository 'OSS' metadata
..................................................................................................................[done]
Building repository 'OSS' cache
.......................................................................................................................[done]
Retrieving repository 'OSS Update' metadata
...........................................................................................................[done]
Building repository 'OSS Update' cache
................................................................................................................[done]
Retrieving repository 'Update Non-Oss' metadata
.......................................................................................................[done]
Building repository 'Update Non-Oss' cache
............................................................................................................[done]
Loading repository data...
Reading installed packages...
Resolving package dependencies...

Problem: libressl-devel-2.2.1-2.6.1.x86_64 conflicts with libopenssl-devel
provided by libopenssl-devel-1.0.1k-2.24.1.x86_64
 Solution 1: do not install libressl-devel-2.2.1-2.6.1.x86_64
 Solution 2: do not install libopenssl-devel-1.0.1k-2.24.1.x86_64

Choose from above solutions by number or cancel [1/2/c] (c):
---------------------------------------------------------------------------------------------------------

For the record libressl-devel is depended by libmysqlclient-devel
I have no idea how to proceed now, shall we upstream the problem?

2015-11-18 15:11 GMT+08:00 Konstantin Boudnik <[email protected]>:

> On Wed, Nov 18, 2015 at 02:54PM, Evans Ye wrote:
> > Well, I need to turn myself in.
>
> Doesn't matter man - it was a joke ;)
>
> > In fact that patch has been tested and +1ed by me,
> > but I remember my manual build was OK by then...
>
> With the complexities like that - this stuff happens, unfortunately. We
> already weeded out a bunch of issues by switching to standardized
> toolchains
> and build environments. I am pretty sure we'll figure out this one as well.
>
> > Anyhow, I can't understand why it has conflict when we only install
> > packages available from official repo...
>
> Yeah, that's weird ;( unless the official packages have some issues, which
> isn't likely I suppose.
>
> Cos
>
>
> > 2015-11-18 12:09 GMT+08:00 Konstantin Boudnik <[email protected]>:
> >
> > > Well, perhaps now Olaf won't brag as much ;)
> > >
> > > (Sorry, Olaf, couldn't resist - the timing was almost perfect ;)
> > >
> > > Cos
> > >
> > > On Wed, Nov 18, 2015 at 11:56AM, Evans Ye wrote:
> > > > Okay, it seems these extra packages introduced in BIGTOP-2120 brings
> up
> > > the
> > > > issue:
> > > >
> > > > "python-devel", "python-setuptools", "libxml2-devel",
> "libxslt-devel", "
> > > > cyrus-sasl-devel", "sqlite3-devel", "openldap2-devel",
> "libyaml-devel", "
> > > > krb5-devel", "asciidoc", "libmysqlclient-devel"
> > > >
> > > > 2015-11-18 11:19 GMT+08:00 Konstantin Boudnik <[email protected]>:
> > > >
> > > > > I haven't seen Peter for awhile, he might know the answer or have a
> > > fix for
> > > > > it.
> > > > >
> > > > > Cos
> > > > >
> > > > > On Wed, Nov 18, 2015 at 11:13AM, Evans Ye wrote:
> > > > > > You got it. The opensuse image is failing for a long while
> > > > > > (All the trunk images will be rebuilt after code change
> regardless
> > > > > whether
> > > > > > it's failing or not
> > > > > >
> http://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-Trunk/)
> > > > > >
> > > > > > The maven things is just some network issue which can be solved
> by
> > > rerun.
> > > > > > However, the package confliction is a bit more difficult to
> handle.
> > > > > >
> > > > > > The build was still ok back in Nov. 8
> > > > > >
> > > > >
> > >
> http://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-Trunk/BUILD_ENVIRONMENTS=opensuse-13.2,label=docker-slave-06/5/
> > > > > >
> > > > > > The only two changes during these days are:
> > > > > > 1. add gmp-devel
> > > > > > 2. remove krb5-mini
> > > > > >
> > > > >
> > >
> https://github.com/apache/bigtop/commits/master/bigtop_toolchain/manifests/packages.pp
> > > > > >
> > > > > > Which seems not related to me.
> > > > > > I don't have awswer yet and still looking into it...
> > > > > >
> > > > > > 2015-11-18 7:27 GMT+08:00 Konstantin Boudnik <[email protected]>:
> > > > > >
> > > > > > > Looking into the recent builds on Suse I see that pretty much
> all
> > > of
> > > > > them
> > > > > > > are
> > > > > > > failing for two reasons:
> > > > > > >  - mvn isn't found
> > > > > > >  - some lib requirements aren't met
> > > > > > >
> > > > > > > While the former seems like a small omission in the container,
> the
> > > > > other
> > > > > > > one
> > > > > > > looks like a bigger issue with the toolchain. I personally
> don't
> > > have
> > > > > any
> > > > > > > cycles to work on this.
> > > > > > >
> > > > > > > Thoughts?
> > > > > > >   Cos
> > > > > > >
> > > > > > > On Sat, Nov 14, 2015 at 11:00AM, Evans Ye wrote:
> > > > > > > > Yeah, that was caused by that images has been changed.
> > > > > > > > For some unknown reason the ant installation failed:
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > >
> > >
> http://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-Trunk/BUILD_ENVIRONMENTS=centos-7,label=docker-slave-06/7/console
> > > > > > > >
> > > > > > > > 14:40:11 ERROR 404: Not Found. [0m
> > > > > > > >  [91m [1;31mError: /usr/bin/wget
> > > > > > > >
> > > > >
> http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz
> > > > > > > > returned 8 instead of one of [0] [0m
> > > > > > > >  [0m [91m [1;31mError:
> > > > > > > > /Stage[main]/Bigtop_toolchain::Deps/Exec[/usr/bin/wget
> > > > > > > >
> > > > > > >
> > > > >
> > >
> http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz]/returns
> > > > > > > :
> > > > > > > > change from notrun to 0 failed: /usr/bin/wget
> > > > > > > >
> > > > >
> http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz
> > > > > > > > returned 8 instead of one of [0] [0m
> > > > > > > >  [0m [mNotice:
> > > /Stage[main]/Bigtop_toolchain::Deps/Exec[/usr/bin/wget
> > > > > > > >
> > > > > > >
> > > > >
> > >
> http://ftp.wayne.edu/apache//maven/maven-3/3.3.3/binaries/apache-maven-3.3.3-bin.tar.gz]/returns
> > > > > > > :
> > > > > > > > executed successfully [0m
> > > > > > > >
> > > > > > > >
> > > > > > > > But the build continue to do downstream image push and pull
> > > because
> > > > > > > > puppet apply returns 0 even with errors.
> > > > > > > >
> > > > > > > > Let me rerun this first and then try to add some thing
> prevent
> > > things
> > > > > > > > happened again.
> > > > > > > >
> > > > > > > >
> > > > > > > > 2015-11-14 9:20 GMT+08:00 Konstantin Boudnik <[email protected]
> >:
> > > > > > > >
> > > > > > > > > Looks like our docker images don't have ant anymore... I
> see
> > > (at
> > > > > least)
> > > > > > > > > datafu
> > > > > > > > > and solr builds failing on all platforms because of that...
> > > > > > > > >
> > > > > > > > > By looking into git history I don't see any evidences of
> it,
> > > but
> > > > > the
> > > > > > > builds
> > > > > > > > > are failing nonetheless... Thoughts?
> > > > > > > > >
> > > > > > > > > Cos
> > > > > > > > >
> > > > > > >
> > > > >
> > >
>

Reply via email to