Hello community,

here is the log from the commit of package patchinfo.15219 for 
openSUSE:Leap:15.1:Update checked in at 2020-12-07 12:06:01
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Leap:15.1:Update/patchinfo.15219 (Old)
 and      /work/SRC/openSUSE:Leap:15.1:Update/.patchinfo.15219.new.5913 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "patchinfo.15219"

Mon Dec  7 12:06:01 2020 rev:1 rq:852706 version:unknown

Changes:
--------
New Changes file:

NO CHANGES FILE!!!

New:
----
  _patchinfo

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ _patchinfo ++++++
<patchinfo incident="15219">
  <issue tracker="bnc" id="1177526">L3: cloud-init-local.service fails in 
19.4-8.23.2 [ref:_00D1igLOd._5001iTd52Z:ref]</issue>
  <issue tracker="bnc" id="1179150"></issue>
  <issue tracker="bnc" id="1179151"></issue>
  <packager>bfilho</packager>
  <rating>important</rating>
  <category>recommended</category>
  <summary>Recommended update for cloud-init</summary>
  <description>This update for cloud-init contains the following fixes:

- Add cloud-init-azure-def-usr-pass.patch (bsc#1179150, bsc#1179151)
  + Properly set the password for the default user in all circumstances

- Patch the full package version into the cloud-init version file

- Update cloud-init-write-routes.patch (bsc#1177526)
  + Fix missing default route when dual stack network setup is used. Once
    a default route was configured for Ipv6 or IPv4 the default route
    configuration for the othre protocol was skipped.

This update was imported from the SUSE:SLE-15-SP1:Update update 
project.</description>
</patchinfo>
_______________________________________________
openSUSE Commits mailing list -- [email protected]
To unsubscribe, email [email protected]
List Netiquette: https://en.opensuse.org/openSUSE:Mailing_list_netiquette
List Archives: 
https://lists.opensuse.org/archives/list/[email protected]

Reply via email to