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 96b3ba3470f11842312e4fdb34b74b391842fc33 (commit) via 2141b7112d237221280781bed2b2bb6efadc963e (commit) via 2f96067fe71e796e9da378620ad16a9f94a7b8ac (commit) via 5ba8b83b8be55b9d7a55cc8bfdef80c37117101d (commit) via cb898be887160e1e14ff0f1e3a3e506fc796ef57 (commit) via 80868b0da696d16c2fdc527cdb6f7fa2c0973044 (commit) via 6a9ed330551e585ce887a2bb53fb022b1c92da31 (commit) via 507a2d15e65aba93a20ee99d90345917866407dc (commit) via b8ef22312b4e5fb6b44b39c290303b2b77a68ea9 (commit) via 2752932d1966488c5bcc0c45282b0de5c8bf561e (commit) from 919b604c29060b3b14162ef331dfccc018606919 (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 96b3ba3470f11842312e4fdb34b74b391842fc33 Merge: 2141b71 507a2d1 Author: Dan McGee <dan@archlinux.org> Date: Sun Nov 20 21:40:50 2011 -0600 Merge branch 'maint' commit 2141b7112d237221280781bed2b2bb6efadc963e Author: Florian Pritz <bluewind@xinu.at> Date: Thu Oct 20 20:39:28 2011 +0200 add key algo to import msg Signed-off-by: Florian Pritz <bluewind@xinu.at> Signed-off-by: Dan McGee <dan@archlinux.org> commit 2f96067fe71e796e9da378620ad16a9f94a7b8ac Author: Florian Pritz <bluewind@xinu.at> Date: Tue Oct 18 22:46:50 2011 +0200 change gpg import message to resemble gpg --list-keys Dan: const pointers, don't worry about bitfields. Signed-off-by: Florian Pritz <bluewind@xinu.at> Signed-off-by: Dan McGee <dan@archlinux.org> commit 5ba8b83b8be55b9d7a55cc8bfdef80c37117101d Author: Phillip Smith <fukawi2@gmail.com> Date: Tue Nov 1 12:00:47 2011 +1100 makepkg: add support for PACKAGER environment var Add support for overriding configuration in /etc/makepkg.conf and ~/.makepkg.conf by setting the environment variable PACKAGER similar to how SRCDEST and PKGDEST behave. Signed-off-by: Allan McRae <allan@archlinux.org> commit cb898be887160e1e14ff0f1e3a3e506fc796ef57 Author: Allan McRae <allan@archlinux.org> Date: Sun Nov 20 13:46:24 2011 +1000 repo-add: Remove .tmp. prefix from output Signed-off-by: Allan McRae <allan@archlinux.org> commit 80868b0da696d16c2fdc527cdb6f7fa2c0973044 Author: Dan McGee <dan@archlinux.org> Date: Tue Nov 15 22:16:42 2011 -0600 repo-add: ensure database and signature files are always viewed in whole This addresses a short but sweet race condition currently existing in repo-add and repo-remove. We do the smart thing and zip the database to a location in a temporary directory and not over the original database directly. However, we then proceed to move this file directly from the temporary directory to our final location, which is more than likely a cross-filesystem move (/tmp on tmpfs) and thus non-atomic. Instead, zip the file to the same directory, prefixing the filename with '.tmp.'. We then move the file into place. This move is guaranteed to be atomic, so any reader of the database file will get either the old version, the new version, or ENOENT. We also perform a hardlink if possible instead of a move when shifting the old database out of the way to '.old'; this ensures there is no chance of a database file not existing during the whole process. Only one small race condition should now be present- when the database has been fully moved into place and the signature has not, you may see a mismatch. There seems to be no good way to address this, and it existed before this patch. A final note- if someone had locked-down permissions on the directory that the database files are in (e.g., could only write to foo.db.tar.gz, foo.db, foo.db.tar.gz.old, foo.db.old, and the lock file), this would break. Signed-off-by: Dan McGee <dan@archlinux.org> commit 6a9ed330551e585ce887a2bb53fb022b1c92da31 Author: Dan McGee <dan@archlinux.org> Date: Tue Nov 15 22:16:41 2011 -0600 repo-add: ensure path to LOCKFILE is always absolute Given our semi-frequent use of pushd/popd, if we are in any directory but the original and the database path given was relative, we won't unlock the database file when cleaning up after an error. Signed-off-by: Dan McGee <dan@archlinux.org> commit 2752932d1966488c5bcc0c45282b0de5c8bf561e Author: Dan McGee <dan@archlinux.org> Date: Wed Nov 16 14:53:34 2011 -0600 Update alpm_errno_t type to non-enum version Signed-off-by: Dan McGee <dan@archlinux.org> ----------------------------------------------------------------------- Summary of changes: NEWS | 10 ++++++-- doc/makepkg.8.txt | 4 +++ lib/libalpm/alpm.h | 3 ++ lib/libalpm/signing.c | 22 +++++++++++++++++++ lib/libalpm/sync.c | 2 +- scripts/makepkg.sh.in | 8 ++++-- scripts/po/Makevars | 4 +-- scripts/repo-add.sh.in | 55 +++++++++++++++++++++++++++++------------------ src/pacman/callback.c | 10 +++++++- src/pacman/po/zh_TW.po | 3 +- 10 files changed, 87 insertions(+), 34 deletions(-) hooks/post-receive -- The official pacman repository