[pacman-dev] [GIT] The official pacman repository branch, master, updated. v5.0.0-19-gc034a33

[Allan McRae]

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  c034a3322b2a53fce51ffce144e36361892abeac (commit)
       via  a724235b6127f9655708614d1e44f9b5c661a506 (commit)
       via  1d6583a58da0904fb7feafd4a666391087955a7b (commit)
       via  ce1f453b74c8fd0966e1d11d3deeb1a777055fc5 (commit)
       via  2ee7a8d89ad693617307260604e1d58757fd2978 (commit)
      from  f63854fa96f658ca5bdf2c21a1cd33cf4e3fbdbd (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 c034a3322b2a53fce51ffce144e36361892abeac
Author: Evangelos Foutras <evangelos at foutrelis.com>
Date:   Wed Feb 17 09:11:38 2016 +0200

    makepkg: do not run prepare() with --noextract
    
    This is partial revert of 8454daa7feef (makepkg: run pkgver() and
    prepare() with --noextract).
    
    Reasoning for the reversion (copied from FS#43498):
    
        Running prepare() when --noextract is used no longer allows running
        'makepkg -o && makepkg -e' with any PKGBUILD that applies patches in
        prepare(). [1]
    
        Sure there's --noprepare which restores the old behavior, but that's
        a lot of extra typing for what I believe is a much more common use
        of --noextract.
    
        For OP's use case of doing git bisects, you can specify the commit
        in the source array and thus skip --noextract since makepkg will
        checkout the correct commit each time.
    
        [1] I often extract the sources using 'makepkg -o', manually edit
        some source files, and then use 'makepkg -e' to package it (while
        possibly repeating the edit/package steps).
    
    Signed-off-by: Allan McRae <allan at archlinux.org>

commit a724235b6127f9655708614d1e44f9b5c661a506
Author: Andrew Gregory <andrew.gregory.8 at gmail.com>
Date:   Mon Feb 22 14:07:57 2016 -0500

    make alpm_unlock and trans_interrupt async safe
    
    RET_ERR calls _alpm_log which includes calls that are not safe for use
    in asynchronous signal handlers (see signal(7)).  Replace it in
    functions called from our signal handlers with a new macro
    RET_ERR_ASYNC_SAFE which is identical except that it lacks the call to
    _alpm_log.
    
    Signed-off-by: Andrew Gregory <andrew.gregory.8 at gmail.com>

commit 1d6583a58da0904fb7feafd4a666391087955a7b
Author: Andrew Gregory <andrew.gregory.8 at gmail.com>
Date:   Sun Feb 21 21:46:38 2016 -0500

    alpm_run_chroot: always connect parent2child pipe
    
    Commit e374e6829cea3512f0b4a4069c5a6168f0f8d8a0 closed stdin before
    running scripts/hooks.  This left the exec'd process with no file
    descriptor 0.  If the process subsequently opened a file it would be
    assigned fd 0, and could potentially be confused for stdin.  Connecting
    and immediately closing the parent2child pipe ensures that the child has
    an fd 0 and that it is empty.
    
    Signed-off-by: Andrew Gregory <andrew.gregory.8 at gmail.com>
    Signed-off-by: Allan McRae <allan at archlinux.org>

commit ce1f453b74c8fd0966e1d11d3deeb1a777055fc5
Author: Andrew Gregory <andrew.gregory.8 at gmail.com>
Date:   Sun Feb 21 21:46:36 2016 -0500

    ensure gpgdir has a trailing slash
    
    init_gpgme checks for various paths under gpgdir by concatenating them
    directly, giving warning messages incorrectly if gpgdir does not end
    with '/'.
    
    Signed-off-by: Andrew Gregory <andrew.gregory.8 at gmail.com>
    Signed-off-by: Allan McRae <allan at archlinux.org>

commit 2ee7a8d89ad693617307260604e1d58757fd2978
Author: Andrew Gregory <andrew.gregory.8 at gmail.com>
Date:   Sun Feb 21 21:46:35 2016 -0500

    do not rely on localdb for hook matching
    
    Relying on localdb to determine which trigger operations should match is
    completely broken for PostTransaction hooks because the localdb has
    already been updated.  Store a copy of the old version of any packages
    being updated to use instead.
    
    Fixes FS#47996
    
    Signed-off-by: Andrew Gregory <andrew.gregory.8 at gmail.com>
    Signed-off-by: Allan McRae <allan at archlinux.org>

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

Summary of changes:
 doc/makepkg.8.txt                                          | 10 +++++-----
 lib/libalpm/add.c                                          | 14 +++-----------
 lib/libalpm/handle.c                                       | 14 ++++----------
 lib/libalpm/hook.c                                         |  4 ++--
 lib/libalpm/package.c                                      |  3 +++
 lib/libalpm/package.h                                      |  1 +
 lib/libalpm/sync.c                                         |  8 ++++++++
 lib/libalpm/trans.c                                        |  8 +++++---
 lib/libalpm/util.c                                         | 13 ++++++-------
 lib/libalpm/util.h                                         |  4 ++++
 scripts/makepkg.sh.in                                      |  6 +++---
 test/pacman/tests/TESTS                                    |  1 +
 ...gger-match.py => hook-pkg-postinstall-trigger-match.py} |  4 ++--
 13 files changed, 47 insertions(+), 43 deletions(-)
 copy test/pacman/tests/{hook-pkg-install-trigger-match.py => hook-pkg-postinstall-trigger-match.py} (78%)


hooks/post-receive
-- 
The official pacman repository