[pacman-dev] [GIT] The official pacman repository branch, master, updated. v5.2.1-42-gd0c487d4
Allan McRae
allan at archlinux.org
Tue Jan 28 00:47:08 UTC 2020
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "The official pacman repository".
The branch, master has been updated
via d0c487d4dcc6fec6f4bd8e1cefa1de9ffbe0e460 (commit)
via 0a25548cd0910f66dea2dfab21f75a6d15366d64 (commit)
via 21af79860403f9120d2c0412a95ec97d06368e11 (commit)
via c3852ff42569542b787d9e49289f5358ad22f900 (commit)
via e54617c7d554e0c14c039432b5f7bef66e43769c (commit)
via d626a17ef94d79975ff17d04250152ea46aaade3 (commit)
via 2856a7dea3c0d4584e126b5ca5957e13e23f83d1 (commit)
via 2e32d51a262fef398a94a17c0a0d4ff3233990b5 (commit)
via 75bf8e887cd9fe0f6ba1eb2b6554dbfbcda0294a (commit)
via 0965023fc57495ca819127eee1d7e881e1ed7c3c (commit)
from acaed30e243ff139b5549fd51dc3cb5472415b0a (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit d0c487d4dcc6fec6f4bd8e1cefa1de9ffbe0e460
Author: morganamilo <morganamilo at archlinux.org>
Date: Sun Jan 26 07:01:42 2020 +0000
Docs docs docs
libalpm: move docs from .c files into alpm.h And fix/expand some
along the way.
Signed-off-by: Allan McRae <allan at archlinux.org>
commit 0a25548cd0910f66dea2dfab21f75a6d15366d64
Author: morganamilo <morganamilo at archlinux.org>
Date: Thu Jan 23 06:38:35 2020 +0000
libalpm: fix alpm_option_set_assumeinstalled
It looks like this function has never actually worked. The current list
is never set to NULL after being freed. So the new deps were just
appended to the already freed list, leading to a segfault.
Signed-off-by: Allan McRae <allan at archlinux.org>
commit 21af79860403f9120d2c0412a95ec97d06368e11
Author: Allan McRae <allan at archlinux.org>
Date: Thu Jan 23 12:14:14 2020 +1000
makepkg: add CRC checksums and set these to be the default
Checksums arrays should be filled with values provided by upstream. We
currently have md5 set as an unsecure default, and are constantly asked to
change it to sha2. However, just changing the default to a stronger checksum
gives the user the impression that "makepkg -g" checksums are perfect.
Instead, change the default checksum to a CRC, to make it clear that any
checksum generated purely by "makepkg -g" is not ideal.
Signed-off-by: Allan McRae <allan at archlinux.org>
commit c3852ff42569542b787d9e49289f5358ad22f900
Author: Allan McRae <allan at archlinux.org>
Date: Thu Jan 23 12:04:28 2020 +1000
Note that checksums from "makepkg -g" are not ideal
Generating checksums with "makepkg -g" only determines that the user of a
PKGBUILD has the same file as the packager (assuming no collision). This
means an upstream source could be maliciously changed and passed on as valid
by a PKGBUILD. To avoid this, it is essential that any checksums used in
a PKGBUILD are as provided by upstream.
Signed-off-by: Allan McRae <allan at archlinux.org>
commit e54617c7d554e0c14c039432b5f7bef66e43769c
Author: Allan McRae <allan at archlinux.org>
Date: Thu Jan 23 10:47:02 2020 +1000
Fix "pacman -U <url>" operations
Commit e6a6d307 detected complete part files by comparing a payload's
max_size to initial_size. However, these values are also equal when we
use pacman -U on a URL as max_size is set to 0 in that case. Add a further
condition to avoid that.
Signed-off-by: Allan McRae <allan at archlinux.org>
commit d626a17ef94d79975ff17d04250152ea46aaade3
Author: Eli Schwartz <eschwartz at archlinux.org>
Date: Thu Jan 16 12:27:34 2020 -0500
makepkg: make per-package files containing '$pkgname' consistently work
Extracting function variables containing arbitrarily scoped variables of
arbitrary nature is a disaster, but let's at least cover the common case
of using the actual '$pkgname' in an install/changelog file. It's the
odd case of actually being basically justified use of disambiguating
between the same variable used in multiple different split packages...
and also, --printsrcinfo already uses and overwrites the variable
'pkgname' in pkgbuild_extract_to_srcinfo, so this "works" in .SRCINFO
but doesn't work in .src.tar.gz
It doesn't work in lint_pkgbuild either, but in that case the problem is
being too permissive, not too restrictive -- we might end up checking
the same file twice, and printing that it is missing twice.
Fixes FS#64932
Signed-off-by: Eli Schwartz <eschwartz at archlinux.org>
Signed-off-by: Allan McRae <allan at archlinux.org>
commit 2856a7dea3c0d4584e126b5ca5957e13e23f83d1
Author: Allan McRae <allan at archlinux.org>
Date: Sun Jan 19 09:30:54 2020 +1000
Increase maximum database size
We previously has the maximum database size as 25MB. This was set in the days
before repos had as many packages as they do now, and before we started
distributing files databases. Increase this limit to 128MB.
Signed-off-by: Allan McRae <allan at archlinux.org>
commit 2e32d51a262fef398a94a17c0a0d4ff3233990b5
Author: Allan McRae <allan at archlinux.org>
Date: Thu Jan 16 21:20:19 2020 +1000
Remove unneeded ltmain patch
Many moons ago, libtool was bad - I mean worse than today! It gobbled all
--as-needed and we ended up with an overlinked libalpm. This was annoying,
particularly when dealing with soname bumps in libraries pacman/libalpm had
no business linking to. Luckily we had a fix, stolen from GNOME I believe.
And with that fix, we lived in harmony with libtool for many years. Until one
day, unbeknownst to us, libtool was "fixed". We kept applying our patch,
because it still applied, but it did worse than nothing. It gobbled up our
other LDFLAGS, and our libalpm started missing out on RELRO and BIND_NOW.
This made the Arch Security Team unhappy. We will make them happy again by
stopping the patch.
Signed-off-by: Allan McRae <allan at archlinux.org>
commit 75bf8e887cd9fe0f6ba1eb2b6554dbfbcda0294a
Author: Allan McRae <allan at archlinux.org>
Date: Thu Jan 16 16:58:50 2020 +1000
Increase meson test timeout
Running the testsuite using "PACTEST_VALGRIND=1 ninja test -C build", I ran
into the following failure:
161/332 smoke001.py TIMEOUT 30.02 s
I figure an i7 @ 3.10GHz should be enough to run our testsuite... so boost
the meson test timeout to 120 seconds (which should be enough time for
anyone...).
Signed-off-by: Allan McRae <allan at archlinux.org>
commit 0965023fc57495ca819127eee1d7e881e1ed7c3c
Author: Allan McRae <allan at archlinux.org>
Date: Wed Jan 8 13:46:35 2020 +1000
tests: Fix typo in test description
-----------------------------------------------------------------------
Summary of changes:
autogen.sh | 6 -
build-aux/ltmain-asneeded.patch | 33 ---
doc/PKGBUILD.5.asciidoc | 16 +-
doc/makepkg.conf.5.asciidoc | 2 +-
etc/makepkg.conf.in | 4 +-
lib/libalpm/add.c | 1 -
lib/libalpm/alpm.c | 33 ---
lib/libalpm/alpm.h | 247 ++++++++++++++++++++-
lib/libalpm/be_sync.c | 39 +---
lib/libalpm/conflict.c | 14 --
lib/libalpm/db.c | 34 ---
lib/libalpm/deps.c | 32 ---
lib/libalpm/dload.c | 3 +-
lib/libalpm/handle.c | 7 +-
lib/libalpm/log.c | 13 --
lib/libalpm/package.c | 28 ---
lib/libalpm/remove.c | 8 -
lib/libalpm/signing.c | 34 ---
lib/libalpm/sync.c | 17 --
lib/libalpm/trans.c | 12 -
lib/libalpm/util.c | 10 -
lib/libalpm/version.c | 14 --
scripts/libmakepkg/lint_pkgbuild/changelog.sh.in | 10 +-
scripts/libmakepkg/lint_pkgbuild/install.sh.in | 10 +-
scripts/libmakepkg/util/schema.sh.in | 2 +-
scripts/makepkg.sh.in | 14 +-
test/pacman/meson.build | 1 +
...nc-update-package-removing-required-provides.py | 2 +-
28 files changed, 283 insertions(+), 363 deletions(-)
delete mode 100755 autogen.sh
delete mode 100644 build-aux/ltmain-asneeded.patch
hooks/post-receive
--
The official pacman repository
More information about the pacman-dev
mailing list