Wiki source for TestingMageia1
TestingMageia > See Blog20101001MageiaMigrationPathForUsers
The objective of testing is to check that packages have correct dependencies and upgrade paths (maybe automatic tools like mancoosi tries to do would help?). Testing for real is good too as it provides effective checking of what actually works, often human testing is better, even though some parts of it can be automated (computers are here to help aren't they? :D).
Related tests:
~- TestingMageia1Upgrade20102 in a VirtualBox VM installed with up-to-date 2010.2
~- TestingMageia1UpgradeEeePC20102 my EeePC up-to-date 2010.2 (a small bug with keyboard with user baud, change default to baud123 **corrected** accessibility was enabled by (my ?) error)
~- TestingMageia1UpgradeLatitudeE640020102 my laptop Latitude E6400 2010.2 i586
===Testing Mageia 1 alpha 1 in a VirtualBox VM===
Virtual Machine is an easy way to test a system, though not on diverse hardware :/
Installation is quite easy, the principle being:
~- take an iso (download a live CD for example)
~- create a VM
~- boot the VM: at first boot, it requires a media (be it a cdrom or an iso in a directory)
~- the VM permits to install a linux, on a 8 GB auto-expanding file for example
~~- partitionning: take care, diskdrake by default uses 4 GB / 500 MB / 3,5 GB for /home, use specific partionning to let only 500 MB for /home for example :-)
~~- you can reboot the OS in the VM, it will stay in the VM, you can even shutdown it and boot the VM afterwards
~~- check how auto-expanding can work (other partition to create ?)
~~- check how to copy an existing VM : cp the file, exporting or using a snapshot? (maybe exporting a snapshot to create a clone of the VM?)
~-
===Testing a One KDE4 for example===
~- install a One KDE 4 in a VM
~- upgrade it to 2010.2 with latest modifications (keep a copy of the initial install to test fresh install upgrade)
~- add some packages (list created from an existing installation, for example)
~- identify the following things
~~- time to upgrade to mageia: can be 4 hours (usual time for ~1000 packages) on current computers (Dell E6400 in my case)
~~- space disk needed for upgrade, space disk at the end
~~- remaining packages (libs, not existing packages)
~- be prepared to relaunch installation upgrade when new packages are available
~~- perhaps have some script to identify automatically what is needed?
===Some useful commands to automate testing===
===How to report correctly a bug concerning upgrade===
===To be added to wiki===
~- choice of installation is Virtualbox but you may proceed at your own risk :)
~~- physical computer: be ready to dedicate it to cauldron testing and be sure to read http://mageia.org/en/alpha/
~~- even pentium II should work, as packages are compiled for i586, PAE is only for kernel-server
~- hybrid iso for all.img at the moment, maybe hybrid livecd iso for alpha2? (liveDVD?)
~- pre-requisites:
~~- a bootable device, be it an internal DVD or external USB DVD or an usb key (with all.img or once there is hybrid ISO)
~~- up-to-date installation (DVD + cauldron repositories configured + ##urpmi --auto-select##)
~~- as the test day is for testing, prepare all you need in advance
~~~- downloading a 2 GB ISO can be done the day before :)
~~~- you may review the test plan in advance and suggest addition to the ML
~- keep in mind that people may get disconnected from irc when rebooting or changing Xorg conf (for video driver for example)
~- use http://mageia.pastebin.com when pasting more than 5 lines
~- announcement for test-day is to be made:
~~- on the wiki, on the blog, on the ML, during meeting
===Usual errors when upgrading===
~- missing rpm
~~- as the upgrade takes time new rpm may appear (previous one being deleted) and hdlists taken into account for update are out-of-sync
~~- just relaunch urpmi --auto-update for missing rpm ; if they are still missing, well maybe there's a problem or you're out of luck :-)
~- choice of rpm
~~- sometimes there are several possibilities
~~- usually the first is the correct one (not always)
~~- you can identify those: just urpmi them and answer questions, so that the installation is not stopped ; then relaunch upgrade for the remaining time
~- disk full
~~- well, just urpme big packages then urpmi then again afterwards, takes less room than upgrading
~~- /bin/rm -R /usr/share/doc/* # well, who reads the documentation anyway ?
~~- remove old kernels, anyway you're upgrading, so... kernel-source can free much space ;-) (only headers are needed for dkms anyway)
===Using repositories for cauldron===
To upgrade from Mandriva Linux you have to replace the repositories you're currently using (be sure to save/backup everything you want to keep: data, configuration, bookmarks...).
##urpmi.removemedia -a## # remove all current repositories used
urpmi.addmedia cauldron_core ftp://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/cauldron/i586/media/core/release/ with media_info/synthesis.hdlist.cz
urpmi.addmedia cauldron_nonfree ftp://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/cauldron/i586/media/nonfree/release/ with media_info/synthesis.hdlist.cz
# to be added: tainted and then updates for each
===""<A name="hw">""Some packages to add: hwreport / smolt for hardware reporting""</a>""===
Tools to report installation / hardware detection
~- check http://faq.tuxfamily.org/CommunicationLibreHardware/En for use-case and hardware compatibility list
~- hwreport ftp://distrib-coffee.ipsl.jussieu.fr/pub/linux/MandrivaLinux/official/2010.1/SRPMS/main/release/hwreport-0.10.0-5mdv2010.1.src.rpm
~- smolt-gui smolt unresolved dependancies : python-urlgrabber python-paste ftp://distrib-coffee.ipsl.jussieu.fr/pub/linux/MandrivaLinux/official/2010.1/SRPMS/contrib/release/smolt-1.4.2-1mdv2010.1.src.rpm
Installation of rpmbuild environment, see http://mageia.org/wiki/doku.php?id=rpm_start
urpmi rpm-build
%%Pour satisfaire les dépendances, les paquetages suivants vont être installés :
Paquetage Version Révision Arch
(média « cauldron_core »)
autoconf 2.68 1.mga1 noarch
automake 1.11.1 3.mga1 noarch
elfutils 0.150 1.mga1 i586
gcc-c++ 4.5.2 2.mga1 i586
gettext 0.18.1.1 1.mga1 i586
libgettextmisc 0.18.1.1 1.mga1 i586
libtool-base 2.4 3.mga1 i586
libunistring0 0.9.3 2.mga1 i586
m4 1.4.15 1.mga1 i586
patch 2.6.1 4.mga1 i586
perl-File-Slurp 9999.130.0 1.mga1 noarch
perl-JSON 2.500.0 2.mga1 noarch
perl-List-MoreUtils 0.300.0 3.mga1 i586
perl-Module-ScanDeps 1.0.0 1.mga1 noarch
perl-YAML 0.720.0 2.mga1 noarch
python-pkg-resources 0.6.14 7.mga1 noarch
rpm-build 4.6.1 10.mga1 i586
rpm-mageia-setup 1.118 1.mga1 i586
rpm-mageia-setup-build 1.118 1.mga1 i586
spec-helper 0.31.5 2.mga1 noarch
un espace additionnel de 24Mo sera utilisé.
7.4Mo de paquets seront récupérés.
Procéder à l'installation des 20 paquetages ? (O/n) %%
rpm -i hwreport-0.10.0-5mdv2010.1.src.rpm
attention: utilisateur mandrake inexistant - utilisation de root
attention: groupe mandrake inexistant - utilisation de root
attention: utilisateur mandrake inexistant - utilisation de root
attention: groupe mandrake inexistant - utilisation de root
rpmbuild -ba hwreport.spec
%%extracting debug info from /home/baud/rpm/BUILDROOT/hwreport-0.10.0-5.mga1.i386/usr/bin/scan-printers
*** WARNING: No build ID note found in /home/baud/rpm/BUILDROOT/hwreport-0.10.0-5.mga1.i386/usr/bin/scan-printers
cpio: /home/iurt/rpm/BUILD/glibc-2.12.1/csu: échec de la fonction : stat: Aucun fichier ou dossier de ce type
7 blocs
%%
hwreport /home/baud/tmp/report # ok works correctly, see http://hardware4linux.info/distrib/44407/
%%rpm -ivh smolt-1.4.2-1.mga1.noarch.rpm smolt-gui-1.4.2-1.mga1.noarch.rpm
erreur: Dépendances requises:
dbus-python est nécessaire pour smolt-1.4.2-1.mga1.noarch
python-urlgrabber est nécessaire pour smolt-1.4.2-1.mga1.noarch
python-paste est nécessaire pour smolt-1.4.2-1.mga1.noarch
python-simplejson est nécessaire pour smolt-1.4.2-1.mga1.noarch
urpmi smolt-1.4.2-1.mga1.noarch.rpm smolt-gui-1.4.2-1.mga1.noarch.rpm
Certains paquetages demandés ne peuvent pas être installés :
smolt-1.4.2-1.mga1.noarch (car python-paste est non satisfait)
smolt-gui-1.4.2-1.mga1.noarch (car smolt[== 1.4.2] est non satisfait)%%
ftp://distrib-coffee.ipsl.jussieu.fr/pub/linux/MandrivaLinux/official/2010.1/SRPMS/contrib/release/python-paste-1.7.2-3mdv2010.0.src.rpm
rpmbuild -ba python-paste.spec
sh: ligne 0 : fg: pas de contrôle de tâche
sh: ligne 0 : fg: pas de contrôle de tâche
erreur: Dépendances de construction manquantes:
python-devel est nécessaire pour python-paste-1.7.2-3.mga1.src
python-setuptools est nécessaire pour python-paste-1.7.2-3.mga1.src
nouvelle version de python-paste à packager : 1.7.5
ftp://distrib-coffee.ipsl.jussieu.fr/pub/linux/MandrivaLinux/official/2010.1/SRPMS/contrib/release/python-urlgrabber-3.9.1-1mdv2010.0.src.rpm
%%rpmbuild -ba python-urlgrabber.spec
erreur: Dépendances de construction manquantes:
python-curl est nécessaire pour python-urlgrabber-3.9.1-1.mga1.src%%
%% urpmi smolt-1.4.2-1.mga1.noarch.rpm smolt-gui-1.4.2-1.mga1.noarch.rpm
Pour satisfaire les dépendances, les paquetages suivants vont être installés :
Paquetage Version Révision Arch
(média « cauldron_core »)
python-dbus 0.83.2 3.mga1 i586
python-simplejson 2.1.2 1.mga1 i586
(ligne de commande)
smolt 1.4.2 1.mga1 noarch
smolt-gui 1.4.2 1.mga1 noarch
un espace additionnel de 1.5Mo sera utilisé.
382Ko de paquets seront récupérés.
Procéder à l'installation des 4 paquetages ? (O/n)
http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/cauldron/i586/media/core/release/python-simplejson-2.1.2-1.mga1.i586.rpm
http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/cauldron/i586/media/core/release/python-dbus-0.83.2-3.mga1.i586.rpm
installation de /var/cache/urpmi/rpms/python-simplejson-2.1.2-1.mga1.i586.rpm
smolt-1.4.2-1.mga1.noarch.rpm
smolt-gui-1.4.2-1.mga1.noarch.rpm
/var/cache/urpmi/rpms/python-dbus-0.83.2-3.mga1.i586.rpm
Préparation ... #############################################################################################################
1/4: python-dbus #############################################################################################################
2/4: python-simplejson #############################################################################################################
3/4: smolt #############################################################################################################
4/4: smolt-gui #############################################################################################################
----------------------------------------------------------------------
Plus d'information sur le paquetage smolt-1.4.2-1.mga1.noarch
The Smolt hardware collector will not send any data until you do
so manually.
To send your hardware profile to http://smolts.org, run the
smoltSendProfile command. If you have installed the smolt-gui package,
you can also start Smolt from the applications menu in Tools -
System Tools.
If you want to update your hardware profile automatically on a monthly
basis, edit the file /etc/sysconfig/smolt and set
ENABLE_MONTHLY_UPDATE=1
----------------------------------------------------------------------%%
smoltGui seems to work, see:
http://www.smolts.org/client/show/pub_5e39c99c-300d-41e7-a36a-75bb3d8ae477
===2011-03-06 update===
%%Transcript written on pdfxmltex.log.
fmtutil: /var/lib/texmf/web2c/pdftex/pdfxmltex.fmt installed.
###############################################################################
fmtutil: Error! Not all formats have been built successfully.
Visit the log files in directory
/var/lib/texmf/web2c
for details.
###############################################################################
This is a summary of all `failed' messages:
`pdftex -ini -jobname=mptopdf -progname=context -translate-file=cp227.tcx mptopdf.tex' failed
/
%%
----
TestingMageia
The objective of testing is to check that packages have correct dependencies and upgrade paths (maybe automatic tools like mancoosi tries to do would help?). Testing for real is good too as it provides effective checking of what actually works, often human testing is better, even though some parts of it can be automated (computers are here to help aren't they? :D).
Related tests:
~- TestingMageia1Upgrade20102 in a VirtualBox VM installed with up-to-date 2010.2
~- TestingMageia1UpgradeEeePC20102 my EeePC up-to-date 2010.2 (a small bug with keyboard with user baud, change default to baud123 **corrected** accessibility was enabled by (my ?) error)
~- TestingMageia1UpgradeLatitudeE640020102 my laptop Latitude E6400 2010.2 i586
===Testing Mageia 1 alpha 1 in a VirtualBox VM===
Virtual Machine is an easy way to test a system, though not on diverse hardware :/
Installation is quite easy, the principle being:
~- take an iso (download a live CD for example)
~- create a VM
~- boot the VM: at first boot, it requires a media (be it a cdrom or an iso in a directory)
~- the VM permits to install a linux, on a 8 GB auto-expanding file for example
~~- partitionning: take care, diskdrake by default uses 4 GB / 500 MB / 3,5 GB for /home, use specific partionning to let only 500 MB for /home for example :-)
~~- you can reboot the OS in the VM, it will stay in the VM, you can even shutdown it and boot the VM afterwards
~~- check how auto-expanding can work (other partition to create ?)
~~- check how to copy an existing VM : cp the file, exporting or using a snapshot? (maybe exporting a snapshot to create a clone of the VM?)
~-
===Testing a One KDE4 for example===
~- install a One KDE 4 in a VM
~- upgrade it to 2010.2 with latest modifications (keep a copy of the initial install to test fresh install upgrade)
~- add some packages (list created from an existing installation, for example)
~- identify the following things
~~- time to upgrade to mageia: can be 4 hours (usual time for ~1000 packages) on current computers (Dell E6400 in my case)
~~- space disk needed for upgrade, space disk at the end
~~- remaining packages (libs, not existing packages)
~- be prepared to relaunch installation upgrade when new packages are available
~~- perhaps have some script to identify automatically what is needed?
===Some useful commands to automate testing===
===How to report correctly a bug concerning upgrade===
===To be added to wiki===
~- choice of installation is Virtualbox but you may proceed at your own risk :)
~~- physical computer: be ready to dedicate it to cauldron testing and be sure to read http://mageia.org/en/alpha/
~~- even pentium II should work, as packages are compiled for i586, PAE is only for kernel-server
~- hybrid iso for all.img at the moment, maybe hybrid livecd iso for alpha2? (liveDVD?)
~- pre-requisites:
~~- a bootable device, be it an internal DVD or external USB DVD or an usb key (with all.img or once there is hybrid ISO)
~~- up-to-date installation (DVD + cauldron repositories configured + ##urpmi --auto-select##)
~~- as the test day is for testing, prepare all you need in advance
~~~- downloading a 2 GB ISO can be done the day before :)
~~~- you may review the test plan in advance and suggest addition to the ML
~- keep in mind that people may get disconnected from irc when rebooting or changing Xorg conf (for video driver for example)
~- use http://mageia.pastebin.com when pasting more than 5 lines
~- announcement for test-day is to be made:
~~- on the wiki, on the blog, on the ML, during meeting
===Usual errors when upgrading===
~- missing rpm
~~- as the upgrade takes time new rpm may appear (previous one being deleted) and hdlists taken into account for update are out-of-sync
~~- just relaunch urpmi --auto-update for missing rpm ; if they are still missing, well maybe there's a problem or you're out of luck :-)
~- choice of rpm
~~- sometimes there are several possibilities
~~- usually the first is the correct one (not always)
~~- you can identify those: just urpmi them and answer questions, so that the installation is not stopped ; then relaunch upgrade for the remaining time
~- disk full
~~- well, just urpme big packages then urpmi then again afterwards, takes less room than upgrading
~~- /bin/rm -R /usr/share/doc/* # well, who reads the documentation anyway ?
~~- remove old kernels, anyway you're upgrading, so... kernel-source can free much space ;-) (only headers are needed for dkms anyway)
===Using repositories for cauldron===
To upgrade from Mandriva Linux you have to replace the repositories you're currently using (be sure to save/backup everything you want to keep: data, configuration, bookmarks...).
##urpmi.removemedia -a## # remove all current repositories used
urpmi.addmedia cauldron_core ftp://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/cauldron/i586/media/core/release/ with media_info/synthesis.hdlist.cz
urpmi.addmedia cauldron_nonfree ftp://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/cauldron/i586/media/nonfree/release/ with media_info/synthesis.hdlist.cz
# to be added: tainted and then updates for each
===""<A name="hw">""Some packages to add: hwreport / smolt for hardware reporting""</a>""===
Tools to report installation / hardware detection
~- check http://faq.tuxfamily.org/CommunicationLibreHardware/En for use-case and hardware compatibility list
~- hwreport ftp://distrib-coffee.ipsl.jussieu.fr/pub/linux/MandrivaLinux/official/2010.1/SRPMS/main/release/hwreport-0.10.0-5mdv2010.1.src.rpm
~- smolt-gui smolt unresolved dependancies : python-urlgrabber python-paste ftp://distrib-coffee.ipsl.jussieu.fr/pub/linux/MandrivaLinux/official/2010.1/SRPMS/contrib/release/smolt-1.4.2-1mdv2010.1.src.rpm
Installation of rpmbuild environment, see http://mageia.org/wiki/doku.php?id=rpm_start
urpmi rpm-build
%%Pour satisfaire les dépendances, les paquetages suivants vont être installés :
Paquetage Version Révision Arch
(média « cauldron_core »)
autoconf 2.68 1.mga1 noarch
automake 1.11.1 3.mga1 noarch
elfutils 0.150 1.mga1 i586
gcc-c++ 4.5.2 2.mga1 i586
gettext 0.18.1.1 1.mga1 i586
libgettextmisc 0.18.1.1 1.mga1 i586
libtool-base 2.4 3.mga1 i586
libunistring0 0.9.3 2.mga1 i586
m4 1.4.15 1.mga1 i586
patch 2.6.1 4.mga1 i586
perl-File-Slurp 9999.130.0 1.mga1 noarch
perl-JSON 2.500.0 2.mga1 noarch
perl-List-MoreUtils 0.300.0 3.mga1 i586
perl-Module-ScanDeps 1.0.0 1.mga1 noarch
perl-YAML 0.720.0 2.mga1 noarch
python-pkg-resources 0.6.14 7.mga1 noarch
rpm-build 4.6.1 10.mga1 i586
rpm-mageia-setup 1.118 1.mga1 i586
rpm-mageia-setup-build 1.118 1.mga1 i586
spec-helper 0.31.5 2.mga1 noarch
un espace additionnel de 24Mo sera utilisé.
7.4Mo de paquets seront récupérés.
Procéder à l'installation des 20 paquetages ? (O/n) %%
rpm -i hwreport-0.10.0-5mdv2010.1.src.rpm
attention: utilisateur mandrake inexistant - utilisation de root
attention: groupe mandrake inexistant - utilisation de root
attention: utilisateur mandrake inexistant - utilisation de root
attention: groupe mandrake inexistant - utilisation de root
rpmbuild -ba hwreport.spec
%%extracting debug info from /home/baud/rpm/BUILDROOT/hwreport-0.10.0-5.mga1.i386/usr/bin/scan-printers
*** WARNING: No build ID note found in /home/baud/rpm/BUILDROOT/hwreport-0.10.0-5.mga1.i386/usr/bin/scan-printers
cpio: /home/iurt/rpm/BUILD/glibc-2.12.1/csu: échec de la fonction : stat: Aucun fichier ou dossier de ce type
7 blocs
%%
hwreport /home/baud/tmp/report # ok works correctly, see http://hardware4linux.info/distrib/44407/
%%rpm -ivh smolt-1.4.2-1.mga1.noarch.rpm smolt-gui-1.4.2-1.mga1.noarch.rpm
erreur: Dépendances requises:
dbus-python est nécessaire pour smolt-1.4.2-1.mga1.noarch
python-urlgrabber est nécessaire pour smolt-1.4.2-1.mga1.noarch
python-paste est nécessaire pour smolt-1.4.2-1.mga1.noarch
python-simplejson est nécessaire pour smolt-1.4.2-1.mga1.noarch
urpmi smolt-1.4.2-1.mga1.noarch.rpm smolt-gui-1.4.2-1.mga1.noarch.rpm
Certains paquetages demandés ne peuvent pas être installés :
smolt-1.4.2-1.mga1.noarch (car python-paste est non satisfait)
smolt-gui-1.4.2-1.mga1.noarch (car smolt[== 1.4.2] est non satisfait)%%
ftp://distrib-coffee.ipsl.jussieu.fr/pub/linux/MandrivaLinux/official/2010.1/SRPMS/contrib/release/python-paste-1.7.2-3mdv2010.0.src.rpm
rpmbuild -ba python-paste.spec
sh: ligne 0 : fg: pas de contrôle de tâche
sh: ligne 0 : fg: pas de contrôle de tâche
erreur: Dépendances de construction manquantes:
python-devel est nécessaire pour python-paste-1.7.2-3.mga1.src
python-setuptools est nécessaire pour python-paste-1.7.2-3.mga1.src
nouvelle version de python-paste à packager : 1.7.5
ftp://distrib-coffee.ipsl.jussieu.fr/pub/linux/MandrivaLinux/official/2010.1/SRPMS/contrib/release/python-urlgrabber-3.9.1-1mdv2010.0.src.rpm
%%rpmbuild -ba python-urlgrabber.spec
erreur: Dépendances de construction manquantes:
python-curl est nécessaire pour python-urlgrabber-3.9.1-1.mga1.src%%
%% urpmi smolt-1.4.2-1.mga1.noarch.rpm smolt-gui-1.4.2-1.mga1.noarch.rpm
Pour satisfaire les dépendances, les paquetages suivants vont être installés :
Paquetage Version Révision Arch
(média « cauldron_core »)
python-dbus 0.83.2 3.mga1 i586
python-simplejson 2.1.2 1.mga1 i586
(ligne de commande)
smolt 1.4.2 1.mga1 noarch
smolt-gui 1.4.2 1.mga1 noarch
un espace additionnel de 1.5Mo sera utilisé.
382Ko de paquets seront récupérés.
Procéder à l'installation des 4 paquetages ? (O/n)
http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/cauldron/i586/media/core/release/python-simplejson-2.1.2-1.mga1.i586.rpm
http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/cauldron/i586/media/core/release/python-dbus-0.83.2-3.mga1.i586.rpm
installation de /var/cache/urpmi/rpms/python-simplejson-2.1.2-1.mga1.i586.rpm
smolt-1.4.2-1.mga1.noarch.rpm
smolt-gui-1.4.2-1.mga1.noarch.rpm
/var/cache/urpmi/rpms/python-dbus-0.83.2-3.mga1.i586.rpm
Préparation ... #############################################################################################################
1/4: python-dbus #############################################################################################################
2/4: python-simplejson #############################################################################################################
3/4: smolt #############################################################################################################
4/4: smolt-gui #############################################################################################################
----------------------------------------------------------------------
Plus d'information sur le paquetage smolt-1.4.2-1.mga1.noarch
The Smolt hardware collector will not send any data until you do
so manually.
To send your hardware profile to http://smolts.org, run the
smoltSendProfile command. If you have installed the smolt-gui package,
you can also start Smolt from the applications menu in Tools -
System Tools.
If you want to update your hardware profile automatically on a monthly
basis, edit the file /etc/sysconfig/smolt and set
ENABLE_MONTHLY_UPDATE=1
----------------------------------------------------------------------%%
smoltGui seems to work, see:
http://www.smolts.org/client/show/pub_5e39c99c-300d-41e7-a36a-75bb3d8ae477
===2011-03-06 update===
%%Transcript written on pdfxmltex.log.
fmtutil: /var/lib/texmf/web2c/pdftex/pdfxmltex.fmt installed.
###############################################################################
fmtutil: Error! Not all formats have been built successfully.
Visit the log files in directory
/var/lib/texmf/web2c
for details.
###############################################################################
This is a summary of all `failed' messages:
`pdftex -ini -jobname=mptopdf -progname=context -translate-file=cp227.tcx mptopdf.tex' failed
/
%%
----
TestingMageia
