Mailinglist Archive: opensuse-factory (765 mails)

< Previous Next >
Re: [opensuse-factory] upgrade packaging not statically built
On Tue, 2017-11-14 at 05:25 -0500, Felix Miata wrote:
martin@xxxxxxxxxxx composed on 2017-11-14 10:58 (UTC+0100):

And "zypper dup" works - installing zypper from Leap 15 on Leap
42.3
does not work - my understatnding from boo#1067737 and from current
discussion is that breakage is not result of upgrading while using
zypper but consequence of user meddling with upgrade process and
trying
to use binary from future release on old one.

What I see is that it broke because zypper depends on something that
its real
world dependency chain does not require be installed/upgraded along
with it, one
potential brokenness my (upgrade package management system first,
then
everything else) process used was intended to avoid. Broken zypper
has never
happened here in over three years of consistently using the (package
management
first script) process for both ordinary updates and distribution
upgrades.
Well according to [1] zypper correctly states that action that you want
it to perform is not possible to procees while maitnaining fulfilled
dependencies. You can of course force zypper to proceed, which is what
I assume happened in attempts before. I still fail to see error on side
of openSUSE/zypper.

Regards

Martin

1. https://bugzilla.opensuse.org/show_bug.cgi?id=1067737#c2
< Previous Next >