- Pacman-dev - lists.archlinux.org

[pacman-dev] [PATCH] Always use proper error code in alpm_initialize.
by Tobias Stoeckmann 06 Jun '16

06 Jun '16

In out of memory conditions, an undefined error value is written into *err, because myerr is never explicitly set in these cases. I have also converted a calloc into a MALLOC call, because the memory will be properly filled by the snprintf call right after it. Signed-off-by: Tobias Stoeckmann <tobias(a)stoeckmann.org> --- lib/libalpm/alpm.c | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/lib/libalpm/alpm.c b/lib/libalpm/alpm.c index 6f02913..6b7fa7a 100644 --- a/lib/libalpm/alpm.c +++ b/lib/libalpm/alpm.c @@ -55,8 +55,7 @@ alpm_handle_t SYMEXPORT *alpm_initialize(const char *root, const char *dbpath, alpm_handle_t *myhandle = _alpm_handle_new(); if(myhandle == NULL) { - myerr = ALPM_ERR_MEMORY; - goto cleanup; + goto nomem; } if((myerr = _alpm_set_directory_option(root, &(myhandle->root), 1))) { goto cleanup; @@ -68,15 +67,15 @@ alpm_handle_t SYMEXPORT *alpm_initialize(const char *root, const char *dbpath, /* to contatenate myhandle->root (ends with a slash) with SYSHOOKDIR (starts * with a slash) correctly, we skip SYSHOOKDIR[0]; the regular +1 therefore * disappears from the allocation */ - MALLOC(hookdir, strlen(myhandle->root) + strlen(SYSHOOKDIR), goto cleanup); + MALLOC(hookdir, strlen(myhandle->root) + strlen(SYSHOOKDIR), goto nomem); sprintf(hookdir, "%s%s", myhandle->root, SYSHOOKDIR + 1); myhandle->hookdirs = alpm_list_add(NULL, hookdir); /* set default database extension */ - STRDUP(myhandle->dbext, ".db", goto cleanup); + STRDUP(myhandle->dbext, ".db", goto nomem); lockfilelen = strlen(myhandle->dbpath) + strlen(lf) + 1; - myhandle->lockfile = calloc(lockfilelen, sizeof(char)); + MALLOC(myhandle->lockfile, lockfilelen, goto nomem); snprintf(myhandle->lockfile, lockfilelen, "%s%s", myhandle->dbpath, lf); if(_alpm_db_register_local(myhandle) == NULL) { @@ -90,9 +89,11 @@ alpm_handle_t SYMEXPORT *alpm_initialize(const char *root, const char *dbpath, return myhandle; +nomem: + myerr = ALPM_ERR_MEMORY; cleanup: _alpm_handle_free(myhandle); - if(err && myerr) { + if(err) { *err = myerr; } return NULL; -- 2.8.3

2 1

[pacman-dev] [PATCH] recursedeps: include cyclic dependencies
by Andrew Gregory 04 Jun '16

04 Jun '16

Cyclic dependencies (A depends on B, B depends on A) were not selected because neither package could be removed individually, so can_remove_package would always return false for both. By preselecting all dependencies then filtering back out any dependencies still required by any packages that will not be uninstalled, groups of unneeded cyclic dependencies can be found. Fixes FS#41031 Signed-off-by: Andrew Gregory <andrew.gregory.8(a)gmail.com> --- lib/libalpm/deps.c | 104 ++++++++++++++-------------- test/pacman/tests/TESTS | 1 + test/pacman/tests/remove-recursive-cycle.py | 41 +++++++++++ 3 files changed, 94 insertions(+), 52 deletions(-) create mode 100644 test/pacman/tests/remove-recursive-cycle.py diff --git a/lib/libalpm/deps.c b/lib/libalpm/deps.c index c35a275..ae5d60b 100644 --- a/lib/libalpm/deps.c +++ b/lib/libalpm/deps.c @@ -551,44 +551,29 @@ error: return NULL; } -/* These parameters are messy. We check if this package, given a list of - * targets and a db is safe to remove. We do NOT remove it if it is in the - * target list, or if the package was explicitly installed and - * include_explicit == 0 */ -static int can_remove_package(alpm_db_t *db, alpm_pkg_t *pkg, - alpm_list_t *targets, int include_explicit) +/** Move package dependencies from one list to another + * @param from list to scan for dependencies + * @param to list to add dependencies to + * @param pkg package whose dependencies are moved + * @param explicit if 0, explicitly installed packages are not moved + */ +static void _alpm_select_depends(alpm_list_t **from, alpm_list_t **to, + alpm_pkg_t *pkg, int explicit) { - alpm_list_t *i; - - if(alpm_pkg_find(targets, pkg->name)) { - return 0; - } - - if(!include_explicit) { - /* see if it was explicitly installed */ - if(alpm_pkg_get_reason(pkg) == ALPM_PKG_REASON_EXPLICIT) { - _alpm_log(db->handle, ALPM_LOG_DEBUG, - "excluding %s -- explicitly installed\n", pkg->name); - return 0; + alpm_list_t *i, *next; + if(!alpm_pkg_get_depends(pkg)) { + return; + } + for(i = *from; i; i = next) { + alpm_pkg_t *deppkg = i->data; + next = i->next; + if((explicit || alpm_pkg_get_reason(deppkg) != ALPM_PKG_REASON_EXPLICIT) + && _alpm_pkg_depends_on(pkg, deppkg)) { + *to = alpm_list_add(*to, deppkg); + *from = alpm_list_remove_item(*from, i); + free(i); } } - - /* TODO: checkdeps could be used here, it handles multiple providers - * better, but that also makes it slower. - * Also this would require to first add the package to the targets list, - * then call checkdeps with it, then remove the package from the targets list - * if checkdeps detected it would break something */ - - /* see if other packages need it */ - for(i = _alpm_db_get_pkgcache(db); i; i = i->next) { - alpm_pkg_t *lpkg = i->data; - if(_alpm_pkg_depends_on(lpkg, pkg) && !alpm_pkg_find(targets, lpkg->name)) { - return 0; - } - } - - /* it's ok to remove */ - return 1; } /** @@ -604,31 +589,46 @@ static int can_remove_package(alpm_db_t *db, alpm_pkg_t *pkg, */ int _alpm_recursedeps(alpm_db_t *db, alpm_list_t **targs, int include_explicit) { - alpm_list_t *i, *j; + alpm_list_t *i, *keep, *rem = NULL; if(db == NULL || targs == NULL) { return -1; } + keep = alpm_list_copy(_alpm_db_get_pkgcache(db)); for(i = *targs; i; i = i->next) { - alpm_pkg_t *pkg = i->data; - for(j = _alpm_db_get_pkgcache(db); j; j = j->next) { - alpm_pkg_t *deppkg = j->data; - if(_alpm_pkg_depends_on(pkg, deppkg) - && can_remove_package(db, deppkg, *targs, include_explicit)) { - alpm_pkg_t *copy = NULL; - _alpm_log(db->handle, ALPM_LOG_DEBUG, "adding '%s' to the targets\n", - deppkg->name); - /* add it to the target list */ - if(_alpm_pkg_dup(deppkg, &copy)) { - /* we return memory on "non-fatal" error in _alpm_pkg_dup */ - _alpm_pkg_free(copy); - return -1; - } - *targs = alpm_list_add(*targs, copy); - } + keep = alpm_list_remove(keep, i->data, _alpm_pkg_cmp, NULL); + } + + /* recursively select all dependencies for removal */ + for(i = *targs; i; i = i->next) { + _alpm_select_depends(&keep, &rem, i->data, include_explicit); + } + for(i = rem; i; i = i->next) { + _alpm_select_depends(&keep, &rem, i->data, include_explicit); + } + + /* recursively select any still needed packages to keep */ + for(i = keep; i && rem; i = i->next) { + _alpm_select_depends(&rem, &keep, i->data, 1); + } + alpm_list_free(keep); + + /* copy selected packages into the target list */ + for(i = rem; i; i = i->next) { + alpm_pkg_t *pkg = i->data, *copy = NULL; + _alpm_log(db->handle, ALPM_LOG_DEBUG, + "adding '%s' to the targets\n", pkg->name); + if(_alpm_pkg_dup(pkg, &copy)) { + /* we return memory on "non-fatal" error in _alpm_pkg_dup */ + _alpm_pkg_free(copy); + alpm_list_free(rem); + return -1; } + *targs = alpm_list_add(*targs, copy); } + alpm_list_free(rem); + return 0; } diff --git a/test/pacman/tests/TESTS b/test/pacman/tests/TESTS index 62d1f2a..bd5a0b6 100644 --- a/test/pacman/tests/TESTS +++ b/test/pacman/tests/TESTS @@ -109,6 +109,7 @@ TESTS += test/pacman/tests/querycheck002.py TESTS += test/pacman/tests/querycheck_fast_file_type.py TESTS += test/pacman/tests/reason001.py TESTS += test/pacman/tests/remove-assumeinstalled.py +TESTS += test/pacman/tests/remove-recursive-cycle.py TESTS += test/pacman/tests/remove001.py TESTS += test/pacman/tests/remove002.py TESTS += test/pacman/tests/remove010.py diff --git a/test/pacman/tests/remove-recursive-cycle.py b/test/pacman/tests/remove-recursive-cycle.py new file mode 100644 index 0000000..b9864c8 --- /dev/null +++ b/test/pacman/tests/remove-recursive-cycle.py @@ -0,0 +1,41 @@ +self.description = "Recursively remove a package with cyclical dependencies" + +lpkg1 = pmpkg('pkg1') +self.addpkg2db('local', lpkg1) +lpkg1.depends = [ 'dep1' ] + +lpkg2 = pmpkg('pkg2') +self.addpkg2db('local', lpkg2) +lpkg2.depends = [ 'dep3' ] + +# cyclic dependency 1 +ldep1 = pmpkg('dep1') +self.addpkg2db('local', ldep1) +ldep1.depends = [ 'dep2', 'dep3', 'dep4' ] +ldep1.reason = 1 + +# cyclic dependency 2 +ldep2 = pmpkg('dep2') +self.addpkg2db('local', ldep2) +ldep2.depends = [ 'dep1' ] +ldep2.reason = 1 + +# dependency required by another package +ldep3 = pmpkg('dep3') +self.addpkg2db('local', ldep3) +ldep3.reason = 1 + +# explicitly installed dependency +ldep4 = pmpkg('dep4') +self.addpkg2db('local', ldep4) +ldep4.reason = 0 + +self.args = "-Rs pkg1" + +self.addrule("PACMAN_RETCODE=0") +self.addrule("PKG_EXIST=pkg2") +self.addrule("PKG_EXIST=dep3") +self.addrule("PKG_EXIST=dep4") +self.addrule("!PKG_EXIST=pkg1") +self.addrule("!PKG_EXIST=dep1") +self.addrule("!PKG_EXIST=dep2") -- 2.8.2

2 1

[pacman-dev] [PATCH] Turn off colours onces finished using them
by Allan McRae 04 Jun '16

04 Jun '16

The colour of the package version could leak onto the next line in both -Qo and -Fo. Signed-off-by: Allan McRae <allan(a)archlinux.org> --- src/pacman/files.c | 4 ++-- src/pacman/query.c | 5 +++-- 2 files changed, 5 insertions(+), 4 deletions(-) diff --git a/src/pacman/files.c b/src/pacman/files.c index 692fcd5..f5cba5b 100644 --- a/src/pacman/files.c +++ b/src/pacman/files.c @@ -78,10 +78,10 @@ static int files_fileowner(alpm_list_t *syncs, alpm_list_t *targets) { print_line_machinereadable(repo, pkg, filename); } else if(!config->quiet) { const colstr_t *colstr = &config->colstr; - printf(_("%s is owned by %s%s/%s%s %s%s\n"), filename, + printf(_("%s is owned by %s%s/%s%s %s%s%s\n"), filename, colstr->repo, alpm_db_get_name(repo), colstr->title, alpm_pkg_get_name(pkg), colstr->version, - alpm_pkg_get_version(pkg)); + alpm_pkg_get_version(pkg), colstr->nocolor); } else { printf("%s/%s\n", alpm_db_get_name(repo), alpm_pkg_get_name(pkg)); } diff --git a/src/pacman/query.c b/src/pacman/query.c index 522212d..a8f4e67 100644 --- a/src/pacman/query.c +++ b/src/pacman/query.c @@ -84,8 +84,9 @@ static void print_query_fileowner(const char *filename, alpm_pkg_t *info) { if(!config->quiet) { const colstr_t *colstr = &config->colstr; - printf(_("%s is owned by %s%s %s%s\n"), filename, colstr->title, - alpm_pkg_get_name(info), colstr->version, alpm_pkg_get_version(info)); + printf(_("%s is owned by %s%s %s%s%s\n"), filename, colstr->title, + alpm_pkg_get_name(info), colstr->version, alpm_pkg_get_version(info), + colstr->nocolor); } else { printf("%s\n", alpm_pkg_get_name(info)); } -- 2.8.3

1 0

[pacman-dev] A WIP fix for removing unneeded dependency cycles
by Ashley Whetter 21 May '16

21 May '16

This is a work in progress patchset. DO NOT MERGE! I've been looking at a fix for FS#41031 [1]. What I've attempted to do in this prototype is to fix the issue without needing to calculate the strongly connected components of the dependency graph to see if I could improve on run time performance or memory consumption. The way this works is I first perform depth-first cycle detection on the graph. When a cycle is detected the list of packages in the cycle is added to the removes list of each package in the cycle. This marks a package as "in a cycle". After this preprocessing step a package is determined as removable by pretending that every other package in the cycle is being removed, and then determining what or not the package itself is removable as normal. My thinking from this prototype though is that it isn't as great a solution as calculating the strongly connected components of the dependency graph. Doing cycle detection this way means that dependency graphs with packages belonging to more than one cycle aren't detected. Although this is a crazy edge case, it's theoretically a potential graph, and implementing Tarjan's strongly connected components algorithm instead of the cycle detection used here shouldn't be much more work. It can still use the removes array and the `_can_remove_cycle` method for determining whether a cycle is removable; only the preprocessing step would need to change. The only way that I think calculating the strongly connected components could be worse than this prototype is that it requires a list of every vertex in the dependency graph. This is easy enough to calculate with a breadth first search but it will use more memory than simple cycle detection. So I wanted to see what people's thoughts were on these two solutions and if there was a preference to one or the other. Ashley [1] https://bugs.archlinux.org/task/41031

3 4

[pacman-dev] [GIT] The official pacman repository branch, release/5.0.x, updated. v5.0.1-6-gc2f9758
by allan＠archlinux.org 18 May '16

18 May '16

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, release/5.0.x has been updated via c2f9758018479c15a34887d960f36ba9b532175f (commit) from 5469161dad387b71d605cfeb2c6c369df6f939e3 (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 c2f9758018479c15a34887d960f36ba9b532175f Author: Leonid Isaev <leonid.isaev(a)jila.colorado.edu> Date: Sat May 7 17:24:17 2016 -0600 Use a more generic regexp when parsing output of gpg(1) in signature verification. The current way of extracting key trust from output of gpg --verify is not very robust against changes in the format of said output. As a result, pacman-key can return an error even if the signature is actuall good. This change relaxes the regexp when parsing output of gpg. Signed-off-by: Leonid Isaev <leonid.isaev(a)jila.colorado.edu> Signed-off-by: Allan McRae <allan(a)archlinux.org> (cherry picked from commit 892a1076c00a2b0097145c35f5d8ef590216dac0) ----------------------------------------------------------------------- Summary of changes: scripts/pacman-key.sh.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- The official pacman repository

1 0

[pacman-dev] [GIT] The official pacman repository branch, master, updated. v5.0.1-35-g839417e
by allan＠archlinux.org 18 May '16

18 May '16

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 839417e8c65e73e632c77d3ecd68539494850de1 (commit) via f018317f488e35f3a9a3ce43c977baceec13d08b (commit) via 4f114f38178aeaffcc571aa42e2f930ca916f79d (commit) via 892a1076c00a2b0097145c35f5d8ef590216dac0 (commit) via 87082e3f44c4f92c63d881db38a0fff0565fc9bc (commit) via 7bebe4deff0afd4e220b5c4d6024bffb08bd794f (commit) via 02a0bf550a22e199f48537b7eee87361b112e8a0 (commit) from 3729ef7a9acf75080fb6f60d13ea80cfd36d855d (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 839417e8c65e73e632c77d3ecd68539494850de1 Author: Christian Hesse <mail(a)eworm.de> Date: Tue May 17 13:23:44 2016 +0200 pacman.8: add link to alpm-hooks(5) in see also Signed-off-by: Christian Hesse <mail(a)eworm.de> Signed-off-by: Allan McRae <allan(a)archlinux.org> commit f018317f488e35f3a9a3ce43c977baceec13d08b Author: Christian Hesse <mail(a)eworm.de> Date: Tue May 17 13:23:43 2016 +0200 libalpm.3: add link to alpm-hooks(5) in see also Signed-off-by: Christian Hesse <mail(a)eworm.de> Signed-off-by: Allan McRae <allan(a)archlinux.org> commit 4f114f38178aeaffcc571aa42e2f930ca916f79d Author: Ashley Whetter <ashley(a)awhetter.co.uk> Date: Sun May 8 17:28:28 2016 +0100 libmakepkg: extract functions for integrity checking Signed-off-by: Ashley Whetter <ashley(a)awhetter.co.uk> Signed-off-by: Allan McRae <allan(a)archlinux.org> commit 892a1076c00a2b0097145c35f5d8ef590216dac0 Author: Leonid Isaev <leonid.isaev(a)jila.colorado.edu> Date: Sat May 7 17:24:17 2016 -0600 Use a more generic regexp when parsing output of gpg(1) in signature verification. The current way of extracting key trust from output of gpg --verify is not very robust against changes in the format of said output. As a result, pacman-key can return an error even if the signature is actuall good. This change relaxes the regexp when parsing output of gpg. Signed-off-by: Leonid Isaev <leonid.isaev(a)jila.colorado.edu> Signed-off-by: Allan McRae <allan(a)archlinux.org> commit 87082e3f44c4f92c63d881db38a0fff0565fc9bc Author: Alastair Hughes <hobbitalastair(a)gmail.com> Date: Sun Apr 3 16:19:49 2016 +1200 makepkg: ignore the architecture for --printsrcinfo Signed-off-by: Alastair Hughes <hobbitalastair(a)gmail.com> Signed-off-by: Allan McRae <allan(a)archlinux.org> commit 7bebe4deff0afd4e220b5c4d6024bffb08bd794f Author: Allan McRae <allan(a)archlinux.org> Date: Tue Mar 29 22:00:02 2016 +1000 Report local file URL for -Sp operations if package is in cache When using "pacman -Sp" operation to get URLs of packages to download, it is useful to know which packages are already in the file cache and do not need downloaded. Print packages in the cache with a file:// prefix. e.g $ pacman -Sp glibc file:///var/cache/pacman/glibc-2.23-1-x86_64.pkg.tar.xz Also use package locations in case statements rather than opersations. This allows the ALPM_PKG_SYNCDB to fall thorough to just printing the package name for weird serverless repo setups. Fixes FS#15868 Signed-off-by: Allan McRae <allan(a)archlinux.org> commit 02a0bf550a22e199f48537b7eee87361b112e8a0 Author: Allan McRae <allan(a)archlinux.org> Date: Sat Apr 2 22:41:17 2016 +1000 makepkg: move build enviroment set-up to function This is a requirement to split the preparation of the build environment into libmakepkg, which will allow dropping in extensions (e.g. to allow PGO). After this patch, disabling buildflags or makeflags and enabling debug CFLAGS will only effect the build(), check() and package() functions. The relevant variables are no longer exported for the prepare() function. This should have zero impact for the prepare() function of a properly written PKGBUILD, as no building/linking is done there... Signed-off-by: Allan McRae <allan(a)archlinux.org> ----------------------------------------------------------------------- Summary of changes: doc/libalpm.3.txt | 3 +- doc/pacman.8.txt | 3 +- scripts/Makefile.am | 6 + scripts/libmakepkg/.gitignore | 2 + .../{lint_package.sh.in => integrity.sh.in} | 37 +- .../libmakepkg/integrity/generate_checksum.sh.in | 107 +++++ .../generate_signature.sh.in} | 44 +- scripts/libmakepkg/integrity/verify_checksum.sh.in | 130 ++++++ .../libmakepkg/integrity/verify_signature.sh.in | 216 +++++++++ scripts/libmakepkg/util/pkgbuild.sh.in | 20 +- scripts/makepkg.sh.in | 509 ++------------------- scripts/pacman-key.sh.in | 2 +- scripts/po/POTFILES.in | 5 + src/pacman/util.c | 27 +- 14 files changed, 600 insertions(+), 511 deletions(-) copy scripts/libmakepkg/{lint_package.sh.in => integrity.sh.in} (53%) create mode 100644 scripts/libmakepkg/integrity/generate_checksum.sh.in copy scripts/libmakepkg/{tidy/purge.sh.in => integrity/generate_signature.sh.in} (56%) create mode 100644 scripts/libmakepkg/integrity/verify_checksum.sh.in create mode 100644 scripts/libmakepkg/integrity/verify_signature.sh.in hooks/post-receive -- The official pacman repository

1 0

[pacman-dev] [PATCH 1/2] libalpm.3: add link to alpm-hooks(5) in see also
by Christian Hesse 18 May '16

18 May '16

From: Christian Hesse <mail(a)eworm.de> Signed-off-by: Christian Hesse <mail(a)eworm.de> --- doc/libalpm.3.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/doc/libalpm.3.txt b/doc/libalpm.3.txt index e2ea32c..aa667a1 100644 --- a/doc/libalpm.3.txt +++ b/doc/libalpm.3.txt @@ -34,6 +34,7 @@ See linkman:pacman.conf[5] for more details on configuring libalpm using the See Also -------- -linkman:pacman[8], linkman:makepkg[8], linkman:pacman.conf[5] +linkman:alpm-hooks[5], linkman:makepkg[8], linkman:pacman[8], +linkman:pacman.conf[5] include::footer.txt[] -- 2.8.2

2 2

[pacman-dev] Proposal to split out makepkg integrity methods
by Ashley Whetter 18 May '16

18 May '16

Hello everyone, I'm looking to split some makepkg methods out into a of makepkg.sh.in and into a new libmakepkg module. My plan is to have an "integrity" folder in libmakepkg. In this folder there would be a "generate.sh" file with the `generate_checksums`, `generate_one_checksum`, and `create_signature` methods. Another file, "check.sh" would contain `check_source_integrity`and it's dependencies; namely `check_checksums`, `check_pgpsigs`, `parse_gpg_statusfile`, `verify_integrity_sums`, and `verify_integrity_one`. "integrity" would depend on "util/pkgbuild.sh" as `check_checksums` and `verify_integrity_sum` both call `array_build`, and `check_pgpsigs` calls `get_all_sources` and `get_all_sources_for_arch`. I also plan on moving `get_integlist` into "util/pkgbuild.sh", or maybe into an "integrity/util.sh" file (but "util/pkgbuild.sh" makes more sense to me). Another option would be to have an "integrity.sh" file under "integrity" (or maybe some other name) and also a "signature.sh" file, and to split the methods by whether they are related to strictly integrity checking or signature checking. Are there any thoughts or suggestions on this plan of attack? Ashley

2 5

[pacman-dev] [PATCH] makepkg: ignore the architecture for --printsrcinfo
by Alastair Hughes 05 May '16

05 May '16

Signed-off-by: Alastair Hughes <hobbitalastair(a)gmail.com> --- It appears that SRCINFO files should be independent of architecture, however makepkg will currently fail if the SRCINFO file is being generated on a machine with a different architecture. This is in the same vein as c72ca3d5; I believe that creating source tarballs would be the only other candidate, but IGNOREARCH gets set later in that case. scripts/makepkg.sh.in | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/scripts/makepkg.sh.in b/scripts/makepkg.sh.in index f80e37a..5487884 100644 --- a/scripts/makepkg.sh.in +++ b/scripts/makepkg.sh.in @@ -1707,7 +1707,8 @@ while true; do -o|--nobuild) NOBUILD=1 ;; -p) shift; BUILDFILE=$1 ;; --packagelist) PACKAGELIST=1 IGNOREARCH=1;; - --printsrcinfo) PRINTSRCINFO=1 ;; + # generating a srcinfo does not depend on architecture + --printsrcinfo) PRINTSRCINFO=1 IGNOREARCH=1;; -r|--rmdeps) RMDEPS=1 ;; -R|--repackage) REPKG=1 ;; --sign) SIGNPKG='y' ;; -- 2.8.0

2 1

[pacman-dev] [GIT] The official pacman repository branch, release/5.0.x, updated. v5.0.1-5-g5469161
by allan＠archlinux.org 05 May '16

05 May '16

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, release/5.0.x has been updated via 5469161dad387b71d605cfeb2c6c369df6f939e3 (commit) via 07ccbc26914bea24983931532b97661a75b8a53c (commit) via a66cba1b08cc7c9f55efcfda6f4ab3cafff6b874 (commit) from d4f499f5638a68a3b7e17c5171aabdf535b79bd4 (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 5469161dad387b71d605cfeb2c6c369df6f939e3 Author: Allan McRae <allan(a)archlinux.org> Date: Mon Mar 28 16:24:22 2016 +1000 PKGBUILD.5: document that the pkgver() function runs after prepare() Signed-off-by: Allan McRae <allan(a)archlinux.org> (cherry picked from commit 59010386106eded2ee67798fa80215f250a53761) commit 07ccbc26914bea24983931532b97661a75b8a53c Author: Allan McRae <allan(a)archlinux.org> Date: Sun Mar 20 21:23:32 2016 +1000 Do not add root prefix twice when checking database files When checking .INSTALL and .CHANGELOG files in the mtree file, we need to find the path they are stored in the local database. This was appending the root prefix twice as alpm_option_get_dbpath already returns the absolute path to the database. While fixing that issue I added checks that the paths for the database files were not longer than PATH_MAX. Fixes FS#48563. Signed-off-by: Allan McRae <allan(a)archlinux.org> (cherry picked from commit 2ee1706a72858ea365c0e7a1a72d92ef2dae2f75) commit a66cba1b08cc7c9f55efcfda6f4ab3cafff6b874 Author: Allan McRae <allan(a)archlinux.org> Date: Mon Mar 21 11:49:16 2016 +1000 libmakepkg: ensure emptydir find command acts on individual directories Using "-exec command {} +" systax exits on any error. Such errors occur when running rmdir on a non-empty directory. Switch to "{} ;" syntax instead which avoids exiting before the find command is completed. Fixes FS#48515. Note, we can not use "-empty" in the find command because it is not supported by Busybox find, and the "--ignore-fail-on-non-empty" flag for rmdir is not available on BSD rmdir variants. Signed-off-by: Allan McRae <allan(a)archlinux.org> (cherry picked from commit baf1ff64e6ea23e93f307480480d87159cd2e487) ----------------------------------------------------------------------- Summary of changes: doc/PKGBUILD.5.txt | 8 ++--- scripts/libmakepkg/tidy/emptydirs.sh.in | 3 +- src/pacman/check.c | 54 ++++++++++++++++++--------------- 3 files changed, 36 insertions(+), 29 deletions(-) hooks/post-receive -- The official pacman repository

1 0