March 2019 - Pacman-dev - lists.archlinux.org

[pacman-dev] should repo-add handle *.links.db?
by Erich Eckner 27 Mar '19

27 Mar '19

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, I'm looking into creating links databases for archlinux32 and saw (thanks, Eli) that they are created asynchronously by systemd timers here: https://git.archlinux.org/infrastructure.git/tree/roles/sogrep/files I was wondering, if it wouldn't be better to create them during repo-add (and repo-remove) at a similar point, where *.files.db entries are created - - ignoring deltas (can we ignore deltas already?), this would be somewhere down in db_write_entry() in repo-add - but even including deltas, it should not need changes at too many places. However, before I start trying to patch repo-add and repo-remove to maintain a *.links.db, I wanted to ask if there are any objections to include this functionality there. Cheers, Erich -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEE3p92iMrPBP64GmxZCu7JB1Xae1oFAlyaLrQACgkQCu7JB1Xa e1o26g/+PU80nwWnMcT/zwhzWuuTAP8hwIlb1dvovfFp5vkq9XjPC/A3yApfSg6m nUPb7Vjq9w3KGoKCMTwBWYO6jXLjLhvcB2gSBmhFlblDrMgGTnABrjNdfcaSUwcB hqF7cYDhSDJuUb+SyMBYKLoGDZL/Rxye/BAItiqBXfgitbxAcPWbNyZCKk3DYOBz /WHCHn3hMHJndxC7FJ9hfpGukES9Um2EW4bB8DGrz44AJwzyA8EyDO9e86QtR64z PX6qC2qEuAix55Ggvk2GILErPaea/5IuwhmyrZy6UtTEDysDfdkMSKWqV+r8wHJY 61fO7RGZnJH6F4h6YEpTncdEI4jnuIuR7FrheWauV83jMJ4E/X4nvNTNBlPDZUIt DC8Nj1nsSrTeD7HZmi6QiKHhPLpA5ZiE0ls+jdb/CcE0RaB+kqRtMRShanKDNiJi E4lhLO7nj6frNtpWhU3Iqb2O7azampIpL7VyCHDAfkuWPrIHfMGSRnwWmG2DW0G/ UTxHqDKqVFTDwBF2h6+4+J/xFO2T1uqm5OrAnR9ZsjGG6UMZEbsNvO0KxFiOdlYc UFPJJlwVn7OS28H94010tRU73LfE1xwZqRKiWxiR2NckjB9fvOf5lPUV5neZfeS1 O9yS9omfa9QzVH6dD/wDJArnt4RGj8mHBEXa3vwOZGEfXaF+waQ= =ny8G -----END PGP SIGNATURE-----

3 7

[pacman-dev] Man page translations
by Mario Blättermann 25 Mar '19

25 Mar '19

Hello, I've just read at [1] that nobody is working on man page translations for Pacman, but translations would be welcome anyway. That's great, because there are only a few developers who are really willing to consider localized man pages as an important part of a good user experience. I've already translated the current man pages based on the latest release into German, and they are currently maintained in the manpages-de project [2]. But this external approach has a few disadvantages: There's some delay between upstream release of the packages where we get the original man pages from, then translation, release of a tarball and finally packaging for the currently upported distributions (Archlinux and Debian unstable, support for Mageia is under construction). Moreover, we translate only into *one* language... It would be better to maintain the localized manpages in Pacman's git repo itself. We don't have that many options to setup i18n for man pages. In my opinion po4a [3] is the best software which can handle such things. We use it also in the manpages-de project. Well, we use it there with Groff and Mdoc, but it is also able to work with Asciidoc (says the documentation, I haven't tested it). I could setup a po4a toolchain in Pacman which takes the asciidoc files, puts the contents in pot templates and merges then the resuting po files back to the asciidoc source format. I've also some basic experience with Meson, but I'm afraid I won't be able to get it working with the GNU Autotools. The translations itself can be maintained at Transifex, as usual, but of course in separate templates for each asiidoc source file. What do you think about this idea? If it's OK for you, then I need some playground for my changes. I consider to fork the git repo at Github. @Allan, it is OK to fork your personal repo, or should I use the main repo at git.archlinux.org? Processing merge requests is maybe easier within Github. [1] https://www.archlinux.org/pacman/translation-help.html [2] https://salsa.debian.org/manpages-de-team/manpages-de [3]https://po4a.org/index.php Best Regards, Mario

1 0

[pacman-dev] [GIT] The official pacman repository branch, master, updated. v5.1.1-160-gd37e6d40
by Allan McRae 25 Mar '19

25 Mar '19

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 d37e6d40a19dadf41a223dcb1fde36c6fa622958 (commit) via 7a598d0845fda08e195e1a709297c761b68d79f4 (commit) from 9f5412d809a50a7ad18013222582d5b943216ae1 (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 d37e6d40a19dadf41a223dcb1fde36c6fa622958 Author: Eli Schwartz <eschwartz(a)archlinux.org> Date: Thu Mar 7 23:22:49 2019 -0500 bash-completion: support file redirection completions The current completions don't properly handle redirection operators, and attempt to complete command completions rather than completing filenames to redirect to. bash-completion provides both _get_comp_words_by_ref and a higher-level wrapper _init_completion, but the latter provides handling of redirection operators, so switch to using that. Signed-off-by: Eli Schwartz <eschwartz(a)archlinux.org> Signed-off-by: Allan McRae <allan(a)archlinux.org> commit 7a598d0845fda08e195e1a709297c761b68d79f4 Author: Allan McRae <allan(a)archlinux.org> Date: Wed Mar 20 09:58:16 2019 +1000 Use bug tracker to track bugs The mailing list requires subscription. So does the bug tracker, but that is more obvious. Signed-off-by: Allan McRae <allan(a)archlinux.org> ----------------------------------------------------------------------- Summary of changes: doc/footer.asciidoc | 5 +++-- scripts/completion/bash_completion.in | 18 +++++++++--------- 2 files changed, 12 insertions(+), 11 deletions(-) hooks/post-receive -- The official pacman repository

1 0

[pacman-dev] ask permission for forking pacman file manager
by dimension breaker 23 Mar '19

23 Mar '19

introduce me Purnomo Hadi I am the Chief Developer at Dracos-linux, one of the founders of LFS Indonesia. founder and developer kolomonggo linux dracOS linux and kolomonggo linux is a LFS based OS https://dracos-linux.org/ the purpose of sending this email is for forking pacman package manager to be a custom file manager with the name we will use. I am as the developer of dracOs linux and columnonggo linux request permission from the Pacman Development Team Thank you for your attention sory for my bad english -- dracOs linux - dev team -- dracOs linux - dev team

3 2

[pacman-dev] Version comparison algorithm.
by Richard Dodd 20 Mar '19

20 Mar '19

I'm writing to ask about the version comparison function `rpmvercmp` in `libalpm/version.cL83`. The algorithm is complex and I'm trying to understand its behavior. I want to hash using the package name and version as a key, and so I need a hash function where `i1 == i2 => hash(i1) == hash(i2)` according to the version comparison operation. I'll describe how the algorithm behaves and then ask my questions. The algorithm works on a byte string and uses ascii comparison rules (no unicode). - First, split the input up into blocks of *alpha*, *digit* or *non-alphanum*. - For each pair of blocks - If the types are different, then *non-alphanum* is newer than *numeric*, which is newer than *alpha* - If the types are the same, then the rules are - For *non-alphanum*, compare lengths, longer is newer, equal lengths are equal segments (so *--* and *::* are the same) - For *alpha* just do a lexicographic comparison (so *b* is newer than *a* etc.) - For *numeric*, do a numeric comparison. (this can be done by skipping leading zeros, then comparing length, then comparing lexicographically, to avoid overflow on integer conversion) - If one input is longer than the other, and all sections so far have been equal, then if the next section of the longer is *alpha*, it is older, and if it is *numeric* it is newer. (so "1a" is older than "1", "a1" is newer than "a"). - If the inputs have the same number of sections that are all equal, then they are equal. Questions: 1. Is the algorithm correctly described here. 2. This should mean that if I hash length for *non-numeric*, the string with stripped zeros for *numeric*, and just the string for *alpha*, the has law should be upheld. Is this correct? Thanks Rich

4 4

[pacman-dev] [PATCH] Use bug tracker to track bugs
by Allan McRae 19 Mar '19

19 Mar '19

The mailing list requires subscription. So does the bug tracker, but that is more obvious. Signed-off-by: Allan McRae <allan(a)archlinux.org> --- doc/footer.asciidoc | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/footer.asciidoc b/doc/footer.asciidoc index 5812aa72..cdaba40c 100644 --- a/doc/footer.asciidoc +++ b/doc/footer.asciidoc @@ -6,8 +6,9 @@ information on pacman and its related tools. Bugs ---- Bugs? You must be kidding; there are no bugs in this software. But if we -happen to be wrong, send us an email with as much detail as possible to -mailto:pacman-dev@archlinux.org[]. +happen to be wrong, submit a bug report with as much detail as possible +at the https://bugs.archlinux.org/index.php?project=3[Arch Linux Bug Tracker] +in the Pacman section. Authors -- 2.21.0

1 0

[pacman-dev] [PATCH] build: remove references to variable replacements from pacman-optimize
by Eli Schwartz 19 Mar '19

19 Mar '19

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(a)archlinux.org> --- build-aux/edit-script.sh.in | 2 -- configure.ac | 10 ---------- meson.build | 2 -- scripts/Makefile.am | 2 -- 4 files changed, 16 deletions(-) diff --git a/build-aux/edit-script.sh.in b/build-aux/edit-script.sh.in index 3b0058ce..a25218cb 100644 --- a/build-aux/edit-script.sh.in +++ b/build-aux/edit-script.sh.in @@ -19,8 +19,6 @@ mode=$3 -e "s|@TEMPLATE_DIR[@]|@TEMPLATE_DIR@|g" \ -e "s|@DEBUGSUFFIX[@]|@DEBUGSUFFIX@|g" \ -e "s|@INODECMD[@]|@INODECMD@|g" \ - -e "s|@OWNERCMD[@]|@OWNERCMD@|g" \ - -e "s|@MODECMD[@]|@MODECMD@|g" \ -e "s|@SEDINPLACEFLAGS[@]|@SEDINPLACEFLAGS@|g" \ -e "s|@SEDPATH[@]|@SEDPATH@|g" \ -e "s|@DUFLAGS[@]|@DUFLAGS@|g" \ diff --git a/configure.ac b/configure.ac index 74bf8c1f..6d2b2410 100644 --- a/configure.ac +++ b/configure.ac @@ -354,24 +354,18 @@ GCC_VISIBILITY_CC DEFAULT_DUFLAGS=" -sk --apparent-size" DEFAULT_SEDINPLACEFLAGS=" --follow-symlinks -i" INODECMD="stat -c '%i %n'" -OWNERCMD="stat -c '%u:%g'" -MODECMD="stat -c '%a'" STRIP_BINARIES="--strip-all" STRIP_SHARED="--strip-unneeded" STRIP_STATIC="--strip-debug" case "${host_os}" in *bsd*) INODECMD="stat -f '%i %N'" - OWNERCMD="stat -f '%u:%g'" - MODECMD="stat -f '%Lp'" DEFAULT_SEDINPLACEFLAGS=" -i \"\"" DEFAULT_DUFLAGS=" -sk" ;; darwin*) host_os_darwin=yes INODECMD="/usr/bin/stat -f '%i %N'" - OWNERCMD="/usr/bin/stat -f '%u:%g'" - MODECMD="/usr/bin/stat -f '%Lp'" DEFAULT_SEDINPLACEFLAGS=" -i ''" DEFAULT_DUFLAGS=" -sk" STRIP_BINARIES="" @@ -383,8 +377,6 @@ AM_CONDITIONAL([DARWIN], test "x$host_os_darwin" = "xyes") AC_PATH_PROGS([DUPATH], [du], [du], [/usr/bin$PATH_SEPARATOR/bin] ) AC_PATH_PROGS([SEDPATH], [sed], [sed], [/usr/bin$PATH_SEPARATOR/bin] ) AC_SUBST(INODECMD) -AC_SUBST(OWNERCMD) -AC_SUBST(MODECMD) AC_SUBST(STRIP_BINARIES) AC_SUBST(STRIP_SHARED) AC_SUBST(STRIP_STATIC) @@ -576,8 +568,6 @@ ${PACKAGE_NAME}: Architecture : ${CARCH} Host Type : ${CHOST} File inode command : ${INODECMD} - File owner command : ${OWNERCMD} - File mode command : ${MODECMD} In-place sed command : ${SEDPATH} ${SEDINPLACEFLAGS} libalpm version : ${LIB_VERSION} diff --git a/meson.build b/meson.build index 8db8c68e..4d96e5ff 100644 --- a/meson.build +++ b/meson.build @@ -319,8 +319,6 @@ substs.set('BUILDSCRIPT', BUILDSCRIPT) substs.set('TEMPLATE_DIR', get_option('makepkg-template-dir')) substs.set('DEBUGSUFFIX', get_option('debug-suffix')) substs.set('INODECMD', inodecmd) -substs.set('OWNERCMD', ownercmd) -substs.set('MODECMD', modecmd) substs.set('SEDINPLACEFLAGS', sedinplaceflags) substs.set('SEDPATH', SED.path()) substs.set('DUFLAGS', duflags) diff --git a/scripts/Makefile.am b/scripts/Makefile.am index 7fffd93b..2964d1b7 100644 --- a/scripts/Makefile.am +++ b/scripts/Makefile.am @@ -177,8 +177,6 @@ edit = sed \ -e 's|@TEMPLATE_DIR[@]|$(TEMPLATE_DIR)|g' \ -e 's|@DEBUGSUFFIX[@]|$(DEBUGSUFFIX)|g' \ -e "s|@INODECMD[@]|$(INODECMD)|g" \ - -e "s|@OWNERCMD[@]|$(OWNERCMD)|g" \ - -e "s|@MODECMD[@]|$(MODECMD)|g" \ -e 's|@SEDINPLACEFLAGS[@]|$(SEDINPLACEFLAGS)|g' \ -e 's|@SEDPATH[@]|$(SEDPATH)|g' \ -e 's|@DUFLAGS[@]|$(DUFLAGS)|g' \ -- 2.21.0

2 2

[pacman-dev] [PATCH] bash-completion: support file redirection completions
by Eli Schwartz 19 Mar '19

19 Mar '19

The current completions don't properly handle redirection operators, and attempt to complete command completions rather than completing filenames to redirect to. bash-completion provides both _get_comp_words_by_ref and a higher-level wrapper _init_completion, but the latter provides handling of redirection operators, so switch to using that. Signed-off-by: Eli Schwartz <eschwartz(a)archlinux.org> --- scripts/completion/bash_completion.in | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/scripts/completion/bash_completion.in b/scripts/completion/bash_completion.in index c3249cd0..a1ab9fec 100644 --- a/scripts/completion/bash_completion.in +++ b/scripts/completion/bash_completion.in @@ -41,9 +41,9 @@ _pacman_keyids() { } _pacman_key() { - local o cur opts prev wantfiles - COMPREPLY=() - _get_comp_words_by_ref cur prev + local o opts wantfiles + local cur prev words cword + _init_completion || return opts=('add config delete edit-key export finger gpgdir help import import-trustdb init keyserver list-keys list-sigs lsign-key nocolor populate recv-keys refresh-keys updatedb @@ -72,9 +72,9 @@ _pacman_key() { _makepkg() { compopt +o default - local cur opts prev - COMPREPLY=() - _get_comp_words_by_ref cur prev + local opts + local cur prev words cword + _init_completion || return if [[ $prev = @(-p|--config) ]]; then compopt -o default elif [[ ! $prev =~ ^-(-(config|help|key|version)$|\w*[Vh]) ]]; then @@ -105,9 +105,9 @@ _pacman_repo_list() { _pacman() { compopt -o default - local common core cur database files prev query remove sync upgrade o - COMPREPLY=() - _get_comp_words_by_ref cur prev + local common core database files query remove sync upgrade o + local cur prev words cword + _init_completion || return database=('asdeps asexplicit') files=('list machinereadable owns search refresh regex' 'l o s x y') query=('changelog check deps explicit file foreign groups info list native owns -- 2.21.0

2 2

[pacman-dev] [PATCH] makepkg: use "shared" git clones when checking out sources
by Eli Schwartz 19 Mar '19

19 Mar '19

In order to cache sources offline, makpekg 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(a)archlinux.org> --- scripts/libmakepkg/source/git.sh.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/libmakepkg/source/git.sh.in b/scripts/libmakepkg/source/git.sh.in index 497a668c..96d79623 100644 --- a/scripts/libmakepkg/source/git.sh.in +++ b/scripts/libmakepkg/source/git.sh.in @@ -91,7 +91,7 @@ extract_git() { exit 1 fi cd_safe "$srcdir" - elif ! git clone "$dir" "${dir##*/}"; then + elif ! git clone -s "$dir" "${dir##*/}"; then error "$(gettext "Failure while creating working copy of %s %s repo")" "${repo}" "git" plain "$(gettext "Aborting...")" exit 1 -- 2.21.0

2 2

[pacman-dev] [PATCH 1/3] doc: describe when and why the prepare function should be used
by Eli Schwartz 19 Mar '19

19 Mar '19

We don't want people to run architecture/OS/makepkg.conf specific processes during prepare() and in fact it's been observed that makepkg by design doesn't even run prepare_buildenv() for it, so the prohibition against this is now baked into makepkg. Reflect this differentiation in the documentation on just what, exactly, a prepare() function is. Signed-off-by: Eli Schwartz <eschwartz(a)archlinux.org> --- This patch coincides with quequotion's clarification of the options=() array, so thanks for inspiring me to write this! I believe that both patches have merit independent of each other. doc/PKGBUILD.5.asciidoc | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/doc/PKGBUILD.5.asciidoc b/doc/PKGBUILD.5.asciidoc index e8ce691f..285627ab 100644 --- a/doc/PKGBUILD.5.asciidoc +++ b/doc/PKGBUILD.5.asciidoc @@ -342,9 +342,12 @@ files into the packaging directory, with optional `prepare()`, `build()`, and *prepare() Function*:: An optional `prepare()` function can be specified in which operations to prepare the sources for building, such as patching, are performed. This - function is run after the source extraction and before the `build()` - function. The `prepare()` function is skipped when source extraction - is skipped. + function is run exactly once, after the source extraction and before the + `build()` function. The `prepare()` function is skipped when source + extraction is skipped. No system-specific or build-specific commands should + be run during `prepare()` under any circumstances, as they are meant to run + exclusively during `build()`, and features like `buildflags` or `makeflags` + are expressly not available. *build() Function*:: The optional `build()` function is use to compile and/or adjust the source -- 2.21.0

2 6