 |
 |
A bug. Lukasz On Thu, 21 May 2015 23:18:06 +0200 Elvin Alin Sindrilaru <[log in to unmask]> wrote: > > That makes perfect sense, except that xrootd-client-compat has an > explicit dependency on xrootd-libs: > > # yum install xrootd-client-compat > Loaded plugins: kernel-module, priorities, refresh-packagekit, > rpm-warm-cache, security Setting up Install Process > 403 packages excluded due to repository priority protections > Resolving Dependencies > --> Running transaction check > ---> Package xrootd-client-compat.x86_64 1:4.1.2-1.slc6 will be > installed --> Processing Dependency: xrootd-libs(x86-64) = > 1:4.1.2-1.slc6 for package: > 1:xrootd-client-compat-4.1.2-1.slc6.x86_64 --> Finished Dependency > Resolution Beginning Kernel Module Plugin Finished Kernel Module > Plugin Error: Package: 1:xrootd-client-compat-4.1.2-1.slc6.x86_64 > (xroot-stable) Requires: xrootd-libs(x86-64) = 1:4.1.2-1.slc6 > Installed: 1:xrootd-libs-4.2.0-1.slc6.x86_64 (@xroot-stable) > xrootd-libs(x86-64) = 1:4.2.0-1.slc6 > Available: 1:xrootd-libs-3.3.6-1.slc6.x86_64 (xroot-stable) > > > Which come from line 309 from the spec file: > http://xrootd.cern.ch/cgi-bin/cgit.cgi/xrootd/tree/packaging/rhel/xrootd.spec.in#n309 > > Cheers, > Elvin > > ________________________________________ > From: [log in to unmask] [[log in to unmask]] on > behalf of Lukasz Janyst [[log in to unmask]] Sent: 21 May 2015 22:45 > To: [log in to unmask] > Subject: Fw: xrootd client compat package > > Begin forwarded message: > > Date: Thu, 21 May 2015 22:43:01 +0200 > From: Lukasz Janyst <[log in to unmask]> > To: Andrew Hanushevsky <[log in to unmask]> > Cc: Elvin Alin Sindrilaru <[log in to unmask]>, "Michal > Kamil Simon" <[log in to unmask]>, <[log in to unmask]>, > <[log in to unmask]> Subject: Re: xrootd client compat package > > > It is needed, but it is needed only once. There is not and should not > be any explicit dependency on the compat package anywhere, only > implicit soname dopendencies. Therefore, the exact name or version of > the compat package is completely immaterial. As long as there is a > package in the yum's universe that has appropriate implicit provide > tags for the wanted sonames, yum will know what to do. > > In the long run these compat packages should come from a separate SRPM > and be on their own release cycle, ie. no cycle at all, since they > contain the code that does not change anymore. In the short term, just > use the one from 4.1.x, the one from 4.2.x would have been identical > modulo the version. > > Lukasz > > > On Mon, 18 May 2015 01:04:18 -0700 > Andrew Hanushevsky <[log in to unmask]> wrote: > > > The client compat package is not needed at this point as the client > > side does not have any multi-versioned plugins. I think Lukasz is > > the best to answer this question but I think you can safely ignore > > this. > > > > Andy > > > > On Mon, 18 May 2015, Elvin Alin Sindrilaru wrote: > > > > > > > > Hi Andy, > > > > > > Over the weekend we received a ticket from Linux support about the > > > fact that there is no xrootd-client-compat package for the last > > > release made by Lukasz. > > > > > > Do you have any idea what is the status of xrootd-client-compat? > > > How is it built? Do we still need it? > > > > > > Thanks, > > > Elvin > > > > > ######################################################################## > Use REPLY-ALL to reply to list > > To unsubscribe from the XROOTD-DEV list, click the following link: > https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1 > ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the XROOTD-DEV list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1