drakx/perl-install, branch 18.51 Mageia Installer and base platform for many utilities 18.51 2022-10-29T11:08:50+00:00 Martin Whitaker mageia@martin-whitaker.me.uk 2022-10-29T11:08:50+00:00 54b997e5fedba82c6e2d626edeeb1b5fc3ff1e96 






Include rpm & rpmdb in stage 2 installer files.
2022-10-29T11:04:08+00:00

Martin Whitaker
mageia@martin-whitaker.me.uk

2022-10-29T11:04:08+00:00

4c5c212e005de3fb7c32ea65da2a64bcfff5fd5c

These are needed to allow the rpm database to be converted to sqlite
when upgrading an older Mageia installation (mga#31024).





These are needed to allow the rpm database to be converted to sqlite
when upgrading an older Mageia installation (mga#31024).







Fix typo in comment.
2022-10-28T16:16:31+00:00

Martin Whitaker
mageia@martin-whitaker.me.uk

2022-10-28T16:16:31+00:00

ec40e19eaa63bd8999628387830320b7888a4341












Adapt to WebKit2 4.1.
2022-10-26T21:09:47+00:00

Martin Whitaker
mageia@martin-whitaker.me.uk

2022-10-26T19:54:22+00:00

f3677bff009545eae1efe984e3704affd6ba2305












Ensure efivarfs is mounted in the chroot when running the installer.
2022-10-25T17:46:55+00:00

Martin Whitaker
mageia@martin-whitaker.me.uk

2022-10-25T17:46:55+00:00

1d1d49e4f422e6e5ef8204b6cdcca8fd8cdf5f14

If the efivarfs was already mounted in the installer runtime environment,
the previous code would detect that and not mount it in the installed
system enviroment. Currently this doesn't happen unless the user manually
mounts it, but protect against that and against future changes.





If the efivarfs was already mounted in the installer runtime environment,
the previous code would detect that and not mount it in the installed
system enviroment. Currently this doesn't happen unless the user manually
mounts it, but protect against that and against future changes.







Ensure efivars are mounted before installing a UEFI bootloader (mga#31008)
2022-10-24T21:03:49+00:00

Martin Whitaker
mageia@martin-whitaker.me.uk

2022-10-24T21:03:49+00:00

4db36433bd629747578ba1e60aff425066dac140

The old way of accessing EFI NVRAM variables via /sys/firmware/efi/vars
was removed in Linux 6.0. The new way is to use the efivarfs pseudo-
filesystem, which is usually mounted at /sys/firmware/efi/efivars. We
need to make sure this is actually mounted before attempting to install
a UEFI bootloader, otherwise any attempt to write to the EFI NVRAM will
fail.





The old way of accessing EFI NVRAM variables via /sys/firmware/efi/vars
was removed in Linux 6.0. The new way is to use the efivarfs pseudo-
filesystem, which is usually mounted at /sys/firmware/efi/efivars. We
need to make sure this is actually mounted before attempting to install
a UEFI bootloader, otherwise any attempt to write to the EFI NVRAM will
fail.







Factor out code to mount the efivarfs pseudo-filesystem.
2022-10-24T20:07:25+00:00

Martin Whitaker
mageia@martin-whitaker.me.uk

2022-10-24T20:07:25+00:00

325cbdb1eeff9310c305bfb4c29bf7f03556655f












18.50
2022-09-17T16:24:10+00:00

Martin Whitaker
mageia@martin-whitaker.me.uk

2022-09-17T16:24:10+00:00

190cbcbf9d6f885cfa713f1ed61acbbb111ac7a3












Update Russian translation from Tx
2022-08-27T08:30:58+00:00

Yuri Chornoivan
yurchor@ukr.net

2022-08-27T08:30:58+00:00

9c5c374d0059894cd2f19c901edc43ed108d820c












Update Russian translation from Tx
2022-08-27T08:30:52+00:00

Yuri Chornoivan
yurchor@ukr.net

2022-08-27T08:30:52+00:00

bc0fc87328a1a4f2560b16fd50001ab34cad4143