two patches still not applicable: SUSE-2020-3304 , SUSE-2021-985
leap 15.3, upgraded from 15.2 zypper lp still lists Loading repository data... Reading installed packages... Repository | Name | Category | Severity | Interactive | Status | Since | Summary -------------------------------------------------------------+----------------+-------------+----------+-------------+--------+-------+--------------------------------------------- Update repository with updates from SUSE Linux Enterprise 15 | SUSE-2020-3304 | recommended | moderate | --- | needed | - | Recommended update for i2c-tools Update repository with updates from SUSE Linux Enterprise 15 | SUSE-2021-985 | recommended | moderate | --- | needed | - | Recommended update for the Azure SDK and CLI Found 2 applicable patches: 2 patches needed (0 security patches) but trying to install them sudo zypper in -t patch SUSE-2021-985 Loading repository data... Reading installed packages... 'patch:SUSE-2021-985' is already installed. Resolving package dependencies... Nothing to do. sudo zypper in -t patch SUSE-2020-3304 Loading repository data... Reading installed packages... Resolving package dependencies... Problem: the to be installed patch:SUSE-2020-3304-1.noarch conflicts with 'libi2c0.x86_64 < 4.0-4.3.2' provided by the installed libi2c0-4.0-bp153.2.13.x86_64 Solution 1: Following actions will be done: deinstallation of libi2c0-4.0-bp153.2.13.x86_64 deinstallation of i2c-tools-4.0-bp153.2.13.x86_64 Solution 2: do not install patch:SUSE-2020-3304-1.noarch Choose from above solutions by number or cancel [1/2/c/d/?] (c): ^C rpm -aq | grep i2c i2c-tools-4.0-bp153.2.13.x86_64 libi2c0-4.0-bp153.2.13.x86_64 How do I finally settle this mess? Can i remove the packages somehow and force to install them funamentally as whole from the repos immediately installing the latest bits without the patch routine or something? I dont remember ever having seen any azure related stuff on my opensuse systems in the past, i dont use or need or want azure? when is 15.3 actually being considered final and settled when leap 15.2 users have had and are still having these fundamental problems due to the upgrade to 15.3? is 15.3 always gonna be a second class citizen? is this to be expected for 15.4 or whatever comes next? i was really irritated and disappointed when like still within the final hours of the 15.3 release the mailing-list already showed that feature lock down for 15.4 was already being done within days. I kind of already feel the next faily stages and procedures and situations incoming for 15.4 over again. I have not yet dared and attampted to upgrade my 15.2 systems so far, when this very simple and most basic 15.2 test system expressed so many woes and bugs with the upgrade to 15.3 already :( ty
On 2021-07-13 1:53 a.m., cagsm wrote:
leap 15.3, upgraded from 15.2
zypper lp still lists
(snip)
How do I finally settle this mess? Can i remove the packages somehow and force to install them funamentally as whole from the repos immediately installing the latest bits without the patch routine or something?
I dont remember ever having seen any azure related stuff on my opensuse systems in the past, i dont use or need or want azure?
I get the same patch showing as needed on my system, and I also do not have azure installed. However, getting the patch info: zypper info SUSE-2021-985 shows a whole bunch of conflicts with many installed python packages. Here also trying to install the patch shows there is nothing to do.
Hi, I am close to finally solving this. We will replace the merged repo of all SLES servicepacks by a new openSUSE-SLES import channel which will only have the correct imported SLES updates in the next days. And then the below unapplicable patches will go away. SOrry for the delay, I was on 1.5 weeks sickleave. Ciao, Marcus On Tue, Jul 13, 2021 at 09:53:20AM +0200, cagsm wrote:
leap 15.3, upgraded from 15.2
zypper lp still lists
Loading repository data... Reading installed packages...
Repository | Name | Category | Severity | Interactive | Status | Since | Summary -------------------------------------------------------------+----------------+-------------+----------+-------------+--------+-------+--------------------------------------------- Update repository with updates from SUSE Linux Enterprise 15 | SUSE-2020-3304 | recommended | moderate | --- | needed | - | Recommended update for i2c-tools Update repository with updates from SUSE Linux Enterprise 15 | SUSE-2021-985 | recommended | moderate | --- | needed | - | Recommended update for the Azure SDK and CLI
Found 2 applicable patches: 2 patches needed (0 security patches)
but trying to install them
sudo zypper in -t patch SUSE-2021-985 Loading repository data... Reading installed packages... 'patch:SUSE-2021-985' is already installed. Resolving package dependencies... Nothing to do.
sudo zypper in -t patch SUSE-2020-3304 Loading repository data... Reading installed packages... Resolving package dependencies...
Problem: the to be installed patch:SUSE-2020-3304-1.noarch conflicts with 'libi2c0.x86_64 < 4.0-4.3.2' provided by the installed libi2c0-4.0-bp153.2.13.x86_64 Solution 1: Following actions will be done: deinstallation of libi2c0-4.0-bp153.2.13.x86_64 deinstallation of i2c-tools-4.0-bp153.2.13.x86_64 Solution 2: do not install patch:SUSE-2020-3304-1.noarch
Choose from above solutions by number or cancel [1/2/c/d/?] (c): ^C
rpm -aq | grep i2c i2c-tools-4.0-bp153.2.13.x86_64 libi2c0-4.0-bp153.2.13.x86_64
How do I finally settle this mess? Can i remove the packages somehow and force to install them funamentally as whole from the repos immediately installing the latest bits without the patch routine or something?
I dont remember ever having seen any azure related stuff on my opensuse systems in the past, i dont use or need or want azure?
when is 15.3 actually being considered final and settled when leap 15.2 users have had and are still having these fundamental problems due to the upgrade to 15.3?
is 15.3 always gonna be a second class citizen? is this to be expected for 15.4 or whatever comes next? i was really irritated and disappointed when like still within the final hours of the 15.3 release the mailing-list already showed that feature lock down for 15.4 was already being done within days. I kind of already feel the next faily stages and procedures and situations incoming for 15.4 over again.
I have not yet dared and attampted to upgrade my 15.2 systems so far, when this very simple and most basic 15.2 test system expressed so many woes and bugs with the upgrade to 15.3 already :(
ty
Hi, this issue should now be gone. Ciao, Marcus On Tue, Jul 13, 2021 at 09:53:20AM +0200, cagsm wrote:
leap 15.3, upgraded from 15.2
zypper lp still lists
Loading repository data... Reading installed packages...
Repository | Name | Category | Severity | Interactive | Status | Since | Summary -------------------------------------------------------------+----------------+-------------+----------+-------------+--------+-------+--------------------------------------------- Update repository with updates from SUSE Linux Enterprise 15 | SUSE-2020-3304 | recommended | moderate | --- | needed | - | Recommended update for i2c-tools Update repository with updates from SUSE Linux Enterprise 15 | SUSE-2021-985 | recommended | moderate | --- | needed | - | Recommended update for the Azure SDK and CLI
Found 2 applicable patches: 2 patches needed (0 security patches)
but trying to install them
sudo zypper in -t patch SUSE-2021-985 Loading repository data... Reading installed packages... 'patch:SUSE-2021-985' is already installed. Resolving package dependencies... Nothing to do.
sudo zypper in -t patch SUSE-2020-3304 Loading repository data... Reading installed packages... Resolving package dependencies...
Problem: the to be installed patch:SUSE-2020-3304-1.noarch conflicts with 'libi2c0.x86_64 < 4.0-4.3.2' provided by the installed libi2c0-4.0-bp153.2.13.x86_64 Solution 1: Following actions will be done: deinstallation of libi2c0-4.0-bp153.2.13.x86_64 deinstallation of i2c-tools-4.0-bp153.2.13.x86_64 Solution 2: do not install patch:SUSE-2020-3304-1.noarch
Choose from above solutions by number or cancel [1/2/c/d/?] (c): ^C
rpm -aq | grep i2c i2c-tools-4.0-bp153.2.13.x86_64 libi2c0-4.0-bp153.2.13.x86_64
How do I finally settle this mess? Can i remove the packages somehow and force to install them funamentally as whole from the repos immediately installing the latest bits without the patch routine or something?
I dont remember ever having seen any azure related stuff on my opensuse systems in the past, i dont use or need or want azure?
when is 15.3 actually being considered final and settled when leap 15.2 users have had and are still having these fundamental problems due to the upgrade to 15.3?
is 15.3 always gonna be a second class citizen? is this to be expected for 15.4 or whatever comes next? i was really irritated and disappointed when like still within the final hours of the 15.3 release the mailing-list already showed that feature lock down for 15.4 was already being done within days. I kind of already feel the next faily stages and procedures and situations incoming for 15.4 over again.
I have not yet dared and attampted to upgrade my 15.2 systems so far, when this very simple and most basic 15.2 test system expressed so many woes and bugs with the upgrade to 15.3 already :(
ty
participants (3)
-
cagsm -
Darryl Gregorash -
Marcus Meissner