[pacman-dev] [GIT] The official pacman repository branch, master, updated. v5.1.1-158-g9f5412d8

Tue Mar 19 04:35:44 UTC 2019

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  9f5412d809a50a7ad18013222582d5b943216ae1 (commit)
       via  7b15918b6526b52823b869050e430b24b30c3ca1 (commit)
       via  ee5f24e50ca5792d37cfbdcbb134fb58777d3eb8 (commit)
       via  35a0d5e744d1c3f93d4f4f79b2ca2e3e411fdd5a (commit)
       via  0a72874734ceafdf0a9f9e7a96c8b3f88507a54b (commit)
       via  226d2c124884c7318b7fb86c2e6bdf792eddd1a9 (commit)
       via  bbfb75fd292e3f2818cdc0eae68c292bb3fbc50b (commit)
       via  f26cb61cb6a16c8ce85f33e6090763aced0118c3 (commit)
       via  c61cd050f9b6475ea128a1da02e88b284ac509b5 (commit)
      from  c0e9be7973be6c81b22fde91516fb8991e7bb07b (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 9f5412d809a50a7ad18013222582d5b943216ae1
Author: Eli Schwartz <eschwartz at archlinux.org>
Date:   Tue Mar 12 13:01:13 2019 -0400

    doc: generalize description of the bash nature of PKGBUILD functions

    Currently this is scoped to the build() function, which is simply wrong
    as it equally applies to any function. Simply moving the paragraphs up
    to the main manpage section makes this clear.

    Signed-off-by: Eli Schwartz <eschwartz at archlinux.org>
    Signed-off-by: Allan McRae <allan at archlinux.org>

commit 7b15918b6526b52823b869050e430b24b30c3ca1
Author: Que Quotion <quequotion at gmail.com>
Date:   Wed Mar 13 01:01:43 2019 +0900

    Clarify that build_options only apply during build()

    Signed-off-by: Que Quotion <quequotion at gmail.com>
    Signed-off-by: Allan McRae <allan at archlinux.org>

commit ee5f24e50ca5792d37cfbdcbb134fb58777d3eb8
Author: Eli Schwartz <eschwartz at archlinux.org>
Date:   Tue Mar 12 13:28:27 2019 -0400

    libmakepkg: fix reporting of invalid archive extensions in compress.sh

    In commit 1825bd6716c2a51c92642e8b96beac0101e83805 this was split out
    from makepkg, but the warning was not properly migrated; $ext did not
    ever exist.

    As a result, no matter what you did, the only possible warning was:

    ==> WARNING: '' is not a valid archive extension.

    Fix to filter based on the presence of .tar in the argument, and
    building the $ext variable for all checking and messaging purposes
    within the function.

    Signed-off-by: Eli Schwartz <eschwartz at archlinux.org>
    Signed-off-by: Allan McRae <allan at archlinux.org>

commit 35a0d5e744d1c3f93d4f4f79b2ca2e3e411fdd5a
Author: Eli Schwartz <eschwartz at archlinux.org>
Date:   Thu Mar 7 23:18:23 2019 -0500

    makepkg: use "shared" git clones when checking out sources

    In order to cache sources offline, makepkg creates *two* copies of every
    git repo. This is a useful tradeoff for network time, but comes at the
    cost of increased disk space.

    Normally, git can smooth this over automagically. Whenever possible, git
    objects are hardlinked to save space, but this does not work when
    SRCDEST and BUILDDIR are on separate filesystems.

    When the repo in question is both very large (linux.git for example is
    2.2 GB) and crosses filesystem boundaries, this results in a lot of
    extra disk space being used; the most likely scenario is where BUILDDIR
    is a tmpfs for bonus ouch.

    git(1) has a builtin feature which serves this case handily: the
    --shared flag will create the info/alternates file instructing git to
    not copy or hardlink or create objects/packs at all, but merely look for
    them in an external location (that being the source of the clone).

    The downside of using shared clones, is that if you modify and drop
    commits from the original repo, or simply delete the whole repo
    altogether, you break the copy. But we don't care about that here,
    because

    1) the BUILDDIR copy is meant to be a temporary copy strictly derived
       via PKGBUILD syntax from the SRCDEST, and must be able to be
       recreated at any time,
    2) if the SRCDEST disappears, makepkg will redownload it, thus restoring
       the objects needed by the BUILDDIR clone,
    3) if the user does non-default things like hacking on the BUILDDIR copy
       then deleting and re-cloning the SRCDEST may result in momentary
       breakage, but ultimately should be fine -- the unique objects they
       created will be stored in the BUILDDIR copy.

    While it's theoretically possible that upstream will force-push to
    overwrite the base tree from which makepkg is building (which they
    should not do), *and* the user deleted their SRCDEST which they should
    not do, *and* they saved work in makepkg's working directory which they
    should not do either...
    ... this is an unlikely chain of events for which we should not care.

    Using --shared is therefore helpful in immediately useful ways and IMHO
    has no actual downsides; we should use it.

    An alternative implementation would be to use worktrees. I've rejected
    this since it is essentially the same as shared clones, except adding
    additional restrictions on the branch namespace, and could potentially
    break existing use cases such as manually handling the SRCDEST in order
    to share repositories with normal working copies.

    Signed-off-by: Eli Schwartz <eschwartz at archlinux.org>
    Signed-off-by: Allan McRae <allan at archlinux.org>

commit 0a72874734ceafdf0a9f9e7a96c8b3f88507a54b
Author: Eli Schwartz <eschwartz at archlinux.org>
Date:   Thu Mar 7 23:10:38 2019 -0500

    build: check for gpgme with pkg-config before gpgme-config

    gpgme in git master now supports pkg-config and with the next release we
    can and should prefer its use. However, retain the legacy code that
    enables building with older versions of gpgme, as a fallback.

    Signed-off-by: Eli Schwartz <eschwartz at archlinux.org>
    Signed-off-by: Allan McRae <allan at archlinux.org>

commit 226d2c124884c7318b7fb86c2e6bdf792eddd1a9
Author: Santiago Torres <santiago at archlinux.org>
Date:   Mon Mar 11 21:18:16 2019 -0400

    drop DU* config variables

    Since DUFLAGS and DUPATH are not needed anymore remove them from the
    source

    Signed-off-by: Santiago Torres <santiago at archlinux.org>
    Signed-off-by: Allan McRae <allan at archlinux.org>

commit bbfb75fd292e3f2818cdc0eae68c292bb3fbc50b
Author: Eli Schwartz <eschwartz at archlinux.org>
Date:   Thu Mar 7 22:07:55 2019 -0500

    build: remove references to variable replacements from pacman-optimize

    MODECMD and OWNERCMD are not used by pacman itself, so we don't need to
    check for and replace them now that pacman-optimize is removed.

    Signed-off-by: Eli Schwartz <eschwartz at archlinux.org>
    Signed-off-by: Allan McRae <allan at archlinux.org>

commit f26cb61cb6a16c8ce85f33e6090763aced0118c3
Author: Santiago Torres <santiago at archlinux.org>
Date:   Mon Mar 11 22:24:35 2019 -0400

    Make makepkg compute sizes properly

    Makepkg used to use du --apparent-size to compute the size of the
    package. Unfortunately, this would result in different sizes depending
    on the filesystem used (e.g., btrfs vs ext4), which would affect
    reproducible builds. Use a wc-based approach to compute sizes

    Signed-off-by: Santiago Torres <santiago at archlinux.org>
    Signed-off-by: Allan McRae <allan at archlinux.org>

commit c61cd050f9b6475ea128a1da02e88b284ac509b5
Author: Florian Wehner <florian at whnr.de>
Date:   Thu Mar 7 20:14:55 2019 -0500

    Reformatting log timestamp to include time-zone

    The time logged is currently given as localtime without any timezone
    information. This is confusing in various scenarios.

    Examples:
    * If one is travelling across time-zones and the timestamps in the log
    appear out of order.
    * Comparing dates with `datediff` gives an offset by the time-zone

    This patch would reformat the time-stamp to a full ISO-8601 version.
    It includes the 'T' separating date and time including seconds.

    Old: [2019-03-04 16:15]
    New: [2019-03-04T16:15:45-05:00]

    Signed-off-by: Florian Wehner <florian at whnr.de>
    Signed-off-by: Allan McRae <allan at archlinux.org>

-----------------------------------------------------------------------

Summary of changes:
 build-aux/edit-script.sh.in            |  4 --
 configure.ac                           | 88 ++++++++++++++--------------------
 doc/PKGBUILD.5.asciidoc                | 25 +++++-----
 lib/libalpm/libalpm.pc.in              |  4 +-
 lib/libalpm/log.c                      |  8 ++--
 meson.build                            | 70 +++++++++++----------------
 meson_options.txt                      |  3 --
 scripts/Makefile.am                    |  4 --
 scripts/libmakepkg/source/git.sh.in    |  2 +-
 scripts/libmakepkg/util/compress.sh.in | 26 +++++-----
 scripts/makepkg.sh.in                  |  3 +-
 11 files changed, 99 insertions(+), 138 deletions(-)

hooks/post-receive
-- 
The official pacman repository