Re: [Solved] Repo incompatibilities in cln package for EL4

Phil Schaffner <[email protected]>
Newsgroups gmane.linux.freshrpms.user
Message-ID <[email protected]>
On Fri, 2005-11-18 at 15:32 +0000, Karanbir Singh wrote:
> There is obviously something broken with the FreshRPMS Mailing list... 
> my reply there from yesterday never made it - and the resend this 
> morning has now shown up either ...

Slow reply - have been out of town.  Still don't see any recent messages
from you there.

> 
> sending this to you directly, so that you know whats going on...
> 
> btw, I am not sure if providing the libcln.so.3 symlink to libcln.so.4 
> would be 'safe' - 

Updates still didn't work from Dries, so forced removal of his cln and
did yum update with exclude=cln for [dries] to install your package and
update others in your repo depending on it, orsa, ginac, and octave-
forge (decided I didn't need qalculate).

> I've never used to the cln libraries myself - how 
> about you

Not directly, just using things that depend on it.

Thanks,
Phil

> 
> - K
> 

Not trimming context due to long lapse and breaking of threading...

> -------- Original Message --------
> Subject: Re: Repo incompatibilities in cln package for EL4
> Date: Fri, 18 Nov 2005 12:25:22 +0000
> From: Karanbir Singh <[email protected]>
> To: General freshrpms.net discussion list <[email protected]>
> References: <[email protected]>
> 
> Hi Phil,
> 
> Phil Schaffner wrote:
> > Dries' new cln-1.1.10-1.2.el4.rf package breaks packages from KBS CentOS
> > packages...
> > 
> > # yum update
> > Setting up Update Process
> > Setting up repositories
> > dries                     100% |=========================|  951 B    00:00
> > kbs-CentOS-Extras         100% |=========================|  951 B    00:00
> > kbs-CentOS-Misc           100% |=========================|  951 B    00:00
> > update                    100% |=========================|  951 B    00:00
> > dag                       100% |=========================| 1.1 kB    00:00
> > base                      100% |=========================| 1.1 kB    00:00
> > contrib                   100% |=========================|  951 B    00:00
> > centosplus                100% |=========================|  951 B    00:00
> > addons                    100% |=========================|  951 B    00:00
> > local                     100% |=========================|  951 B    00:00
> > extras                    100% |=========================| 1.1 kB    00:00
> > Reading repository metadata in from local files
> > Resolving Dependencies
> > --> Populating transaction set with selected packages. Please wait.
> > ---> Package cln.i386 0:1.1.10-1.2.el4.rf set to be updated
> > --> Running transaction check
> > --> Processing Dependency: libcln.so.3 for package: octave-forge
> > --> Processing Dependency: libcln.so.3 for package: qalculate
> > --> Processing Dependency: libcln.so.3 for package: libqalculate
> > --> Processing Dependency: libcln.so.3 for package: ginac
> > --> Processing Dependency: libcln.so.3 for package: orsa
> > --> Finished Dependency Resolution
> > Error: Missing Dependency: libcln.so.3 is needed by package octave-forge
> > Error: Missing Dependency: libcln.so.3 is needed by package qalculate
> > Error: Missing Dependency: libcln.so.3 is needed by package libqalculate
> > Error: Missing Dependency: libcln.so.3 is needed by package ginac
> > Error: Missing Dependency: libcln.so.3 is needed by package orsa
> > # rpm -q octave-forge qalculate libqalculate ginac cln
> > octave-forge-2004.11.16-9.el4.kb
> > qalculate-0.8.2-2.el4.kb
> > libqalculate-0.8.2-2.el4.kb
> > ginac-1.3.2-1.el4.kb
> > cln-1.1.9-3.el4.kb
> 
> SONAME update moving from cln-1.1.9 to 1.1.10 seems to have caused this
> issue, I've requeued the problem pkgs to build against the new 1.1.10 pkg.
> 
> Updates should show up on centos.karan.org within the next 24 hrs, I'll
> also post an email here to let you know.
> 
> Thanks for pointing this out.
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.