<?xml version="1.0" encoding="UTF-8"?>
<otherdata xmlns="http://linux.duke.edu/metadata/other" packages="10">
<package pkgid="ab244b679d3185eee0d7bfce5752c101c78bbe0528cff82e99d9f3f3f2a5a004" name="python3-migration" arch="noarch">
  <version epoch="0" ver="2.1.35" rel="3.1"/>
  <changelog author="cfamullaconrad@suse.com" date="1777464000">- Add ResolvConf class for unified name resolver mgmt
  Implement a new ResolvConf class to provide a consistent approach for
  handling /etc/resolv.conf during migrations. The class introduces
  logic to:
  - Detect if /etc/resolv.conf is managed by netconfig or NetworkManager.
  - Verify user customizations using MD5 checksums (compatible with
  netconfig) and header analysis.
  - Preserve custom configurations by moving them to a static file
  and creating a symlink to prevent future overwrites by network tools.
  - Support resolver setup for both the target root and live systems.</changelog>
  <changelog author="cfamullaconrad@suse.com" date="1777464001">- Integrate ResolvConf class and reorder network setup services
  Refactor SetupNameResolver and WickedToNetworkManager to use the new
  ResolvConf class for unified resolver handling.
  Swap systemd service dependencies to ensure name resolver setup
  runs before host network setup.</changelog>
  <changelog author="cfamullaconrad@suse.com" date="1777550400">- Avoid temporary test/unit/.coverage in dist archive
  This temporary file, generated by pytest-cov, is created within each
  `make test` call containing different content, also if no
  source files has changed.</changelog>
  <changelog author="cfamullaconrad@suse.com" date="1778068800">- Workaround for bsc#1263889 -- preserve resolv.conf</changelog>
  <changelog author="vzhestkov@suse.com" date="1778068801">- Fix loading SELinux policy of Salt Bundle with workaround</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1778068802">- Make sure to add multipath to the initrd
  Add multipath dracut code to the initrd. This is related
  to bsc#1260340</changelog>
  <changelog author="cfamullaconrad@suse.com" date="1778241600">- Mount /system-root/run as tmpfs
  Use tmpfs for /run, so we do not write temporal
  files during migration to disk.</changelog>
  <changelog author="cfamullaconrad@suse.com" date="1778241601">- Bind mount resolv.conf to /system-root/run/.../resolv.conf
  This makes the resolv.conf available in the chroot environment
  if a none custom symlink is used.</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1778500800">- Fix missing tests for latest apparmor code change</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1778587200">- Fix install of NetworkManager
  Check if NetworkManager is installed already and only install it
  when needed. In addition run the installation of packages inside
  of the upgraded system as a chroot operation. We identified
  zypper metadata read issues when driving a package install from
  the outside (live migration system) into the target and we also
  want this operation to be as close as possible to a standard
  package installation on the target system.</changelog>
  <changelog author="yu.daike@suse.com" date="1779105600">- Add precheck for POWER architecture version on SLES16 migration</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1780315200">- Make sure to add multipath to the initrd for SAP
  Add multipath dracut code to the initrd for the SLE16 SAP
  migration system. This is related to bsc#1260340</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781524800">- Explicitly request python3-base
  Due to changes on the SUSE python packaging it's required
  to request python3-base such that symlinks like /usr/bin/python3
  exists</changelog>
  <changelog author="1080430+greygoo@users.noreply.github.com" date="1781524801">- Handle multipath root (#493)
  Add handling of multipath_wnn kernel parameter for multipath
  root. This allows to detect multipath mapped systems and mount
  them properly in the DMS live migration system and Fixes #491
  - --------
  Co-authored-by: Marcus Schäfer &lt;marcus.schaefer@suse.com&gt;</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781524802">- Add production/staging profiles for SLE16
  In contrast to SLE15, SLE16 is still actively developed and
  not in maintenance mode. Therefore the rolling build for
  devel:DMS should use the latest version of SLE16 but should
  also allow for maintenance releases into production. For
  production the repository setup should come from the project
  as it is setup in the SUSE namespace. For the staging project
  we set the repositories as they fit the current development.
  This is SLE16.1 at the moment.</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781524803">- Add production profile for Makefile target</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781611200">- Update suse-migration-rpm
  Make sure optional profile name does not interfere with
  the package name</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781697600">- Bump Migration changelog version: 2.1.35</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781697601">- Bump version: 2.1.34 → 2.1.35</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781784000">- yq is only recommended not required</changelog>
</package>
<package pkgid="e075a3c3c2fecab8fa49f0f1dc9175ec3abe3d9ef1775772db46d387b1d2d243" name="suse-migration" arch="noarch">
  <version epoch="0" ver="2.1.35" rel="3.1"/>
  <changelog author="cfamullaconrad@suse.com" date="1777464000">- Add ResolvConf class for unified name resolver mgmt
  Implement a new ResolvConf class to provide a consistent approach for
  handling /etc/resolv.conf during migrations. The class introduces
  logic to:
  - Detect if /etc/resolv.conf is managed by netconfig or NetworkManager.
  - Verify user customizations using MD5 checksums (compatible with
  netconfig) and header analysis.
  - Preserve custom configurations by moving them to a static file
  and creating a symlink to prevent future overwrites by network tools.
  - Support resolver setup for both the target root and live systems.</changelog>
  <changelog author="cfamullaconrad@suse.com" date="1777464001">- Integrate ResolvConf class and reorder network setup services
  Refactor SetupNameResolver and WickedToNetworkManager to use the new
  ResolvConf class for unified resolver handling.
  Swap systemd service dependencies to ensure name resolver setup
  runs before host network setup.</changelog>
  <changelog author="cfamullaconrad@suse.com" date="1777550400">- Avoid temporary test/unit/.coverage in dist archive
  This temporary file, generated by pytest-cov, is created within each
  `make test` call containing different content, also if no
  source files has changed.</changelog>
  <changelog author="cfamullaconrad@suse.com" date="1778068800">- Workaround for bsc#1263889 -- preserve resolv.conf</changelog>
  <changelog author="vzhestkov@suse.com" date="1778068801">- Fix loading SELinux policy of Salt Bundle with workaround</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1778068802">- Make sure to add multipath to the initrd
  Add multipath dracut code to the initrd. This is related
  to bsc#1260340</changelog>
  <changelog author="cfamullaconrad@suse.com" date="1778241600">- Mount /system-root/run as tmpfs
  Use tmpfs for /run, so we do not write temporal
  files during migration to disk.</changelog>
  <changelog author="cfamullaconrad@suse.com" date="1778241601">- Bind mount resolv.conf to /system-root/run/.../resolv.conf
  This makes the resolv.conf available in the chroot environment
  if a none custom symlink is used.</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1778500800">- Fix missing tests for latest apparmor code change</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1778587200">- Fix install of NetworkManager
  Check if NetworkManager is installed already and only install it
  when needed. In addition run the installation of packages inside
  of the upgraded system as a chroot operation. We identified
  zypper metadata read issues when driving a package install from
  the outside (live migration system) into the target and we also
  want this operation to be as close as possible to a standard
  package installation on the target system.</changelog>
  <changelog author="yu.daike@suse.com" date="1779105600">- Add precheck for POWER architecture version on SLES16 migration</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1780315200">- Make sure to add multipath to the initrd for SAP
  Add multipath dracut code to the initrd for the SLE16 SAP
  migration system. This is related to bsc#1260340</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781524800">- Explicitly request python3-base
  Due to changes on the SUSE python packaging it's required
  to request python3-base such that symlinks like /usr/bin/python3
  exists</changelog>
  <changelog author="1080430+greygoo@users.noreply.github.com" date="1781524801">- Handle multipath root (#493)
  Add handling of multipath_wnn kernel parameter for multipath
  root. This allows to detect multipath mapped systems and mount
  them properly in the DMS live migration system and Fixes #491
  - --------
  Co-authored-by: Marcus Schäfer &lt;marcus.schaefer@suse.com&gt;</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781524802">- Add production/staging profiles for SLE16
  In contrast to SLE15, SLE16 is still actively developed and
  not in maintenance mode. Therefore the rolling build for
  devel:DMS should use the latest version of SLE16 but should
  also allow for maintenance releases into production. For
  production the repository setup should come from the project
  as it is setup in the SUSE namespace. For the staging project
  we set the repositories as they fit the current development.
  This is SLE16.1 at the moment.</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781524803">- Add production profile for Makefile target</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781611200">- Update suse-migration-rpm
  Make sure optional profile name does not interfere with
  the package name</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781697600">- Bump Migration changelog version: 2.1.35</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781697601">- Bump version: 2.1.34 → 2.1.35</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781784000">- yq is only recommended not required</changelog>
</package>
<package pkgid="29748ecfb21f0fc4e20a95ad0b9103eebedf09d14e2d84b187dec96028107fa2" name="suse-migration-pre-checks" arch="noarch">
  <version epoch="0" ver="2.1.35" rel="3.1"/>
  <changelog author="cfamullaconrad@suse.com" date="1777464000">- Add ResolvConf class for unified name resolver mgmt
  Implement a new ResolvConf class to provide a consistent approach for
  handling /etc/resolv.conf during migrations. The class introduces
  logic to:
  - Detect if /etc/resolv.conf is managed by netconfig or NetworkManager.
  - Verify user customizations using MD5 checksums (compatible with
  netconfig) and header analysis.
  - Preserve custom configurations by moving them to a static file
  and creating a symlink to prevent future overwrites by network tools.
  - Support resolver setup for both the target root and live systems.</changelog>
  <changelog author="cfamullaconrad@suse.com" date="1777464001">- Integrate ResolvConf class and reorder network setup services
  Refactor SetupNameResolver and WickedToNetworkManager to use the new
  ResolvConf class for unified resolver handling.
  Swap systemd service dependencies to ensure name resolver setup
  runs before host network setup.</changelog>
  <changelog author="cfamullaconrad@suse.com" date="1777550400">- Avoid temporary test/unit/.coverage in dist archive
  This temporary file, generated by pytest-cov, is created within each
  `make test` call containing different content, also if no
  source files has changed.</changelog>
  <changelog author="cfamullaconrad@suse.com" date="1778068800">- Workaround for bsc#1263889 -- preserve resolv.conf</changelog>
  <changelog author="vzhestkov@suse.com" date="1778068801">- Fix loading SELinux policy of Salt Bundle with workaround</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1778068802">- Make sure to add multipath to the initrd
  Add multipath dracut code to the initrd. This is related
  to bsc#1260340</changelog>
  <changelog author="cfamullaconrad@suse.com" date="1778241600">- Mount /system-root/run as tmpfs
  Use tmpfs for /run, so we do not write temporal
  files during migration to disk.</changelog>
  <changelog author="cfamullaconrad@suse.com" date="1778241601">- Bind mount resolv.conf to /system-root/run/.../resolv.conf
  This makes the resolv.conf available in the chroot environment
  if a none custom symlink is used.</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1778500800">- Fix missing tests for latest apparmor code change</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1778587200">- Fix install of NetworkManager
  Check if NetworkManager is installed already and only install it
  when needed. In addition run the installation of packages inside
  of the upgraded system as a chroot operation. We identified
  zypper metadata read issues when driving a package install from
  the outside (live migration system) into the target and we also
  want this operation to be as close as possible to a standard
  package installation on the target system.</changelog>
  <changelog author="yu.daike@suse.com" date="1779105600">- Add precheck for POWER architecture version on SLES16 migration</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1780315200">- Make sure to add multipath to the initrd for SAP
  Add multipath dracut code to the initrd for the SLE16 SAP
  migration system. This is related to bsc#1260340</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781524800">- Explicitly request python3-base
  Due to changes on the SUSE python packaging it's required
  to request python3-base such that symlinks like /usr/bin/python3
  exists</changelog>
  <changelog author="1080430+greygoo@users.noreply.github.com" date="1781524801">- Handle multipath root (#493)
  Add handling of multipath_wnn kernel parameter for multipath
  root. This allows to detect multipath mapped systems and mount
  them properly in the DMS live migration system and Fixes #491
  - --------
  Co-authored-by: Marcus Schäfer &lt;marcus.schaefer@suse.com&gt;</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781524802">- Add production/staging profiles for SLE16
  In contrast to SLE15, SLE16 is still actively developed and
  not in maintenance mode. Therefore the rolling build for
  devel:DMS should use the latest version of SLE16 but should
  also allow for maintenance releases into production. For
  production the repository setup should come from the project
  as it is setup in the SUSE namespace. For the staging project
  we set the repositories as they fit the current development.
  This is SLE16.1 at the moment.</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781524803">- Add production profile for Makefile target</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781611200">- Update suse-migration-rpm
  Make sure optional profile name does not interfere with
  the package name</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781697600">- Bump Migration changelog version: 2.1.35</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781697601">- Bump version: 2.1.34 → 2.1.35</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781784000">- yq is only recommended not required</changelog>
</package>
<package pkgid="fd88b4f61de573f89be2ace073738f46797a219464eebf7565c6246d6cb8b706" name="suse-migration-rpm" arch="src">
  <version epoch="0" ver="1.0.1" rel="6.1"/>
  <changelog author="ms@suse.com" date="1542196800">- Post Processing package for SLES15-Migration live image.
  This package provides metadata used at the end of an
  appliance build to package the image results into a
  package</changelog>
  <changelog author="ms@suse.com" date="1548417600">- Install SLES15-Migration live image to /boot</changelog>
  <changelog author="ms@suse.com" date="1551700800">- Install SLES15-Migration live image to /usr/share/migration-image
  See https://github.com/SUSE/suse-migration-services/issues/54
  for details</changelog>
  <changelog author="ms@suse.com" date="1556798400">- Reference commit for SUSE maintenance
  This submission creates a reference to fate#327175 and bsc#1133919</changelog>
  <changelog author="ms@suse.com" date="1563364800">- Install run_migration from suse-migration-services package
  that is now a build requirement. For details see:
  https://github.com/SUSE/suse-migration-services/issues/108</changelog>
  <changelog author="jesusbv@suse.com" date="1565784000">- This submission creates a reference to bsc#1142108</changelog>
  <changelog author="jesusbv@suse.com" date="1566302400">- Reference commit for SUSE maintenance
  Fix BYOS upgrade from 12SP4-SAP to 15 (BSC#1142108)</changelog>
  <changelog author="ms@suse.com" date="1573473600">- Add product version requirement to spec file
  For further details see: https://github.com/SUSE/suse-migration-services/pull/143</changelog>
  <changelog author="ms@suse.com" date="1573732800">- Reference commit for SUSE maintenance
  This submission creates a reference to bsc#1155192</changelog>
  <changelog author="marcus.schaefer@gmail.com" date="1730289600">- Install migration live image to /migration-image
  This change helps to run migrations on systems which stores
  /usr/share in a special way, e.g. as LVM volume or other
  type that cannot be read via the loopback grub or kexec
  method</changelog>
  <changelog author="fcrozat@suse.com" date="1751457600">- Add build and perl(Date::Parse) to ensure we can append changelog
  entries to generated package.</changelog>
  <changelog author="fcrozat@suse.com" date="1754049600">- Exit silently if no migration iso is found.</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1754654400">- Add product requirement according to image name.
  This is based on the migration live image naming policy
  SLES[CODE]-[PRODUCT]_Migration. CODE is a number, 12, 15
  PRODUCT is optional and specifies a name used to identify
  a product that is not just SLES</changelog>
  <changelog author="marcus.schaefer@gmail.com" date="1759838400">- Fix MinSLEVersion value depending on target
  The MinSLEVersion global variable was set to a value
  suitable for migrations from SLE12 to SLE15. Now that the
  scope of the DMS is not only this target we have to add
  a mechanism to dynamically set an appropriate value.
  I added explanatory comments which hopefully makes sense
  to explain when this information is taken into account</changelog>
  <changelog author="marcus.schaefer@gmail.com" date="1781611200">- Add handling for Staging builds
  Make sure the profile name does not interfere with the
  built package name</changelog>
  <changelog author="chuller@suse.com" date="1786708800">- Allow the migration packages to install on Leap 16
  The SLES16-Migration package requires product(SLES), which causes
  an installation on Leap to fail. This extends the product
  requirement to Leap products.</changelog>
</package>
<package pkgid="2a75cf62001b5a979959c7fffe903968a3b441c3a94786cfc336d2a355ebaa72" name="suse-migration-rpm" arch="x86_64">
  <version epoch="0" ver="1.0.1" rel="6.1"/>
  <changelog author="ms@suse.com" date="1542196800">- Post Processing package for SLES15-Migration live image.
  This package provides metadata used at the end of an
  appliance build to package the image results into a
  package</changelog>
  <changelog author="ms@suse.com" date="1548417600">- Install SLES15-Migration live image to /boot</changelog>
  <changelog author="ms@suse.com" date="1551700800">- Install SLES15-Migration live image to /usr/share/migration-image
  See https://github.com/SUSE/suse-migration-services/issues/54
  for details</changelog>
  <changelog author="ms@suse.com" date="1556798400">- Reference commit for SUSE maintenance
  This submission creates a reference to fate#327175 and bsc#1133919</changelog>
  <changelog author="ms@suse.com" date="1563364800">- Install run_migration from suse-migration-services package
  that is now a build requirement. For details see:
  https://github.com/SUSE/suse-migration-services/issues/108</changelog>
  <changelog author="jesusbv@suse.com" date="1565784000">- This submission creates a reference to bsc#1142108</changelog>
  <changelog author="jesusbv@suse.com" date="1566302400">- Reference commit for SUSE maintenance
  Fix BYOS upgrade from 12SP4-SAP to 15 (BSC#1142108)</changelog>
  <changelog author="ms@suse.com" date="1573473600">- Add product version requirement to spec file
  For further details see: https://github.com/SUSE/suse-migration-services/pull/143</changelog>
  <changelog author="ms@suse.com" date="1573732800">- Reference commit for SUSE maintenance
  This submission creates a reference to bsc#1155192</changelog>
  <changelog author="marcus.schaefer@gmail.com" date="1730289600">- Install migration live image to /migration-image
  This change helps to run migrations on systems which stores
  /usr/share in a special way, e.g. as LVM volume or other
  type that cannot be read via the loopback grub or kexec
  method</changelog>
  <changelog author="fcrozat@suse.com" date="1751457600">- Add build and perl(Date::Parse) to ensure we can append changelog
  entries to generated package.</changelog>
  <changelog author="fcrozat@suse.com" date="1754049600">- Exit silently if no migration iso is found.</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1754654400">- Add product requirement according to image name.
  This is based on the migration live image naming policy
  SLES[CODE]-[PRODUCT]_Migration. CODE is a number, 12, 15
  PRODUCT is optional and specifies a name used to identify
  a product that is not just SLES</changelog>
  <changelog author="marcus.schaefer@gmail.com" date="1759838400">- Fix MinSLEVersion value depending on target
  The MinSLEVersion global variable was set to a value
  suitable for migrations from SLE12 to SLE15. Now that the
  scope of the DMS is not only this target we have to add
  a mechanism to dynamically set an appropriate value.
  I added explanatory comments which hopefully makes sense
  to explain when this information is taken into account</changelog>
  <changelog author="marcus.schaefer@gmail.com" date="1781611200">- Add handling for Staging builds
  Make sure the profile name does not interfere with the
  built package name</changelog>
  <changelog author="chuller@suse.com" date="1786708800">- Allow the migration packages to install on Leap 16
  The SLES16-Migration package requires product(SLES), which causes
  an installation on Leap to fail. This extends the product
  requirement to Leap products.</changelog>
</package>
<package pkgid="e67a2355643098cc403646c26e4eb86f5966c58ea1e044d0fbff87b8a7d7e909" name="suse-migration-scripts" arch="noarch">
  <version epoch="0" ver="2.1.35" rel="3.1"/>
  <changelog author="cfamullaconrad@suse.com" date="1777464000">- Add ResolvConf class for unified name resolver mgmt
  Implement a new ResolvConf class to provide a consistent approach for
  handling /etc/resolv.conf during migrations. The class introduces
  logic to:
  - Detect if /etc/resolv.conf is managed by netconfig or NetworkManager.
  - Verify user customizations using MD5 checksums (compatible with
  netconfig) and header analysis.
  - Preserve custom configurations by moving them to a static file
  and creating a symlink to prevent future overwrites by network tools.
  - Support resolver setup for both the target root and live systems.</changelog>
  <changelog author="cfamullaconrad@suse.com" date="1777464001">- Integrate ResolvConf class and reorder network setup services
  Refactor SetupNameResolver and WickedToNetworkManager to use the new
  ResolvConf class for unified resolver handling.
  Swap systemd service dependencies to ensure name resolver setup
  runs before host network setup.</changelog>
  <changelog author="cfamullaconrad@suse.com" date="1777550400">- Avoid temporary test/unit/.coverage in dist archive
  This temporary file, generated by pytest-cov, is created within each
  `make test` call containing different content, also if no
  source files has changed.</changelog>
  <changelog author="cfamullaconrad@suse.com" date="1778068800">- Workaround for bsc#1263889 -- preserve resolv.conf</changelog>
  <changelog author="vzhestkov@suse.com" date="1778068801">- Fix loading SELinux policy of Salt Bundle with workaround</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1778068802">- Make sure to add multipath to the initrd
  Add multipath dracut code to the initrd. This is related
  to bsc#1260340</changelog>
  <changelog author="cfamullaconrad@suse.com" date="1778241600">- Mount /system-root/run as tmpfs
  Use tmpfs for /run, so we do not write temporal
  files during migration to disk.</changelog>
  <changelog author="cfamullaconrad@suse.com" date="1778241601">- Bind mount resolv.conf to /system-root/run/.../resolv.conf
  This makes the resolv.conf available in the chroot environment
  if a none custom symlink is used.</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1778500800">- Fix missing tests for latest apparmor code change</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1778587200">- Fix install of NetworkManager
  Check if NetworkManager is installed already and only install it
  when needed. In addition run the installation of packages inside
  of the upgraded system as a chroot operation. We identified
  zypper metadata read issues when driving a package install from
  the outside (live migration system) into the target and we also
  want this operation to be as close as possible to a standard
  package installation on the target system.</changelog>
  <changelog author="yu.daike@suse.com" date="1779105600">- Add precheck for POWER architecture version on SLES16 migration</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1780315200">- Make sure to add multipath to the initrd for SAP
  Add multipath dracut code to the initrd for the SLE16 SAP
  migration system. This is related to bsc#1260340</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781524800">- Explicitly request python3-base
  Due to changes on the SUSE python packaging it's required
  to request python3-base such that symlinks like /usr/bin/python3
  exists</changelog>
  <changelog author="1080430+greygoo@users.noreply.github.com" date="1781524801">- Handle multipath root (#493)
  Add handling of multipath_wnn kernel parameter for multipath
  root. This allows to detect multipath mapped systems and mount
  them properly in the DMS live migration system and Fixes #491
  - --------
  Co-authored-by: Marcus Schäfer &lt;marcus.schaefer@suse.com&gt;</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781524802">- Add production/staging profiles for SLE16
  In contrast to SLE15, SLE16 is still actively developed and
  not in maintenance mode. Therefore the rolling build for
  devel:DMS should use the latest version of SLE16 but should
  also allow for maintenance releases into production. For
  production the repository setup should come from the project
  as it is setup in the SUSE namespace. For the staging project
  we set the repositories as they fit the current development.
  This is SLE16.1 at the moment.</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781524803">- Add production profile for Makefile target</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781611200">- Update suse-migration-rpm
  Make sure optional profile name does not interfere with
  the package name</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781697600">- Bump Migration changelog version: 2.1.35</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781697601">- Bump version: 2.1.34 → 2.1.35</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781784000">- yq is only recommended not required</changelog>
</package>
<package pkgid="52a7b324b25d59f6616c20d0dd55d9a718ad00bea6d9076662b1adbbcb195d4d" name="suse-migration-services" arch="noarch">
  <version epoch="0" ver="2.1.35" rel="3.1"/>
  <changelog author="cfamullaconrad@suse.com" date="1777464000">- Add ResolvConf class for unified name resolver mgmt
  Implement a new ResolvConf class to provide a consistent approach for
  handling /etc/resolv.conf during migrations. The class introduces
  logic to:
  - Detect if /etc/resolv.conf is managed by netconfig or NetworkManager.
  - Verify user customizations using MD5 checksums (compatible with
  netconfig) and header analysis.
  - Preserve custom configurations by moving them to a static file
  and creating a symlink to prevent future overwrites by network tools.
  - Support resolver setup for both the target root and live systems.</changelog>
  <changelog author="cfamullaconrad@suse.com" date="1777464001">- Integrate ResolvConf class and reorder network setup services
  Refactor SetupNameResolver and WickedToNetworkManager to use the new
  ResolvConf class for unified resolver handling.
  Swap systemd service dependencies to ensure name resolver setup
  runs before host network setup.</changelog>
  <changelog author="cfamullaconrad@suse.com" date="1777550400">- Avoid temporary test/unit/.coverage in dist archive
  This temporary file, generated by pytest-cov, is created within each
  `make test` call containing different content, also if no
  source files has changed.</changelog>
  <changelog author="cfamullaconrad@suse.com" date="1778068800">- Workaround for bsc#1263889 -- preserve resolv.conf</changelog>
  <changelog author="vzhestkov@suse.com" date="1778068801">- Fix loading SELinux policy of Salt Bundle with workaround</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1778068802">- Make sure to add multipath to the initrd
  Add multipath dracut code to the initrd. This is related
  to bsc#1260340</changelog>
  <changelog author="cfamullaconrad@suse.com" date="1778241600">- Mount /system-root/run as tmpfs
  Use tmpfs for /run, so we do not write temporal
  files during migration to disk.</changelog>
  <changelog author="cfamullaconrad@suse.com" date="1778241601">- Bind mount resolv.conf to /system-root/run/.../resolv.conf
  This makes the resolv.conf available in the chroot environment
  if a none custom symlink is used.</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1778500800">- Fix missing tests for latest apparmor code change</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1778587200">- Fix install of NetworkManager
  Check if NetworkManager is installed already and only install it
  when needed. In addition run the installation of packages inside
  of the upgraded system as a chroot operation. We identified
  zypper metadata read issues when driving a package install from
  the outside (live migration system) into the target and we also
  want this operation to be as close as possible to a standard
  package installation on the target system.</changelog>
  <changelog author="yu.daike@suse.com" date="1779105600">- Add precheck for POWER architecture version on SLES16 migration</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1780315200">- Make sure to add multipath to the initrd for SAP
  Add multipath dracut code to the initrd for the SLE16 SAP
  migration system. This is related to bsc#1260340</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781524800">- Explicitly request python3-base
  Due to changes on the SUSE python packaging it's required
  to request python3-base such that symlinks like /usr/bin/python3
  exists</changelog>
  <changelog author="1080430+greygoo@users.noreply.github.com" date="1781524801">- Handle multipath root (#493)
  Add handling of multipath_wnn kernel parameter for multipath
  root. This allows to detect multipath mapped systems and mount
  them properly in the DMS live migration system and Fixes #491
  - --------
  Co-authored-by: Marcus Schäfer &lt;marcus.schaefer@suse.com&gt;</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781524802">- Add production/staging profiles for SLE16
  In contrast to SLE15, SLE16 is still actively developed and
  not in maintenance mode. Therefore the rolling build for
  devel:DMS should use the latest version of SLE16 but should
  also allow for maintenance releases into production. For
  production the repository setup should come from the project
  as it is setup in the SUSE namespace. For the staging project
  we set the repositories as they fit the current development.
  This is SLE16.1 at the moment.</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781524803">- Add production profile for Makefile target</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781611200">- Update suse-migration-rpm
  Make sure optional profile name does not interfere with
  the package name</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781697600">- Bump Migration changelog version: 2.1.35</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781697601">- Bump version: 2.1.34 → 2.1.35</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781784000">- yq is only recommended not required</changelog>
</package>
<package pkgid="23a2f80bc80c90140bd00582be7f0b8ac81da77bf5e50eb8a24f641fe0a683a3" name="suse-migration-services" arch="src">
  <version epoch="0" ver="2.1.35" rel="3.1"/>
  <changelog author="cfamullaconrad@suse.com" date="1777464000">- Add ResolvConf class for unified name resolver mgmt
  Implement a new ResolvConf class to provide a consistent approach for
  handling /etc/resolv.conf during migrations. The class introduces
  logic to:
  - Detect if /etc/resolv.conf is managed by netconfig or NetworkManager.
  - Verify user customizations using MD5 checksums (compatible with
  netconfig) and header analysis.
  - Preserve custom configurations by moving them to a static file
  and creating a symlink to prevent future overwrites by network tools.
  - Support resolver setup for both the target root and live systems.</changelog>
  <changelog author="cfamullaconrad@suse.com" date="1777464001">- Integrate ResolvConf class and reorder network setup services
  Refactor SetupNameResolver and WickedToNetworkManager to use the new
  ResolvConf class for unified resolver handling.
  Swap systemd service dependencies to ensure name resolver setup
  runs before host network setup.</changelog>
  <changelog author="cfamullaconrad@suse.com" date="1777550400">- Avoid temporary test/unit/.coverage in dist archive
  This temporary file, generated by pytest-cov, is created within each
  `make test` call containing different content, also if no
  source files has changed.</changelog>
  <changelog author="cfamullaconrad@suse.com" date="1778068800">- Workaround for bsc#1263889 -- preserve resolv.conf</changelog>
  <changelog author="vzhestkov@suse.com" date="1778068801">- Fix loading SELinux policy of Salt Bundle with workaround</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1778068802">- Make sure to add multipath to the initrd
  Add multipath dracut code to the initrd. This is related
  to bsc#1260340</changelog>
  <changelog author="cfamullaconrad@suse.com" date="1778241600">- Mount /system-root/run as tmpfs
  Use tmpfs for /run, so we do not write temporal
  files during migration to disk.</changelog>
  <changelog author="cfamullaconrad@suse.com" date="1778241601">- Bind mount resolv.conf to /system-root/run/.../resolv.conf
  This makes the resolv.conf available in the chroot environment
  if a none custom symlink is used.</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1778500800">- Fix missing tests for latest apparmor code change</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1778587200">- Fix install of NetworkManager
  Check if NetworkManager is installed already and only install it
  when needed. In addition run the installation of packages inside
  of the upgraded system as a chroot operation. We identified
  zypper metadata read issues when driving a package install from
  the outside (live migration system) into the target and we also
  want this operation to be as close as possible to a standard
  package installation on the target system.</changelog>
  <changelog author="yu.daike@suse.com" date="1779105600">- Add precheck for POWER architecture version on SLES16 migration</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1780315200">- Make sure to add multipath to the initrd for SAP
  Add multipath dracut code to the initrd for the SLE16 SAP
  migration system. This is related to bsc#1260340</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781524800">- Explicitly request python3-base
  Due to changes on the SUSE python packaging it's required
  to request python3-base such that symlinks like /usr/bin/python3
  exists</changelog>
  <changelog author="1080430+greygoo@users.noreply.github.com" date="1781524801">- Handle multipath root (#493)
  Add handling of multipath_wnn kernel parameter for multipath
  root. This allows to detect multipath mapped systems and mount
  them properly in the DMS live migration system and Fixes #491
  - --------
  Co-authored-by: Marcus Schäfer &lt;marcus.schaefer@suse.com&gt;</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781524802">- Add production/staging profiles for SLE16
  In contrast to SLE15, SLE16 is still actively developed and
  not in maintenance mode. Therefore the rolling build for
  devel:DMS should use the latest version of SLE16 but should
  also allow for maintenance releases into production. For
  production the repository setup should come from the project
  as it is setup in the SUSE namespace. For the staging project
  we set the repositories as they fit the current development.
  This is SLE16.1 at the moment.</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781524803">- Add production profile for Makefile target</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781611200">- Update suse-migration-rpm
  Make sure optional profile name does not interfere with
  the package name</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781697600">- Bump Migration changelog version: 2.1.35</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781697601">- Bump version: 2.1.34 → 2.1.35</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1781784000">- yq is only recommended not required</changelog>
</package>
<package pkgid="73811ee960287aa1941103850f98bb24837fda08b5d72c08624bf22b6912faa9" name="suse-migration-sle16-activation" arch="src">
  <version epoch="0" ver="2.1.35" rel="2.1"/>
  <changelog author="fcrozat@suse.com" date="1749816000">- ensure migration to SLES16 uses selinux, not apparmor</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1751025600">- Support product specifier in ISO name</changelog>
  <changelog author="yu.daike@suse.com" date="1753185600">- fix: set path according to current arch in grub.d/99_migration</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1754654400">- Fix product related requirement settings
  The activation as well as the migration live image packages
  set a specific product requirement for the product named
  product(SLES). However this is in conflict with all products
  SUSE creates that are based on SLES. One example here is
  SLES for SAP which defines its own product product(SLES_SAP).
  The activation of the migration should not be product specific.
  These packages just sets up a bootloader setup to boot the
  respective live image. Therefore this commit drops the
  product requirement from the activation packages. The live
  image however must be product specific and therefore this
  commit adds code that allows to identify the target
  product by the given image name and sets the respective
  product requirement to the package that wraps the image.
  This change also follows the new strategy to provide
  migration live images for specific SUSE products, beginning
  with SAP. This Fixes #349 and Fixes #354</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1754913600">- Make activation package require by provides tag
  With the introduction of product specific migrations packaged
  up in different package names we can no longer make the activation
  package require a specific package. Instead the activation requires
  a capability which can be provided by different packages</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1757505600">- Setup ExclusiveArch for activation packages
  For migrations of SLE12 to SLE15 the DMS was used in
  the cloud context only. grub based activation is supported
  there only on x86_64 and aarch64
  For migrations of SLE15 to SLE16 the DMS is used in a broader
  context across SUSE products and architectures. grub based
  activation is supported for all archs except s390. On s390
  we support the kexec (run_migration) based method for
  activation only.
  This commit sets the ExclusiveArch option respectively</changelog>
  <changelog author="jorik.cronenberg@suse.com" date="1757505601">- Add wicked2nm network migration</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1757678400">- Add missing pre snapshot setup to run_migration
  The suse-migration-sle16-activation-spec-template provides code
  in %pre which is not fully covered by the run_migration tool.
  As we support both activation+grub and kexec (run_migration)
  modes, the pre code should match in either case.
  This Fixes #370</changelog>
  <changelog author="yu.daike@suse.com" date="1758283200">- architecture check before allowing migration to be activated
  SLE16 will panic on CPUs older than x86_64_v1 (i.e. x86_64). To
  avoid panicing the system we check for the architecture before
  activating the migration.
  Co-authored-by: Marcus Schäfer &lt;marcus.schaefer@suse.com&gt;</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1758283201">- Activation packages can no longer be noarch
  As we have architectures that does not support the grub
  based activation and therefore an ExclusiveArch setup in
  the spec, the package can no longer be noarch</changelog>
  <changelog author="jorik.cronenberg@suse.com" date="1758888000">- Add changes for newest wicked2nm
  With the new wicked2nm version 1.3.0 hopefully wicked2nm-continue-migration is
  less necessary so this removes the default true in SLE16.
  Also there are some changes to the netconfig handling so it makes more sense to
  read the base netconfig dir instead of copying the files to
  '/var/cache/wicked_config'.
  I've also added an explanation to the pre-checks to explain how to apply the
  `--continue-migration` flag to the migration.</changelog>
  <changelog author="cfamullaconrad@suse.com" date="1759147200">- Create systemd.link files for virtual VMware/Hyper-V NICs
  The 75-persistent-net-generator.rules does not create udev-rules
  for virtual nics, matching the hwaddr "00:0c:29:*|00:50:56:*" (VMware)
  or "00:15:5d:*" (Hyper-V).
  When migrating to SLE16, predictable ifnames are enabled and it
  is very likely, that the nic will get a different name.
  To fix this, create 'systemd.link' files matching the DRIVER and
  PCI_ID to ensure the virtual NIC retains its  expected name.
  (bsc#1250076)</changelog>
  <changelog author="yu.daike@suse.com" date="1759233600">- check migration target before testing for architecture version
  The x86_64 architecture version check only applies to migrations to
  SLE16. Do not check for it if we are migrating to SLE15.</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1760356800">- shellcheck heavily complained
  Fix shell coding in run_migration and %post scripts
  to match with standards reported by shellcheck</changelog>
  <changelog author="jorik.cronenberg@suse.com" date="1760616000">- Simplify interface naming by disabling predictable names at boot
  Currently our most difficult problem with regards to the network interface
  naming scheme is that when the migration image boots the interfaces get
  predictable names like 'enp1s0' which we then have to revert/write custom rules
  around. To simplify this we can install a file at
  /etc/systemd/network/99-default.link. This skips all naming schemes and the
  kernel names are used. Then we can remove this file again and copy over all the
  necessary udev rules and link files from the host and with udevadm trigger apply
  these. This should imitate the behavior of the final migrated system most
  closely.</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1762344000">- Refactor mount_system service
  So far the mount_system unit run through all disk devices
  and uses the first one providing a system with an fstab file.
  This concept is weak and fails on machines with multiple
  linux OS disks attached. This commit refactors mount_system
  such that it reads the migration_target= variable from the
  kernel cmdline. The kernel cmdline gets this information
  added by either the grub.d/99_migration menuentry or via
  the run_migration kexec method. The migration_target=
  variable is expected to contain the rootfs UUID value
  of the host that should be migrated. This is a unique
  identifier and as such cannot be confused by other devices
  attached to the system.</changelog>
  <changelog author="cfamullaconrad@suse.com" date="1763726400">- Create lib file for common network-prereq tasks</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1764158400">- Move script package to the main migration provider
  In the effort to provide a common script code package, the
  package suse-migration-sle16-scripts was provided. During
  testing I found that not all places where script duplication
  exists was covered. This commit addresses the code that was
  missed and also suggests that we move the common script
  code as a sub package to the main suse-migration-services
  package. The reason here is that the common code is not
  only used in the activation package. In addition I also
  suggest that the package name changes to be more generic.
  The reason here is that this will go beyond sle16 and can
  also contain common script code for sle15 migrations as
  well as for past sle16 migrations as we are moving forward.
  As such my suggestion to also rename the package to just
  suse-migration-scripts.</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1775563200">- Fix md device detection
  Fix detection of device mapper layered rootfs. Software
  raid disks are not found by findmnt if the actual rootfs
  is one or more layers down. This commit fixes the detection
  if we need to pass along the rd.auto cmdline option to
  let the boot process activate them.</changelog>
  <changelog author="1080430+greygoo@users.noreply.github.com" date="1781524800">- Handle multipath root (#493)
  Add handling of multipath_wnn kernel parameter for multipath
  root. This allows to detect multipath mapped systems and mount
  them properly in the DMS live migration system and Fixes #491
  - --------
  Co-authored-by: Marcus Schäfer &lt;marcus.schaefer@suse.com&gt;</changelog>
</package>
<package pkgid="4ab9a54b0002fd8cf0cb671c4f662fb4ed9524672606a10fc38f14614d292eb5" name="suse-migration-sle16-activation" arch="x86_64">
  <version epoch="0" ver="2.1.35" rel="2.1"/>
  <changelog author="fcrozat@suse.com" date="1749816000">- ensure migration to SLES16 uses selinux, not apparmor</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1751025600">- Support product specifier in ISO name</changelog>
  <changelog author="yu.daike@suse.com" date="1753185600">- fix: set path according to current arch in grub.d/99_migration</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1754654400">- Fix product related requirement settings
  The activation as well as the migration live image packages
  set a specific product requirement for the product named
  product(SLES). However this is in conflict with all products
  SUSE creates that are based on SLES. One example here is
  SLES for SAP which defines its own product product(SLES_SAP).
  The activation of the migration should not be product specific.
  These packages just sets up a bootloader setup to boot the
  respective live image. Therefore this commit drops the
  product requirement from the activation packages. The live
  image however must be product specific and therefore this
  commit adds code that allows to identify the target
  product by the given image name and sets the respective
  product requirement to the package that wraps the image.
  This change also follows the new strategy to provide
  migration live images for specific SUSE products, beginning
  with SAP. This Fixes #349 and Fixes #354</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1754913600">- Make activation package require by provides tag
  With the introduction of product specific migrations packaged
  up in different package names we can no longer make the activation
  package require a specific package. Instead the activation requires
  a capability which can be provided by different packages</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1757505600">- Setup ExclusiveArch for activation packages
  For migrations of SLE12 to SLE15 the DMS was used in
  the cloud context only. grub based activation is supported
  there only on x86_64 and aarch64
  For migrations of SLE15 to SLE16 the DMS is used in a broader
  context across SUSE products and architectures. grub based
  activation is supported for all archs except s390. On s390
  we support the kexec (run_migration) based method for
  activation only.
  This commit sets the ExclusiveArch option respectively</changelog>
  <changelog author="jorik.cronenberg@suse.com" date="1757505601">- Add wicked2nm network migration</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1757678400">- Add missing pre snapshot setup to run_migration
  The suse-migration-sle16-activation-spec-template provides code
  in %pre which is not fully covered by the run_migration tool.
  As we support both activation+grub and kexec (run_migration)
  modes, the pre code should match in either case.
  This Fixes #370</changelog>
  <changelog author="yu.daike@suse.com" date="1758283200">- architecture check before allowing migration to be activated
  SLE16 will panic on CPUs older than x86_64_v1 (i.e. x86_64). To
  avoid panicing the system we check for the architecture before
  activating the migration.
  Co-authored-by: Marcus Schäfer &lt;marcus.schaefer@suse.com&gt;</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1758283201">- Activation packages can no longer be noarch
  As we have architectures that does not support the grub
  based activation and therefore an ExclusiveArch setup in
  the spec, the package can no longer be noarch</changelog>
  <changelog author="jorik.cronenberg@suse.com" date="1758888000">- Add changes for newest wicked2nm
  With the new wicked2nm version 1.3.0 hopefully wicked2nm-continue-migration is
  less necessary so this removes the default true in SLE16.
  Also there are some changes to the netconfig handling so it makes more sense to
  read the base netconfig dir instead of copying the files to
  '/var/cache/wicked_config'.
  I've also added an explanation to the pre-checks to explain how to apply the
  `--continue-migration` flag to the migration.</changelog>
  <changelog author="cfamullaconrad@suse.com" date="1759147200">- Create systemd.link files for virtual VMware/Hyper-V NICs
  The 75-persistent-net-generator.rules does not create udev-rules
  for virtual nics, matching the hwaddr "00:0c:29:*|00:50:56:*" (VMware)
  or "00:15:5d:*" (Hyper-V).
  When migrating to SLE16, predictable ifnames are enabled and it
  is very likely, that the nic will get a different name.
  To fix this, create 'systemd.link' files matching the DRIVER and
  PCI_ID to ensure the virtual NIC retains its  expected name.
  (bsc#1250076)</changelog>
  <changelog author="yu.daike@suse.com" date="1759233600">- check migration target before testing for architecture version
  The x86_64 architecture version check only applies to migrations to
  SLE16. Do not check for it if we are migrating to SLE15.</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1760356800">- shellcheck heavily complained
  Fix shell coding in run_migration and %post scripts
  to match with standards reported by shellcheck</changelog>
  <changelog author="jorik.cronenberg@suse.com" date="1760616000">- Simplify interface naming by disabling predictable names at boot
  Currently our most difficult problem with regards to the network interface
  naming scheme is that when the migration image boots the interfaces get
  predictable names like 'enp1s0' which we then have to revert/write custom rules
  around. To simplify this we can install a file at
  /etc/systemd/network/99-default.link. This skips all naming schemes and the
  kernel names are used. Then we can remove this file again and copy over all the
  necessary udev rules and link files from the host and with udevadm trigger apply
  these. This should imitate the behavior of the final migrated system most
  closely.</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1762344000">- Refactor mount_system service
  So far the mount_system unit run through all disk devices
  and uses the first one providing a system with an fstab file.
  This concept is weak and fails on machines with multiple
  linux OS disks attached. This commit refactors mount_system
  such that it reads the migration_target= variable from the
  kernel cmdline. The kernel cmdline gets this information
  added by either the grub.d/99_migration menuentry or via
  the run_migration kexec method. The migration_target=
  variable is expected to contain the rootfs UUID value
  of the host that should be migrated. This is a unique
  identifier and as such cannot be confused by other devices
  attached to the system.</changelog>
  <changelog author="cfamullaconrad@suse.com" date="1763726400">- Create lib file for common network-prereq tasks</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1764158400">- Move script package to the main migration provider
  In the effort to provide a common script code package, the
  package suse-migration-sle16-scripts was provided. During
  testing I found that not all places where script duplication
  exists was covered. This commit addresses the code that was
  missed and also suggests that we move the common script
  code as a sub package to the main suse-migration-services
  package. The reason here is that the common code is not
  only used in the activation package. In addition I also
  suggest that the package name changes to be more generic.
  The reason here is that this will go beyond sle16 and can
  also contain common script code for sle15 migrations as
  well as for past sle16 migrations as we are moving forward.
  As such my suggestion to also rename the package to just
  suse-migration-scripts.</changelog>
  <changelog author="marcus.schaefer@suse.com" date="1775563200">- Fix md device detection
  Fix detection of device mapper layered rootfs. Software
  raid disks are not found by findmnt if the actual rootfs
  is one or more layers down. This commit fixes the detection
  if we need to pass along the rd.auto cmdline option to
  let the boot process activate them.</changelog>
  <changelog author="1080430+greygoo@users.noreply.github.com" date="1781524800">- Handle multipath root (#493)
  Add handling of multipath_wnn kernel parameter for multipath
  root. This allows to detect multipath mapped systems and mount
  them properly in the DMS live migration system and Fixes #491
  - --------
  Co-authored-by: Marcus Schäfer &lt;marcus.schaefer@suse.com&gt;</changelog>
</package>
</otherdata>