Why http://download.opensuse.org/update/leap/15.3/sle/ includes all previous service packs?
Since SLE 11 (or may be even SLE 10) each service pack needs just two repositories - Pool and Updates (there were some deviations and of course this should be adjusted for each module but in general this holds true). I thought may be I forgot something so I installed SLES 15 SP2 (with subscription) yesterday and sure thing - the only repositories are those for SP2, there is no SP1 or SP0 anywhere. I do not have beta subscription for SLE 15 SP3 so cannot test but I would be surprised if it had been different. Why Leap 15.3 now suddenly has all previous service packs in its sle update repository? This is what seems to cause all those problems with patches for wrong SP.
On Sat, Jun 12, 2021 at 05:14:28PM +0300, Andrei Borzenkov wrote:
Since SLE 11 (or may be even SLE 10) each service pack needs just two repositories - Pool and Updates (there were some deviations and of course this should be adjusted for each module but in general this holds true).
I thought may be I forgot something so I installed SLES 15 SP2 (with subscription) yesterday and sure thing - the only repositories are those for SP2, there is no SP1 or SP0 anywhere. I do not have beta subscription for SLE 15 SP3 so cannot test but I would be surprised if it had been different.
Why Leap 15.3 now suddenly has all previous service packs in its sle update repository? This is what seems to cause all those problems with patches for wrong SP.
SLES 15 SP3 is built out of layered "codestream". We do not rebuild all packages for all service packs, on new service packs only the changed packages are in the "service pack level" codestream, others are taken from lower ones. e.g. "vim" is only built in the SLES 15 GA codestream and used in GA, SP1, SP2 and SP3. So for the sle/ tree vim updates will appear in sle-sp0/ only. This various from package to package. Some are also in all service packs, like the kernel is in every codestream level. This works as we guarantee compatibility from lower service packs to higher ones. This is different to how Leap was done before, there we rebuilt everything on the same codestream level. The problems in update stack are unrelated to that, there are 2 core problems: - the build of the sle repo assumed that all service packs have same or higher released package version-releases (so linear increasing only). We had some cases where this was not the case (same version, lower releasenr) and these showed up as errors. (gzip, numactl, build, webkit2gtk3, libreoffice, tomcat, google-poppins-fonts, etc.) - We so far strictly assumed that Backports and SLE packages do not overlap. Still we have several cases where this happens (libmodulemd, librepo, gnu-hpc-compilers, obs-service-tar_scm, eclipse) where it was violated and now leads to problems. I am resolving those as I find them / they get reported. Ciao, Marcus
On Mon, Jun 14, 2021 at 5:57 PM Marcus Meissner <meissner@suse.de> wrote:
I am resolving those as I find them / they get reported.
15.3, current at UTC at 9:51, June 15, 2021 still shows to patches that apparently have trouble being applied? zypper lp 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 zypper patch 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): ======= ty.
On Tue, Jun 15, 2021 at 11:52:44AM +0200, cagsm wrote:
On Mon, Jun 14, 2021 at 5:57 PM Marcus Meissner <meissner@suse.de> wrote:
I am resolving those as I find them / they get reported.
15.3, current at UTC at 9:51, June 15, 2021
still shows to patches that apparently have trouble being applied?
zypper lp 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
zypper patch 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):
=======
ty.
Here we have another case where i2c-tools is in BOTH backports and SLE in the same version, which should not have happened. I need to find out how to fix that. What is the conflict with SUSE-2021-985 ? (If it is python3-pycryptodome it is known and will be fixed.) zypper in -t patch SUSE-2021-985 Ciao, Marcus
On Tue, Jun 15, 2021 at 11:59 AM Marcus Meissner <meissner@suse.de> wrote:
What is the conflict with SUSE-2021-985 ? (If it is python3-pycryptodome it is known and will be fixed.) zypper in -t patch SUSE-2021-985
dunno, it says it is already installed: sudo zypper in -t patch SUSE-2021-985 [sudo] password for root: Loading repository data... Reading installed packages... 'patch:SUSE-2021-985' is already installed. Resolving package dependencies... Nothing to do. but a zypper lp still lists both of them, same as above in my reply. sudo zypper lp 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) ======= ty.
On Monday, 14 June 2021 16:39:54 CEST Marcus Meissner wrote: [...]
Still we have several cases where this happens (libmodulemd, librepo, gnu-hpc-compilers, obs-service-tar_scm, eclipse) where it was violated and now leads to problems.
I am resolving those as I find them / they get reported.
Ciao, Marcus
I have another problem: patch:SUSE-2021-750-1 (I guess SUSE-2020-2950-1 is the soon fixed python3-pycryptodome problem?) The details # zypper patch Loading repository data... Reading installed packages... Resolving package dependencies... 2 Problems: Problem: the to be installed patch:SUSE-2021-750-1.noarch conflicts with 'python3-Cython.x86_64 < 0.29.14-4.3.1' provided by the installed python3-Cython-0.29.14-1.36.x86_64 Problem: the to be installed patch:SUSE-2020-2950-1.noarch conflicts with 'python3-pycryptodome.x86_64 < 3.9.0-3.3.2' provided by the installed python3-pycryptodome-3.9.0-1.44.x86_64 Problem: the to be installed patch:SUSE-2021-750-1.noarch conflicts with 'python3-Cython.x86_64 < 0.29.14-4.3.1' provided by the installed python3-Cython-0.29.14-1.36.x86_64 Solution 1: Following actions will be done: deinstallation of python3-Cython-0.29.14-1.36.x86_64 deinstallation of python3-pandas-0.23.4-bp153.1.19.x86_64 deinstallation of python3-xarray-0.13.0-bp153.1.14.noarch Solution 2: do not install patch:SUSE-2021-750-1.noarch Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c/d/?] (c): # zypper in -t patch patch:SUSE-2021-750-1 Loading repository data... Reading installed packages... Resolving package dependencies... Problem: the to be installed patch:SUSE-2021-750-1.noarch conflicts with 'python3-Cython.x86_64 < 0.29.14-4.3.1' provided by the installed python3-Cython-0.29.14-1.36.x86_64 Solution 1: Following actions will be done: deinstallation of python3-Cython-0.29.14-1.36.x86_64 deinstallation of python3-pandas-0.23.4-bp153.1.19.x86_64 deinstallation of python3-xarray-0.13.0-bp153.1.14.noarch Solution 2: do not install patch:SUSE-2021-750-1.noarch Choose from above solutions by number or cancel [1/2/c/d/?] (c): # zypper in -t patch patch:SUSE-2020-2950-1 Loading repository data... Reading installed packages... Resolving package dependencies... Problem: the to be installed patch:SUSE-2020-2950-1.noarch conflicts with 'python3-pycryptodome.x86_64 < 3.9.0-3.3.2' provided by the installed python3-pycryptodome-3.9.0-1.44.x86_64 Solution 1: deinstallation of python3-pycryptodome-3.9.0-1.44.x86_64 Solution 2: do not install patch:SUSE-2020-2950-1.noarch Choose from above solutions by number or cancel [1/2/c/d/?] (c): -- Mit freundlichen Gruessen, Andreas Vetter
On Wednesday, 16 June 2021 09:27:37 CEST Andreas Vetter wrote:
On Monday, 14 June 2021 16:39:54 CEST Marcus Meissner wrote: [...]
Still we have several cases where this happens (libmodulemd, librepo, gnu-hpc-compilers, obs-service-tar_scm, eclipse) where it was violated and now leads to problems.
I am resolving those as I find them / they get reported.
Ciao, Marcus
I have another problem: patch:SUSE-2021-750-1 (I guess SUSE-2020-2950-1 is the soon fixed python3-pycryptodome problem?) The details
# zypper patch Loading repository data... Reading installed packages... Resolving package dependencies... 2 Problems: Problem: the to be installed patch:SUSE-2021-750-1.noarch conflicts with 'python3-Cython.x86_64 < 0.29.14-4.3.1' provided by the installed python3-Cython-0.29.14-1.36.x86_64 Problem: the to be installed patch:SUSE-2020-2950-1.noarch conflicts with 'python3-pycryptodome.x86_64 < 3.9.0-3.3.2' provided by the installed python3-pycryptodome-3.9.0-1.44.x86_64
Problem: the to be installed patch:SUSE-2021-750-1.noarch conflicts with 'python3-Cython.x86_64 < 0.29.14-4.3.1' provided by the installed python3-Cython-0.29.14-1.36.x86_64 Solution 1: Following actions will be done: deinstallation of python3-Cython-0.29.14-1.36.x86_64 deinstallation of python3-pandas-0.23.4-bp153.1.19.x86_64 deinstallation of python3-xarray-0.13.0-bp153.1.14.noarch Solution 2: do not install patch:SUSE-2021-750-1.noarch
Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c/d/?] (c):
# zypper in -t patch patch:SUSE-2021-750-1 Loading repository data... Reading installed packages... Resolving package dependencies...
Problem: the to be installed patch:SUSE-2021-750-1.noarch conflicts with 'python3-Cython.x86_64 < 0.29.14-4.3.1' provided by the installed python3-Cython-0.29.14-1.36.x86_64 Solution 1: Following actions will be done: deinstallation of python3-Cython-0.29.14-1.36.x86_64 deinstallation of python3-pandas-0.23.4-bp153.1.19.x86_64 deinstallation of python3-xarray-0.13.0-bp153.1.14.noarch Solution 2: do not install patch:SUSE-2021-750-1.noarch
Choose from above solutions by number or cancel [1/2/c/d/?] (c):
# zypper in -t patch patch:SUSE-2020-2950-1 Loading repository data... Reading installed packages... Resolving package dependencies...
Problem: the to be installed patch:SUSE-2020-2950-1.noarch conflicts with 'python3-pycryptodome.x86_64 < 3.9.0-3.3.2' provided by the installed python3-pycryptodome-3.9.0-1.44.x86_64 Solution 1: deinstallation of python3-pycryptodome-3.9.0-1.44.x86_64 Solution 2: do not install patch:SUSE-2020-2950-1.noarch
Choose from above solutions by number or cancel [1/2/c/d/?] (c):
https://bugzilla.opensuse.org/show_bug.cgi?id=1187450 -- Mit freundlichen Gruessen, Andreas Vetter
On Thu, Jun 17, 2021 at 10:06:38AM +0200, Andreas Vetter wrote:
On Wednesday, 16 June 2021 09:27:37 CEST Andreas Vetter wrote:
On Monday, 14 June 2021 16:39:54 CEST Marcus Meissner wrote: [...]
Still we have several cases where this happens (libmodulemd, librepo, gnu-hpc-compilers, obs-service-tar_scm, eclipse) where it was violated and now leads to problems.
I am resolving those as I find them / they get reported.
Ciao, Marcus
I have another problem: patch:SUSE-2021-750-1 (I guess SUSE-2020-2950-1 is the soon fixed python3-pycryptodome problem?) The details
# zypper patch Loading repository data... Reading installed packages... Resolving package dependencies... 2 Problems: Problem: the to be installed patch:SUSE-2021-750-1.noarch conflicts with 'python3-Cython.x86_64 < 0.29.14-4.3.1' provided by the installed python3-Cython-0.29.14-1.36.x86_64 Problem: the to be installed patch:SUSE-2020-2950-1.noarch conflicts with 'python3-pycryptodome.x86_64 < 3.9.0-3.3.2' provided by the installed python3-pycryptodome-3.9.0-1.44.x86_64
Problem: the to be installed patch:SUSE-2021-750-1.noarch conflicts with 'python3-Cython.x86_64 < 0.29.14-4.3.1' provided by the installed python3-Cython-0.29.14-1.36.x86_64 Solution 1: Following actions will be done: deinstallation of python3-Cython-0.29.14-1.36.x86_64 deinstallation of python3-pandas-0.23.4-bp153.1.19.x86_64 deinstallation of python3-xarray-0.13.0-bp153.1.14.noarch Solution 2: do not install patch:SUSE-2021-750-1.noarch
Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c/d/?] (c):
# zypper in -t patch patch:SUSE-2021-750-1 Loading repository data... Reading installed packages... Resolving package dependencies...
Problem: the to be installed patch:SUSE-2021-750-1.noarch conflicts with 'python3-Cython.x86_64 < 0.29.14-4.3.1' provided by the installed python3-Cython-0.29.14-1.36.x86_64 Solution 1: Following actions will be done: deinstallation of python3-Cython-0.29.14-1.36.x86_64 deinstallation of python3-pandas-0.23.4-bp153.1.19.x86_64 deinstallation of python3-xarray-0.13.0-bp153.1.14.noarch Solution 2: do not install patch:SUSE-2021-750-1.noarch
Choose from above solutions by number or cancel [1/2/c/d/?] (c):
# zypper in -t patch patch:SUSE-2020-2950-1 Loading repository data... Reading installed packages... Resolving package dependencies...
Problem: the to be installed patch:SUSE-2020-2950-1.noarch conflicts with 'python3-pycryptodome.x86_64 < 3.9.0-3.3.2' provided by the installed python3-pycryptodome-3.9.0-1.44.x86_64 Solution 1: deinstallation of python3-pycryptodome-3.9.0-1.44.x86_64 Solution 2: do not install patch:SUSE-2020-2950-1.noarch
Choose from above solutions by number or cancel [1/2/c/d/?] (c):
Danke! pycryptodome ist released, python3-Cython ist in qa. Ciao, Marcus
participants (4)
-
Andreas Vetter -
Andrei Borzenkov -
cagsm -
Marcus Meissner