>>> On 5/3/2016 at 03:01 PM, Marcy Cortes <[email protected]> >>> wrote: > Mark wrote: >> I just recently inherited maintainership of that package. Lucky me. > > Ha! Well, we have 3 SRs open. Jeff M will probably be looking for you. > And yay me! Glad someone I know got this :)
Don't count on that producing any better results than you've seen so far. I have very little idea what goes on with that package and the others I inherited at this point in time. >> Right. That might be in the libica2 package, but I'm not sure. > I'll go read that doc too. I hope it is newer that the pdf from 2005 :) I didn't mean the documentation associated with libica2, rather that it might have some samples or actually update a configuration file somewhere. >>I recently asked IBM about that. They said, essentially, "yeah we didn't do > one for SP4." :( > > This is a big enough change that it needs to go somewhere. Perhaps SP4 > release notes then? That might have been a good idea if I had been responsible for it back then. We don't actually _use_ this stuff in any real sense, so it's hard for us to know for sure what impacts are going to be seen by the end customer. Perhaps during the process of resolving your problem an update to the release notes can be developed. The fact that you seem to be the first to run into this indicates that not many people are doing this sort of thing. Or they're figuring it out somehow and not telling us about it. -snip- > It seems like that CCA rpm should have been included with SP4 as well since > the config file shipped indicates its use. Well, we can't include what IBM doesn't provide us for inclusion. I never even heard of this RPM until today. And, in general, we don't like to simply repackage someone else's RPMs and ship them. I think at best we would do something like a release notes entry that points to the other RPM or have some sort of text message display during installation that points to the other RPM. Neither is a very good option since so few people read the release notes or pop-ups. > And I wonder if this is part of the problem Apparently the upgrade to SP4 > left us with lots of libica's > > rpm -qa | grep libica > libica-2_0_2-2.0.2-0.6.3 > libica-2_1_0-2.1.0-0.12.28 > libica2-32bit-2.4.2-0.14.1 > libica-2_0_2-32bit-2.0.2-0.6.3 > libica-2_1_0-32bit-2.1.0-0.12.28 > libica2-2.4.2-0.14.1 You could try uninstalling all but the libica2-2.4.2-0.14.1 package and see what happens. It's the most current version at the time SP4 was shipped. I don't think you'll need any of the 32bit packages, but I can't be sure of that. Just don't force things during that process. Mark Post ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
