how many breakage is 15.2 online dup to 15.3 beta supposed to bring?
Hi there hard factory workers, just wanted to zypper --releasever=15.3 dup --download-in-advance --allow-vendor-change Warning: Enforced setting: $releasever=15.3 Loading repository data... Reading installed packages... Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Computing distribution upgrade... Problem: nothing provides libgenrand-samba4.so(SAMBA_4.11.14_GIT.202.344B137B75D4.14.1_SUSE_OS15.0_I386) needed by libndr0-32bit-4.11.14+git.202.344b137b75d-4.14.1.x86_64 Solution 1: Following actions will be done: keep obsolete libndr0-32bit-4.11.14+git.202.344b137b75d-lp152.3.16.1.x86_64 keep obsolete samba-libs-32bit-4.11.14+git.202.344b137b75d-lp152.3.16.1.x86_64 Solution 2: deinstallation of libndr0-32bit-4.11.14+git.202.344b137b75d-lp152.3.16.1.x86_64 Solution 3: break libndr0-32bit-4.11.14+git.202.344b137b75d-4.14.1.x86_64 by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/3/c/d/?] (c): ---------- What now? normal working 15.2 x64 here, test machine. why no dup to 15.3? package missing on the 15.3 level? TY
On Fri, Mar 5, 2021 at 2:08 PM cagsm <cumandgets0mem00f@gmail.com> wrote:
zypper --releasever=15.3 dup --download-in-advance --allow-vendor-change Problem: nothing provides libgenrand-samba4.so(SAMBA_4.11.14_GIT.202.344B137B75D4.14.1_SUSE_OS15.0_I386) needed by libndr0-32bit-4.11.14+git.202.344b137b75d-4.14.1.x86_64 Solution 1: Following actions will be done: keep obsolete libndr0-32bit-4.11.14+git.202.344b137b75d-lp152.3.16.1.x86_64 keep obsolete samba-libs-32bit-4.11.14+git.202.344b137b75d-lp152.3.16.1.x86_64 Solution 2: deinstallation of libndr0-32bit-4.11.14+git.202.344b137b75d-lp152.3.16.1.x86_64 Solution 3: break libndr0-32bit-4.11.14+git.202.344b137b75d-4.14.1.x86_64 by ignoring some of its dependencies
this 15.2 system has that file at: /usr/lib64/samba/libgenrand-samba4.so rpm -qf /usr/lib/samba/libgenrand-samba4.so samba-libs-32bit-4.11.14+git.202.344b137b75d-lp152.3.16.1.x86_64 rpm -qi samba-libs-32bit-4.11.14+git.202.344b137b75d-lp152.3.16.1.x86_64 Name : samba-libs-32bit Version : 4.11.14+git.202.344b137b75d Release : lp152.3.16.1 Architecture: x86_64 Install Date: Mon Nov 2 18:45:54 2020 Group : Development/Libraries/C and C++ Size : 15347748 License : GPL-3.0-or-later Signature : RSA/SHA256, Thu Oct 29 23:53:48 2020, Key ID b88b2fd43dbdc284 Source RPM : samba-4.11.14+git.202.344b137b75d-lp152.3.16.1.src.rpm Build Date : Thu Oct 29 23:53:03 2020 Build Host : build85 Relocations : (not relocatable) Packager : http://bugs.opensuse.org Vendor : openSUSE URL : https://www.samba.org/ Summary : Samba libraries Description : The samba-libs package contains the libraries needed by programs that link against the SMB, RPC and other protocols provided by the Samba suite. Distribution: openSUSE Leap 15.2 So what now? Should we stay away from 15.3 beta just for a good longer little while? Wasnt zypper dup not as well listed in the spreadsheet of 15.3 beta for bugreporting et al? Is it simply pointless to test 15.3 beta? just yet? What would happen when trying to go for an offline .iso based 15.3 upgrade? What would the update routine do about this situation? TY
Here I'd open a bug against 15.3/samba specifically, because we've "unified" samba functionality and seems like we also broke the upgrade path. Thank you On Fri, 2021-03-05 at 15:17 +0100, cagsm wrote:
On Fri, Mar 5, 2021 at 2:08 PM cagsm <cumandgets0mem00f@gmail.com> wrote:
zypper --releasever=15.3 dup --download-in-advance --allow-vendor- change Problem: nothing provides libgenrand- samba4.so(SAMBA_4.11.14_GIT.202.344B137B75D4.14.1_SUSE_OS15.0_I386) needed by libndr0-32bit-4.11.14+git.202.344b137b75d-4.14.1.x86_64 Solution 1: Following actions will be done: keep obsolete libndr0-32bit-4.11.14+git.202.344b137b75d- lp152.3.16.1.x86_64 keep obsolete samba-libs-32bit-4.11.14+git.202.344b137b75d- lp152.3.16.1.x86_64 Solution 2: deinstallation of libndr0-32bit-4.11.14+git.202.344b137b75d-lp152.3.16.1.x86_64 Solution 3: break libndr0-32bit-4.11.14+git.202.344b137b75d-4.14.1.x86_64 by ignoring some of its dependencies
this 15.2 system has that file at:
/usr/lib64/samba/libgenrand-samba4.so
rpm -qf /usr/lib/samba/libgenrand-samba4.so samba-libs-32bit-4.11.14+git.202.344b137b75d-lp152.3.16.1.x86_64
rpm -qi samba-libs-32bit-4.11.14+git.202.344b137b75d- lp152.3.16.1.x86_64 Name : samba-libs-32bit Version : 4.11.14+git.202.344b137b75d Release : lp152.3.16.1 Architecture: x86_64 Install Date: Mon Nov 2 18:45:54 2020 Group : Development/Libraries/C and C++ Size : 15347748 License : GPL-3.0-or-later Signature : RSA/SHA256, Thu Oct 29 23:53:48 2020, Key ID b88b2fd43dbdc284 Source RPM : samba-4.11.14+git.202.344b137b75d-lp152.3.16.1.src.rpm Build Date : Thu Oct 29 23:53:03 2020 Build Host : build85 Relocations : (not relocatable) Packager : http://bugs.opensuse.org Vendor : openSUSE URL : https://www.samba.org/ Summary : Samba libraries Description : The samba-libs package contains the libraries needed by programs that link against the SMB, RPC and other protocols provided by the Samba suite. Distribution: openSUSE Leap 15.2
So what now? Should we stay away from 15.3 beta just for a good longer little while? Wasnt zypper dup not as well listed in the spreadsheet of 15.3 beta for bugreporting et al? Is it simply pointless to test 15.3 beta? just yet? What would happen when trying to go for an offline .iso based 15.3 upgrade? What would the update routine do about this situation?
TY
-- Best regards Lubos Kocman Release Manager openSUSE Leap SUSE LINUX, s.r.o. Krizikova 148/34 tel: +49 173 5876850 186 00 Praha 8 http://www.suse.com Czech Republic
On Fri, Mar 5, 2021 at 4:26 PM Lubos Kocman <lubos.kocman@suse.com> wrote:
Here I'd open a bug against 15.3/samba specifically, because we've "unified" samba functionality and seems like we also broke the upgrade path.
There seem to be some bugs filed on bugzilla already about dup troubles. But how would I continue from that zypper question from there, what is the ultimate decision to be made to be able to continue the dup from 15.2 to 15.3? Or is this currently impossible to continue the upgrade in a meaningful way. How often does the 15.3 repositories become updated and enhanced that such a bug would vanish and that a dup could continue onwards successfully? TY.
participants (2)
-
cagsm -
Lubos Kocman