Last zypper dup on this 64 bit system belonging to Bob Stia was less than a week ago. None of my own systems have anything 64 bit. Today I tried again, after 'zypper dup -r KDE49'. Now it wants to downgrade 23 packages including Firefox and SeaMonkey, and install 68 new packages, most of which are lib*32bit. There are only 5 to upgrade, 4 of which are qt3/kde3. Should I try again some other time? Something else?
On Fri, 17 Aug 2012 15:33:16 -0400 Felix Miata mrmazda@earthlink.net wrote:
Last zypper dup on this 64 bit system belonging to Bob Stia was less than a week ago. None of my own systems have anything 64 bit. Today I tried again, after 'zypper dup -r KDE49'. Now it wants to downgrade 23 packages including Firefox and SeaMonkey, and install 68 new packages, most of which are lib*32bit. There are only 5 to upgrade, 4 of which are qt3/kde3. Should I try again some other time? Something else?
Have the same issue...
Hello,
Am Freitag, 17. August 2012 schrieb Felix Miata:
Last zypper dup on this 64 bit system belonging to Bob Stia was less than a week ago. None of my own systems have anything 64 bit. Today I tried again, after 'zypper dup -r KDE49'. Now it wants to downgrade 23 packages including Firefox and SeaMonkey, and install 68 new packages, most of which are lib*32bit. There are only 5 to upgrade, 4 of which are qt3/kde3. Should I try again some other time? Something else?
That sounds like you should try again later - probably some packages were not built for x86_64 yet.
If you want to upgrade _now_, use zypper up instead of dup. This will update less packages, but avoids the arch change.
That's a general answer for everybody running "zypper dup".
The only thing I can say about the KDE 4.9 repo is that is has lots of packages that are still building or scheduled for build, which means: wait ;-) (It might take some time, the OBS monitor says there are about 10000 packages for each arch in the queue.)
Regards,
Christian Boltz
On 2012/08/17 22:51 (GMT+0200) Christian Boltz composed:
Felix Miata composed:
Last zypper dup on this 64 bit system belonging to Bob Stia was less than a week ago. None of my own systems have anything 64 bit. Today I tried again, after 'zypper dup -r KDE49'. Now it wants to downgrade 23 packages including Firefox and SeaMonkey, and install 68 new packages, most of which are lib*32bit. There are only 5 to upgrade, 4 of which are qt3/kde3. Should I try again some other time? Something else?
That sounds like you should try again later - probably some packages were not built for x86_64 yet.
If you want to upgrade _now_, use zypper up instead of dup. This will update less packages, but avoids the arch change.
I waited a few hours and did zypper up. Only the 5 packages were upgraded, nothing else affected.
That's a general answer for everybody running "zypper dup".
I don't sense that's a sensible answer on this mailing list. On any release-next prior to version freeze, I expect only dup to do what's needed, so I'm in the habit of using dup for the duration of any release-next. What might I be misunderstanding about the difference between dup and up?
The only thing I can say about the KDE 4.9 repo is that is has lots of packages that are still building or scheduled for build, which means: wait ;-) (It might take some time, the OBS monitor says there are about 10000 packages for each arch in the queue.)
On Bob's system I needed 4.9 due to https://bugs.kde.org/show_bug.cgi?id=305161 which unfortunately doesn't go far enough.
Hello,
Am Samstag, 18. August 2012 schrieb Felix Miata:
On 2012/08/17 22:51 (GMT+0200) Christian Boltz composed:
Felix Miata composed:
[zypper dup wants to drop in several 32bit packages]
That's a general answer for everybody running "zypper dup".
I don't sense that's a sensible answer on this mailing list. On any release-next prior to version freeze, I expect only dup to do what's needed, so I'm in the habit of using dup for the duration of any release-next. What might I be misunderstanding about the difference between dup and up?
dup updates more aggressive and does some things that up doesn't: - vendor/repo changes - arch changes
Yes, usually[tm] dup is the recommended way for upgrading your system, but if you see some strange things (like installing 32bit packages on a 64bit system), stay on the safe side and use only up.
I hope this answers your question - if not, ask ;-)
The only thing I can say about the KDE 4.9 repo is that is has lots of packages that are still building or scheduled for build, which means: wait ;-) (It might take some time, the OBS monitor says there are about 10000 packages for each arch in the queue.)
On Bob's system I needed 4.9 due to https://bugs.kde.org/show_bug.cgi?id=305161 which unfortunately doesn't go far enough.
In the meantime, the KDE49 repo has completely been build and published: https://build.opensuse.org/project/monitor?project=KDE%3ARelease%3A49
Try zypper dup (yes, dup) again ;-)
Regards,
Christian Boltz
On 2012/08/19 14:17 (GMT+0200) Christian Boltz composed:
dup updates more aggressive and does some things that up doesn't:
- vendor/repo changes
- arch changes
This I knew, assuming zypp.conf defaults remain in place.
Yes, usually[tm] dup is the recommended way for upgrading your system, but if you see some strange things (like installing 32bit packages on a 64bit system), stay on the safe side and use only up.
I hope this answers your question - if not, ask ;-)
In the meantime, the KDE49 repo has completely been build and published: https://build.opensuse.org/project/monitor?project=KDE%3ARelease%3A49
Try zypper dup (yes, dup) again ;-)
On first try of zypper dup -r KDE49 it complained of a dep to an unavailable 586 package. Doing zypper rm libkolabxml0 first than then doing zypper dup -r KDE49 again fixed that, though 7 packages were downgrades, e.g. konsole from installed -56.2 to -55.1 & gwenview from -53.2 to -52.1. How does that happen?
Afterward I tried another dup but without -r KDE49. Again it wanted to downgrade the Geckos and several others and install a heap of new 32 bit packages. Doing zypper up instead upgraded 8.
It seems the KDE3 repo must be being rebuilt constantly. I can't remember the last time I updated any system with any KDE3 packages installed that there weren't at least some KDE3 packages updated.
After I was done I did rpm -qa | grep 586, which produced master-boot-code and xf86-video-geode. The first I can understand, but why anything Xorg?
On Sunday 2012-08-19 16:12, Felix Miata wrote:
On 2012/08/19 14:17 (GMT+0200) Christian Boltz composed:
On first try of zypper dup -r KDE49 [...] After I was done I did rpm -qa | grep 586, which produced master-boot-code and xf86-video-geode. The first I can understand, but why anything Xorg?
Could it be that xorg-x11-driver-video was updated? xorg-x11-driver-video has a "Recommends: xf86-video-geode", and zypper defaults to installing recommends. ("onlyRequires=off" in zypp.conf or zypper dup --no-rec)
And once one allows recommends to creep in, lots of extra branches in the dependency tree suddenly light up and can install packages you never even heard of. :)
-
Christian Boltz -
Felix Miata -
Jan Engelhardt -
Robert Milasan