OpenJDK 1.8.0/SeaMonkey 2.48 incompatibility on Leap 42.3

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

OpenJDK 1.8.0/SeaMonkey 2.48 incompatibility on Leap 42.3

Tristan Miller
Dear all,

It seems it is not possible to install the latest official release of
OpenJDK (1.8.0, from the update repository) together with the latest
official release of SeaMonkey (2.48, from the mozilla repository) on
Leap 42.3.

Zypper and YaST tell me that this is because seamonkey-2.48-1.3.x86_64
requires mozilla-nspr >= 4.15, whereas
java-1_8_0-openjdk-headless-1.8.0.144-13.3.x86_64 requires
mozilla-nss = 3.28.5.

This incompatibility does not seem to exist on Tumbleweed, where both
packages live together in peace and harmony.  This leads me to believe
it's a packaging problem.  Where would be the best place to report this?

Regards,
Tristan

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
                  Tristan Miller
Free Software developer, ferret herder, logologist
             https://logological.org/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

attachment0 (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: OpenJDK 1.8.0/SeaMonkey 2.48 incompatibility on Leap 42.3

Simon Lees-3


On 31/08/17 22:24, Tristan Miller wrote:

> Dear all,
>
> It seems it is not possible to install the latest official release of
> OpenJDK (1.8.0, from the update repository) together with the latest
> official release of SeaMonkey (2.48, from the mozilla repository) on
> Leap 42.3.
>
> Zypper and YaST tell me that this is because seamonkey-2.48-1.3.x86_64
> requires mozilla-nspr >= 4.15, whereas
> java-1_8_0-openjdk-headless-1.8.0.144-13.3.x86_64 requires
> mozilla-nss = 3.28.5.
>
> This incompatibility does not seem to exist on Tumbleweed, where both
> packages live together in peace and harmony.  This leads me to believe
> it's a packaging problem.  Where would be the best place to report this?
>
> Regards,
> Tristan
>
This is likely not a packaging bug, nor a bug at all, its a design
decision we have taken with Leap to stay at a fixed version of many
software components for stability, as such its not going to always be
possible to install the latest versions of software like seamonkey on
leap as we don't meet there version requirements for dependencies.

In openSUSE we only give you 2 options, run sometimes older software
that was tested together with other software from a similar time to
create a "Stable" Distro ie Leap, or you can run the latest of
everything being tumbleweed (which is mostly quite stable because most
developers of most software run the latest everything anyway).

We don't officially support a middle position ie Leap with some newer
apps because its much harder due to issues like the one you are seeing.

--

Simon Lees (Simotek)                            http://simotek.net

Emergency Update Team                           keybase.io/simotek
SUSE Linux                           Adelaide Australia, UTC+10:30
GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B


signature.asc (499 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: OpenJDK 1.8.0/SeaMonkey 2.48 incompatibility on Leap 42.3

Felix Miata-3
Simon Lees composed on 2017-09-02 11:47 (UTC+0930):
...
> Tristan Miller wrote:

>> It seems it is not possible to install the latest official release of
>> OpenJDK (1.8.0, from the update repository) together with the latest
>> official release of SeaMonkey (2.48, from the mozilla repository) on
>> Leap 42.3.

FWIW, the SeaMonkey 2.48 with which I write this on openSUSE came from
https://archive.mozilla.org/pub/seamonkey/releases/2.48/contrib/

>> Zypper and YaST tell me that this is because seamonkey-2.48-1.3.x86_64
>> requires mozilla-nspr >= 4.15, whereas
>> java-1_8_0-openjdk-headless-1.8.0.144-13.3.x86_64 requires
>> mozilla-nss = 3.28.5.
...
> This is likely not a packaging bug, nor a bug at all, its a design
> decision we have taken with Leap to stay at a fixed version of many
> software components for stability, as such its not going to always be
> possible to install the latest versions of software like seamonkey on
> leap as we don't meet there version requirements for dependencies.

Surely something must be wrong with *something*, if not packaging, that any
java* package can require any specific mozilla* (Portable Runtime) package that
can block keeping a web browser, particularly a mozilla browser, current.
"Latest" SeaMonkey isn't even current. Current arguably would be the yet to be
released SeaMonkey 2.49.x, equivalent to Firefox ESR52/rv52, which *is* in
standard 42.3 update repo.
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: OpenJDK 1.8.0/SeaMonkey 2.48 incompatibility on Leap 42.3

Wolfgang Rosenauer-4
In reply to this post by Tristan Miller
Hi,

Am 31.08.2017 um 14:54 schrieb Tristan Miller:
> It seems it is not possible to install the latest official release of
> OpenJDK (1.8.0, from the update repository) together with the latest
> official release of SeaMonkey (2.48, from the mozilla repository) on
> Leap 42.3.
>
> Zypper and YaST tell me that this is because seamonkey-2.48-1.3.x86_64
> requires mozilla-nspr >= 4.15, whereas
> java-1_8_0-openjdk-headless-1.8.0.144-13.3.x86_64 requires
> mozilla-nss = 3.28.5.

Is this really the correct message? I do not see a correlation between
mozilla-nspr and mozilla-nss like described above.

I think what you see is the outfall of
https://bugzilla.suse.com/show_bug.cgi?id=1026102

In the current situation you can only ignore the Java<->NSS dependency and
update NSS as required by Seamonkey (or any other package from mozilla).
Your probability that Java still works is 99% anyway.


Wolfgang

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: OpenJDK 1.8.0/SeaMonkey 2.48 incompatibility on Leap 42.3

Manfred Hollstein
Moin,

On Sun, 03 Sep 2017, 08:08:04 +0200, Wolfgang Rosenauer wrote:

> Hi,
>
> Am 31.08.2017 um 14:54 schrieb Tristan Miller:
> > It seems it is not possible to install the latest official release of
> > OpenJDK (1.8.0, from the update repository) together with the latest
> > official release of SeaMonkey (2.48, from the mozilla repository) on
> > Leap 42.3.
> >
> > Zypper and YaST tell me that this is because seamonkey-2.48-1.3.x86_64
> > requires mozilla-nspr >= 4.15, whereas
> > java-1_8_0-openjdk-headless-1.8.0.144-13.3.x86_64 requires
> > mozilla-nss = 3.28.5.
>
> Is this really the correct message? I do not see a correlation between
> mozilla-nspr and mozilla-nss like described above.
>
> I think what you see is the outfall of
> https://bugzilla.suse.com/show_bug.cgi?id=1026102
>
> In the current situation you can only ignore the Java<->NSS dependency and
> update NSS as required by Seamonkey (or any other package from mozilla).
> Your probability that Java still works is 99% anyway.
in addition you could also add my home repo which I use to rebuild all
java-1_8_0-openjdk packages against Wolfgang's mozilla repo. This way I
can always use the latest mozilla packages.

I do this for openSUSE_Leap_42.2 and _42.3; add the repo as follows:

  zypper ar home:mhnovell:Rebuilds:openSUSE_Leap_42.2 java4mozilla
  zypper ar home:mhnovell:Rebuilds:openSUSE_Leap_42.3 java4mozilla

> Wolfgang

HTH, cheers.

l8er
manfred

signature.asc (188 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: OpenJDK 1.8.0/SeaMonkey 2.48 incompatibility on Leap 42.3

Tristan Miller
In reply to this post by Wolfgang Rosenauer-4
Dear Wolfgang,

On Sun, 3 Sep 2017 08:08:04 +0200, Wolfgang Rosenauer
<[hidden email]> wrote:

> Am 31.08.2017 um 14:54 schrieb Tristan Miller:
> > It seems it is not possible to install the latest official release
> > of OpenJDK (1.8.0, from the update repository) together with the
> > latest official release of SeaMonkey (2.48, from the mozilla
> > repository) on Leap 42.3.
> >
> > Zypper and YaST tell me that this is because
> > seamonkey-2.48-1.3.x86_64 requires mozilla-nspr >= 4.15, whereas
> > java-1_8_0-openjdk-headless-1.8.0.144-13.3.x86_64 requires
> > mozilla-nss = 3.28.5.  
>
> Is this really the correct message? I do not see a correlation between
> mozilla-nspr and mozilla-nss like described above.
No, sorry, it's not the correct message.  I was trying to summarize
what was actually a complicated set of conflicts.  Looks like I didn't
notice the difference between "mozilla-nspr" and "mozilla-nss".

The actual conflict message from trying to install SeaMonkey 2.48 is as
follows:

seamonkey-2.48-1.3.x86_64 requires mozilla-nspr >= 4.15, but this
requirement cannot be provided uninstallable providers:
mozilla-nspr-4.15-1.1.i586[mozilla]
mozilla-nspr-4.15-1.1.x86_64[mozilla] [ ] do not install
seamonkey-2.48-1.3.x86_64

    [ ] break seamonkey-2.48-1.3.x86_64 by ignoring some of its
    dependencies

    [ ] Following actions will be done:
install mozilla-nspr-4.15-1.1.x86_64 (with vendor change)
  openSUSE  -->  obs://build.opensuse.org/mozilla
install mozilla-nspr-devel-4.15-1.1.x86_64 (with vendor change)
  openSUSE  -->  obs://build.opensuse.org/mozilla
install mozilla-nss-devel-3.31-1.1.x86_64 (with vendor change)
  openSUSE  -->  obs://build.opensuse.org/mozilla
deinstallation of java-1_8_0-openjdk-headless-1.8.0.144-13.3.x86_64
deinstallation of java-1_8_0-openjdk-1.8.0.144-13.3.x86_64
deinstallation of java-1_8_0-openjdk-devel-1.8.0.144-13.3.x86_64


If the vendor change is accepted, then a second conflict arises:

seamonkey-2.48-1.3.x86_64 requires mozilla-nss >= 3.31, but this
requirement cannot be provided uninstallable providers:
mozilla-nss-3.31-1.1.i586[mozilla] mozilla-nss-3.31-1.1.x86_64[mozilla]
    [ ] break seamonkey-2.48-1.3.x86_64 by ignoring some of its
dependencies

    [ ] Following actions will be done:
do not install mozilla-nss-devel-3.31-1.1.x86_64
do not install seamonkey-2.48-1.3.x86_64
    [ ] Following actions will be done:
do not install seamonkey-2.48-1.3.x86_64
do not install mozilla-nss-devel-3.31-1.1.x86_64
    [ ] install mozilla-nss-3.31-1.1.x86_64 (with vendor change)
  openSUSE  -->  obs://build.opensuse.org/mozilla


Trying to switch all packages to the "mozilla" repository results in an
even more complicated set of conflicts.  No matter what resolution
path is followed, it doesn't seem possible to have both SeaMonkey 2.48
and OpenJDK 1.8.0 installed at the same time.

As Felix mentioned, there is no problem running the 64-bit "contrib"
build from the SeaMonkey website.

> I think what you see is the outfall of
> https://bugzilla.suse.com/show_bug.cgi?id=1026102

I can't pretend to understand the entirety of that issue, but I'll take
your word for it that it's the cause.

> In the current situation you can only ignore the Java<->NSS
> dependency and update NSS as required by Seamonkey (or any other
> package from mozilla). Your probability that Java still works is 99%
> anyway.

OK, I'll give it a try.  In the worst case, I can revert to SeaMonkey
2.46.  (I can't live without OpenJDK 1.8.0 as I need to develop in Java
8.)

Regards,
Tristan

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
                  Tristan Miller
Free Software developer, ferret herder, logologist
             https://logological.org/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

attachment0 (849 bytes) Download Attachment