- Pacman-dev - lists.archlinux.org

Re: [pacman-dev] Breaking change in pacman from 5.0.1 -> 5.0.2 with regards to user account resolution
by Thomas Karlsson 21 Jun '17

21 Jun '17

Hello! I have several packages that install files that need to be owned by specific users on the target system. To achieve that I'm using the install command with the -o <username> and -g <group name> flags in the package() function. I'm not using a install script with a post_install() function. Example of the relevant part of the package function package() { install -m 600 -o username -g groupname the_file "$pkgdir"/some/path/to/the_file } The package is built on a build server and then installed on a number of targets. This has worked fine up until I upgraded to 5.0.2 After upgrading pacman to 5.0.2 the file does not get the correct owner on the target system any more. It gets own by the user that has the UID that the user has on the build server which is not the same UID as the user has on the target. To clarify. In my setup the UID of the user is different on the build server compared to the UID of the target system. Before this did not matter. The file got the correct ownership anyway. After 5.0.2 the file gets owned by whatever user account that has the UID and GID that the user has on the build server no matter what UID and GID the user has on the target system. As far as I can tell this is probably the commit that changed the behavior https://git.archlinux.org/pacman.git/commit/?h=release/5.0.x&id=908769b5400… Temporarily I have changed my PKGBUILD file to specify UID and GID that the target system has instead of the username and groupname on the install command but this seems fragile as it now requires that the UID/GID is the same on all target systems. Both existing and future. Is this an unintended side effect of the commit referenced above, or is this the expected behavior? Best regards, Thomas Karlsson

3 3

[pacman-dev] Correct alpm version to bind to?
by Colin Woodbury 13 Jun '17

13 Jun '17

Hi all, I'm the Aura dev. I'm writing alpm bindings for it, and I got a fair distance through before I realized that my up-to-date paper copies and the version of `alpm.h` actually bundled with pacman on my machine are quite different. The local one (/usr/include/alpm.h) is dated 2016 and has types / function signatures that vary a fair amount from what's currently on master, although they both report their versions to be 10.0.1. Is the most recent alpm supposed to be bundled with pacman? What incarnation of alpm does our installed pacman (5.0.1-5 as of this writing) bind to itself? Which version should be considered the "ground truth" for people writing bindings? Thanks, Colin

2 1

Re: [pacman-dev] [PATCH 1/1] alpm: use flock() for db lock
by Allan McRae 06 Jun '17

06 Jun '17

On 07/06/17 07:56, Christian Hesse wrote: > Allan McRae <allan(a)archlinux.org> on Wed, 2017/06/07 07:37: >> On 07/06/17 07:26, Christian Hesse wrote: >>> From: Christian Hesse <mail(a)eworm.de> >>> >>> We used to check for file existens, but that suffers from stale lock >>> files caused by unexpected events like crash, shutdown, etc. >>> >>> Instead use flock() to lock the file. It does not matter whether or >>> not the file exists but whether an exclusive lock can be obtained. >>> >>> Also remove the hint about removing the file from pacman. >> >> This does not work with NFS filesystems. > > Uh, did not know NFS has issues here. However, this is from NFS FAQ [0]: > >> The NFS client in 2.6.12 provides support for flock()/BSD locks on NFS files >> by emulating the BSD-style locks in terms of POSIX byte range locks. Other >> NFS clients that use the same emulation mechanism, or that use fcntl()/POSIX >> locks, will then see the same locks that the Linux NFS client sees. > > Given the fact that linux 2.6.12 has been released nearly twelve years ago... > We still do not want to use this? > > Does any other locking mechanism has a chance to be accepted? > > [0] http://nfs.sourceforge.net/#faq_d10 > Bringing back on list. We has issues with NFS/OSX last time this was run (need to look up last time this was discussed). I think out support for OSX is dead, so we could ignore that... I would not mind flock being used to lock individual files, but leaving an overall lock file during a transaction is useful. A

2 1

[pacman-dev] [PATCH 1/1] alpm: use flock() for db lock
by Christian Hesse 06 Jun '17

06 Jun '17

From: Christian Hesse <mail(a)eworm.de> We used to check for file existens, but that suffers from stale lock files caused by unexpected events like crash, shutdown, etc. Instead use flock() to lock the file. It does not matter whether or not the file exists but whether an exclusive lock can be obtained. Also remove the hint about removing the file from pacman. Signed-off-by: Christian Hesse <mail(a)eworm.de> --- lib/libalpm/handle.c | 17 +++++++++++++++-- src/pacman/util.c | 5 ----- 2 files changed, 15 insertions(+), 7 deletions(-) diff --git a/lib/libalpm/handle.c b/lib/libalpm/handle.c index b6b27881..bb5cc907 100644 --- a/lib/libalpm/handle.c +++ b/lib/libalpm/handle.c @@ -24,6 +24,7 @@ #include <stdlib.h> #include <string.h> #include <limits.h> +#include <sys/file.h> #include <sys/types.h> #include <syslog.h> #include <sys/stat.h> @@ -120,10 +121,20 @@ int _alpm_handle_lock(alpm_handle_t *handle) FREE(dir); do { - handle->lockfd = open(handle->lockfile, O_WRONLY | O_CREAT | O_EXCL | O_CLOEXEC, 0000); + handle->lockfd = open(handle->lockfile, O_WRONLY | O_CREAT | O_CLOEXEC, 0000); } while(handle->lockfd == -1 && errno == EINTR); - return (handle->lockfd >= 0 ? 0 : -1); + if (handle->lockfd == -1) + return -1; + + /* try to get an exclusive lock */ + if (flock(handle->lockfd, LOCK_EX | LOCK_NB) == -1) { + close(handle->lockfd); + handle->lockfd = -1; + return -1; + } + + return 0; } /** Remove the database lock file @@ -137,6 +148,8 @@ int SYMEXPORT alpm_unlock(alpm_handle_t *handle) ASSERT(handle->lockfile != NULL, return 0); ASSERT(handle->lockfd >= 0, return 0); + flock(handle->lockfd, LOCK_UN); + close(handle->lockfd); handle->lockfd = -1; diff --git a/src/pacman/util.c b/src/pacman/util.c index ae8a74d3..c3f9d3ba 100644 --- a/src/pacman/util.c +++ b/src/pacman/util.c @@ -81,13 +81,8 @@ void trans_init_error(void) pm_printf(ALPM_LOG_ERROR, _("failed to init transaction (%s)\n"), alpm_strerror(err)); if(err == ALPM_ERR_HANDLE_LOCK) { - const char *lockfile = alpm_option_get_lockfile(config->handle); pm_printf(ALPM_LOG_ERROR, _("could not lock database: %s\n"), strerror(errno)); - if(access(lockfile, F_OK) == 0) { - fprintf(stderr, _(" if you're sure a package manager is not already\n" - " running, you can remove %s\n"), lockfile); - } } } -- 2.13.1

2 2

[pacman-dev] [PATCH 1/1] fix typo in libalpm comment
by Christian Hesse 06 Jun '17

06 Jun '17

From: Christian Hesse <mail(a)eworm.de> contatenate -> concatenate Signed-off-by: Christian Hesse <mail(a)eworm.de> --- lib/libalpm/alpm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/libalpm/alpm.c b/lib/libalpm/alpm.c index d3f951d5..28685fef 100644 --- a/lib/libalpm/alpm.c +++ b/lib/libalpm/alpm.c @@ -64,7 +64,7 @@ alpm_handle_t SYMEXPORT *alpm_initialize(const char *root, const char *dbpath, goto cleanup; } - /* to contatenate myhandle->root (ends with a slash) with SYSHOOKDIR (starts + /* to concatenate 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 nomem); -- 2.13.1

1 0

[pacman-dev] [GIT] The official pacman repository annotated tag, v5.0.2, created. v5.0.2
by andrew＠archlinux.org 05 Jun '17

05 Jun '17

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 annotated tag, v5.0.2 has been created at 95fd1a379aa279da7f2260ae6c269f3c333c5238 (tag) tagging 0c633c27eaeab2a9d30efb01199579896ccf63c9 (commit) replaces v5.0.1 tagged by Andrew Gregory on Sat Jun 3 22:21:35 2017 -0400 - Log ----------------------------------------------------------------- v5.0.2 -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEuBUbEXA3eBCVUUynu9/8kjBrESEFAlkzbq8ACgkQu9/8kjBr ESGkNgf/YEnAWmX0UK9ZIdObD3iaQJxQJOW15UaHvd58P6RPM7M/HKkJUl2usroy 2EDX5qEmaKuzkJ6tRdLjquxaBJZZij9H5vr5lcQAJn6H/lm253A3g4TGIl8TxW1o xvFOmI1n8pcDi0YDS1TyupJEzKp6W2y2sTrXI6dxtryFZGL5HvenZzGqyOzmuU0J 0lskI+GMKbC4FmEFChCYICgFtPXkQqosR0xcCkdZuGQIX50Gjk5SLFolB1NXiglL RRxxleNGQrFiE1xEaexUmRT0SLO9RNZl5DckSmFiNRPwo5TObcCheEDo3EHu0LE/ OuhkvzFk+ES7IdWnMqGwPEpxxx0L3g== =w4ld -----END PGP SIGNATURE----- Alad Wenter (1): libmakepkg: generate all scripts Alastair Hughes (3): makepkg: ignore the architecture for --printsrcinfo Remove AC_FUNC_MALLOC check. Add missing newline in paclog-pkglist help output Allan McRae (17): Update NEWS for pacman-5.0.1 libmakepkg: fix is_array function libmakepkg: ensure emptydir find command acts on individual directories Do not add root prefix twice when checking database files PKGBUILD.5: document that the pkgver() function runs after prepare() Consider provides when labelling optdepends status as pending install Consider provides when warning about optdepnd removal Use versions specified in optdepends repo-add: do not alter the database if only verifying signature Prevent wrapping of enum items Avoid logical OR duplication warning from gcc-6 Fix typo in pacman-db-upgrade usage message Fix memory leak in remove_notify_needed_optdepends Move bash/zsh completion out of contrib Ensure makepkg-wrapper is built after makepkg Prepare translations for 5.0.2 release Pull translation changes for 5.0.2 Andrew Gregory (8): use multi-byte character matching for user input recursedeps: include cyclic dependencies hook.c: replace readdir_r with readdir hook.c: replace fstatat with stat unlink_file: strip trailing slashes extract db files with dbonly update NEWS for v5.0.2 Release v5.0.2 Armin K (1): libalpm: Use archive_read_extract2 Ashley Whetter (1): pacsort help clearly states that files contain inputs to be sorted Christian Hesse (4): libalpm.3: add link to alpm-hooks(5) in see also pacman.8: add link to alpm-hooks(5) in see also libalpm/signing: support EDDSA from gpgme 1.7.0 add generated scripts to gitignore Dave Reisner (1): makepkg.conf: add -g to default curl options Eli Schwartz (1): bash-completion: fix leaking "files" array into shell environment Eric Engestrom (1): fix spelling mistakes Fabio Castell (1): repo-add: fix error in directories with a space in their name Giulio Fidente (1): Merge Giolio Fidente into "Pacman Development Team" contribution Ivy Foster (2): lib/libalpm/be_sync.c: Close memory leaks when mallocing while out of memory Do not #define _RESERVED_IDENTIFIERS Jack O'Connor (1): libmakepkg: look for architecture-specific hashes in get_integlist Leonid Isaev (1): Use a more generic regexp when parsing output of gpg(1) in signature verification. Levente Polyak (1): fix --printsrcinfo unify arch and non-arch specific variables Lukas Fleischer (1): pacman.8: fix typo in the documentation of --asexplicit Martin Kühne (1): Use f_bavail for diskspace calculations Olivier Brunel (1): configure.ac: Fix handling --with-libcurl Rikard Falkeborn (3): Fix gcc strict-overflow error Return boolean from db_populate Change type of count in be_sync Tobias Stoeckmann (4): Always use proper error code in alpm_initialize. Release resources on error paths. Reject files larger than 16384 bytes in read_sigfile. Handle all POSIX compliant systems in mbscasecmp. ----------------------------------------------------------------------- hooks/post-receive -- The official pacman repository

1 0

[pacman-dev] [GIT] The official pacman repository branch, release/5.0.x, updated. v5.0.2
by andrew＠archlinux.org 05 Jun '17

05 Jun '17

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 0c633c27eaeab2a9d30efb01199579896ccf63c9 (commit) via fdf53393bc996a514bbfc9fcd6ea19a8bb2f02ed (commit) from 34d8beaef87bab7bb01dd5825b8ffa0a8fda010c (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 0c633c27eaeab2a9d30efb01199579896ccf63c9 Author: Andrew Gregory <andrew(a)archlinux.org> Date: Sat Jun 3 22:17:02 2017 -0400 Release v5.0.2 Signed-off-by: Andrew Gregory <andrew(a)archlinux.org> commit fdf53393bc996a514bbfc9fcd6ea19a8bb2f02ed Author: Andrew Gregory <andrew(a)archlinux.org> Date: Sat Jun 3 22:15:22 2017 -0400 update NEWS for v5.0.2 Signed-off-by: Andrew Gregory <andrew(a)archlinux.org> ----------------------------------------------------------------------- Summary of changes: NEWS | 18 ++++++++++++++++++ configure.ac | 4 ++-- doc/index.txt | 1 + 3 files changed, 21 insertions(+), 2 deletions(-) hooks/post-receive -- The official pacman repository

1 0

[pacman-dev] [GIT] The official pacman repository branch, release/5.0.x, updated. v5.0.1-53-g34d8beae
by allan＠archlinux.org 31 May '17

31 May '17

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 34d8beaef87bab7bb01dd5825b8ffa0a8fda010c (commit) via d39271ab56a1ac33001d26823e7b563655668eed (commit) from 831cc8d9cd51921370e20befa4672f232ea2fbdf (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 34d8beaef87bab7bb01dd5825b8ffa0a8fda010c Author: Allan McRae <allan(a)archlinux.org> Date: Wed May 31 23:47:00 2017 +1000 Pull translation changes for 5.0.2 Signed-off-by: Allan McRae <allan(a)archlinux.org> commit d39271ab56a1ac33001d26823e7b563655668eed Author: Allan McRae <allan(a)archlinux.org> Date: Mon May 22 11:03:33 2017 +1000 Prepare translations for 5.0.2 release Pull translation updates from transifex and regenerate po files. Signed-off-by: Allan McRae <allan(a)archlinux.org> ----------------------------------------------------------------------- Summary of changes: lib/libalpm/po/ar.po | 121 +++---- lib/libalpm/po/ast.po | 135 ++++---- lib/libalpm/po/bg.po | 152 ++++---- lib/libalpm/po/br.po | 117 ++++--- lib/libalpm/po/ca.po | 149 ++++---- lib/libalpm/po/cs.po | 118 ++++--- lib/libalpm/po/da.po | 117 ++++--- lib/libalpm/po/de.po | 120 ++++--- lib/libalpm/po/el.po | 119 ++++--- lib/libalpm/po/en_GB.po | 117 ++++--- lib/libalpm/po/eo.po | 117 ++++--- lib/libalpm/po/es.po | 143 ++++---- lib/libalpm/po/es_419.po | 123 +++---- lib/libalpm/po/eu.po | 135 ++++---- lib/libalpm/po/{eu.po => eu_ES.po} | 142 ++++---- lib/libalpm/po/fi.po | 117 ++++--- lib/libalpm/po/fr.po | 159 ++++----- lib/libalpm/po/gl.po | 117 ++++--- lib/libalpm/po/hr.po | 232 +++++++------ lib/libalpm/po/hu.po | 144 ++++---- lib/libalpm/po/id.po | 117 ++++--- lib/libalpm/po/is.po | 117 ++++--- lib/libalpm/po/it.po | 117 ++++--- lib/libalpm/po/ja.po | 119 ++++--- lib/libalpm/po/ka.po | 117 ++++--- lib/libalpm/po/kk.po | 117 ++++--- lib/libalpm/po/ko.po | 120 ++++--- lib/libalpm/po/libalpm.pot | 113 +++--- lib/libalpm/po/lt.po | 119 ++++--- lib/libalpm/po/nb.po | 136 ++++---- lib/libalpm/po/nl.po | 117 ++++--- lib/libalpm/po/pl.po | 127 +++---- lib/libalpm/po/pt.po | 119 ++++--- lib/libalpm/po/pt_BR.po | 117 ++++--- lib/libalpm/po/ro.po | 117 ++++--- lib/libalpm/po/ru.po | 120 ++++--- lib/libalpm/po/sk.po | 120 ++++--- lib/libalpm/po/sl.po | 115 ++++--- lib/libalpm/po/sr.po | 117 ++++--- lib%2Flibalpm%2Fpo%2Fsr(a)latin.po | 117 ++++--- lib/libalpm/po/sv.po | 115 ++++--- lib/libalpm/po/tr.po | 120 ++++--- lib/libalpm/po/uk.po | 117 ++++--- lib/libalpm/po/ur.po | 133 +++---- lib/libalpm/po/uz.po | 136 ++++---- lib/libalpm/po/vi.po | 133 +++---- lib/libalpm/po/zh_CN.po | 117 ++++--- lib/libalpm/po/zh_TW.po | 214 ++++++------ scripts/po/ar.po | 328 +++++++++--------- scripts/po/ast.po | 332 +++++++++--------- scripts/po/az_AZ.po | 328 +++++++++--------- scripts/po/bg.po | 687 +++++++++++++++++++------------------ scripts/po/br.po | 332 +++++++++--------- scripts/po/ca.po | 505 ++++++++++++++------------- scripts/po/cs.po | 333 +++++++++--------- scripts/po/da.po | 341 +++++++++--------- scripts/po/de.po | 344 ++++++++++--------- scripts/po/el.po | 334 +++++++++--------- scripts/po/en_GB.po | 332 +++++++++--------- scripts/po/eo.po | 332 +++++++++--------- scripts/po/es.po | 617 ++++++++++++++++----------------- scripts/po/es_419.po | 403 ++++++++++++---------- scripts/po/eu.po | 334 +++++++++--------- scripts/po/{eu.po => eu_ES.po} | 341 +++++++++--------- scripts/po/fi.po | 421 ++++++++++++----------- scripts/po/fr.po | 394 +++++++++++---------- scripts/po/gl.po | 334 +++++++++--------- scripts/po/hr.po | 508 ++++++++++++++------------- scripts/po/hu.po | 398 +++++++++++---------- scripts/po/id.po | 337 +++++++++--------- scripts/po/is.po | 330 +++++++++--------- scripts/po/it.po | 332 +++++++++--------- scripts/po/ja.po | 333 +++++++++--------- scripts/po/ka.po | 328 +++++++++--------- scripts/po/kk.po | 328 +++++++++--------- scripts/po/ko.po | 352 +++++++++---------- scripts/po/lt.po | 335 +++++++++--------- scripts/po/nb.po | 358 +++++++++---------- scripts/po/nl.po | 333 +++++++++--------- scripts/po/pacman-scripts.pot | 326 +++++++++--------- scripts/po/pl.po | 444 ++++++++++++------------ scripts/po/pt.po | 363 ++++++++++---------- scripts/po/pt_BR.po | 347 +++++++++---------- scripts/po/ro.po | 331 +++++++++--------- scripts/po/ru.po | 360 ++++++++++--------- scripts/po/sk.po | 354 ++++++++++--------- scripts/po/sl.po | 328 +++++++++--------- scripts/po/sr.po | 332 +++++++++--------- scripts%2Fpo%2Fsr(a)latin.po | 332 +++++++++--------- scripts/po/sv.po | 330 +++++++++--------- scripts/po/tr.po | 349 +++++++++---------- scripts/po/uk.po | 335 +++++++++--------- scripts/po/uz.po | 333 +++++++++--------- scripts/po/zh_CN.po | 334 +++++++++--------- scripts/po/zh_TW.po | 511 ++++++++++++++------------- src/pacman/po/ar.po | 127 +++---- src/pacman/po/ast.po | 207 +++++------ src/pacman/po/az_AZ.po | 178 +++++----- src/pacman/po/bg.po | 298 ++++++++-------- src/pacman/po/br.po | 129 +++---- src/pacman/po/ca.po | 241 ++++++------- src/pacman/po/cs.po | 130 +++---- src/pacman/po/da.po | 138 ++++---- src/pacman/po/de.po | 142 ++++---- src/pacman/po/el.po | 131 +++---- src/pacman/po/en_GB.po | 129 +++---- src/pacman/po/eo.po | 134 ++++---- src/pacman/po/es.po | 214 ++++++------ src/pacman/po/es_419.po | 201 ++++++----- src/pacman/po/eu.po | 207 +++++------ src/pacman/po/{eu.po => eu_ES.po} | 214 ++++++------ src/pacman/po/fa.po | 127 +++---- src/pacman/po/fi.po | 129 +++---- src/pacman/po/fr.po | 164 ++++----- src/pacman/po/gl.po | 133 +++---- src/pacman/po/hr.po | 319 +++++++++-------- src/pacman/po/hu.po | 235 +++++++------ src/pacman/po/id.po | 129 +++---- src/pacman/po/is.po | 129 +++---- src/pacman/po/it.po | 162 +++++---- src/pacman/po/ja.po | 133 +++---- src/pacman/po/ka.po | 129 +++---- src/pacman/po/kk.po | 127 +++---- src/pacman/po/ko.po | 136 ++++---- src/pacman/po/lt.po | 132 +++---- src/pacman/po/nb.po | 210 ++++++------ src/pacman/po/nl.po | 129 +++---- src/pacman/po/pacman.pot | 125 +++---- src/pacman/po/pl.po | 149 ++++---- src/pacman/po/pt.po | 136 ++++---- src/pacman/po/pt_BR.po | 136 ++++---- src/pacman/po/ro.po | 129 +++---- src/pacman/po/ru.po | 136 ++++---- src/pacman/po/sk.po | 132 +++---- src/pacman/po/sl.po | 127 +++---- src/pacman/po/sr.po | 129 +++---- src%2Fpacman%2Fpo%2Fsr(a)latin.po | 129 +++---- src/pacman/po/sv.po | 127 +++---- src/pacman/po/th.po | 127 +++---- src/pacman/po/tr.po | 138 ++++---- src/pacman/po/uk.po | 141 ++++---- src/pacman/po/ur.po | 205 +++++------ src/pacman/po/uz.po | 208 +++++------ src/pacman/po/vi.po | 127 +++---- src/pacman/po/zh_CN.po | 129 +++---- src/pacman/po/zh_TW.po | 340 +++++++++--------- 146 files changed, 16237 insertions(+), 15486 deletions(-) copy lib/libalpm/po/{eu.po => eu_ES.po} (89%) copy scripts/po/{eu.po => eu_ES.po} (92%) copy src/pacman/po/{eu.po => eu_ES.po} (94%) hooks/post-receive -- The official pacman repository

1 0

[pacman-dev] %PGPSIG% vs .sig
by Brandon Milton 29 May '17

29 May '17

Hello all, This is my first post to the mailing list, so please feel free to correct me if I'm in the wrong place. While exploring the pacman mirror layout (ie what is hosted by mirrors), I noticed that for each package, there are two copies of the same signature: one in %PGPSIG% in the desc file of the database and one in the {package}-{version}.pkg.tar.gz.sig file I understand that for the AUR, the .sig file is necessary given that there is no official database. However, is there any reasoning behind having two copies of the signature for official repositories? To me, this simply seems like extra cruft that mirrors have to carry around. Thanks /brandon

5 7

[pacman-dev] [Feature Suggestion] Option to install packages one-by-one when upgrading
by Lakshay Garg 28 May '17

28 May '17

Hello all This is my first email to the pacman mailing-list and I am writing to suggest and discuss a possible feature for future versions of pacman. [Problem] Whenever a full system upgrade is run with pacman -Syyu, pacman downloads all the packages which need to be installed and then upgrades all at once. This approach sometimes leads to problems on computers with unreliable internet connections as in my case. It often happens that while downloading one of then several packages to be upgraded, one of the download will get corrupted and in the end when it tries to install, none of the packages would get upgraded due to a single corrupted package. In such a case, I run pacman -Scc followed by pacman -Syyu to try and upgrade again leading to lots of wasted data and time. [Suggested Solution] What I suggest is that a new commandline flag be created in pacman which changes the default behaviour. When the flag is enabled, pacman downloads upgrade files for a single package (or a few interdependent packages) and upgrade it and then move on to upgrade other packages. Thus installing packages one-by-one. [Request] Please let me know if this is a possibility or is there another way my problem can be solved without modifying pacman. I am willing to contribute the patch myself if you can guide me on how to proceed. Would like to know if anyone is interested. -- Lakshay Garg Senior Undergraduate, EE IIT Kanpur

3 4