[opensuse] why so many 32-bit packages in my install of 64-bit SUSE 11?
(aside: this is actually an install of SLES 11, so i hope it's not wildly inappropriate to ask about it here since i suspect it might also apply here.) i installed SLES 11 x86-64 on a gateway AMD and just now noticed that there are almost 200 packages installed with "32bit" as part of the package name -- i'm guessing because they're 32-bit, of course. i ran "rpm -q --whatrequires" on each one of them to figure out what could have forced them to be installed but, as far as i can see, there is *nothing* that requires any of those 32-bit packages. so ... why were they installed? is the same true for 64-bit opensuse? rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA Linux Consulting, Training and Annoying Kernel Pedantry. Web page: http://crashcourse.ca Twitter: http://twitter.com/rpjday ======================================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Robert P. J. Day wrote:
so ... why were they installed? is the same true for 64-bit opensuse?
It is. I just ran an update the other day and it bit me hard on a few things. Namely KDM was looking for something in pam-modules for 32bit package. When I installed I know I purposely did not pick any 32 bit packages, and I went through yast and saw A LOT of 32 bit packages installed too. I don't know why, but can confirm on opensuse 64 bit. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sat, 26 Sep 2009, Michael S. Dunsavage wrote:
Robert P. J. Day wrote:
so ... why were they installed? is the same true for 64-bit opensuse?
It is. I just ran an update the other day and it bit me hard on a few things. Namely KDM was looking for something in pam-modules for 32bit package. When I installed I know I purposely did not pick any 32 bit packages, and I went through yast and saw A LOT of 32 bit packages installed too. I don't know why, but can confirm on opensuse 64 bit.
well, that's just weird since, as i mentioned, "rpm" showed *nothing* on the system that depended on any of those. since this is a play system, i'm tempted to just remove them all and see what happens. if the system falls over and dies, no big deal. i'll play with rpm a bit longer -- there must be *something* that's causing all those packages to be dragged in. rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA Linux Consulting, Training and Annoying Kernel Pedantry. Web page: http://crashcourse.ca Twitter: http://twitter.com/rpjday ======================================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 26/09/09 11:53, Robert P. J. Day wrote:
(aside: this is actually an install of SLES 11, so i hope it's not wildly inappropriate to ask about it here since i suspect it might also apply here.)
i installed SLES 11 x86-64 on a gateway AMD and just now noticed that there are almost 200 packages installed with "32bit" as part of the package name -- i'm guessing because they're 32-bit, of course.
rpmqpack | grep 32bit | wc -l 147 You most likely have a 586/686 app installed that requires all of those packages. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sat, 26 Sep 2009, Cristian Rodríguez wrote:
On 26/09/09 11:53, Robert P. J. Day wrote:
(aside: this is actually an install of SLES 11, so i hope it's not wildly inappropriate to ask about it here since i suspect it might also apply here.)
i installed SLES 11 x86-64 on a gateway AMD and just now noticed that there are almost 200 packages installed with "32bit" as part of the package name -- i'm guessing because they're 32-bit, of course.
rpmqpack | grep 32bit | wc -l
147
You most likely have a 586/686 app installed that requires all of those packages.
but, as i said, i ran "rpm -q --whatrequires" using a shell loop on all of them, and not a single one reported being required for anything else. oh, wait: sles11:~ # rpm -e $(rpm -qa | grep 32bit) error: Failed dependencies: libc.so.6 is needed by (installed) grub-0.97-158.2.x86_64 libc.so.6(GLIBC_2.0) is needed by (installed) grub-0.97-158.2.x86_64 libc.so.6(GLIBC_2.1) is needed by (installed) grub-0.97-158.2.x86_64 libc.so.6(GLIBC_2.2) is needed by (installed) grub-0.97-158.2.x86_64 libc.so.6(GLIBC_2.3) is needed by (installed) grub-0.97-158.2.x86_64 libc.so.6(GLIBC_2.3.4) is needed by (installed) grub-0.97-158.2.x86_64 libc.so.6(GLIBC_2.4) is needed by (installed) grub-0.97-158.2.x86_64 libncurses.so.5 is needed by (installed) grub-0.97-158.2.x86_64 sles11:~ # rpm -qa | grep ncurses libncurses5-5.6-90.55 libncurses6-5.6-90.55 libncurses6-32bit-5.6-90.55 yast2-ncurses-pkg-2.17.13-1.25 ncurses-devel-5.6-90.55 libncurses5-32bit-5.6-90.55 yast2-ncurses-2.17.14-1.4 ncurses-utils-5.6-90.55 ncurses-devel-32bit-5.6-90.55 sles11:~ # hang on ... sles11:~ # rpm -qR grub fileutils sh-utils udev /bin/sh /bin/sh rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1 /bin/sh libc.so.6 libc.so.6(GLIBC_2.0) libc.so.6(GLIBC_2.1) libc.so.6(GLIBC_2.2) libc.so.6(GLIBC_2.3) libc.so.6(GLIBC_2.3.4) libc.so.6(GLIBC_2.4) libncurses.so.5 rpmlib(PayloadIsLzma) <= 4.4.2-1 sles11:~ # ok, i'm just confused here. rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA Linux Consulting, Training and Annoying Kernel Pedantry. Web page: http://crashcourse.ca Twitter: http://twitter.com/rpjday ========================================================================
Hi Robert, On Sat, 26 Sep 2009, 17:53:20 +0200, Robert P. J. Day wrote:
(aside: this is actually an install of SLES 11, so i hope it's not wildly inappropriate to ask about it here since i suspect it might also apply here.)
i installed SLES 11 x86-64 on a gateway AMD and just now noticed that there are almost 200 packages installed with "32bit" as part of the package name -- i'm guessing because they're 32-bit, of course.
i ran "rpm -q --whatrequires" on each one of them to figure out what could have forced them to be installed but, as far as i can see, there is *nothing* that requires any of those 32-bit packages.
so ... why were they installed? is the same true for 64-bit opensuse?
I guess you left the "32-Bit Runtime Environment" pattern enabled?!?! A pattern is actually/normally a collection/description of packages which are required (or recommended, or suggested) for a particular use case, but it appears that the 32-bit pattern is different, as it is *empty*. It is my understanding, that _any_ package you install, for which a package-32bit version exists, will result in installing that 32-bit version as well. If you *know* that you don't need any of them, you should de-select the pattern during installation, but I actually found too much software which still requires a working 32-bit runtime environment (e.g. Acroread).
rday
HTH, cheers. l8er manfred -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, Sep 29, 2009 at 03:18:46PM +0200, Manfred Hollstein wrote:
Hi Robert,
On Sat, 26 Sep 2009, 17:53:20 +0200, Robert P. J. Day wrote:
(aside: this is actually an install of SLES 11, so i hope it's not wildly inappropriate to ask about it here since i suspect it might also apply here.)
i installed SLES 11 x86-64 on a gateway AMD and just now noticed that there are almost 200 packages installed with "32bit" as part of the package name -- i'm guessing because they're 32-bit, of course.
i ran "rpm -q --whatrequires" on each one of them to figure out what could have forced them to be installed but, as far as i can see, there is *nothing* that requires any of those 32-bit packages.
so ... why were they installed? is the same true for 64-bit opensuse?
I guess you left the "32-Bit Runtime Environment" pattern enabled?!?! A pattern is actually/normally a collection/description of packages which are required (or recommended, or suggested) for a particular use case, but it appears that the 32-bit pattern is different, as it is *empty*. It is my understanding, that _any_ package you install, for which a package-32bit version exists, will result in installing that 32-bit version as well. If you *know* that you don't need any of them, you
Not expected.
should de-select the pattern during installation, but I actually found too much software which still requires a working 32-bit runtime environment (e.g. Acroread).
We just have lots of 32bit pam modules that are recommended by their normal equivalents. (just to have both installed). And there are the 32bit acroread, flashplayer and wine which would pull in 32bit dependencies. Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 29 Sep 2009, Manfred Hollstein wrote:
I guess you left the "32-Bit Runtime Environment" pattern enabled?!?!
hmmmm ... i don't recall doing that. again, keeping in mind that this SLES 11, would that be a *default* selection? i guess i can just test install again and see. but if you do that with opensuse, how many packages would you estimate that would drag in? thanks. rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA Linux Consulting, Training and Annoying Kernel Pedantry. Web page: http://crashcourse.ca Twitter: http://twitter.com/rpjday ======================================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 29 Sep 2009, 22:40:52 +0200, Robert P. J. Day wrote:
On Tue, 29 Sep 2009, Manfred Hollstein wrote:
I guess you left the "32-Bit Runtime Environment" pattern enabled?!?!
hmmmm ... i don't recall doing that. again, keeping in mind that this SLES 11, would that be a *default* selection? i guess i can just test install again and see. but if you do that with opensuse, how many packages would you estimate that would drag in? thanks.
I don't really know; it actually depends on which 32-bit packages (not those from the 32-bit runtime environment, but _actual_ 32-bit applications) you install, and how many 32-bit packages are recommended based on the packages you have selected for installation. As the 32-bit pattern is just a virtual one, its only purpose is to ensure that for any package you want to install and for which a package-32bit counterpart exists, that both packages will be installed. So, e.g. if you de-select an optional libfoo package, no libfoo-32bit would be installed; if, however, you select an optional libzoo, libzoo-32bit will be automatically installed, too.
rday
HTH, cheers. l8er manfred PS: No need to copy me on your e-mails ;-) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, Sep 30, 2009 at 2:45 AM, Manfred Hollstein
I don't really know; it actually depends on which 32-bit packages (not those from the 32-bit runtime environment, but _actual_ 32-bit applications) you install, and how many 32-bit packages are recommended based on the packages you have selected for installation. As the 32-bit pattern is just a virtual one, its only purpose is to ensure that for any package you want to install and for which a package-32bit counterpart exists, that both packages will be installed. So, e.g. if you de-select an optional libfoo package, no libfoo-32bit would be installed; if, however, you select an optional libzoo, libzoo-32bit will be automatically installed, too.
I have 70 32bit installed on 11.0/x64. When I tried to remove some, I got dependencies on the packages from the 64bit versions. I have 64bit flash installed. I also have WINE installed, but it shows no 32bit dependencies. Example: Consolekit-0.2.10-14.4.x86_64 requires Consolekit-32bit kdebase3-3.5.9-100.1.x86_64 requires Mesa-32bit And many more x86_64 packages that require the 32bit package or a 32bit package. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hi Larry, On Wed, 30 Sep 2009, 15:53:32 +0200, Larry Stotler wrote:
On Wed, Sep 30, 2009 at 2:45 AM, Manfred Hollstein
wrote: I don't really know; it actually depends on which 32-bit packages (not those from the 32-bit runtime environment, but _actual_ 32-bit applications) you install, and how many 32-bit packages are recommended based on the packages you have selected for installation. As the 32-bit pattern is just a virtual one, its only purpose is to ensure that for any package you want to install and for which a package-32bit counterpart exists, that both packages will be installed. So, e.g. if you de-select an optional libfoo package, no libfoo-32bit would be installed; if, however, you select an optional libzoo, libzoo-32bit will be automatically installed, too.
I have 70 32bit installed on 11.0/x64. When I tried to remove some, I got dependencies on the packages from the 64bit versions. I have 64bit flash installed. I also have WINE installed, but it shows no 32bit dependencies.
Example: Consolekit-0.2.10-14.4.x86_64 requires Consolekit-32bit kdebase3-3.5.9-100.1.x86_64 requires Mesa-32bit
And many more x86_64 packages that require the 32bit package or a 32bit package.
That's why I wrote about "optional" packages in my posting above. The packages you are refering to obviously "require" some of the 32bit packages. Everybody could now try to figure out, how many of these packages are actually required by the x86_64 packages - if time permits ;-) Cheers. l8er manfred -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (6)
-
Cristian Rodríguez
-
Larry Stotler
-
Manfred Hollstein
-
Marcus Meissner
-
Michael S. Dunsavage
-
Robert P. J. Day