Hi Folks, I have a question about zypper or libzypp. I found out that on SLES 15 SP1 the package openswan has been updated from 5.6.0 to 5.8.2 via patch:SUSE-SLE-Module-Basesystem-15-SP1-2020-743-1. That's bad because the update breaks my connection via IPsec to SAP. So I reverted to the old packages. The connection runs again. But how can I make sure that this patch is never applied again? I tried "zypper al 'strongsw*'". "zypper al" shows that, and "zypper up" does not show any package with "strongsw" at the beginning in the list of packages to be updated. That's OK. But "zypper patch" still annoys me by showing 2 "Solutions": No 1 being to remove the lock, No 2 "do not install patch:SUSE-SLE-Module-Basesystem-15-SP1-2020-743-1.noarch. So I used "zypper al" to add this patch. It shows with "zypper ll", but it is ignored, "zypper patch" still shows 2 solutions. Since there is a "zypper -n patch" running daily, and it exits with Errorlevel 4, I'd love to have a way so that this patch does not show up for "zypper patch", which works fine with "zypper up". "zypper patch" should see that there is a patch in the zypper lock list and should ignore this patch for its action. Can I get this to work? Regards, Werner -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello, In the Message; Subject : [opensuse] how to not apply a patch Message-ID : <120befd8-4cd2-a472-cb0e-863a340286d8@email.de> Date & Time: Tue, 7 Apr 2020 12:42:21 +0200 [WF] == Werner Flamme <werner.flamme@email.de> has written: WF> Hi Folks, WF> I have a question about zypper or libzypp. WF> I found out that on SLES 15 SP1 the package openswan has been updated WF> from 5.6.0 to 5.8.2 via patch:SUSE-SLE-Module-Basesystem-15-SP1-2020-743-1. WF> That's bad because the update breaks my connection via IPsec to SAP. So WF> I reverted to the old packages. The connection runs again. WF> But how can I make sure that this patch is never applied again? WF> I tried "zypper al 'strongsw*'". "zypper al" shows that, and "zypper up" WF> does not show any package with "strongsw" at the beginning in the list WF> of packages to be updated. That's OK. WF> But "zypper patch" still annoys me by showing 2 "Solutions": No 1 being WF> to remove the lock, No 2 "do not install WF> patch:SUSE-SLE-Module-Basesystem-15-SP1-2020-743-1.noarch. WF> So I used "zypper al" to add this patch. It shows with "zypper ll", but WF> it is ignored, "zypper patch" still shows 2 solutions. WF> Since there is a "zypper -n patch" running daily, and it exits with WF> Errorlevel 4, I'd love to have a way so that this patch does not show up WF> for "zypper patch", which works fine with "zypper up". "zypper patch" WF> should see that there is a patch in the zypper lock list and should WF> ignore this patch for its action. WF> Can I get this to work? How about doing this? Write to /etc/zypy/locks, as follows; type: package match_type: exact case_sensitive: on solvable_name: openswan Regards, --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Bill! You married with Computer. Not with Me!" "No..., with money." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 07.04.2020 um 13:09 schrieb Masaru Nomiya:
Hello,
In the Message;
Subject : [opensuse] how to not apply a patch Message-ID : <120befd8-4cd2-a472-cb0e-863a340286d8@email.de> Date & Time: Tue, 7 Apr 2020 12:42:21 +0200
[WF] == Werner Flamme <werner.flamme@email.de> has written:
WF> Hi Folks,
WF> I have a question about zypper or libzypp.
WF> I found out that on SLES 15 SP1 the package openswan has been updated WF> from 5.6.0 to 5.8.2 via patch:SUSE-SLE-Module-Basesystem-15-SP1-2020-743-1.
WF> That's bad because the update breaks my connection via IPsec to SAP. So WF> I reverted to the old packages. The connection runs again.
WF> But how can I make sure that this patch is never applied again?
WF> I tried "zypper al 'strongsw*'". "zypper al" shows that, and "zypper up" WF> does not show any package with "strongsw" at the beginning in the list WF> of packages to be updated. That's OK.
WF> But "zypper patch" still annoys me by showing 2 "Solutions": No 1 being WF> to remove the lock, No 2 "do not install WF> patch:SUSE-SLE-Module-Basesystem-15-SP1-2020-743-1.noarch.
WF> So I used "zypper al" to add this patch. It shows with "zypper ll", but WF> it is ignored, "zypper patch" still shows 2 solutions.
WF> Since there is a "zypper -n patch" running daily, and it exits with WF> Errorlevel 4, I'd love to have a way so that this patch does not show up WF> for "zypper patch", which works fine with "zypper up". "zypper patch" WF> should see that there is a patch in the zypper lock list and should WF> ignore this patch for its action.
WF> Can I get this to work?
How about doing this?
Write to /etc/zypy/locks, as follows;
type: package match_type: exact case_sensitive: on solvable_name: openswan
Thank you. My entry reads: type: package match_type: glob case_sensitive: on solvable_name: strongsw* There are several packages with names beginning with "strongswan", so I did not want this as an exact text. It works fine for "zypper up", but does not for "zypper patch". Regards, Werner -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/04/2020 12.42, Werner Flamme wrote:
Hi Folks,
I have a question about zypper or libzypp.
I found out that on SLES 15 SP1 the package openswan has been updated from 5.6.0 to 5.8.2 via patch:SUSE-SLE-Module-Basesystem-15-SP1-2020-743-1.
That's bad because the update breaks my connection via IPsec to SAP. So I reverted to the old packages. The connection runs again.
You should report this in bugzilla. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
Am 07.04.2020 um 13:15 schrieb Carlos E.R.:
On 07/04/2020 12.42, Werner Flamme wrote:
Hi Folks,
I have a question about zypper or libzypp.
I found out that on SLES 15 SP1 the package openswan has been updated from 5.6.0 to 5.8.2 via patch:SUSE-SLE-Module-Basesystem-15-SP1-2020-743-1.
That's bad because the update breaks my connection via IPsec to SAP. So I reverted to the old packages. The connection runs again.
You should report this in bugzilla.
I will do soon, but this won't solve my "zypper patch" probelm :-\ -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
07.04.2020 14:59, Werner Flamme пишет:
Am 07.04.2020 um 13:15 schrieb Carlos E.R.:
On 07/04/2020 12.42, Werner Flamme wrote:
Hi Folks,
I have a question about zypper or libzypp.
I found out that on SLES 15 SP1 the package openswan has been updated from 5.6.0 to 5.8.2 via patch:SUSE-SLE-Module-Basesystem-15-SP1-2020-743-1.
That's bad because the update breaks my connection via IPsec to SAP. So I reverted to the old packages. The connection runs again.
You should report this in bugzilla.
I will do soon, but this won't solve my "zypper patch" probelm :-\
You should report this in bugzilla too ... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 4/7/20 7:59 AM, Werner Flamme wrote:
Am 07.04.2020 um 13:15 schrieb Carlos E.R.:
On 07/04/2020 12.42, Werner Flamme wrote:
Hi Folks,
I have a question about zypper or libzypp.
I found out that on SLES 15 SP1 the package openswan has been updated from 5.6.0 to 5.8.2 via patch:SUSE-SLE-Module-Basesystem-15-SP1-2020-743-1.
That's bad because the update breaks my connection via IPsec to SAP. So I reverted to the old packages. The connection runs again.
You should report this in bugzilla.
I will do soon, but this won't solve my "zypper patch" probelm :-\
In YaST a package can be given a "Protect - Do Not Modify" status, which should prevent patching (I think, I've never tested this specifically for this purpose). I don't know the zypper equivalent. --dg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 07.04.2020 um 18:54 schrieb DennisG:
In YaST a package can be given a "Protect - Do Not Modify" status, which should prevent patching (I think, I've never tested this specifically for this purpose). I don't know the zypper equivalent.
Both "yast sw_single" and setting the lock and "zypper al" result in an entry in file /etc/zypp/locks :) Werner -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello, Am Dienstag, 7. April 2020, 12:42:21 CEST schrieb Werner Flamme:
So I used "zypper al" to add this patch. It shows with "zypper ll", but it is ignored, "zypper patch" still shows 2 solutions.
try zypper al -t patch $patchname Regards, Christian Boltz -- I prefer to inconvenience the burglars if I can ;-) [Carlos E. R. in opensuse-factory about disk encryption] -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
Andrei Borzenkov -
Carlos E.R. -
Christian Boltz -
DennisG -
Masaru Nomiya -
Werner Flamme