What's the deal with all of the new dependencies for xulrunner-devel in the last update? I'm updating my servers and the update for xulrunner-devel is forcing me to install 43 new packages! Is this a packaging problem, or are all of those packages really needed?
For the moment, I've been removing xulrunner-devel from my machines to avoid the problem. I figure since it is a development package, I can always reinstall it later if I need it.
Bowie
From: Bowie Bailey Bowie_Bailey@BUC.com
What's the deal with all of the new dependencies for xulrunner-devel in the last update? I'm updating my servers and the update for
Dunno, but: # yum install xulrunner-devel ... Installing: xulrunner-devel i386 1.9.2.4-9.el5 updates 4.1 M Installing for dependencies: libXt-devel i386 1.0.2-3.2.el5 base 330 k libnotify-devel i386 0.4.2-6.el5 base 19 k startup-notification-devel i386 0.8-4.1 base 8.6 k ... Install 4 Package(s) Upgrade 0 Package(s)
Maybe you were not up to date on many packages?
JD
John Doe wrote:
From: Bowie Bailey Bowie_Bailey@BUC.com
What's the deal with all of the new dependencies for xulrunner-devel in the last update? I'm updating my servers and the update for
Dunno, but: # yum install xulrunner-devel ... Installing: xulrunner-devel i386 1.9.2.4-9.el5 updates 4.1 M Installing for dependencies: libXt-devel i386 1.0.2-3.2.el5 base 330 k libnotify-devel i386 0.4.2-6.el5 base 19 k startup-notification-devel i386 0.8-4.1 base 8.6 k ... Install 4 Package(s) Upgrade 0 Package(s)
Maybe you were not up to date on many packages?
Maybe you already had the dependencies installed for something else. What I'm seeing is that I already had an older version of xulrunner-devel installed without all of the dependencies and then when I do an update to the newer version, I get an extra 43 dependencies.
Since I don't need it (AFAIK), I just removed the package and that solved (or at least worked around) the problem. But it still doesn't make sense. A new version of a package sometimes has a few new dependencies, but 43 is a bit much.
On 01/07/2010 15:50, Bowie Bailey wrote:
Since I don't need it (AFAIK), I just removed the package and that solved (or at least worked around) the problem. But it still doesn't make sense. A new version of a package sometimes has a few new dependencies, but 43 is a bit much.
how many of the 43 were cross-architecture ?
- KB
Karanbir Singh wrote:
On 01/07/2010 15:50, Bowie Bailey wrote:
Since I don't need it (AFAIK), I just removed the package and that solved (or at least worked around) the problem. But it still doesn't make sense. A new version of a package sometimes has a few new dependencies, but 43 is a bit much.
how many of the 43 were cross-architecture ?
None, they are all devel packages. Actually, now that I take a closer look, the main dependencies are:
freetype-devel startup-notification-devel pango-devel libgnome-devel libXt-devel gtk2-devel libjpeg-devel libgnomeui-devel libIDL-devel libXrender-devel gnome-vfs2-devel alsa-lib-devel libnotify-devel
Then these start pulling in their own dependencies and I wind up with a list of 43 new packages being installed for dependencies. I just find this really strange since none of these were required for the previous version.
On 01/07/2010 16:08, Bowie Bailey wrote:
Then these start pulling in their own dependencies and I wind up with a list of 43 new packages being installed for dependencies. I just find this really strange since none of these were required for the previous version.
That is quite interesting. I guess the question next is : was the machine in a state where all deps resolved cleanly before you attempted the install ?
Although, the new xul ad firefox update were a major step forward.
- KB
Karanbir Singh wrote:
On 01/07/2010 16:08, Bowie Bailey wrote:
Then these start pulling in their own dependencies and I wind up with a list of 43 new packages being installed for dependencies. I just find this really strange since none of these were required for the previous version.
That is quite interesting. I guess the question next is : was the machine in a state where all deps resolved cleanly before you attempted the install ?
As far as I know, these machines had everything installed cleanly via yum. And all of my 5.x systems show the same behavior.
Although, the new xul ad firefox update were a major step forward.
That may explain it. That's basically why I was asking here. I saw two options -- either the package had been legitimately updated with the new deps, or it was a packaging error that added in some extraneous deps.
-------- Original Message -------- Subject: [CentOS] xulrunner-devel dependencies From: Bowie Bailey Bowie_Bailey@BUC.com To: CentOS mailing list centos@centos.org Date: Wednesday, June 30, 2010 11:49:06 AM
What's the deal with all of the new dependencies for xulrunner-devel in the last update? I'm updating my servers and the update for xulrunner-devel is forcing me to install 43 new packages! Is this a packaging problem, or are all of those packages really needed?
For the moment, I've been removing xulrunner-devel from my machines to avoid the problem. I figure since it is a development package, I can always reinstall it later if I need it.
Bowie
I noticed the same thing, and took the same steps toward resolution. xulrunner/xulrunner-devel apparently wasn't a dependency for any software that I use and was installed when I selected the "Development/Libraries" group at install time.
The current xulrunner-devel (1.9.2.4-9.el5) actually has 46 dependencies (91 on x86_64). The previous version (1.9.0.19-1.el5_5) had 28.
[root@mail ~]# yum deplist xulrunner-devel-1.9.2.4-9.el5 | grep dependency: | wc -l 91
--Blake
-
Blake Hudson -
Bowie Bailey -
John Doe -
Karanbir Singh