September 2017 - Arch-projects - lists.archlinux.org

[arch-projects] [archweb] Licensing issues with JS code
by Adonay Felipe Nogueira 15 Jan '18

15 Jan '18

Hi all, I have an issue to report. However, please note that I'm not subscribed to this mailing list, so I'd recommend you to Cc me when replying. For a short description of the issue, see: [[https://labs.parabola.nu/issues/1405]] However, we must also note that Archweb is now newer than the Archweb release used by Parabola. Nonethless, as far as I know, each of the files still exist, although some of them don't even have license indication for the site's visitor (this is true for "visualize/static/visualize.js" and "mirrors/static/mirror_status.js"). In case of doubt, I might be able to help with some of the points described in the referenced issue. Respectfully, Adonay. -- - [[https://libreplanet.org/wiki/User:Adfeno]] - Palestrante e consultor sobre /software/ livre (não confundir com gratis). - "WhatsApp"? Ele não é livre, por isso não uso. Iguais a ele prefiro GNU Ring, ou Tox. Quer outras formas de contato? Adicione o vCard que está no endereço acima aos teus contatos. - Pretende me enviar arquivos .doc, .ppt, .cdr, ou .mp3? OK, eu aceito, mas não repasso. Entrego apenas em formatos favoráveis ao /software/ livre. Favor entrar em contato em caso de dúvida.

6 17

[arch-projects] [projects][PATCH] wpa_actiond: Wait for three "failed" PONGs before disconnecting
by Emil Velikov 14 Nov '17

14 Nov '17

When the system is very low on resources, select() may return 0 even when wpa_supplicant is alive and kicking. Don't disconnect as soon at that occurs - wait three times and clearly log it. Signed-off-by: Emil Velikov <emil.l.velikov(a)gmail.com> --- Hi all, Using [projects] since [wpa_actiond] gets kicked by the email filter. Can anyone update the message to include a list of supported tags, or link to an article/wiki with information? Back on topic: This is a small patch I had for 2 months and I thought about getting upstreamed. In particular - on certain workloads my system can get really low on memory (and available fds). With the patch in place, wpa_actiond no longer kills my connection although in practise I never seen two consecutive "wpa_supplicant failed to reply (PONG)" messages. My patch could be completely bonkers, so any suggestions how to address this correctly will be appreciated. --- wpa_actiond.c | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/wpa_actiond.c b/wpa_actiond.c index d60d885..03a9d7f 100644 --- a/wpa_actiond.c +++ b/wpa_actiond.c @@ -292,6 +292,7 @@ static void loop(const char *iface, const char *ctrlpath, const int disconnect_t /* path to control socket */ char *ctrlsock = NULL; int ctrlsocklen; + int pong_failures = 0; ssid[0] = '\0'; old_ssid[0] = '\0'; @@ -359,6 +360,7 @@ static void loop(const char *iface, const char *ctrlpath, const int disconnect_t } logevent(WPA_ACTIOND_LOG_TERMINATE, iface, ""); state = WPA_ACTIOND_STATE_TERMINATED; + pong_failures = 0; break; case 0: if (state == WPA_ACTIOND_STATE_CONNECTION_LOST) { @@ -372,8 +374,15 @@ static void loop(const char *iface, const char *ctrlpath, const int disconnect_t reply_len = 0; reply[reply_len] = '\0'; if(!str_match(reply, "PONG")) { + if (pong_failures <= 3) { + logevent(WPA_ACTIOND_LOG_CUSTOM_ERROR, iface, "wpa_supplicant failed to reply (PONG)"); + pong_failures++; + break; + } + /* supplicant has been terminated */ if(state == WPA_ACTIOND_STATE_CONNECTED || state == WPA_ACTIOND_STATE_CONNECTION_LOST) { + logevent(WPA_ACTIOND_LOG_CUSTOM_ERROR, iface, "wpa_supplicant failed to reply three times in a row - disconnecting"); logevent(WPA_ACTIOND_LOG_DISCONNECTED, iface, ssid); action(WPA_ACTIOND_ACTION_DISCONNECT, iface, ssid, idstr, wpa_ctrl_get_fd(ctrl), script); } @@ -381,6 +390,7 @@ static void loop(const char *iface, const char *ctrlpath, const int disconnect_t state = WPA_ACTIOND_STATE_TERMINATED; } } + pong_failures = 0; break; default: /* event received */ @@ -446,6 +456,7 @@ static void loop(const char *iface, const char *ctrlpath, const int disconnect_t /* we are not interested in this event */ break; } + pong_failures = 0; } } -- 2.14.0

2 4

[arch-projects] [devtools] [GIT] The official devtools repository branch master updated. 20170813-10-gddd508e
by heftig＠archlinux.org 04 Nov '17

04 Nov '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 devtools repository". The branch, master has been updated via ddd508efc083fc9beb6f2c96e2537521b31c1e6f (commit) via 0f3778c3d36028e5c9d4e5ec702c8f167e1cebba (commit) from 6b55282bd702afd9a36409f85d9cb4c608ada5e5 (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 ddd508efc083fc9beb6f2c96e2537521b31c1e6f Author: Jan Alexander Steffens (heftig) <jan.steffens(a)gmail.com> Date: Thu Sep 14 23:31:41 2017 +0200 makechrootpkg: Reopen console to assign the CTTY nspawn does not give us a controlling terminal, hence we ignore interrupts. Apparently this was lost in systemd at some point. Hack around this by reopening the console to make it the controlling terminal. commit 0f3778c3d36028e5c9d4e5ec702c8f167e1cebba Author: Jan Alexander Steffens (heftig) <jan.steffens(a)gmail.com> Date: Thu Sep 14 22:21:47 2017 +0200 makechrootpkg: Prevent collecting coredumps Coredumps from build chroots are not generally useful. Prevent them from being generated. Avoids a lot of annoyance from the GCC testsuite spawning lots of systemd-coredump processes. Just set the soft limit so the user can still raise it in the PKGBUILD if they insist. ----------------------------------------------------------------------- Summary of changes: makechrootpkg.in | 7 +++++++ 1 file changed, 7 insertions(+) hooks/post-receive -- The official devtools repository

3 3

[arch-projects] [devtools][PATCH 1/1] use makepkg library instead of local function copies
by Luke Shumaker 30 Oct '17

30 Oct '17

This mirrors dbscripts commit 625fa02 by Pierre Schmitz <pierre(a)archlinux.de> at 2017-04-18 14:20:49 --- lib/common.sh | 100 ++++------------------------------------------------------ 1 file changed, 7 insertions(+), 93 deletions(-) diff --git a/lib/common.sh b/lib/common.sh index 0fb93d9..a3c2ec2 100644 --- a/lib/common.sh +++ b/lib/common.sh @@ -6,62 +6,21 @@ [[ -z ${_INCLUDE_COMMON_SH:-} ]] || return 0 _INCLUDE_COMMON_SH=true +# shellcheck disable=1091 +. /usr/share/makepkg/util.sh + # Avoid any encoding problems export LANG=C shopt -s extglob # check if messages are to be printed using color -declare ALL_OFF='' BOLD='' BLUE='' GREEN='' RED='' YELLOW='' if [[ -t 2 ]]; then - # prefer terminal safe colored and bold text when tput is supported - if tput setaf 0 &>/dev/null; then - ALL_OFF="$(tput sgr0)" - BOLD="$(tput bold)" - BLUE="${BOLD}$(tput setaf 4)" - GREEN="${BOLD}$(tput setaf 2)" - RED="${BOLD}$(tput setaf 1)" - YELLOW="${BOLD}$(tput setaf 3)" - else - ALL_OFF="\e[1;0m" - BOLD="\e[1;1m" - BLUE="${BOLD}\e[1;34m" - GREEN="${BOLD}\e[1;32m" - RED="${BOLD}\e[1;31m" - YELLOW="${BOLD}\e[1;33m" - fi + colorize +else + # shellcheck disable=2034 + declare -gr ALL_OFF='' BOLD='' BLUE='' GREEN='' RED='' YELLOW='' fi -readonly ALL_OFF BOLD BLUE GREEN RED YELLOW - -plain() { - local mesg=$1; shift - # shellcheck disable=2059 - printf "${BOLD} ${mesg}${ALL_OFF}\n" "$@" >&2 -} - -msg() { - local mesg=$1; shift - # shellcheck disable=2059 - printf "${GREEN}==>${ALL_OFF}${BOLD} ${mesg}${ALL_OFF}\n" "$@" >&2 -} - -msg2() { - local mesg=$1; shift - # shellcheck disable=2059 - printf "${BLUE} ->${ALL_OFF}${BOLD} ${mesg}${ALL_OFF}\n" "$@" >&2 -} - -warning() { - local mesg=$1; shift - # shellcheck disable=2059 - printf "${YELLOW}==> WARNING:${ALL_OFF}${BOLD} ${mesg}${ALL_OFF}\n" "$@" >&2 -} - -error() { - local mesg=$1; shift - # shellcheck disable=2059 - printf "${RED}==> ERROR:${ALL_OFF}${BOLD} ${mesg}${ALL_OFF}\n" "$@" >&2 -} stat_busy() { local mesg=$1; shift @@ -110,51 +69,6 @@ die() { cleanup 255 } -## -# usage : in_array( $needle, $haystack ) -# return : 0 - found -# 1 - not found -## -in_array() { - local needle=$1; shift - local item - for item in "$@"; do - [[ $item = "$needle" ]] && return 0 # Found - done - return 1 # Not Found -} - -## -# usage : get_full_version( [$pkgname] ) -# return : full version spec, including epoch (if necessary), pkgver, pkgrel -## -get_full_version() { - # set defaults if they weren't specified in buildfile - local pkgbase=${pkgbase:-${pkgname[0]}} - local epoch=${epoch:-0} - local pkgver=${pkgver} - local pkgrel=${pkgrel} - if [[ -z $1 ]]; then - if (( ! epoch )); then - printf '%s\n' "$pkgver-$pkgrel" - else - printf '%s\n' "$epoch:$pkgver-$pkgrel" - fi - else - local pkgver_override='' pkgrel_override='' epoch_override='' - for i in pkgver pkgrel epoch; do - local indirect="${i}_override" - eval "$(declare -f "package_$1" | sed -n "s/$^[[:space:]]*$i=$/${i}_override=/p")" - [[ -z ${!indirect} ]] && eval ${indirect}=\"${!i}\" - done - if (( ! epoch_override )); then - printf '%s\n' "$pkgver_override-$pkgrel_override" - else - printf '%s\n' "$epoch_override:$pkgver_override-$pkgrel_override" - fi - fi -} - ## # usage : lock( $fd, $file, $message, [ $message_arguments... ] ) ## -- 2.14.1

4 4

[arch-projects] [devtools] A better sogrep
by Eli Schwartz 02 Oct '17

02 Oct '17

After realizing that the links tarballs are publicly available via soyuz, I've written a version of sogrep that is usable by anyone. Is this useful enough to maybe include here, e.g. together with lddd? https://paste.xinu.at/Vh5uiA/ -- Eli Schwartz

2 2

[arch-projects] [devtools][PATCH 1/1] makechrootpkg: Fix function usage comments
by Luke Shumaker 16 Sep '17

16 Sep '17

A couple of the comments noting which globals are used by functions are outdated/wrong. - download_sources() : Remove USER from the list. It was always wrong. Originally, it should have been SUDO_USER (not USER), but I should have removed it entirely in 4f23609. - move_products() : Add SRCPKGDEST to the list. Though the commit adding the comment was only recently upstreamed (as 2fd5931), it originated in 2013 in a commit that has since been rebased many times. Anyway, in this rebasing, it missed move_products() starting to pay attention to SRCPKGDEST in fd1be1b (since nothing made git think there was a "conflict"). --- makechrootpkg.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/makechrootpkg.in b/makechrootpkg.in index 05826b2..ab6bfb4 100644 --- a/makechrootpkg.in +++ b/makechrootpkg.in @@ -245,7 +245,6 @@ _chrootnamcap() { # Usage: download_sources $copydir $makepkg_user # Globals: # - SRCDEST -# - USER download_sources() { local copydir=$1 local makepkg_user=$2 @@ -267,6 +266,7 @@ download_sources() { # Globals: # - PKGDEST # - LOGDEST +# - SRCPKGDEST move_products() { local copydir=$1 local src_owner=$2 -- 2.14.1

1 0

[arch-projects] [devtools] [PATCH 1/2] makechrootpkg: Fix unconditionally running namcap
by Eli Schwartz 16 Sep '17

16 Sep '17

Fixes regression in 49088b0860276c664933c2b3e36a2fef714b7a07 $run_namcap will always be set to "" `if $not_a_var; then ...; fi` is always truthful when $not_a_var is unset or equal to "" and the `then` clause will always be run. I'm not entirely sure why everything had to be moved into functions purely for the sake of being moved into functions, as it goes against the general theme of devtools/makepkg/etc. especially since it doesn't seem to have been thoroughly tested. I'm also not sure why global state variables need to be cloned locally for their sole explicit purpose. But for now this patch implements the minimum necessary work to properly pass the "do I want namcap" variable into prepare_chroot() according to the current logic flow. Note that I have still not thorougly tested makechrootpkg. Signed-off-by: Eli Schwartz <eschwartz(a)archlinux.org> --- makechrootpkg.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/makechrootpkg.in b/makechrootpkg.in index 664f9f6..b1c9545 100644 --- a/makechrootpkg.in +++ b/makechrootpkg.in @@ -403,7 +403,7 @@ main() { download_sources "$copydir" "$makepkg_user" - prepare_chroot "$copydir" "$USER_HOME" "$keepbuilddir" + prepare_chroot "$copydir" "$USER_HOME" "$keepbuilddir" "$run_namcap" if arch-nspawn "$copydir" \ --bind="$PWD:/startdir" \ -- 2.14.1

3 10

[arch-projects] [devtools] [GIT] The official devtools repository branch master updated. 20170813-8-g6b55282
by heftig＠archlinux.org 12 Sep '17

12 Sep '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 devtools repository". The branch, master has been updated via 6b55282bd702afd9a36409f85d9cb4c608ada5e5 (commit) from 6a7dcdeff9dee3c3b1192e61ad8e5a58f2215db0 (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 6b55282bd702afd9a36409f85d9cb4c608ada5e5 Author: Jan Alexander Steffens (heftig) <jan.steffens(a)gmail.com> Date: Wed Sep 13 00:25:06 2017 +0200 Revert "arch-nspawn: Hack to give the inner process a controlling terminal" Whoops, this will of course mess with nspawn arguments passed to arch-nspawn. ----------------------------------------------------------------------- Summary of changes: arch-nspawn.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- The official devtools repository

1 0

[arch-projects] [devtools] [GIT] The official devtools repository branch master updated. 20170813-7-g6a7dcde
by heftig＠archlinux.org 12 Sep '17

12 Sep '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 devtools repository". The branch, master has been updated via 6a7dcdeff9dee3c3b1192e61ad8e5a58f2215db0 (commit) via cd500d161fc174841486c6f204ae81d450086e92 (commit) from 5ebb9c16c055747e0501ac58b4cb05c20b8f7439 (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 6a7dcdeff9dee3c3b1192e61ad8e5a58f2215db0 Author: Jan Alexander Steffens (heftig) <jan.steffens(a)gmail.com> Date: Wed Sep 13 00:08:30 2017 +0200 arch-nspawn: Hack to give the inner process a controlling terminal This was lost at some point. commit cd500d161fc174841486c6f204ae81d450086e92 Author: Jan Alexander Steffens (heftig) <jan.steffens(a)gmail.com> Date: Tue Sep 12 23:26:34 2017 +0200 arch-nspawn: Pass --as-pid2 As not all commands we run are capable of reaping processes correctly. For example, pacman is not. ----------------------------------------------------------------------- Summary of changes: arch-nspawn.in | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) hooks/post-receive -- The official devtools repository

1 0

[arch-projects] [devtools] [GIT] The official devtools repository tag 20170911 created. 20170813-5-g5ebb9c1
by seblu＠archlinux.org 11 Sep '17

11 Sep '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 devtools repository". The tag, 20170911 has been created at 5ebb9c16c055747e0501ac58b4cb05c20b8f7439 (commit) - Log ----------------------------------------------------------------- commit 5ebb9c16c055747e0501ac58b4cb05c20b8f7439 Author: Sébastien Luttringer <seblu(a)seblu.net> Date: Mon Sep 11 21:26:07 2017 +0200 Version 20170911 ----------------------------------------------------------------------- hooks/post-receive -- The official devtools repository

1 0