suse-migration-pre-checks-2.0.35-150000.1.56.1 >
A c^p9|?q \_1 |ϒ+R%ݬBtU.AQKSXAԽ> eWY+4u$>S8>:fϻHI= [ \làq_m2 y^v o 'm/qC̎og^[W7n ba,sdc\I4P_myI`|v/5_'bLfh9+n0 $/a6b9a026dec4532737214e2dd50971513070c693 dbf7037ee2921054f73d90bb230369ce5a25169ea3940ce2a76511655dd3c913 S c^p9|?3ڥKk!Sw'gkEY{5~\m; lC\^Ў0ÕȮ
Eea ,,<-'8gz# DaH PeWk T}%s@fD:9|>84XNyU9 7!y n&` &m.SZ>L)G?81 vtR j,|Z<+SԼ1\W\q%caGx Ks Xx > p A
?
d # 1 g + [ a h ' ' R '
' < ' '
' '
k ' . d ' < $ ( + 8 4 t 9 t : ) t F G ' H ' I X ' X Y \ ' ] 8 ' ^ b U c d e f l u ' v @ w ' x 8 ' y z
@
P
T
Z
C suse-migration-pre-checks 2.0.35 150000.1.56.1 The pre-checks code used with suse-migration-services Checks to be performed before starting a distribution migration process c^|sheep10 :mSUSE Linux Enterprise 15 SUSE LLC GPL-3.0+ https://www.suse.com/ System/Management https://github.com/SUSE/suse-migration-services linux noarch
# ( {
Y < t
+ tAA큤A큤AA큤 c^yc^yc^yc^yc^yc^yc^ycc^yc^yccc^yc^yc^yc^yc^yc^yc^yc^yccccccccccccccc^yc^yc^yc^yc^yc^ycccccccccccc0a81b22480d0febfba03047a9b0f65bdf8d5388c5600bdcc70e8b7149fe312c4 4b24732571bc7688f45cf0f0a4aa2c50809b5cf2c28ff9298dfcd287aaa38520 0e6bade24b5c305d2ee2780676aae54cd05761df5847941996224f9ee3885eb2 01ba4719c80b6fe911b091a7c05124b64eeece964e09c058ef8f9805daca546b 64cf60d41fadaa8bd4fb4349dc7b5e619e300f1ce0209c9c502f224c7bdca1f7 01ba4719c80b6fe911b091a7c05124b64eeece964e09c058ef8f9805daca546b 9fa8dc06131a1fddab463cccc5c140a6d761312833bfe01435e4a4f8b1b756f8 b0f6e3792c34f1544f6540936cda3ec0818d6085a642c7a65093e8bd2a952ee5 e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 daecc05bc824263a4394b993cd267461d0bf32fc984dd06300ab539ef633093c aa89496f7f83f0cc28c8fd9237a9b3f10a3c21132c14210324557417fcfda821 fb26a1bfb89ce8c50fc83c6b428c1de11d03e572e6c5ab86ff62ee5cd974fe97 96e252a53037ef2a092734428272ca2f04e1f423fd1ce56a8c6adfabe657afc8 a8d3bbc278f099f8236e0f82b387c45835ad54047969606779155a6e21283736 40fa55d188caf10fddbaaddba6c5add05026f0d5699aea23c4b2dd34ea0498dd 6dd563f9e020bac52ffd48333dbc8aa630a175dbb22bb6d538e3695b426896ee 3ef6526fdb7b2636dbb8374e9d239cb00ed787b866293e6c1eedbc6f501944b1 fc34bd4e9c6c29d0b49cc574c407117eec3b1c191069e65416dbf301a10de7b7 aab829cb48e4ebc31d52bad7757fa99e5bd83f8df24a8dc860e7debfdd89e6b1 1e9323adb7c269742c8482868612e9b3c7c895d3f4c40d066ea330e3c8cf252e 122dd1076acc86de2456ec0d92e044daf67e73266be2afff711b6b5e84b96bf4 5d23b82b117522ffe60b6808596ac19dc164d120a89e688a72f0ec3e62a6029c aba655d0792e84d9bba91fff59dd69cdc9b6e1db4bd89d84720975c4e218835a 2a37373d173465e51fc70a2200437ca7380920748c0a87a9a52ed8786aaf3f8a ee8cfaa7854ee6e9bd1642dafe1245bbf139c1138fde3b5929c2ac0dff722f5b 3cc5943c01dc5e98d8fc03fb00d5db945bce43f6fbdaf867df5cc2f24d5f6e8d 087d7d4d4972f7b1eebeb2a218b9cec7b0c5a8ee92f8b3be8eaacc334769847c 63ee7bfb163e91b853f338d6ff805ee17646cc6413c90337c76509d03e9d43f2 2f822fc9995cb8613beb702621b1bd22b36f4a73669c7b2bc0f6af7aaa9a41af c9f04e14c7e75308f414d940d34fb6b64feac299d10a448a7702fb64d91de22b 6546493862d6f30ed1f5a8660e37f075f6661f6a9b6fe1d0f12d4992644cb5da 9efcd19c67e4c6879b0bb6f450d3940567b9f3c450bcfff8e9ba07c7e91d4ca6 f5355d138b5c9fca76756374ee156de7e47aada86f65f4a06b0bf7831fb8ae3c f326fd4e6e191659167c1ed3097e9d41933d090d768583e7b5aae4820d95a3f6 root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root root suse-migration-services-2.0.35-150000.1.56.1.src.rpm suse-migration-pre-checks @ @
/usr/bin/python3 python(abi) python3-Cerberus python3-PyYAML rpmlib(CompressedFileNames) rpmlib(FileDigests) rpmlib(PayloadFilesHavePrefix) rpmlib(PayloadIsXz) 3.6 3.0.4-1 4.6.0-1 4.0-1 5.2-1 suse-migration-sle15-activation 2.0.33 4.14.1 ccd@cbTb@bk@bgbgbgb]Rb]Rb]RbUibF@b%b%b @b@ba@a5a@aa]a\>@aUaD@aC1aC1aC1aC1aC1aC1aC1aC1aC1aC1aA@aA@aA@aA@aA@a(a(a&0a^a
@aaaa@a
$@aFaFaF`@` @` @` @````@`@```@````e@`e@```~@`~@`}p`y|@`u`u`t6@`t6@`t6@`t6@`\{@`>(`6?`3`/@`.V` 3@` 3@` 3@` 3@``>_i_u@_FN_FN_D@_D@_D@_C_?@_?@_ L_ L_X@_@_@_c^{G^y@^r
@^S^S^S^O@^J@^J@^:@^1s^0"@^)^!^ P@^ @^ [^ [^ [^g@^g@^g@^^^@^@^@^@^@^@^@^@]]]A]A]A]ʞ]ʞ]ʞ]ʞ]ʞ]ʞ]ʞ]ʞ]ʞ]ʞ]ʞ]ʞ]ʞ]M@]X]X]µ]d@]d@]d@]d@]]]{@]{@]]@]@]][][][][][]S]@1@]@1@]>]>]9]0_@]0_@]/
]/
]/
],j] ;] ;]]]]@]^@]@]] @\F@\Q\ @\ @\ @\\\\\\\\\]@\]@\]@\]@\]@\h\\t@\t@\t@\t@\"\"\"\\\ڭ\!\\\\Ɋ@\8\8\8\@\O\O\}\,@\\\@\@\@\\@\|\|\|\|\|\|\|\+@\+@\+@\\\\\~d\}@\}@\y \mA@\k\d\b@\ac\]o@\]o@\J@\J@\G\@n@\? \? \? \=@\=@\=@\=@\=@\=@\= 4.13
and SLES_SAP provides product(SLES) = %{version}-%{release} - Bump version: 1.1.7 → 1.1.8 - Disable use of bool expressions in Requires
Available with rpm >= 4.13. Thus we can't build for SLE12
because rpm is older there - Bump version: 1.1.6 → 1.1.7 - Fixed Requires syntax
According to https://rpm.org/user_doc/more_dependencies.html
boolean expressions must be embedded into brackets - Bump version: 1.1.5 → 1.1.6 - Fixed superfluous newline in changelog generator - Bump version: 1.1.4 → 1.1.5 - Fixed changelog reference commit
An old reference commit was used which has to be updated because
a manual change to the .changes file on obs was done :( - Add or condition properly - Bump version: 1.1.3 → 1.1.4 - Added activation spec changes to changelog
Changes that happened on the activation package spec file
were not part of the package changelog generated by
helper/update_changelog.py - Bump version: 1.1.2 → 1.1.3 - The minimum migration starting point should be
SLES 12 SP3
or
SLES For SAP 12 SP3. - Bump version: 1.1.1 → 1.1.2 - Fixed reboot call procedure
the systemd magic that detects whether to do kexec or not, is only
applied if we invoke reboot. systemd internally maps reboot to one or
the other of 'systemctl reboot' or 'systemctl kexec'. Therefore the
current implementation which just call 'systemctl reboot' does not
transparently detect for kexec. As we don't want to rely on the
magic behind the reboot call we explicitly call systemctl with
reboot or kecec depending on the configured soft_reboot
configuration option. This is then also in line with the code
that runs 'kexec load' which also depends on the configured
soft_reboot value. - Bump version: 1.1.0 → 1.1.1 - Fixed reading of config files
There are two potential config files, both are optional
but one of them was opened in any case and if not present
raises an exception. This should not be the case and gets
fixed by this commit - Fix changelog inconsistency
It seems there was a changelog entry added in obs but not
in the git history for the suse-migration-sle15-activation
package. This commit brings all in line again - Bump version: 1.0.5 → 1.1.0 - Do kernel mounts in mount service (not in prepare service)
If the /dev, /proc and /sys mounts are done in the prepare service,
then exceptions thrown between mount system and prepare result in
the grub config not being applied. Moving these mounts earlier in
the process ensures that the grub setup service has everything it
needs (see https://github.com/SUSE/suse-migration-services/pull/142
for more detailed discussion of the problem). - Require SUSEConnect updated version
In a failed distribution migration scenario,
zypper-migration does a rollback. During this
rollback, zypper tries to refresh deactivated
repos, making the rollback fail.
This has been fixed in the newer (0.3.20) version of SUSEConnect.
This Fixes #133 - Add schema validation for migration config file
If the custom config file is empty or contains only comment lines,
it will now be ignored (rather than raising an exception and killing
the migration). If the file is corrupt somehow, or violates schema
validation, an error will be logged and the migration will abort.
Validation is *also* applied to the default config file (the one
inside the migration image). This makes automated testing easy,
because we'll effectively do automatic validation on any of the
test config files, whether they're for default config or custom
config. - Delete left over debug print statement - Auto detect migration product
As there could be different targets (SLES, SLES_SAP, etc)
instead of setting the target in the custom file, the migration
system auto detects the migration product.
In order to do so, the target version is read from the live system.
This Fixes #129 - Bump version: 1.0.4 → 1.0.5 - Perform reboot through systemd
reboot is performed through systemd. The call through systemd
checks if there is a kexec loaded kernel and transparently
turns 'systemctl reboot' into 'systemctl kexec'. Thus both ways,
soft and hard reboot are managed in one call. This is related
to Issue #111 - Allow for vendor change during migration
The migration concept allows for the zypper dup as well as
for the zypper migrate approach. In the first case the user
is responsible for setting up the repos and we expect that
to be done in a way that vendor changes are acceptable. In
the second case a repository server is used to serve the
repos and we expect that registration instance to be trustworthy
such that potential vendor changes are also allowed - Add option to configure reboot method
This adds a soft_reboot option, which if set to false results in
a hard reboot, as opposed to using kexec.
Fixes #111 - Reference commit for SUSE maintenance
Fix BYOS upgrade from 12SP4-SAP to 15 (BSC#1142108) - Bump version: 1.0.3 → 1.0.4 - Switch changelog generation to UTC
For new entries the UTC format is used because package
submissions will happen from different time zones - Bump version: 1.0.2 → 1.0.3 - Update changelog creation process
In the same way like in the kiwi project we apply the
creation of the changelog based on a reference file.
This allows to work with maintenance which declines
any request that changes an entry of the changes file
even if this change just updates the full author name - This submission creates a reference to bsc#1142108 - Refactor product setup
Add SUSEBaseProduct class to detect and handle the
installed base product. Related to Issue #129 - Bump version: 1.0.1 → 1.0.2 - Try to find a more generic name
glob match can return, files and directories. We only
work on files but the variable should not indicate scope
when there is none - Fixed network setup
The network setup was based on an overlay bind mount of the
entire /etc/sysconfig/network directory. However that directory
also contains script code and functions that are used by system
tools like netconfig. The scripts here are not compatible between
distributions. Thus the overmount of /etc/sysconfig/network/scripts
from SLE12 to SLE15 as one example breaks the netconfig tool and
prevents the update of the /etc/resolv.conf file on network
restart. Other negative effects of that overmounting are likely.
Therefore this commit changes the way we inherit the network setup.
Only the plugin directory and the interface configurations are
taken from the host, all the rest stays untouched. - Language/typo fixes - - User doc
+ Clarification around the choices of invoking the migration process using
reboot or kexec - Bump version: 1.0.0 → 1.0.1 - Update documentation
Mention the two methods to start the migration - Partially revert the no bootloader based startup
After testing the kexec based implementation to start the
migration live image, we found that kexec does not work in
all cloud providers. Especially those using Xen like AWS
do not work. Thus it's required to keep the alternative
bootloader based startup sequence - Bump version: 0.6.5 → 1.0.0 - Avoid bootloader to run the migration
Instead of a reboot the customer should run the migration
by calling run_migration. This commit adds a service utility
to run the migration. The concept is based on kexec and
avoids the modification to the bootloader setup. This allows
more flexibility for clouds that runs instances not directly
through a bootloader and also avoids infinite boot/reboot
cycles in case of an early error of the migration mount
service. This Fixes #108 - Bump version: 0.6.4 → 0.6.5 - Fixup udev reload on rule changes
The current restart sequence is missing the actual set/change
of device nodes. This also prevented network interface names
to be added/renamed. - Bump version: 0.6.3 → 0.6.4 - Fixed post mount service unit file
Wrong path to executable - Bump version: 0.6.2 → 0.6.3 - Added limitation note as suggested by Robert - Rename migration package
Avoid confusion and possible error due to wrong package name.
Fix #122 - Added doc chapter for new preserve section - Added post mount service
The post mount service is used to preserve data from the
system to be migrated into the live migration system directly
after the mounting of the system to be migrated. It is is
also responsible for making that data effective in the live
migration system. The current implementation allows for
preserving udev rules file and make them active.
This Fixes #100 - Capitalize steps list - Rename config option to use zypper migration
Rename the option to use zypper migration path, wether a plugin or
a sub-command is not relevant for the name.
Fixes #118 - Bump version: 0.6.1 → 0.6.2 - Update per suggestions by Tom - Update per review by Robert - Update per review by Robert - update per review by Jesus - update per review - update per review by Tom - Update per review - Support PARTUUID specifier in fstab - Update documentation
Added section about possible config file values including
the explanation for the different zypper install modes.
This Fixes #99 - Allow to skip local fstab paths
If a device path is referenced as local path in the fstab file
but can't be found on the system, this device path is skipped.
Usually a device path references a storage node that exists
as /dev/.. node on the machine. However it's possible to also
reference files e.g for loop mount in the fstab file. If that
file reference is not present in the live migration system it
is ignored because considered harmless. file references in
fstab are sometimes used for swapfiles or other file mapped
data. For the purpose of the migration we consider such paths
as not belonging to the system. This assumption of course
could be wrong which is why we also write a warning message
to the log file once this situation is disovered. This
Fixes #110 - Bump version: 0.6.0 → 0.6.1 - Place network logging in network service - Fixed SSH identity copy
The SSH host identity is provided by the server credentials that
makes up the fingerprint of that host. However the copy of the
files should exclude the encrypted private key ssh_host_key which
can only be read on the origin host. In fact a copy of that file
to another host will lead to a segfault in sshd and kills the
connection without any further information. - Log bondN info if bonding directory exists - Bump version: 0.5.30 → 0.6.0 - Ignore blank lines and comments when parsing fstab - Provide detailed network information
After network.online target is done, we log
the network status, interfaces and relevant information.
Fixes #84 - Inherit ssh host keys
The live image creates its ssh host key on boot. However that
host key does not match the host key from the system to migrate.
This leads to a warning message on a changed host key when a
ssh login attempt is made while the migration runs. As the
migration live system inherits the network setup it should
also inherit the ssh host key. This Fixes #86 - Cosmetic changes to handle error codes from zypper
Make it more explicit to the reader that we treat specific
values from zypper as errors. Positive side effect is that
if the list gets longer the condition does not need to
change - Try to mount raid partitions
`lsblk` returns "raid1" (or similar) for /dev/md devices, so we need
to attempt to mount these as well as regular partitions in case the
root disk is on mdraid. - Fix grub setup if root is on a raid device
If the root filesystem is on a raid device the boot parameter
rd.auto must be passed to the boot such that the dracut raid
module can setup the raid prior to iso-scan.sh searching
through the devices. Related to Issue #96 - Rebuild grub conf on uninstall of activation rpm
If the activation package is installed a grub config file
extension is applied. On uninstall of the package that
extension will be deleted but it only becomes effective
if the grub config will be rebuild. This Fixes #94 - Add support for zypper dup mode
By default the migration system uses the zypper migration plugin
to migrate the system. This works if the system is SLES registered
and an upgrade path from SCC exists. For system where this is not
possible an alternative method can be switched on with the
custom configuration option use_zypper_migration_plugin set
to: false. In this mode we just call zypper dup. Please note
this requires that the user has pre setup the repositories before
the migration system gets started. This Fixes #72 - Use `uniq` when finding root device in grub activation script
If the system is using mdraid on the root disk, the `lsblk` invocation
will return two lines matching "/$", e.g.:
/dev/md1
/dev/md1
This then breaks the subsequent `blkid` invocations, so $root_uuid and
$root_type are set to empty strings. When you later boot into the
migration system, grub gives two errors:
error: one argument expected.
error: no such device: root.
Adding `uniq` fixes this. - Implement import of custom configuration file
Instead of the system-root/etc/sle-migration-service file which
was used to setup debugging only we now allow the custom config
file system-root/etc/sle-migration-service.yml whose contents
gets migrated into the existing /etc/migration-config.yml on
the live migration host. - optional file - Change debug flag file to option
Before, to stop rebooting it was needed to place a
file as a debug flag. Now there must be a debug key option set
in the custom file. - User documentation
Add distribution migration system user documentation.
- Caveats and unsupported conditions
- Structure and content for the doc tool chain
- Recommendation about ssh key access
- State that clean up of /etc/issue is needed
- Daps style for suse docs - Fixed spec file of activation package
A %install and %build section is required otherwise the
default contents of those sections applies which leads
to the creation of a debuginfo setup that failed on a
noarch package - Reference commit for SUSE maintenance
This submission creates a reference to fate#327175 and bsc#1133919 - Bump version: 0.5.29 → 0.5.30 - Reference commit for SUSE maintenance
This submission creates a reference to fate#327175 and bsc#1133919 - Bump version: 0.5.28 → 0.5.29 - Fix reboot race condition
The issue described here came up with the package split and
rename of the activation package. The grub setup service
deletes the activation package and calls grub2-mkconfig which
deletes the migration live boot entry as well as updates grub
to boot the migrated system. However if the activation package
could not be removed the process ends in a boot loop. Therefore
one part of this patch makes the removal of the migration
packages more robust. Another part provides detailed log
information about the removal and the grub setup in the log
file.
Last but not least the patch includes a refactoring of the
umount and reboot process which offers a race condition if
the grub-setup service has failed. The patch here also
Delete the umount service and put the code in the reboot
service. Only on reboot we umount the system. In case of
debugging we want to have full access to the root of the
system that should have become migrated. In addition the
systemd dependency chain for the kernel-load vs. reboot
service was racy and got fixed by a clear dependency
for grub-setup -> kernel-load -> reboot - Bump version: 0.5.27 → 0.5.28 - Fixed deletion of activation package
Due to the split of the services package the activation
package name is target specific and needs to be matched
by a pattern - Split activation package from services
From a release process it doesn't make sense to keep the activation
script as a sub package of the services. The reason is because the
suse-migration-services package will be released to the migration
target distribution and the activation package will be released to
the migration start distribution. Thus the code is relevant on
different distributions and it is not useful to maintain that in
one package. This Fixes #74 - Bump version: 0.5.26 → 0.5.27 - Fixed network requirement
To come up with a race free network start the setup-host-network
service has to be called after network.target. This ensures the
wicked service is already active. An active wicked service allows
for a reload of the network service. The setup-host-network
service overmounts /etc/sysconfig/network and reloads the network
service. That tells the running wicked service to elaborate
over the new ifcfg configurations and updates the network status.
In the prepare unit we require the network-online target which
makes sure it operates only on an online network. - Bump version: 0.5.25 → 0.5.26 - Fix network setup service
The network setup service for the migration inherits the
network as it is configured on the system to become migrated.
As part of that process the network is restarted through
systemctl. However this is a problem because it interferes
with the network service dependency chain. This could result
in a failed network startup depending on how fast other
services e.g dbus are up and running. So the way we do it
causes a race condition. This commit deletes the network
startup from our network setup service. Our network setup
service runs by definition of the unit file before the
network.target. This means at the time the network service
activates the network our setup routine is already done and
a normal network startup should be guaranteed. - Bump version: 0.5.24 → 0.5.25 - Make sure /var/lib/cloudregister exists
At cloud registration time information about the SMT/RMT server
is provided below /var/lib/cloudregister. For migration it's
required to bind mount this path from the system to become
migrated into the live migration system. - Support new cloud regionsrv client
The new cloud region service client comes with a plugin for
zypper that translates repo URIs into a specific plugin format
such that it's no longer possible to gain access to the SLES
repositories of our public cloud infrastructure by playing
tricks with snapshotting an on-demand instance without the
billingtag. However the new and fancy way makes migration of
such a system more difficult because the new repo URI format
must be known to zypper migration. This requires all software
components to be provided in the live migration image which
has been done in the image description but furthermore requires
that the cloud specific /etc/regionserverclnt.cfg and the
contents of /usr/lib/zypp/plugins from the system to migrate
are available in the migration live image. The later is
implemented in this commit and Fixes #69 - Bump version: 0.5.23 → 0.5.24 - Fix pattern for initrd
Some images have an extra boot partition,
so there are grub files with '/vmlinuz'
and we need to handle that case. - Bump version: 0.5.22 → 0.5.23 - Copy kernel and initrd for access
It copies the files in-memory so kexec can access them
once root-path gets umounted.
Fixes #65 - Bump version: 0.5.21 → 0.5.22 - Fixed dependency for reboot service
The reboot service must be called after mount-service and
after umount-service. The mount-service handles the setup
of the debug flag. If the reboot service is too fast the
debug flag setup is not respected - Fixed logging to logfile
The setup of the logfile has to be done on each service
at import time. Each service is an extra python call
done by systemd. The setup of the logfile needs to be done
as an initializer for any unit invocation - Bump version: 0.5.20 → 0.5.21 - Added systemctl status output to logfile
As part of the reboot service add the systemctl status information
collected up to that point into the logfile. - Fixed log reference in console log service
The systemd unit file was still pointing to the old file
name but that has changed to var/log/distro_migration.log - Initialize logging and debug as early as possible
The earliest opportunity to setup the log file and the
debug flag is directly after the mount-system code has
successfully mounted the target to migrate. At this point
we should init the logfile and also the debugging if
needed. The code before this commit has potential to
not even reach the log/debug setup. With this commit
the only requirement is a successful mount of the target
system. - Bump version: 0.5.19 → 0.5.20 - Add option to handle file conflicts
In the scenario where there are packaging bugs,
this option install packages even if they
replaces files from other packages.
Fixes #58 - Fixed handling of debug flag file
If this file is present we want to stay in the migration system
no matter what happened. This is urgently required to keep us
with a way to debug the process. Current testing has shown that
only the log file is not enough to debug the complete pipeline. - Bump version: 0.5.18 → 0.5.19 - Add flag to handle zypper migration errors
Zypper has extra error codes that does not necessarily have to
stop a distribution migration.
Fixes #52 - Bump version: 0.5.17 → 0.5.18 - Path for log file
After reboot, if the migration has failed, the file
/etc/issue has a message pointing to the log file.
The path of that log file must exist inside the rebooted system. - Bump version: 0.5.16 → 0.5.17 - Add rootpart detection to grub activation script
The live migration image gets installed to the system again
because of the space limitation on /boot. This affects the
menuentry created on grub side in a way that we can't use
the pre-allocated pointer to the boot device but have to search
the root partition like in a real grub root entry. This patch
adds the needed code changes to locate the root part, insert
the needed filesystem module and initializes the root variable
to allow the loopback loading of the image. This Fixes #54 - Revert location change from /usr/share to /boot
This reverts commit 66dd8d4943d38f121f4b16b70bf0ab8d0b2ec82d.
If there is an extra boot partition and it's too small we
are not able to install the migration system and the customer
will not be able to use the migration concept. The image is
usually around ~300MB of size and that can often be too much
for an extra boot partition which is often designed to be small - Bump version: 0.5.15 → 0.5.16 - Right path for debug file
Copy debug file in a different path so reboot code
can read that location in case of debugging. - Bump version: 0.5.14 → 0.5.15 - Reboot system after migration unless debug
The migration process will reboot the system whether it has succeeded or not
unless there is a file indicating not to reboot.
Fixes #48 - Bump version: 0.5.13 → 0.5.14 - Report migration error in /etc/issue
In order to be able to reboot and still report errors in case the migration fails,
the error will be reported in a log file (/var/log/distro_migration.log).
The message and log file name to check will be indicated in /etc/issue.
Fixes #47 - Bump version: 0.5.12 → 0.5.13 - Rename migration log file
As zypper is part of the process but not the only
component, 'zypper_migration.log' does not describe it properly. - Bump version: 0.5.11 → 0.5.12 - Change location for live migration ISO image
Instead of /usr/share expect the image in /boot. The reason
for this change is because we don't know if the system uses
an extra boot partition to load the kernel and initrd from.
However the way we add the extra loop boot entry to grub
is based on reading the value for ($root) as it was configured
on the system. The location ($root) points to in grub could
be anywhere but we can trust /boot to be in there.
This Fixes the run of the migration in Azure and also
stabilizes the concept. - Bump version: 0.5.10 → 0.5.11 - Detection of baseproduct
Find the .prod files inside /etc/products.d
which does not contain a flavor tag.
Remove the target registration in that .prod file. - Bump version: 0.5.9 → 0.5.10 - Revert/Refactor distro_target handling
zypper implements a handling for the distro_target attribute.
If present in the repository metadata, zypper compares the
value with the baseproduct setup in /etc/products.d.
If they mismatch zypper refuses to create the repo. In the
process of a migration from distribution [A] to [B] this mismatch
always applies by design and prevents the zypper migration plugin
to work. In SCC or RMT the repositories doesn't contain the
distro_target attribute which is the reason why we don't see
this problem there. SMT however creates repos including
distro_target.
The refactored workaround solution is now to delete the target
specification in the baseproduct registration if present, because
the overlay mounting of etc/products.d did not work as it would
lead to a wrong upgrade path on response from SCC.
In addition a backup of the original products.d data is created
and used in the zypper migration plugin in case of an error - Bump version: 0.5.8 → 0.5.9 - Added comments to explain the driver of the change - Added product setup service
During migration etc/products is a bind mounted location
to handle the distro_target issue. At the end of a successful
migration the data written to that location must be synced
into the migrated system. This task is done by the product
service - Handle distro_target
Long time ago zypper added a distro_target information into
the repository file and matches those with the product
information of the system. If the distro doesn't match
zypper refused to create the repository. In the migration
process using SMT this caused the zypper migration plugin
to fail because zypper never created repositories. That's
because in a migration process the repository and the
system to migrate never match. Therefore we bind mount
the /etc/products.d information from the migration live
system into the /system-root of the system to become
migrated. At the end of a successful migration the new
product information is copied to the migrated system - Bump version: 0.5.7 → 0.5.8 - Fixed handling of os.listdir result
os.listdir only returns the names of the files in the
directory. Thus the file reference in the subsequent
copy call was wrong. - Bump version: 0.5.6 → 0.5.7 - Import certificates
Copy certificates from /usr/share/pki/trust/anchors of the
system to become migrated into the live migration system
and update the certificate pool. This Fixes #37 - Bump version: 0.5.5 → 0.5.6 - Fixed console log service
The systemd unit file was missing an install target - Bump version: 0.5.4 → 0.5.5 - Changed service type for console logger
Move to simple type service and set a restart policy.
The way the console logger was started before caused
a stop of the service as soon as the kernel or some
other program logs information on the console. However
during migration we want the console logger to be
actively occupy the console such that it's clear a
migration process is currently running - Bump version: 0.5.3 → 0.5.4 - Fixed console log service
Allow to start console log at any time. Make sure it starts
after prepare but do not require prepare as it causes the
prepare service to be called again. - Bump version: 0.5.2 → 0.5.3 - Update prepare service on hosts file
In the cloud the translation from a name into an IP might also
be configured via the static etc/hosts file. In case of SUSE's
public cloud infrastructure the connected smt server is
configured that way at registration time. For the migration
process this means that this information must be present otherwise
the host to upgrade cannot be resolved. - Don't truncate migration log file
If the zypper based migration process runs it truncates the
so far written logfile information. We want to keep all logging
data, thus the zypper call has to append information to the
existing log file and not overwrite them. - Fixed executable path in console log service
systemd requires an absolute path to the called program.
This patch fixes the path to the dialog program such
that systemd calls it - Bump version: 0.5.1 → 0.5.2 - Mount kernel file systems inside /system-root
The file systems were previously mounted in grub
service but because the migration service needs to
have access proc, dev and sys inside system-root
(e.g. when updating the bootloader) they are mounted
in an earlier step. There is no need to mount them
again in grub. They are unmounted properly before
rebooting.
This Fixes #32 - Bump version: 0.5.0 → 0.5.1 - Fix log file initialization
We agreed on writing the log file into the root filesystem
of the system to migrate. This implies that the first time
to initialize this log file is in the prepare service
after the mount system service has succeeded. Calling
set_logfile in the mount system service before the system
got mounted is the wrong place. This patch fixes this
and also improves the unit test for this condition. - Bump version: 0.4.3 → 0.5.0 - Migration file (#30)
* Add migration file
This file is used to document the migration process inside the system.
* Add logging for the services - Require dialog package in spec file - Added zypper migration console logging
If the migration process starts the console should show a
progress information. We use a dialog tailbox which shows
the output of the zypper migration plugin while it runs.
The output is processed using a systemd service connected
to the console. In addition the log file
var/log/zypper_migrate.log
Is created inside of the system which gets migrated. This
allows for later inspection of what the migration plugin
did. This Fixes #27 - Bump version: 0.4.2 → 0.4.3 - Fixed typo in spec file
syse vs. suse - Bump version: 0.4.1 → 0.4.2 - Fixed spec file
Missing installation of ssh service systemd unit file - Bump version: 0.4.0 → 0.4.1 - Provide ssh access
Copy the authorized key files into the authorized key file
of migration user to be able to access through ssh.
This checks in /home and /root paths.
Fixes #26 - Proper class name for test - Bump version: 0.3.6 → 0.4.0 - Refactor reboot system
The system gets rebooted via kexec or if failed by a hard reboot.
For kexec it's required to load kernel, initrd and boot parameters
from the migrated system. Thus the kexec load must be done before
umount of the system and the actual reboot after umount of the
system. Therefore this patch splits the kernel-reboot service
into two services, whereas the umount service will be called
in between of them. - Fixup ExecStart in kernel reboot service
The binary is named suse-migration-kernel-reboot not
suse-migration-kernel-load - Bump version: 0.3.5 → 0.3.6 - Fixed removal of suse-migration-activation
A simple rpm -e call leads to an error because the package
depends on the master package providing the image. Thus it's
better to instruct zypper to remove the package including its
dependencies - Fixed invocation of Command.run
Use of unexpected keyword argument - Fixed kexec reboot kernel and grub lookup
In the reboot service the kernel files and the grub config
was not searched in the root of the migrated system but in
the root of the migration live system, which is the wrong
place. - Fixed kernel reboot service
The unit requirements and dependencies were set wrong - Bump version: 0.3.4 → 0.3.5 - Update target for uninstall
Set the target properly to uninstall package suse-migration-activation.
Fixes #17 - Bump version: 0.3.3 → 0.3.4 - Add kexec-tools (#16)
* Add kexec-tools
This is nedded for rebooting the migrated system
with the new kernel. - Uninstall suse-migration-activation
The new grub menu should not have this entry.
This solves issue #12 - Bump version: 0.3.2 → 0.3.3 - Set the Migration boot entry to be the default
In addition set the boot timeout to 1sec - Refactor get_cmdline
More generic parameter name and better search
of target kernel command line options. - Bump version: 0.3.1 → 0.3.2 - Add kexec reboot service - Added grub config extension to activate migration
Provide /etc/grub.d/99_migration plugin which causes
the creation of a Migration grub menu entry. In addition
the package build was cleaned up and extended by a new
sub-package suse-migration-activation which provides
that grub config plugin. - Remount system root if booted via grub loopback
if the system to become migrated was booted via a grub
loopback menuentry, the disk is blocked by that readonly
loopback mount and needs to be remounted for read write
access first - Bump version: 0.3.0 → 0.3.1 - Hotfix fstab export method
Put newline at the end of each fstab entry - Bump version: 0.2.1 → 0.3.0 - Resolve the mount stack in reverse order - Remove variable - Cleanup of mounted paths - Mount sys - Test add entry of services calls - Store service calls - Make one call - Add dependencies - Specific service names - Umount service must run after grub-setup service - Refactor mount path handling
Instead of duplicating code in the cleanup service make sure
all services which mounts a location updates the mount meta
data file /etc/system-root.fstab. The cleanup service in the
end just reverse reads that file and umounts all locations - Update grub file to migrated version - Added umount service
The umount service cleans up the migration host such that
no active mount reference into the migrated systems exists
anymore and we are safe to reboot - Fix typo in doc string - Bump version: 0.2.0 → 0.2.1 - Fix agree-licenses test - Fix agree-licenses option typo - Bump version: 0.1.2 → 0.2.0 - Use --non-interactive flag
Instead of pre selecting a menu index use the non
interactive flag and make the code more robust - Added zypper migration service
The service which actually runs the zypper migration plugin.
The service is called after the preparation step has completed
successfully - Bump version: 0.1.1 → 0.1.2 - make sure to restart the network actively - Bump version: 0.1.0 → 0.1.1 - The presence of /etc/SUSEConnect is optional
Do not fail the prepare service if there is no /etc/SUSEConnect
file available on the system to become migrated. Copy the
file if present and just continue otherwise - Bump version: 0.0.1 → 0.1.0 - Added prepare service
The prepare service runs the preparation tasks for systemd
to perform the migration. This includes the import of the
SUSEConnect configuration from the host as well as the
bind mount of the zypp metadata - Added setup host network service
Added service to activate the migration host system network - Implement mount_system service
The mount_system service looks for existing disk partitions
and for an fstab file on that partitions. The first partition
found with an fstab file is considered the system to upgrade.
The fstab file is read in and mounted /system-root
in the order of the fstab entries - Activate travis Ci - Added command and path helper classes sheep10 1675779708
! " # $ % & ' ( ) * + , - . / 2.0.35-150000.1.56.1 suse-migration-pre-checks suse_migration_services suse_migration_services-2.0.35-py3.6.egg-info PKG-INFO SOURCES.txt dependency_links.txt entry_points.txt not-zip-safe requires.txt top_level.txt __init__.py __pycache__ __init__.cpython-36.pyc command.cpython-36.pyc defaults.cpython-36.pyc exceptions.cpython-36.pyc fstab.cpython-36.pyc logger.cpython-36.pyc version.cpython-36.pyc command.py defaults.py exceptions.py fstab.py logger.py migration_config.py path.py prechecks __pycache__ fs.cpython-36.pyc kernels.cpython-36.pyc pre_checks.cpython-36.pyc repos.cpython-36.pyc fs.py kernels.py pre_checks.py repos.py schema.py suse_product.py version.py /usr/bin/ /usr/lib/python3.6/site-packages/ /usr/lib/python3.6/site-packages/suse_migration_services-2.0.35-py3.6.egg-info/ /usr/lib/python3.6/site-packages/suse_migration_services/ /usr/lib/python3.6/site-packages/suse_migration_services/__pycache__/ /usr/lib/python3.6/site-packages/suse_migration_services/prechecks/ /usr/lib/python3.6/site-packages/suse_migration_services/prechecks/__pycache__/ -fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -g obs://build.suse.de/SUSE:Maintenance:27313/SUSE_SLE-15_Update/006067f4d370d8019aa2fca08a32c62d-suse-migration-services.SUSE_SLE-15_Update cpio xz 5 noarch-suse-linux Python script, ASCII text executable directory ASCII text empty python 3.6 byte-compiled
R R R R R R R R R R R R R R R R R R R R R R R R R R R 0C9jB]qك utf-8 c2965d2fdcd5049fb786af17680496bd63afb7461c5421b4dd686d42f72f5f9c ? 7zXZ
! t/XwDp]
crv9w!\h554杼|_zP#"Mt"ICD2>/C:i({gنNN} x-}~I $>&8p5 ܴ^)6ـwGӷ6S|7+ua -W&^You9)P{kABA -oq*Ї
ɝSg|rm )@>5?+ kwXro?,&0Iqe˘x{:tSrb )Jʸdm}?gn7{A7lI3_#Nj3 s N6 %?lBa7`!ֈvVn*D \,L8 NŃq o5_NjKֆθ4U'QdpVBf1 Do8 _ss1U "Sr )vQBQHjWg|Cd@ A>K t'2JHu0 1 ]*QY}I孀V^b4a\*G{/=R@ܷC3dT!\̜'*dYCdW(0];]$O ^ XQ|{ٯ=:tC50-aKk~{u -
͛ PF,s^m&XUmYY~ d Կ4QF}mjjT;Yn{' Fs8tUp?6\-A K
'4oMڷ[Kv6:5,4k/k AQ{VY ^ ci w[JLffSͳ^)DD< My'!~Gڴ t5=V}-^:V5Dz%
@|= wu|YC=6ލ萱I:>i±zTu4Mm툋nM'bndƪ
9X"Wz1K!ф':8vJYs㝙ZoJ_:Lѱ
n?Qۦ$ [`ǐM[xR3yP fϘT8'L K } lgD\!NXtӜłLK"P^wԘv@W "I/)-Ɗ׳Xow lLolSR
g1_s_Wdb0t<4.P:쵗 +)30S N~9`cśGExJŦ{r eB=eħ G}|Kigpә'ud* `#wQO\xn[[ M f=E f-Ӻ^OץnӾD) 7 EwB7mH;r֮ ;=3OIKJmi ʰElYPzxE.@Ky4?0H= >Dtߛ8h|_u,^9 z\x$jDvbPa(}v օePe.;i!jF,H*?XG9(k vj+ZmlsjxLm!%s2)M ky)# dU
'HWgd
Y7!K57Q&',ɹYǯV3cˠ_(RKEkv]
HPM!\CF*[' <8
09 &~o',zio9? "7@##}'Gg}AyoK~O\k#a]w I( *ˢW>k2 f:e/ڱ i+߫d':w>fh&V5YdfZt7C,OzRrQ(j;S@`-A(>[Le1! ڍ]cpR9q K'u
8RSq(FR9n䞏Ou=ȯ*r[J" sT7dļ#/SO_!S9>|# *Dgz̮I.< 0_Tm (rV$k;7uNg_KC?[luSx%8NbYb9aj雬8Gwi;iԔE,r* _oRd@ \oCW֕g?9Kr^B460Ċxٴx
l qEZ\*<$Ƽ= [r
CļֿR2esgXj *P=uE$%URm)嚆pB:s`Wʑu6x ;DY
XJ mNUORylQB&Mdk]bE []x3]<<9/E`{63Dhh !HגjQ/]FUfx]3$5hKLL%t4. |q%eHUxO%'DILGGz`yl1 >@ U
nDzkϙk}Y/)w[G] 29#'ŌI.ŋᬄPzXpv z+e
o<,GVד`+gu{X
**}kl[p^0>$ !À~KUe6{]~ PmB Oj!5Ow 2[:Nl>7Qnmja
t9n% ( V
q# ~TFȆw!j:*Yx-αTP90FBxaG?5yG'W>8'Tehm9s* 孆I []R 3m`[=\;Wqk迒;:jAWS*~gg4Es_eYVǺؙwc 0
f+d;u,v2 *Nc@)
ɠFɒldB0UE xdT5+зd"K}yFH^>|9߬CBO
{i}e%kBD$h$0楶{&ݏ;69 Ed}hFᇯ
5gJ ܤ(qҺE!Տ Nds!dTgR朢6mgS'-1m2pT:bmF|խ:ճ
Rwj[RoX7d'*9ƇX UK[F| 'L5$]s9Byʣ`z1.rH?k>}N.H-FbXt1N6G2M7 aQ
x)yFZpŋ3䄈M>]1}J*կ7/+f4.8nA"Q0>\9cȞ PmA>SQ&sR: >5֤ \e: shzH,U`qhcg >2}T5S'́ؤ
kNCI\0o7h++K _]hhHmmtQɋ0
߿}rC`A PO[=)Nܪnc(c` T7@˗4? K +R\#xLLm
i/fNT٤r.7y;:\JZP/Qg rfh*?A䦩좱#G`d# !<~ͦ+2/ԘYkGzw[ aͼv7O/$CY
<vueRzPP67Dc$im*Ld0
wT`S&}V2FvgPtPz:Mj,Hss̓!gsu^!(x?["_ IaNI {u)*K_2OL EfM A& )\3AH: H[G0S^U̽ N7j8gS8 ӧFݷFK"
(kE$J2[|L@ ǜ1@Iʦ
:sDjzI6 | cФ$^[e^BՄTskEB|8*JD QOq<˽WP\ZwOԤwk+ EEĥrEg JZ/D!|/\WG0Z [.Χ!6 fh%kMڂ*w F刽E6upcJ+U]y6F3a=u8 liBLM J^=&PKxĴZVXm0k>ϢV\=769TӶ dѨk#hEIBZn4JP`$&~.P&Z]ߧ2Zԯzu9lTbL G,te![5י
`ݛ8`ְbCr[)Qd b㩲Lr``
ێ8`2Yʸ gxj+#6q2|\1oQ^C˅7\='Gblny4NB̢F ώFtzZ_8N Ci\/?zW*L Y5}5ps܍|V=ٯR0.E _~QW -k-is_<` ܍|m#-eH=ox~I 6Qp%rhq ''r/31`8*A7L ܲ ?χ d, Z}x4,*v skٔ,nfP7NbN[5Ԁ˭e|
\R)jȽM?g6[]w։
%ҁVb. pmDޗ^+^QVTs1j.,ykuOs &ooNz}< w8oNcY ͼOm i T -T?!zH$եyN:(&Zxhio-%Ң'4W]
8\G9# CxIRMxNRGjrw_CM{n^HԳ
r ?o]] }lA^*҅$}F P'ԃP.YyZdtʐ
jMdY @-T:ato|ךJ1+ҟڇ҈߉9LF,V3rHa
VژyOjPoFnj|@YҽLTHu
#'KkB_o='@}7F6AneRh&w/eA1iV 8~r{.. v}1
z\= A`0tx5-=^ õ,n8ǛYraϭgxR}|h}'{Nb;|ʡq)P hQ\ޫRjjL-pD!0Tj "nF1|484+n
8 ؏課g , .'z_Vmg3,q[oD$CU
!'ȭ1dbOfڧBi?Q3>7i!(+
QΞl>peMjұý5[e~`0zWHF)HkԉY~.[rQ#X
QZ ;Y j*X*_*DaW4_b 㪡 i%ꔶx=R6$% N4ey
,f:N0$*"w-'l`Hm
C AyllV1[/d$C\>1}W,lk㺽Rq( R,F}rШɵߠ Kiߞ`
uCR꘠O~K L> lV5kK
91 5"/Aq.f O'Ѕ"2US4^]DMh8G G4HJU5I SDsouL>U{tdՠbF $Zl)LÏ> FM%oe(x)R;;{t #ܨRoWQ>n"[PmSs@7w9ʠ-ړ: ێ(i ay O9On|{e(8 13+U=A\*e>.m{;#d:Iy8CIi1eI#o`t[:\
gRrdI?oD0Y~4e59&|uUiT^ͥC%TrPjSfJKDo Ѝ&tQD|y.Q=5L2-W ,2@`[, 1y)z&Au.U/YjN[4JE}qIH4Ӫ$t BKa[V8&) EiHʜDxpd TpIkܕdI%O}wѢUrΊ lqtP:6 T[Z5aMU1gR:vi wP~:-pP,HAe
]43|sD;3G1 ]kҌ#ֶJ+_rv~3Qte V D"~8; 4k|5K *T8
OѴmv> % !}ЃɠbXo(j U_6^$"g] =n:72*1`-Vq%Z|H(ty_:o8]E"t.7~=f 8/5IQٴɫg[fwL&/y5bX\ҋR{xdG=>I6 lș`+kФjZ[kqj^>
gC%] #½iB'e%2v'6%c !lvn%3*Jd3My~TȟI!7-BJ]!/Mn!U }G@2}c6uU|o !Aϋ;(+'b[]$ rBAOǺ\&-s?|pX!q!:$E^AY6A q~0.)xd `pyы2׃5y$%4ǹ`r[fF 'd
4F ڴ'|yq7 xf5d2İXek0b_$$Ea>Yg"o' ~oaI 1*^d[1-y G?'ReS
[%A
;Ag$b BM#|P
Vi/2G/b3lw.H.FnZG 9ڨK˰*r@Vo\hb6y)
sr7*9k-+q 轛wa1[<\2a3#?p} b-A@nr +)൚n$
ܻJ 摿grx.
:-ݲ0λ3eKҺSx ӣDY.'柽@!picL5c^|+XJ))` X\2ء힏3~S/PC ) zgҋA+(\% W/ @Tq[Ԓ~ɇI$dj3x`ʌ͋9g,}k8aC\VHwm٣\}xgJ5h43 (R{ޞpLi"i#|T:S1&r~Jd=Y<0
b'@yB5;65aB_aJeze>CQiD]qDݵlvYBr "/x@< eZ:ry\'d@A :B#~%݇EzB̥ZWMIPW<"mZY,
;c%ԶJY۪<]{Rb[uA'A)~g Xq~ yr} eelS v { ơ
$|qeDdW
9+KM Zܬmݦ5ˀChFa";E]Z0>Ӛٮ漜BD33 c@0'y|hqJr\U`}<ʀhޢ2楨vK/n่"*
H?I($]A0OaO"x磋j%#> nqk4|~La! ,<4ll֛rU( CF R; 8|/O1Nt" #P~2k/Y}Sn9#b=~Gв(h{UÄRNsE.?_sW\K?cGHfۃ9˸+p gQyFy \Ʒ #TbI ,|3[EI,v,}$4܄VT2Ox{{<ڬ|7Ut
vɾ4eNϻF&Z=\# h#ʹsĨaQ@:=sNW 8Xx KM02gN/t:7:i?=
L@X&_L_ V 4[gwWzS t̉jׅ_# FLY=ڇ$P=293lK4+Z\ 4*ut FV+laҋO
$ _dz@ʙ|^#_ͺ
_9x4.H>,5̾mBJ
r.5 iONP=rOq,v
y$mMk^sn)3lsd \):%# \F{;rl,3g\ ՁX-Jڎ a(oD j)(&'
-%w3$vyL%;G+n#[;]wlpAvIѐ%.~{K) P19-GCE ZCh293
6_l =و{XR@ MAq:| y[
wT jv| Y yO:ʼn2 !lds8.$:-~Z1}Y#WB S窇 M\.tvÚjGj<c:%
[h;A J=u?{ƓsY^J5-_yiN;,[U 2KE1؍eR]Ÿ J}v g/4 fABK3 qH-EP3cNލV!zZ;^l2 5#ue*dagI"=K[2l(,CPC
kKV5Oh +:-,ɬo8nPpr
i͕G2D+ZIIb p-bZԗ^O@[!@7 ZfUd
F& bߜ*TeZ}N!\{Upd ;mwg5&+uez҃LKrs`{]M!`cK2"{20IˬX{0M@mInRb6~gԥHȩ7s6 -EbL l:=3QOn=
-{c[uEeR2̧ "]%3
~[wJ~2oH7n4 gu |wTd Jm!F }N{ Pd+!7,"3 B|/e%Dn8[fɀE+ f JTO먣??l=R@ '˘)>+=?Aczt 5ſj v)Ŕ`M1"queڰM^4olp?8c6<\j.I;u t !Te(7H I1Sy-UtU~au8 n9>-]#:}aݗЬt1 z 4)bUiQy`h֢ p"]:P.SϸQwt0JBh#3ܯq6 8? `\ ԾD!C2).q6&H!^
-%44Y~ LִahVܮXY
=ԨTC͇^&hL$"gO~)eU.4N=qԯtlf4³{\w߹68Q\Ɣ -3_ud.Ri؊JK;Ab6.
`n73b6a53TKX :(EjjFXb넖,ֹIYkN*0P+{TM/Ff
N,p+
t5۱
c_4
<QE7i_^ץrh9HQ[?wƻX ߸]<R]`qtDE
<LW7]GDE m@Cq'ŲzL]z%|>)_ڃN+7ʿm<8%f
Vv't o҃u¯&$ wWuv l89 Ë0]
i'rX6}yzpuޙ4 fԃ%ArT=ma1'H8YT}wU 9.sƃV"aҵ[[[|Z]#%<,6Gh1igH0}N,c,{ޡ {s Rfx
j!O; k鍕c#>U
E>IǗ<3 ȵY63pVWՊnIα-"Z5W>éU*O+Gi)GJJj< @W$ Pg=pM~T֘Fks-V:T>!Γ8+0Gza<溽
b}=Q%( Nԙ. #ZTQ衍>>M轳`0kF^zb\}eVy=H+8*+$05kF(T[lzNG 9P̮ei t^e}j}lPju{/͛GftNUPunOtIJ1AJN7KN{3ae[]8o'KQB+ȑiش`̱c=NE_ j⽂WJ7~}#䳢AU
ZzD`}h X!;!&b -dC2ڗ5um(Ŏ+&tO>U4lɟe fc +Rc6dwoCOc7sucܟͬFQ`xtfGb\۹
HqZ Jo#[>ˬ)bKk Jj
YZ