| Age | Commit message (Collapse) | Author |
|---|
|
also:
* added keyring update openrc service file
* add dummy.conf
empty.conf and the remaining changes were mainly to minimize the diff against arch
|
|
|
|
|
|
|
|
Without that fix, when creating a chroot with the following commands
on Parabola x86_64, the resulting chroot is 64bit:
# mkdir rootfs
# pacstrap -C /usr/share/pacman/defaults/pacman.conf.i686 ./rootfs/
# file rootfs/usr/bin/pacman
rootfs/usr/bin/pacman: ELF 64-bit LSB pie executable, x86-64, [...]
In addition, if we run Parabola i686 on an x86_64 computer with
linux-libre-64, and that we try to install packages (after pacman -Sy),
some packages will refuse to be installed because they have
dependencies on 64bit libraries packages while we have 32bit ones
instead:
# pacman -S e2fsprogs
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing e2fsprogs (1.46.5-1) breaks dependency 'libss.so=2-32' required by krb5
:: installing e2fsprogs (1.46.5-1) breaks dependency 'libcom_err.so=2-32' required by krb5
but packages without such dependencies (like xterm or coreutils) can
be installed without warnings and we end up with non-working
packages:
# pacman -S xterm
[the installation proceeds]
# file /usr/bin/xterm
/usr/bin/xterm: ELF 64-bit LSB pie executable, x86-64, [...]
# xterm
bash: /usr/bin/xterm: No such file or directory
So it's a good idea to hardcode the architecture by default.
The Arch Linux 32 installer uses auto to auto-detect the CPU currently
in use to select matching repositories.
But in Parabola, for x86 32bit we only have one i686 repository and no
pentium4 or i586.
In addition, all the Parabola installers don't depend on auto (the
multi architecture installer has two complete Parabola systems, one
for i686 and one for x86_64, so it doesn't need auto).
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
|
|
|
|
|
|
|
|
|
|
pacman.conf
|
|
|
|
|
|
https://lists.parabola.nu/pipermail/dev/2017-December/006177.html
|
|
https://labs.parabola.nu/issues/1136
|
|
[nonprism-multilib-testing], [pcr-multilib] and [pcr-multilib-testing]
|
|
https://lists.parabola.nu/pipermail/dev/2016-October/004528.html
|
|
before running install scripts for armv7h; fix nonprism repos in pacman.conf files
|
|
|
|
/etc/pacman.conf before any other repos -> https://labs.parabola.nu/issues/610
|
|
|
|
|
|
|
|
|
|
pacman.conf.x86_64
|
|
|
|
|
|
There were more changes recently when updating pacman first broke it
(e.g. it depended on newer libarchive or glibc) than when it was
needed.
Keyring packages need to be updated first if updates signed by new
keys are downloaded.
|
|
|
|
I did this with this command:
git diff d62bd1^..d62bd1 | egrep '^old mode ' -C1 \
| tr '\n' ' ' | sed 's/diff --git/\n&/g' \
| sed -r 's|^diff --git a/([^ ]*) b/([^ ]*) old mode 100([0-9]*) new mode 100([0-9]*)|chmod \3 ./\1|' \
| bash
The first line finds all of the file-permission changes in the commit.
The second line squashes some newlines to get one line per file. This line
is in the format:
diff --git a/FILE b/FILE old mode OLDMODE new mode NEWMODE
The third line extracts the values from those lines and transforms the line
into:
chmod FILE ./OLDMODE
The fourth line (obviously) just executes the output.
|
|
|
|
recovered rePKGBUILD
|
|
|
|
|
|
|
