# zypper patch date command is directely updating latest kerne

**URL:** <https://forums.suse.com/t/zypper-patch-date-command-is-directely-updating-latest-kerne/30660>\
**Category:** SLES Updates\
**Created:** [December 11, 2017, 9:44pm UTC](https://forums.suse.com/t/zypper-patch-date-command-is-directely-updating-latest-kerne/30660 "2017-12-11T21:44:55Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![bpquerries](https://avatars.discourse-cdn.com/v4/letter/b/57b2e6/32.png) [@bpquerries](https://forums.suse.com/u/bpquerries)\
**Post date:** [December 11, 2017, 9:44pm UTC](https://forums.suse.com/t/zypper-patch-date-command-is-directely-updating-latest-kerne/30660/1 "2017-12-11T21:44:55Z")

</div>

We have updated patch on our server SP2 with patch date 2017-10-04. It is updated to the kernel version 4.4.90-92.45.1 which is released on 2017-10-25. How it is updated to the latest one even if we have provided the patch date as 2017-10-04. It should be the patch level released before 2017-10-04?

---

<div class="post-metadata">

**Author:** ![ab1](https://avatars.discourse-cdn.com/v4/letter/a/d2c977/32.png) [@ab1](https://forums.suse.com/u/ab1)\
**Post date:** [December 11, 2017, 10:10pm UTC](https://forums.suse.com/t/zypper-patch-date-command-is-directely-updating-latest-kerne/30660/2 "2017-12-11T22:10:06Z")

</div>

What command did you apply to your server to do the update?

Also, I presume this is SLES 12 SP2, as nothing else makes sense. You may  
have specified that in the forum web UI, but I cannot tell from here.

–  
Good luck.

If you find this post helpful and are logged into the web interface,  
show your appreciation and click on the star below.

If you want to send me a private message, please let me know in the  
forum as I do not use the web interface often.

---

<div class="post-metadata">

**Author:** ![bpquerries](https://avatars.discourse-cdn.com/v4/letter/b/57b2e6/32.png) [@bpquerries](https://forums.suse.com/u/bpquerries)\
**Post date:** [December 12, 2017, 8:19am UTC](https://forums.suse.com/t/zypper-patch-date-command-is-directely-updating-latest-kerne/30660/3 "2017-12-12T08:19:05Z")

</div>

zypper patch --date 2017-10-04

yes, it is SLES12 SP2

---

<div class="post-metadata">

**Author:** ![smflood](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/smflood/32/10576_2.png) [@smflood](https://forums.suse.com/u/smflood)\
**Post date:** [December 12, 2017, 2:52pm UTC](https://forums.suse.com/t/zypper-patch-date-command-is-directely-updating-latest-kerne/30660/4 "2017-12-12T14:52:44Z")

</div>

On 12/12/17 06:24, bpquerries wrote:  
[color=blue]

> zypper patch --date 2017-10-04[/color]

My understanding of the above is the same as yours, in that it should  
not install patches on or after the date given.  
[color=blue]

> yes, it is SLES12 SP2[/color]

I’ve just set up a test server with SLES12 SP2 and can duplicate this.  
Interestingly, on a freshly installed (and so unpatched) server at the  
very beginning of “zypper patch --date 2017-04” it reports various  
patches, including SUSE-SLE-SERVER-12-SP2-2017-1786, as being issued  
after the specified date … yet it still installed them.

Let me ask my SUSE contacts.

## HTH.

Simon  
SUSE Knowledge Partner

* * *

## If you find this post helpful and are logged into the web interface, please show your appreciation and click on the star below. Thanks.

---

<div class="post-metadata">

**Author:** ![bpquerries](https://avatars.discourse-cdn.com/v4/letter/b/57b2e6/32.png) [@bpquerries](https://forums.suse.com/u/bpquerries)\
**Post date:** [December 12, 2017, 5:47pm UTC](https://forums.suse.com/t/zypper-patch-date-command-is-directely-updating-latest-kerne/30660/5 "2017-12-12T17:47:30Z")

</div>

Hi, thanks for the response… will wait for your further updates

---

<div class="post-metadata">

**Author:** ![bpquerries](https://avatars.discourse-cdn.com/v4/letter/b/57b2e6/32.png) [@bpquerries](https://forums.suse.com/u/bpquerries)\
**Post date:** [December 14, 2017, 5:36am UTC](https://forums.suse.com/t/zypper-patch-date-command-is-directely-updating-latest-kerne/30660/6 "2017-12-14T05:36:57Z")

</div>

Hi Simon,

Do you have any update?

Regards  
Vineesh

---

<div class="post-metadata">

**Author:** ![smflood](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/smflood/32/10576_2.png) [@smflood](https://forums.suse.com/u/smflood)\
**Post date:** [December 14, 2017, 12:49pm UTC](https://forums.suse.com/t/zypper-patch-date-command-is-directely-updating-latest-kerne/30660/7 "2017-12-14T12:49:14Z")

</div>

On 14/12/17 03:44, bpquerries wrote:  
[color=blue]

> Do you have any update?[/color]

Not this soon and given the holidays are, or will soon be, upon us I  
don’t expect one so soon. Once I hear something back I will post an  
update here.

## HTH.

Simon  
SUSE Knowledge Partner

* * *

## If you find this post helpful and are logged into the web interface, please show your appreciation and click on the star below. Thanks.

---

<div class="post-metadata">

**Author:** ![rjschwei](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/rjschwei/32/8937_2.png) [@rjschwei](https://forums.suse.com/u/rjschwei)\
**Post date:** [December 21, 2017, 4:49pm UTC](https://forums.suse.com/t/zypper-patch-date-command-is-directely-updating-latest-kerne/30660/8 "2017-12-21T16:49:23Z")

</div>

And for completeness:

‘patch --date’ selects _which_ patches get selected, not _how_ they are applied.

A ‘patch’ is a meta-object conflicting with the affected/vulnerable versions of a set of packages. As long as any of these affected/vulnerable versions is installed, the conflict triggers and the patch is classified as `needed`. Selecting the patch, the conflict is resolved by updating all installed and affected/vulnerable packages mentioned in the patch.

When updating packages, zypper will always head for the latest version.

It behaves as expected.
