- Mar 04, 2024
-
-
Allan McRae authored
Signed-off-by: Allan McRae <allan@archlinux.org>
-
Allan McRae authored
Signed-off-by: Allan McRae <allan@archlinux.org>
-
Allan McRae authored
Signed-off-by: Allan McRae <allan@archlinux.org>
-
Allan McRae authored
Signed-off-by: Allan McRae <allan@archlinux.org>
-
Allan McRae authored
Signed-off-by: Allan McRae <allan@archlinux.org>
-
Setting sysroot to / is not the same as having no sysroot, because the sysroot is prepended to ALL config paths including relative ones: $ cd /etc $ pacman --config=pacman.conf error: config file /pacman.conf could not be read: No such file or directory Signed-off-by: Andrew Gregory <andrew.gregory.8@gmail.com>
-
Allows sysroot to be left NULL. Signed-off-by: Andrew Gregory <andrew.gregory.8@gmail.com>
-
- Feb 28, 2024
-
-
Levente Polyak authored
We use an extended glob here, but were relying on having it globally set in makepkg. This causes it to fail when used in scripts. Since scripts using libmakepkg may not want extglob to be set, save and restore the environment while explicitly setting extglob only where we need it. Signed-off-by: Levente Polyak <anthraxx@archlinux.org>
-
- Feb 27, 2024
-
-
Allan McRae authored
Signed-off-by: Allan McRae <allan@archlinux.org>
-
- Feb 26, 2024
-
-
Allan McRae authored
Signed-off-by: Allan McRae <allan@archlinux.org>
-
Allan McRae authored
In pacman's progress callback, pkgname being null may result in a segfault, due to undefined printf behaviour. libalpm always passes at least an empty string for pkgname, so this situation is largely avoided. However, the callback mostly checked for pkgname's being non-null and not empty. This means a additional space was being added to the output messages (although with zero actual effect on the output). Be a bit more robust here by treating null and empty pkgname the same and fixing the invisible output issue... Signed-off-by: Allan McRae <allan@archlinux.org>
-
Allan McRae authored
Signed-off-by: Allan McRae <allan@archlinux.org>
-
Allan McRae authored
Signed-off-by: Allan McRae <allan@archlinux.org>
-
Allan McRae authored
A potential buffer overflow could occur if a detected terminal escape sequence was not for a terminal colour (i.e. did not contain an "m"). Fix the potential buffer overflow while explicitly detecting only terminal colour escape sequences. Any other escape sequence is unexpected, and just gets pushed to the terminal. Signed-off-by: Allan McRae <allan@archlinux.org>
-
Allan McRae authored
I'm not sure why this was originally included, but it has now become a problem with multiple processes updating the keyring (e.g. the systemd timer for WKD updates from Arch Linux). Signed-off-by: Allan McRae <allan@archlinux.org>
-
- Feb 24, 2024
-
-
Signed-off-by: Allan McRae <allan@archlinux.org>
-
Allan McRae authored
Adding more and more languages will make the man page become increasingly difficult to navigate. Move documentation into the configuration file where variables are defined. Signed-off-by: Allan McRae <allan@archlinux.org>
-
Allan McRae authored
Signed-off-by: Allan McRae <allan@archlinux.org>
-
- Feb 19, 2024
-
-
Allan McRae authored
Signed-off-by: Allan McRae <allan@archlinux.org>
-
- Feb 18, 2024
-
-
Allan McRae authored
Bailing early caused problems with makepkg failing on verify but expired signatures. As this is often out of the packagers control, and it is better to verify a signature than not, we try bailing as late as possible and let makepkg warn about the expired signature. Signed-off-by: Allan McRae <allan@archlinux.org>
-
The previous chroot-based sysroot often broke due to glibc's delayed loading for much of its functionality when the sysroot did not contain compatible copies of the necessary libraries. This approach instead manually prepends the sysroot to all configuration paths. BREAKING CHANGE: targets to -U are no longer interpreted relative to sysroot Signed-off-by: Andrew Gregory <andrew.gregory.8@gmail.com> Signed-off-by: Allan McRae <allan@archlinux.org>
-
- Feb 16, 2024
-
-
Ensure relevant signature files are downloaded when using the fetch callback. Signed-off-by: Allan McRae <allan@archlinux.org>
-
- Feb 15, 2024
-
-
Allan McRae authored
Guile 2.2 uses ELF format for its byte-compiled files. These are not normal executables, and are not strippable in the normal sense. Given these are ELF files and detected by "file" as non-stripped binaries, it is only possible to skip these using the file path. Fixes #73 Signed-off-by: Allan McRae <allan@archlinux.org>
-
Allan McRae authored
Also include a section encouraging discussion of large changes as there have been a number of case of rejected features being reinvented. Fixes #34 Signed-off-by: Allan McRae <allan@archlinux.org>
-
Allan McRae authored
We have added more options to makepkg, but adding them to the man page entry would result in line wrapping on a standard width terminal. Instead, trucate and add ellipsis to indicate more members (as described in the section below). Fixes #91 Signed-off-by: Allan McRae <allan@archlinux.org>
-
Allan McRae authored
Signed-off-by: Allan McRae <allan@archlinux.org>
-
-
-
-
-
-
- Feb 10, 2024
-
-
Signed-off-by: Allan McRae <allan@archlinux.org>
-
- Feb 09, 2024
-
-
Allan McRae authored
Return ALPM_PKG_REASON_UNKNOWN when parsing of %REASON% in the local database fails. Signed-off-by: Allan McRae <allan@archlinux.org>
-
atio's behaviour is undefined if the input is not valid. Also it does all sorts of whitespace and prefix handling which we don't need for pkgreason. Instead of going into UB on invalid input we now return EXPLICIT as the fallback and print an error. However we don't actually error out as the DB parsing tries to be error tolerant. Signed-off-by: Allan McRae <allan@archlinux.org>
-
- Feb 07, 2024
-
-
alpm has certain requirements for package metadata necessary for proper functioning, name and version in particular. These requirements are already enforced in makepkg, but nowhere in alpm. Exceptions are treated as errors for non-local packages because they cannot be installed without potentially resulting in undefined behavior. Exceptions for local packages are treated as warnings because they are already installed, so any damage has already been done, and the user would otherwise have no way to uninstall them. Signed-off-by: Andrew Gregory <andrew.gregory.8@gmail.com>
-
The error path uconditinally tries to free the archive, leading to a double-free segmentation fault if the error path is triggered after already freeing it. Signed-off-by: Andrew Gregory <andrew.gregory.8@gmail.com>
-
Cleanup was only being performed when libarchive failed to actually read the file. Signed-off-by: Andrew Gregory <andrew.gregory.8@gmail.com>
-
The free function was checking DB_STATUS_PKGCACHE, which is only set once the package cache has been fully built. Signed-off-by: Andrew Gregory <andrew.gregory.8@gmail.com>
-
- Feb 06, 2024
-
-
Allan McRae authored
Signed-off-by: Allan McRae <allan@archlinux.org>
-
- Feb 04, 2024
-
-
David Runge authored
To ensure we are not dropping the return code of the `gpg` call due to piping into `grep`, we make use of `PIPESTATUS` to check the return code of each command separately. Additionally, we can now distinguish between two states: The signature does not verify (e.g. due to technical reasons) and the signature is not trusted. Signed-off-by: David Runge <dvzrv@archlinux.org>
-