Issues after upgrading fro 2006 to 2007.1 - Mandriva

This is a discussion on Issues after upgrading fro 2006 to 2007.1 - Mandriva ; So, I upgrading a 2006 workstation to 2007.1. I used boot.iso burned to a CD, then did a network upgrade from the campus mirror. It took a while, but when it came up the system seemed to be running pretty ...

+ Reply to Thread
Results 1 to 11 of 11

Thread: Issues after upgrading fro 2006 to 2007.1

  1. Issues after upgrading fro 2006 to 2007.1

    So, I upgrading a 2006 workstation to 2007.1. I used boot.iso
    burned to a CD, then did a network upgrade from the campus mirror. It
    took a while, but when it came up the system seemed to be running pretty
    well. There are, however, a couple of issues...

    1. The mirror today has a mismatch on the md5sum for the Main updates
    section, so in order to try to update I have to add --no-md5sum. That's
    not the issue, the issue is the signature on glibc, because:

    % urpmi --no-md5sum --auto-update --auto

    ftp://toughguy.caltech.edu//pub/mand...esis.hdlist.cz
    medium "Main" is up-to-date


    ftp://toughguy.caltech.edu//pub/mand...esis.hdlist.cz
    medium "Main Updates" is up-to-date


    ftp://toughguy.caltech.edu//pub/mand...esis.hdlist.cz
    medium "Contrib" is up-to-date


    ftp://toughguy.caltech.edu//pub/mand...esis.hdlist.cz
    medium "Contrib Updates" is up-to-date


    ftp://toughguy.caltech.edu//pub/mand...esis.hdlist.cz
    medium "Non-free" is up-to-date


    ftp://toughguy.caltech.edu//pub/mand...esis.hdlist.cz
    medium "Non-free Updates" is up-to-date

    The following packages have to be removed for others to be upgraded:
    glibc-2.4-8mdv2007.1.i586
    (in order to install glibc-2.4-8mdv2007.1.i586)

    The following packages have bad signatures:
    /var/cache/urpmi/rpms/glibc-2.4-8mdv2007.1.i586.rpm: Invalid Key ID (OK
    (DSA/SHA1, Wed 28 Mar 2007 12:47:41 PM PDT, Key ID e7898ae070771ff3))


    Of course one cannot blithely remove glibc since more or less everything
    in the system depends upon it! Note also what it wants to do, it wants
    to remove glibc and then reinstall it. So while I was able to upgrade
    to 7.1, so far I've not been able to install any of the updates TO 7.1.
    Blech.

    2. Following the update there seems to be an awful lot of detritus in
    the rpm system.

    % rpm -qa | grep 20060mdk | wc
    22 22 733

    Of the ones I've checked, there always seems to be a replacement already
    installed, for instance:

    % rpm -qa | grep libopenssl
    libopenssl0.9.8-0.9.8e-2.1mdv2007.1
    libopenssl0.9.8-devel-0.9.8e-2.1mdv2007.1
    libopenssl0.9.7-0.9.7g-2.5.20060mdk

    and some of these seem to be tied in with other 2006 dependencies:

    rpm -e libopenssl0.9.7-0.9.7g-2.5.20060mdk
    error: Failed dependencies:
    libcrypto.so.0.9.7 is needed by (installed)
    libRosegarden0-1.0-5mdk.i586
    libcrypto.so.0.9.7 is needed by (installed)
    libclamav1-0.90-0.1.20060mdk.i586
    libcrypto.so.0.9.7 is needed by (installed)
    pine-4.64-1.1.20060plf.i586
    libcrypto.so.0.9.7 is needed by (installed)
    libgwenhywfar17-1.17.0-1mdk.i586
    libcrypto.so.0.9.7 is needed by (installed)
    libcurl3-7.14.0-2.2.20060mdk.i586
    libssl.so.0.9.7 is needed by (installed)
    libRosegarden0-1.0-5mdk.i586
    libssl.so.0.9.7 is needed by (installed)
    libclamav1-0.90-0.1.20060mdk.i586
    libssl.so.0.9.7 is needed by (installed)
    pine-4.64-1.1.20060plf.i586
    libssl.so.0.9.7 is needed by (installed)
    libgwenhywfar17-1.17.0-1mdk.i586
    libssl.so.0.9.7 is needed by (installed)
    libcurl3-7.14.0-2.2.20060mdk.i586

    I'm going to start working through this list cleaning up, but it's
    a pretty painful thing to do manually. Why didn't the update
    take care of this? None of this stuff was running during the update,
    so there shouldn't have been any problem removing it.

    Thanks,

    David Mathog

  2. Re: Issues after upgrading fro 2006 to 2007.1

    On Thu, 10 May 2007 12:08:47 -0700, David Mathog wrote:
    >
    > 1. The mirror today has a mismatch on the md5sum for the Main updates
    > section, so in order to try to update I have to add --no-md5sum. That's
    > not the issue, the issue is the signature on glibc, because:


    Maybe your mirror was downloading updates from France which caused the
    md5sum mismatch. Or worse, it was corrupt.


    > % urpmi --no-md5sum --auto-update --auto
    >
    > ftp://toughguy.caltech.edu//pub/mand...esis.hdlist.cz
    > medium "Main" is up-to-date



    I thought the new and improved urpmi used the sums to verify
    if it would be required to download the *list.cz files.

    I noticed it takes a lot less time to decide to not download them when
    they are the same.

    I also have see the bad md5sum on the hdlist files recently. Deleting
    and adding back the same mirror as before fixed the problem on two of
    my systems.


    > The following packages have bad signatures:
    > /var/cache/urpmi/rpms/glibc-2.4-8mdv2007.1.i586.rpm: Invalid Key ID (OK
    > (DSA/SHA1, Wed 28 Mar 2007 12:47:41 PM PDT, Key ID e7898ae070771ff3))


    I have seen bad signatures on bad downloads. Deleted them from
    /var/cache/urpmi/rpms and next retry fetched without problem.

    I would do a ifconfig -a and check the fault counters
    rx errors:0 dropped:0 overruns:0 frame:0
    tx errors:0 dropped:0 overruns:0 carrier:0

    to rule out nic and nic cable problems.

    I always have a spare ~10 gig partition so there is a fallback one to
    use when Murphy helps on new install/updates.


  3. Re: Issues after upgrading fro 2006 to 2007.1

    Bit Twister wrote:
    >
    > I have seen bad signatures on bad downloads. Deleted them from
    > /var/cache/urpmi/rpms and next retry fetched without problem.


    That worked. Well that and using a different mirror, there was
    something screwy about ours at the time I tried to use it. Thanks!

    It has been, umm, interesting doing this 2006 to 2007.1 update.
    Here are a few observations that might come in handy for others:

    1. shorewall broke. I have no idea why. To fix it I did:

    rpm -e shorewall
    rm -f /etc/shorewall/*
    urpmi shorewall
    drakconf (configured the firewall)
    service shorewall stop
    nedit /etc/shorewall/rules
    (put in exactly the same rules that used to be there)
    service shorewall start

    and it was back the way it was before the upgrade.

    2. gimp broke. This probably has something to do with having had
    gimpshop-2.2.11 installed in /usr/local and regular gimp-2.2.11
    in /usr package. gimpshop tends to feel more natural for many
    users since it looks a lot like photoshop, and they are used to that
    interface. Anyway, removing the gimp rpms and reinstalling them
    did not clear things up, here's what happens:

    % gimp
    gimp: symbol lookup error: gimp: undefined symbol: gimp_micro_version

    Seems like it's confused about which libraries to use, since

    % ldd `which gimp`

    showed it using

    /usr/local/lib/libgimpwidgets-2.0.so.0

    instead of

    /usr/lib/libgimpwidgets-2.0.so.0

    I have no idea why it's looking in /usr/local/lib before /usr/lib.
    Running ldconfig again didn't make it stop doing so.
    So I deleted every bit of "gimp" in /usr/local and then the Mandriva
    2007.1 gimp started working. I guess we'll have to live without
    Gimpshop. There seems not to be a current version in any case.

    3. Cleaned out all the residual Mandriva 2006 rpms, at least those with
    an obvious name containing a 2006. Part of the reason there were so
    many may have been that PLF pine was installed, and that had some
    dependencies on some 2006 rpms. Removed pine, cleaned out the 2006
    rpms, (re)installed a PLF for Mandriva 2007 (which seems to work ok).
    Unfortunately there seem to be zillions of other rpms which were not
    removed, especially of the lib* type. I've been going through these
    manually trying "rpm -e" on them and backing off if the dependency
    chain hits a mdv2007 entry. There must be a better way. And why didn't
    the Mandriva update do this for me???

    4. /etc/updatedb.conf in 2007.1 is not compatible with the one from
    2006, different syntax. Turns out they went from slocate to mlocate,
    and the two are not quite compatible. Keep the "prune" lines but
    replace commas with spaces, and delete all of the other flags (which
    mlocate won't recognize). Then updatedb will work.

    5. Most of the .rpmnew changes aren't needed but one is important.
    After the update from root:

    % su - someuser

    did not work. To fix it I did:

    % mv /etc/pam.d/su.rpmnew /etc/pam.d/su

    Regards,

    David Mathog

  4. Re: Issues after upgrading fro 2006 to 2007.1

    On Thu, 10 May 2007 16:00:22 -0700, David Mathog wrote:
    >
    > 1. shorewall broke. I have no idea why. To fix it I did:
    >


    I'll guess new control files wiped out your connection/rules.
    I have seen it do that in the past.
    >
    > Unfortunately there seem to be zillions of other rpms which were not
    > removed, especially of the lib* type. I've been going through these
    > manually trying "rpm -e" on them and backing off if the dependency
    > chain hits a mdv2007 entry. There must be a better way. And why didn't
    > the Mandriva update do this for me???


    Hey, package names/contents change/split or become obsolete. rpms do
    not take care of those.

    That is the best reason to do clean installs between major release numbers.


    >
    > 4. /etc/updatedb.conf in 2007.1 is not compatible with the one from
    > 2006, different syntax.


    Yep, another reason to do clean installs. Old config files may not do
    well with new version of software.

    > 5. Most of the .rpmnew changes aren't needed but one is important.


    I have seen them matter on updates let alone on new installs.
    I always merge my changes into the newrpm and
    mv whatever.newrpm whatever
    After each daily update check/run I run the updatedb and locate newrpm
    to check any via an update.

  5. Re: Issues after upgrading fro 2006 to 2007.1

    Bit Twister wrote:
    > On Thu, 10 May 2007 16:00:22 -0700, David Mathog wrote:
    >> 1. shorewall broke. I have no idea why. To fix it I did:
    >>

    >
    > I'll guess new control files wiped out your connection/rules.


    Oddly no, I checked, they were untouched, and there were .rpmnew
    versions in the same directory. Yet it wouldn't start.


    > Hey, package names/contents change/split or become obsolete. rpms do
    > not take care of those.
    >
    > That is the best reason to do clean installs between major release numbers.


    I'm convinced now. This "upgrade" has now taken at least as long
    as a clean install and reconfigure plus other software reinstall,
    so since there's no time savings involved, there's no reason to do
    it this way again. Pity, it would have been nice to be able to upgrade
    (keeping all configurations and layered software) instead of having to
    nuke everything, install, and (re)install all of the other programs.

    What's up with the (lack of a) Java Runtime Environment
    in Mandriva 2007.1? Is there some special trick to download a
    JRE rpm or do they really expect you to go to another system
    which already has it, download there, and transfer to the Mandriva
    system? The download site java.sun.com uses Java web start
    to download JRE, so on a clean 2007.1 you may have a browser but I
    don't see how you're going to get JRE from Sun with it.

    Thanks

    David Mathog

  6. Re: Issues after upgrading fro 2006 to 2007.1

    On Thu, 10 May 2007 16:43:53 -0700, David Mathog wrote:

    > Pity, it would have been nice to be able to upgrade
    > (keeping all configurations and layered software) instead of having to
    > nuke everything, install, and (re)install all of the other programs.


    I just keep an admin diary with commands. That allows me to just cut
    from diary and paste into config file.

    Copying did not do too well since 2007 release wantes to go with UTF 8.

    > What's up with the (lack of a) Java Runtime Environment
    > in Mandriva 2007.1? Is there some special trick to download a
    > JRE rpm or do they really expect you to go to another system
    > which already has it, download there, and transfer to the Mandriva
    > system?


    Yep, had you looked in the Errata or Release notes prior to install,
    you would seen the reason and with a little forethought, get the new
    release prior to starting install.


    > The download site java.sun.com uses Java web start
    > to download JRE, so on a clean 2007.1 you may have a browser but I
    > don't see how you're going to get JRE from Sun with it.



    Yes, that is a pretty brain dead decision on Sun's part.

    I have a download partition where I keep the latest third party
    packages like that. Helps on new installs.

    Only major problem I have found is KDE gets it's brains scrambled
    about where the mouse is. It will be off 2 or more inches down the
    screen.

    I have yet to find a good way to get it reset easily. If I do not see
    the mouse pointer in the middle of the screen when KDE is loading I know I
    will be playing with logout/in again. Last time I tried reboots and
    switching systems and OSs with my desktop switcher.
    No help there. Next time I'll watch the led glow on the bottom of the
    optical mouse and note the state to see if it will make a difference.




  7. Re: Issues after upgrading fro 2006 to 2007.1

    On Thu, 10 May 2007, David Mathog wrote:

    >
    > Bit Twister wrote:
    >> On Thu, 10 May 2007 16:00:22 -0700, David Mathog wrote:
    >>> 1. shorewall broke. I have no idea why. To fix it I did:
    >>>

    >>
    >> I'll guess new control files wiped out your connection/rules.

    >
    > Oddly no, I checked, they were untouched, and there were .rpmnew
    > versions in the same directory. Yet it wouldn't start.
    >
    >


    The new version of shorewall has various incompatibilities between the
    config files (nothing to do with mandriva) in - I think - the zones
    definition. I had a go at hand mofiying the files but eventually ran
    drakfirewall which got it up and running (having backed up my rules)

    2007 also seems to have got rid of the AllowSMB etc etc files that
    made hand config rather easy
    (whinge! not sure whether they were shorewall or mdv added)

    Robert
    --
    La grenouille songe..dans son ch√Ęteau d'eau
    Links and things http://rmstar.blogspot.com/

  8. Re: Issues after upgrading fro 2006 to 2007.1

    On 2007-05-11, Robert Marshall wrote:
    > On Thu, 10 May 2007, David Mathog wrote:
    >
    >>
    >> Bit Twister wrote:
    >>> On Thu, 10 May 2007 16:00:22 -0700, David Mathog wrote:
    >>>> 1. shorewall broke. I have no idea why. To fix it I did:
    >>>>
    >>>
    >>> I'll guess new control files wiped out your connection/rules.

    >>
    >> Oddly no, I checked, they were untouched, and there were .rpmnew
    >> versions in the same directory. Yet it wouldn't start.
    >>
    >>

    >
    > The new version of shorewall has various incompatibilities between the
    > config files (nothing to do with mandriva) in - I think - the zones
    > definition. I had a go at hand mofiying the files but eventually ran
    > drakfirewall which got it up and running (having backed up my rules)
    >
    > 2007 also seems to have got rid of the AllowSMB etc etc files that
    > made hand config rather easy
    > (whinge! not sure whether they were shorewall or mdv added)


    FWIW, snorewall/shorewall is not the only way to manage
    iptables. My luck with guarddog as a front-end for iptables
    has been very good, including creating a couple of
    user-defined protocols, and I'm _not_ an expert at iptables
    or guarrdog.

    --
    Robert Riches
    spamtrap42@verizon.net
    (Yes, that is one of my email addresses.)

  9. Re: Issues after upgrading fro 2006 to 2007.1

    On Fri, 11 May 2007 16:31:01 GMT, Robert M. Riches Jr. wrote:
    >
    > FWIW, shorewall is not the only way to manage
    > iptables. My luck with guarddog as a front-end for iptables
    > has been very good


    I like shorewalls blacklist feature and
    shorewall show -x
    command for checking the hit counters. That allows me to remove rules
    which no longer seem to be taking hits or have very low counts.

    I have
    xconsole -display wb:0 -geom 1032x50+400+00 -file /var/log/messages &
    running on my firewall pc and pinned to my desktop. Any hits
    getting past rules or blacklist, show right up.

    For the above xconsole to work for the none root user, you need the
    following tab separated values

    /var/log/messages current 644

    in /etc/security/msec/perm.local

    and have done a
    chmod 644 /var/log/messages

  10. Re: Issues after upgrading fro 2006 to 2007.1

    Bit Twister wrote:

    >> What's up with the (lack of a) Java Runtime Environment
    >> in Mandriva 2007.1? Is there some special trick to download a
    >> JRE rpm or do they really expect you to go to another system
    >> which already has it, download there, and transfer to the Mandriva
    >> system?

    >
    > Yep, had you looked in the Errata or Release notes prior to install,
    > you would seen the reason and with a little forethought, get the new
    > release prior to starting install.


    I cannot find the words "java","jre","browser", or "plugin" in the text
    version of the release notes on our mirror. However, you're right,
    there was a link from the release notes to the errata, and 2/3 of the
    way down that it did explain about Java. Also about mlocate, which
    contrary to what the errata said, apparently was installed on my
    upgraded system.

    If it were my choice and everything common didn't fit I would have
    probably included an option network step in the upgrade to pick up Java
    and any other common but omitted packages. That is, after the current
    install, it would pop up one more window and ask if these common
    packages should be retrieved over the network. And if that wasn't
    possible, at least an extra message saying that these are missing and
    that's the only way to get them.

    Regards,

    David Mathog

  11. Re: Issues after upgrading fro 2006 to 2007.1

    On Mon, 14 May 2007 08:57:24 -0700, David Mathog wrote:
    >
    > I cannot find the words "java","jre","browser", or "plugin" in the text
    > version of the release notes on our mirror. However, you're right,
    > there was a link from the release notes to the errata, and 2/3 of the
    > way down that it did explain about Java. Also about mlocate, which
    > contrary to what the errata said, apparently was installed on my
    > upgraded system.


    It seems like every other major releae, they toggle between slocate
    and mlocate. :-(

    >
    > If it were my choice and everything common didn't fit I would have
    > probably included an option network step in the upgrade to pick up Java
    > and any other common but omitted packages. That is, after the current
    > install, it would pop up one more window and ask if these common
    > packages should be retrieved over the network.


    The problem is jre was not GPL'ed, so the free release cannot have the
    "other common omitted rpms". What is common for some is not used for
    others. I was supprised to find kuickshow also missing from the media.

    What shows up in the Release Canidate does not show up in the
    Official and vice/versa.

    I just add them to my admin diary. Next install, cut from admin diary,
    paste into root terminal. Example snippet

    export _auto='--auto'

    # programming tools
    urpmi --wget checkinstall $_auto
    urpmi --wget cmake $_auto
    urpmi --wget ddd $_auto
    urpmi --wget expect $_auto
    urpmi --wget kdewebdev $_auto
    urpmi --wget perltidy $_auto
    urpmi --wget php-manual-en $_auto
    urpmi --wget slang-doc $_auto
    urpmi --wget tidy $_auto

    # admin stuff
    urpmi --wget axel $_auto
    urpmi --wget drakwizard $_auto
    urpmi --wget expect $_auto
    urpmi --wget howto-html-en $_auto
    urpmi --wget howto-utils $_auto
    urpmi --wget lshw $_auto
    urpmi --wget mesa-demos $_auto
    urpmi --wget nfs-utils $_auto
    urpmi --wget rkhunter $_auto
    urpmi --wget shorewall-doc $_auto
    urpmi --wget udev-tools $_auto
    urpmi --wget webmin $_auto
    urpmi --wget whois $_auto
    urpmi --wget wireshark $_auto

    # fetch hotmail/yahoo email from web server

    urpmi --wget fetchyahoo $_auto
    urpmi --wget gotmail $_auto
    urpmi --wget /downloads/skype-1.3.0.53-1mdk.i586.rpm --force
    urpmi --wget /downloads/RealPlayer10GOLD.rpm

+ Reply to Thread