Hi! I recently encountered a situation when a x86_64 package is dependent on i686 packages.. Does anyone with packaging experience know why this could be necessary? What arguments (logical and technical) can i bring to the said packager in order to stop this chain of dependencies?
Thanks! Adrian
On 1/30/2014 1:17 AM, Adrian Sevcenco wrote:
Hi! I recently encountered a situation when a x86_64 package is dependent on i686 packages.. Does anyone with packaging experience know why this could be necessary? What arguments (logical and technical) can i bring to the said packager in order to stop this chain of dependencies?
I suspect that would depend on just what this package is, and what 32bit packages its dependent on.
-----Original Message----- From: John R Pierce Sent: Thursday, January 30, 2014 4:21
On 1/30/2014 1:17 AM, Adrian Sevcenco wrote:
Hi! I recently encountered a situation when a x86_64 package is dependent on i686 packages..
RPM and Specfile please? Also if it is not a CentOS package try: rpm-list@lists.rpm.org .
Does anyone with packaging experience know why this could
be necessary?
What arguments (logical and technical) can i bring to the said packager in order to stop this chain of dependencies?
I suspect that would depend on just what this package is, and what 32bit packages its dependent on.
-- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100 - - +1 (443) 269-1555 x333 Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is copyright PD Inc, subject to license 20080407P00.
On 01/30/2014 03:28 PM, Jason Pyeron wrote:
-----Original Message----- From: John R Pierce Sent: Thursday, January 30, 2014 4:21
On 1/30/2014 1:17 AM, Adrian Sevcenco wrote:
Hi! I recently encountered a situation when a x86_64 package is dependent on i686 packages..
RPM and Specfile please? Also if it is not a CentOS package try: rpm-list@lists.rpm.org .
Does anyone with packaging experience know why this could
be necessary?
What arguments (logical and technical) can i bring to the said packager in order to stop this chain of dependencies?
I suspect that would depend on just what this package is, and what 32bit packages its dependent on.
Hi everyone! The question was purely academic (in the sense that i think that this is wrong but i don't have the experience and knowledge to have arguments for my opinion). The package in question is from a particular science-related repo and i i got an answer that the package is that way because there are potential users that use i686 software (in the context that that software is only supported for x86_64 distros..)
So: are there any best-practices rules that say :"do not mix arch in packages, better split them" ?
Thanks! Adrian
On Thu, Jan 30, 2014 at 1:17 AM, Adrian Sevcenco Adrian.Sevcenco@cern.ch wrote:
Hi! I recently encountered a situation when a x86_64 package is dependent on i686 packages.. Does anyone with packaging experience know why this could be necessary? What arguments (logical and technical) can i bring to the said packager in order to stop this chain of dependencies?
You can find such an example in a recent bug report. Turns out it was due to user's set up ...
http://bugs.centos.org/view.php?id=6944
So, you'd need to analyse your situation (decipher the yum output etc) and determine what's causing it.
Akemi
On Thu, Jan 30, 2014 at 04:55:56AM -0800, Akemi Yagi wrote:
On Thu, Jan 30, 2014 at 1:17 AM, Adrian Sevcenco Adrian.Sevcenco@cern.ch wrote:
Hi! I recently encountered a situation when a x86_64 package is dependent on i686 packages.. Does anyone with packaging experience know why this could be necessary? What arguments (logical and technical) can i bring to the said packager in order to stop this chain of dependencies?
You can find such an example in a recent bug report. Turns out it was due to user's set up ...
http://bugs.centos.org/view.php?id=6944
So, you'd need to analyse your situation (decipher the yum output etc) and determine what's causing it.
One that comes to mind is Google Earth. Their alleged 64-bit packages have dependencies on 32-bit packages. Go figure.
-
Adrian Sevcenco -
Akemi Yagi -
Fred Smith -
Jason Pyeron -
John R Pierce