[Bug 216100] New: Various dependency problems with mozilla-xulrunner/gecko based applications.
https://bugzilla.novell.com/show_bug.cgi?id=216100 Summary: Various dependency problems with mozilla-xulrunner/gecko based applications. Product: openSUSE 10.2 Version: Beta 1 Platform: All OS/Version: All Status: NEW Severity: Major Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: andreas.hanke@gmx-topmail.de QAContact: qa@suse.de The packages seamonkey mozilla-xulrunner180 mozilla-xulrunner181 all provide (in the rpm "Provides" sense) Gecko libraries like libgtkembedmoz.so & friends, but only the xulrunners can actually be used for Gecko embedding, and there are two of these. This is problematic; I have identified the following problems so far: (1) seamonkey.spec contains code to filter some libraries out, but it does not cover everyting, most specifically it does not cover libgtkembedmoz.so. (2) Most GNOME applications that use Gecko have an explicit dependency on a specific xulrunner version, which works around the problem and might be "good enough". (3) liferea does not have an explicit dependency on a specific xulrunner version or even xulrunner in general. Therefore, dependency-wise, even seamonkey can fulfill the requirements of liferea. This is undefined behaviour and broken. (4) The situation with gnome-web-photo is similar to that of liferea, but luckily it is linked to libxul.so which only the two xulrunners provide, so the behavior is a little bit less undefined as with liferea. (5) epiphany is totally broken because it has rpm "Requires: mozilla-xulrunner181" even though the binaries in the package are clearly linked to mozilla-xulrunner180. This causes bug 204907. What needs to be done: (1) Decide whether to filter the Gecko libraries out of the "Provides" of seamonkey. It's not strictly necessary, but can maybe prevent future problems if more xulrunners and Gecko based applications are added. (2) Fix gnome-web-photo and liferea to have a "Requires" on the xulrunner version that was used to build them. (3) Fix epiphany which already has an explicit dependency on xulrunner to have a dependency on the _right_ one. I don't know which of the two xulrunners was really intended. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=216100 aj@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jpr@novell.com, cthiel@novell.com, aj@novell.com AssignedTo|bnc-team- |sbrabec@novell.com |screening@forge.provo.novell| |.com | ------- Comment #1 from aj@novell.com 2006-10-30 06:48 MST ------- Stanislav, can you take care of this, please? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=216100 sbrabec@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Comment #2 from sbrabec@novell.com 2006-10-31 05:43 MST ------- Yes, I think, that removal of unversioned gecko Provides from all packages is a good idea. Each package then must filter gecko Requires and explicitly specify, which version of gecko it requires. It will break some packages, but the fix will be easy and clean. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=216100 ------- Comment #3 from andreas.hanke@gmx-topmail.de 2006-10-31 14:05 MST ------- No, what I had in mind was: - filter gecko Provides from seamonkey, but not from the xulrunners and not from Requires of other packages; - add versioned Requires too all Gecko-embedding packages in _addition_ to the autogenerated Requires. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=216100 ------- Comment #4 from andreas.hanke@gmx-topmail.de 2006-11-01 00:40 MST ------- Just for clarity: Removing the rpm auto-generated dependencies for all gecko apps is not what I meant. These are not a problem, the only problem is that they are matching multiple packages. Therefore the packages need fixed "BuildRequires" and "Requires" in addition to the rpm auto-generated dependencies. But removing the gecko provides from the xulrunners is not what I meant, this would break 3rd party packages. Only for seamonkey this makes sense because seamonkey does not really "provide" them, only the xulrunners do, but these really do. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=216100 ------- Comment #5 from sbrabec@novell.com 2006-11-01 06:58 MST ------- OK. Your solution is technically more correct (and simpler to implement). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=216100 ------- Comment #6 from sbrabec@novell.com 2006-11-01 07:11 MST ------- Packages, which currently contain libgtkembedmoz.so: mozilla-xulrunner180, mozilla-xulrunner181, nvu, seamonkey Packages, which currently provide libgtkembedmoz.so: mozilla-xulrunner180, mozilla-xulrunner181, seamonkey Packages, which currently require libgtkembedmoz.so: blam, devhelp, epiphany, epiphany-extensions, gnome-web-photo, liferea, yelp List is valid also for libxpcom.so, but it is alsos required by seamonkey-* subpackages. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=216100 sbrabec@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |jpr@novell.com ------- Comment #7 from sbrabec@novell.com 2006-11-07 10:39 MST ------- I am just testing packages and it seems, that epiphany is built with 181. Other application can be built with 181, too, without any compilation problems. Should we prefer 180 or 181 for all packages or should we keep half of gnome linked with 180 and other half with 181 (which will probably increase memory requirements)? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=216100 sbrabec@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|jpr@novell.com | ------- Comment #8 from sbrabec@novell.com 2006-11-07 10:54 MST ------- It seems to be confusing. epiphany: BuildRequires: ... gecko-sdk ... %if %suse_version > 1010 BuildRequires: mozilla-xulrunner181 .. %endif gecko-sdk is provided by mozilla-xulrunner180-devel. It means, that it tries to load both geckos for build. But in reality it links with 180. So everything is linked with 180. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=216100 ------- Comment #9 from andreas.hanke@gmx-topmail.de 2006-11-07 11:08 MST ------- Yes, epiphany is broken in a way that it claims to be built against 181, but is in reality built against 180 (this can be proven by looking at the RPATH of the binary). That is exactly what led to this bug report: Cleanup of all gecko applications. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=216100 sbrabec@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Comment #10 from sbrabec@novell.com 2006-11-07 11:28 MST ------- All packages can be linked with both 180 and 181. 181 was probably intended for epiphany and can be used for all other packages. So I am doing so. If it will cause any problems, it is simply possible for >= 10.2 to define gecko version in the spec file by: %define xulrunner_version 181 Done for packages: blam, devhelp, epiphany, epiphany-extensions, gecko-sharp, gnome-web-photo, liferea, yelp Note that it may be superfluous for gecko-sharp, which seems to be gecko-version independent and the requirement should be "any xulrunner". But it seems not to break anything to hardcode 181 just now (blam requires it, too). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=216100 gekker@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mrmazda@ij.net ------- Comment #11 from gekker@novell.com 2006-11-07 15:17 MST ------- *** Bug 204907 has been marked as a duplicate of this bug. *** -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=216100 ------- Comment #12 from mrmazda@ij.net 2006-11-07 15:56 MST ------- Gary, why do you dupe the first bug filed to a newer bug? I should file another bug about this and then dupe this one to that. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=216100 andreas.hanke@gmx-topmail.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | ------- Comment #13 from andreas.hanke@gmx-topmail.de 2006-11-10 05:14 MST ------- I have read all related commit messages and it is mostly fine. I have identified one problem, however. Give me some time to write it down together with a solution. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=216100 ------- Comment #14 from andreas.hanke@gmx-topmail.de 2006-11-10 08:45 MST ------- What you're doing for nvu and seamonkey now is: (1) Remove all Provides that come from a private library in the package. (2) Remove all Requires that come from a private library in the package. (1) is correct, but (2) is not. The correct semantics here is: Remove all Requires on a private library which is in the same package. Otherwise you lose some legitimate Requires while keeping some illegitimate ones in. I spent several hours today writing something and didn't come up with something better than what nvu previously had. What nvu previously had was exactly correct: Remove all Provides from libraries in the package, and remove all Requires on (ON, not FROM) libraries files which are part of the same package. Simply revert the last change to nvu and copy the logic from there to seamonkey. That's it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=216100 sbrabec@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED ------- Comment #15 from sbrabec@novell.com 2006-11-15 09:29 MST ------- Fixed for nvu and now also for seamonkey. I hope, that now it is really correct. %if %suse_version >= 1000 cat << EOF > %{my_provides} #! /bin/sh grep -v ^$RPM_BUILD_ROOT/usr/%{_lib}/seamonkey | /usr/lib/rpm/find-provides EOF cat << EOF > %{my_requires} #! /bin/sh /usr/lib/rpm/find-requires | while read ; do if ! test -e $RPM_BUILD_ROOT/usr/%{_lib}/seamonkey/\${REPLY%%%%(*} ; then #) echo "\$REPLY" fi done EOF chmod 755 %{my_provides} %{my_requires} %define __find_provides %{my_provides} %define __find_requires %{my_requires} %endif -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=216100 aj@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | ------- Comment #16 from aj@novell.com 2006-11-15 12:02 MST ------- thanks a lot! Does this mean we can drop mozilla-xulrunner180 completely? Could you do so, please? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=216100 sbrabec@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- BugsThisDependsOn| |219354 ------- Comment #17 from sbrabec@novell.com 2006-11-16 03:00 MST ------- Not yet. We must be sure, that: - Bug 219354 is fixed. - All packages work correctly with 181. - No third party package require 180. Tested & works with 181: devhelp, epiphany, epiphany-extensions, liferea (works with "Unhandled property: 12 border-collapse", but once crashed), yelp (shows lots of probably unrelated warnings) Tested & crashes: blam (bug 215499) Untested: gnome-web-photo -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=216100 wolfgang@rosenauer.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wolfgang@rosenauer.org ------- Comment #18 from wolfgang@rosenauer.org 2006-11-16 03:41 MST ------- (In reply to comment #8)
It seems to be confusing. epiphany:
BuildRequires: ... gecko-sdk ... %if %suse_version > 1010 BuildRequires: mozilla-xulrunner181 ... %endif
gecko-sdk is provided by mozilla-xulrunner180-devel. It means, that it tries to load both geckos for build. But in reality it links with 180.
So everything is linked with 180.
Unfortunately I've missed this bug up to now. I wonder if people were reading my mails a few months ago. (No I'm not wondering since it's clear that they haven't.) http://lists.opensuse.org/opensuse-packaging/2006-08/msg00046.html (and I'm pretty sure I've sent another one to gnome-maintainers) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=216100 Bug 216100 depends on bug 219354, which changed state. Bug 219354 Summary: Registration requires browser to run (but misses package for that) https://bugzilla.novell.com/show_bug.cgi?id=219354 What |Old Value |New Value ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=216100 ------- Comment #19 from andreas.hanke@gmx-topmail.de 2006-11-21 20:51 MST ------- May I carefully ask for the status here? - The yastbrowser works with *181, actually it even requires *181. - Stanislav has tested all dependent packages and says that all except blam and gnome-web-photo are working. - I have tested gnome-web-photo and it works for me. - I have a strong indication that the blam crash is unrelated to the xulrunner version because basically the same report exists also in the Debian bugtracker (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=385875) and Debian still uses *180. IMHO you should really try to avoid shipping two xulrunner versions, as it means double work and double bandwidth usage in case of a security update. Standardizing on a single version simplifies everything a lot. What should be done IMHO is: - Smoke-test gnome-web-photo. Do gnome-web-photo http://www.opensuse.org/ opensuse.png gnome-web-photo https://bugzilla.novell.com/show_bug.cgi?id=216100 bugzilla.png If you get PNG files, the application can be considered basically working. - Do a test build of gecko-sharp and blam against the old xulrunner package on x86_64. It must be x86_64 because the crash doesn't happen on i586. If this one crashes, too, then the xulrunner version is not the problem and there is no value in keeping the *180 package around. - If the above tests succeed, transfer the compatibility Provides/Obsoletes from *180 to *181 and get rid of *180 for good. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=216100 sbrabec@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |ASSIGNED ------- Comment #20 from sbrabec@novell.com 2006-11-22 08:16 MST ------- Tested & works with 181: gnome-web-photo Tested & crashes consistently with both 180 and 181: blam (bug 215499) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=216100 sbrabec@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |aj@novell.com ------- Comment #21 from sbrabec@novell.com 2006-11-22 08:18 MST ------- AFAIK, no package depends on mozilla-xulrunner-180 any more. Should we add Obsoletes (not Provides) to 181 and drop 180 for 10.2 or should we do it for 10.3? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=216100 aj@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Info Provider|aj@novell.com |ro@novell.com ------- Comment #22 from aj@novell.com 2006-11-22 08:22 MST ------- drop 180 for 10.2! Rudi, do you agree? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=216100 ro@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|ro@novell.com | ------- Comment #23 from ro@novell.com 2006-11-22 08:30 MST ------- I'm all for dropping it now. # whatdependson mozilla-xulrunner180 - no dependent package found -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=216100 ------- Comment #24 from andreas.hanke@gmx-topmail.de 2006-11-22 08:38 MST ------- Don't forget to transfer the "Obsoletes" tags from *180 to *181 for a smooth upgrade path: mozilla-xulrunner181 obsoletes mozilla-xulrunner mozilla-xulrunner181-devel obsoletes gecko-sdk -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=216100 ------- Comment #26 from wolfgang@rosenauer.org 2006-11-22 23:40 MST ------- nit: we never had a mozilla-xulrunner-l10n package ;-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com