>>> On Fri, Mar 2, 2007 at 12:49 PM, in message
<[EMAIL PROTECTED]>,
James Melin <[EMAIL PROTECTED]> wrote: 
> Well I managed to get things mostly sane.....There was a bunch of Yast 
> maintenance that didn't go in. I applied it and got it down to the package -
> yast2- http- server being not updated
> 
>       mudlake:~ # SPident - vv
> 
>       Summary            (using 890 packages)
>       Product/ServicePack     conflict        match  update      (shipped)
>       SLES- 9- s390x          0    0%    431 48.4%     147   (1555 27.7%)
>       SLES- 9- s390x- SP1      0    0%     84  9.4%      89    (529 15.9%)
>       SLES- 9- s390x- SP2      0    0%    155 17.4%     108    (684 22.7%)
>       SLES- 9- s390x- SP3      1  0.1%    276 31.0%     120    (793 34.8%)
>         -  yast2- http- server  2.9.31- 0.4.1 < 2.9.31- 0.5
>       Unknown                          179 20.1%

I'm way more interested in what the 179 packages are that SPident doesn't know 
what to think about.

-snip-
> Just to see what SPident would do, I un- installed this package through 
> install/remove software.
> 
> 
>       mudlake:~ # SPident - vv
> 
>       Summary            (using 889 packages)
>       Product/ServicePack     conflict        match  update      (shipped)
>       SLES- 9- s390x          0    0%    431 48.5%     146   (1555 27.7%)
>       SLES- 9- s390x- SP1      0    0%     84  9.4%      88    (529 15.9%)
>       SLES- 9- s390x- SP2      0    0%    155 17.4%     107    (684 22.7%)
>       SLES- 9- s390x- SP3      0    0%    275 30.9%     120    (793 34.7%)
>       Unknown                          179 20.1%
> 
>        Legend for Package Details:
>         -   conflicting package (found < expected)
> 
>       CONCLUSION: System is up- to- date!
>         found    SLES- 9- s390x- SP3 + "online updates"
> 
> And now SPident is happy. I am not, however. What functionality did I lose 
> here, and how, if anyone has an idea, do I put this back and get it so that
> YOU pulls the  update for it?

All the yast-* packages provide modules to YaST to manage things.  So, in your 
case, yast2-http-server would be the module you would use to set up and 
configure your HTTP server.  I just checked the git390 system, and I have 
yast2-http-server-2.9.31-0.5 installed, as of March 2006, so just under a year. 
 I don't see it in the list of stuff at 
https://you.novell.com/update/s390x/update/SUSE-CORE/9/rpm/s390x/, so it might 
have been included in the "youfix" stuff that came out last year.  You might 
try pointing YOU to https://you.novell.com/youfix/ and see what happens.


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

Reply via email to