- Arch-projects - lists.archlinux.org

[arch-projects] [netctl] [GIT] Network control utility based on systemd branch master updated. 1.16-5-g4be6904
by Jouke Witteveen 26 Jun '18

26 Jun '18

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 "Network control utility based on systemd". The branch, master has been updated via 4be6904e2518b5b13675439d6b89592e6bb4a6e3 (commit) via 580f80add61423343d8ec35363a5eab39989d104 (commit) via e4638274ac7f84b749cdcbd8e93f06a5564280e7 (commit) from 1ae84f054368f012ffa3b70b873e24c35767f4d3 (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 4be6904e2518b5b13675439d6b89592e6bb4a6e3 Author: Jouke Witteveen <j.witteveen(a)gmail.com> Date: Tue Jun 26 18:26:13 2018 +0200 1.17 release updates commit 580f80add61423343d8ec35363a5eab39989d104 Author: Jouke Witteveen <j.witteveen(a)gmail.com> Date: Tue Jun 26 17:58:34 2018 +0200 Small documentation updates commit e4638274ac7f84b749cdcbd8e93f06a5564280e7 Author: Jouke Witteveen <j.witteveen(a)gmail.com> Date: Sat Jun 23 13:14:25 2018 +0200 wifi-menu: Support UTF-8 encoded SSIDs (FS#45384) Strictly speaking, we should check with the SSIDEncoding value sent out by the station, as specified in the 2012 version of 802.11 (page 566), but wpa_supplicant does not (yet) expose this information and stations may not set the field to UTF-8 and still encode their SSID accordingly. We therefore assume SSIDs to be UTF-8 encoded (the only real alternative is treating SSIDs as raw byte string) in wifi-menu. Note that wifi-menu is only provided as a convenience and many/most use cases involve writing profile files manually. When the current character map is not set to UTF-8, wifi-menu will only use ASCII characters in its screen output. This can be forced using for example `LC_CTYPE=C wifi-menu`. Thanks to Declspeck <declspeck(a)declblog.com> for their activity on the Flyspray task. ----------------------------------------------------------------------- Summary of changes: Makefile | 2 +- NEWS | 4 ++++ docs/netctl.profile.5.txt | 10 ++++++---- src/wifi-menu | 46 +++++++++++++++++++++++++++++++++------------- 4 files changed, 44 insertions(+), 18 deletions(-) hooks/post-receive -- Network control utility based on systemd

1 0

[arch-projects] [netctl] [PATCH] wifi-menu: Support UTF-8 encoded SSIDs (FS#45384)
by Jouke Witteveen 26 Jun '18

26 Jun '18

Strictly speaking, we should check with the SSIDEncoding value sent out by the station, as specified in the 2012 version of 802.11 (page 566), but wpa_supplicant does not (yet) expose this information and stations may not set the field to UTF-8 and still encode their SSID accordingly. We therefore assume SSIDs to be UTF-8 encoded (the only real alternative is treating SSIDs as raw byte string) in wifi-menu. Note that wifi-menu is only provided as a convenience and many/most use cases involve writing profile files manually. When the current character map is not set to UTF-8 , wifi-menu will only use ASCII characters in its screen output. This can be forced using for example `LC_CTYPE=C wifi-menu`. --- src/wifi-menu | 40 ++++++++++++++++++++++++++++++---------- 1 file changed, 30 insertions(+), 10 deletions(-) diff --git a/src/wifi-menu b/src/wifi-menu index 42c4c53..525830f 100755 --- a/src/wifi-menu +++ b/src/wifi-menu @@ -20,6 +20,11 @@ Arguments: END } +# Undo printf escaping in $1 +printf_decode() { + printf -- "${1//%/%%}" +} + # Prepare $1 for use in a special quoting context quote_safe() { if [[ "$1" = \"* ]]; then @@ -38,6 +43,9 @@ init_profiles() { unset Interface ESSID source "$PROFILE_DIR/$profile" > /dev/null if [[ "$Interface" = "$1" && -n "$ESSID" ]]; then + if [[ "$ESSID" = \"\"*\" ]]; then + ESSID=${ESSID:2:-1} + fi printf "%s" "$ESSID" if [[ "$Description" =~ "Automatically generated" ]]; then return 2 @@ -62,14 +70,19 @@ init_profiles() { # Build ENTRIES as an argument list for dialog based on scan results in $1 init_entries() { - local i=0 sep=$'\t' flags signal ssid + local i=0 sep=$'\t' decoded flags signal ssid while IFS=$'\t' read -r signal flags ssid; do + decoded=$(printf_decode "$ssid") ENTRIES[i++]="--" # the SSID might look like an option to dialog - ENTRIES[i++]=$ssid - if is_yes "${CONNECTED:-no}" && [[ "$ssid" = "$CONNECTION" ]]; then + if [[ "$CHARMAP" = "UTF-8" ]]; then + ENTRIES[i++]=$decoded + else + ENTRIES[i++]=$ssid + fi + if is_yes "${CONNECTED:-no}" && [[ "$decoded" = "$CONNECTION" ]]; then ENTRIES[i]="*" # Currently connected - elif in_array "$ssid" "${ESSIDS[@]}"; then - if in_array "$(ssid_to_profile "$ssid")" "${GENERATED[@]}"; then + elif in_array "$decoded" "${ESSIDS[@]}"; then + if in_array "$(ssid_to_profile "$decoded")" "${GENERATED[@]}"; then ENTRIES[i]="." # Automatically generated else ENTRIES[i]=":" # Handmade @@ -115,11 +128,14 @@ Do you want to overwrite it?" # Create a profile for ssid $1 create_profile() { - local box flags key msg security - PROFILE="$INTERFACE-${1//\//_}" + local box flags key msg security signal ssid + PROFILE=$(iconv -c -f UTF-8 -t //TRANSLIT <<< "$1") + PROFILE="$INTERFACE-${PROFILE//[?\/]/_}" [[ -e "$PROFILE_DIR/$PROFILE" ]] && PROFILE+=".wifi-menu" confirm_profile || return $? - flags=$(grep -m 1 $'\t'"$1\$" "$NETWORKS" | cut -f 2) + while IFS=$'\t' read -r signal flags ssid; do + [[ "$(printf_decode "$ssid")" != "$1" ]] || break + done < "$NETWORKS" if [[ "$flags" =~ WPA|WEP ]]; then security=${BASH_REMATCH[0],,} else @@ -221,6 +237,8 @@ ensure_root "$(basename "$0")" if ! type dialog &> /dev/null; then exit_error "Please install 'dialog' to use wifi-menu" fi +CHARMAP=$(locale charmap) +cd / # We do not want to spawn anything that can block unmounting INTERFACE=$1 if [[ -z "$INTERFACE" ]]; then @@ -237,7 +255,6 @@ elif ! is_interface "$INTERFACE"; then fi load_interface_config "$INTERFACE" -cd / # We do not want to spawn anything that can block unmounting if [[ "$RFKill" && "$(rf_status "$INTERFACE" "$RFKill")" ]]; then if ! rf_enable "$INTERFACE" "$RFKill"; then exit_error "Could not unblock transmission on interface '$INTERFACE'" @@ -247,7 +264,7 @@ fi echo -n "Scanning for networks... " if CONNECTION=$(wpa_call "$INTERFACE" status 2> /dev/null | grep -m 1 "^ssid="); then - CONNECTION=${CONNECTION#ssid=} + CONNECTION=$(printf_decode "${CONNECTION#ssid=}") CONNECTED=yes fi NETWORKS=$(wpa_supplicant_scan "$INTERFACE" 3,4,5) @@ -270,6 +287,9 @@ Flags description: CHOICE=$(dialog --menu "$MSG" 24 50 12 "${ENTRIES[@]}" --stdout) RETURN=$? if (( RETURN == 0 )); then + if [[ "$CHARMAP" != "UTF-8" ]]; then + CHOICE=$(printf_decode "$CHOICE") + fi connect_to_ssid "$CHOICE" RETURN=$? fi -- 2.18.0

2 3

[arch-projects] [netctl] [PATCH] Simplify init_profiles() implementation
by Emil Velikov 26 Jun '18

26 Jun '18

From: Emil Velikov <emil.velikov(a)collabora.com> Currently each profile is handles in two stages: - a unique value is returned for a set of patterns matches - depending on the value the profile/essid is added to global lists A shorter and simpler solution is to omit the unnecessary value passing/processing all together. Cc: Jouke Witteveen <j.witteveen(a)gmail.com> Signed-off-by: Emil Velikov <emil.l.velikov(a)gmail.com> --- Jouke, let me know if you'd like this rebased on top of your patch. Pardon if you're getting this twice. The initial submission was rejected by the ML :-\ --- src/wifi-menu | 40 ++++++++++++++-------------------------- 1 file changed, 14 insertions(+), 26 deletions(-) diff --git a/src/wifi-menu b/src/wifi-menu index 42c4c53..928cf5e 100755 --- a/src/wifi-menu +++ b/src/wifi-menu @@ -29,34 +29,22 @@ quote_safe() { fi } -# Fill PROFILES and ESSIDS with the profile names and essids of the profiles -# for interface $1 +# Fill GENERATED, PROFILES and ESSIDS with the profile names and essids of the +# profiles for interface $1 init_profiles() { - local i=0 essid profile + local i=0 profile while IFS= read -r profile; do - essid=$( - unset Interface ESSID - source "$PROFILE_DIR/$profile" > /dev/null - if [[ "$Interface" = "$1" && -n "$ESSID" ]]; then - printf "%s" "$ESSID" - if [[ "$Description" =~ "Automatically generated" ]]; then - return 2 - else - return 1 - fi - fi - return 0 - ) - case $? in - 2) - GENERATED+=("$profile") - ;& - 1) - PROFILES[i]=$profile - ESSIDS[i]=$essid - (( ++i )) - ;; - esac + unset Interface ESSID + source "$PROFILE_DIR/$profile" > /dev/null + if [[ "$Interface" != "$1" || -z "$ESSID" ]]; then + continue; + fi + if [[ "$Description" =~ "Automatically generated" ]]; then + GENERATED+=("$profile") + fi + PROFILES[i]=$profile + ESSIDS[i]=$ESSID + (( ++i )) done < <(list_profiles) } -- 2.18.0

2 2

[arch-projects] [dbscripts] [PATCH 0/5] Be less tightly coupled with SVN
by Luke Shumaker 24 Jun '18

24 Jun '18

From: Luke Shumaker <lukeshu(a)parabola.nu> This patchset is intended to clean up dbscripts' interaction with SVN. Besides (IMO) improved code clarity, this should make it easier for those who wish to replace SVN with something else. There are two major themes here: 1. Avoid asking SVN for information; to the extent possible, get all information directly from the pacman repos. 2. Isolate SVN-interfacing code in to functions; making it clear what interfaces the PKGBUILD tracking needs to provide. This does not touch the test suite, which is still firmly SVN-dependent. I've cc'd Florian Pritz because of his related work on migrating to git. https://wiki.archlinux.org/index.php/User:Bluewind/dbscripts-rewrite Luke Shumaker (5): db-move, db-remove: Don't parse PKGBUILD files db-move: Clarify the flow of the preflight check testing2x: Discover correct repos based on the DBEXT files, not SVN Centralize all SVN access into 'abs_*' functions in a new 'db-abs' file db-move, db-abs: Simplify the abs_move_* functions cron-jobs/sourceballs | 4 +- db-abs | 114 ++++++++++++++++++++++++++++++++++++++++++ db-functions | 61 +++++++++++++++------- db-move | 95 +++++++++-------------------------- db-remove | 18 ++----- testing2x | 40 +++++++-------- 6 files changed, 204 insertions(+), 128 deletions(-) create mode 100644 db-abs -- 2.17.1

2 8

[arch-projects] [netctl] [GIT] Network control utility based on systemd branch master updated. 1.16-2-g1ae84f0
by Jouke Witteveen 23 Jun '18

23 Jun '18

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 "Network control utility based on systemd". The branch, master has been updated via 1ae84f054368f012ffa3b70b873e24c35767f4d3 (commit) via 8c873b494c4df5c64af64aa6b1abb898d9a5301f (commit) from dbc32d470420396f4af360af9ac17680fe99b368 (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 1ae84f054368f012ffa3b70b873e24c35767f4d3 Author: Jouke Witteveen <j.witteveen(a)gmail.com> Date: Sat Jun 23 12:51:29 2018 +0200 Code and comments streamlining commit 8c873b494c4df5c64af64aa6b1abb898d9a5301f Author: Jouke Witteveen <j.witteveen(a)gmail.com> Date: Sat Jun 23 12:41:51 2018 +0200 Improved handling of exposed variables Hooks can now tell the command to be executed by looking at $Command. The value will be "start", "stop", or "" (undefined), depending on the reason a profile is being sourced. ----------------------------------------------------------------------- Summary of changes: src/lib/connections/ethernet | 11 ++++------- src/lib/globals | 1 + src/lib/network | 3 ++- src/lib/wpa | 23 ++++++++--------------- src/wifi-menu | 34 +++++++++++++++++----------------- 5 files changed, 32 insertions(+), 40 deletions(-) hooks/post-receive -- Network control utility based on systemd

1 0

[arch-projects] [dbscripts] [PATCH v2 0/6] Be less tightly coupled with SVN
by Luke Shumaker 22 Jun '18

22 Jun '18

From: Luke Shumaker <lukeshu(a)parabola.nu> This patchset is intended to clean up dbscripts' interaction with SVN. Besides (IMO) improved code clarity, this should make it easier for those who wish to replace SVN with something else. There are two major themes here: 1. Avoid asking SVN for information; to the extent possible, get all information directly from the pacman repos. 2. Isolate SVN-interfacing code in to functions; making it clear what interfaces the PKGBUILD tracking needs to provide. This does not touch the test suite, which is still firmly SVN-dependent. I've cc'd Florian Pritz because of his related work on migrating to git. https://wiki.archlinux.org/index.php/User:Bluewind/dbscripts-rewrite v2: - Add a test to verify that db-move works with single-arch packages; which was broken in v1 of this patchset - Don't break db-move with single-arch packages Luke Shumaker (6): test: db-move: Verify that it works on single-arch packages db-move, db-remove: Don't parse PKGBUILD files db-move: Clarify the flow of the preflight check testing2x: Discover correct repos based on the DBEXT files, not SVN Centralize all SVN access into 'abs_*' functions in a new 'db-abs' file db-move, db-abs: Simplify calling the abs_move_* functions cron-jobs/sourceballs | 4 +- db-abs | 114 ++++++++++++++++++++++++++++++++++++++++ db-functions | 61 ++++++++++++++------- db-move | 92 ++++++++------------------------ db-remove | 18 ++----- test/cases/db-move.bats | 19 +++++++ testing2x | 40 ++++++-------- 7 files changed, 222 insertions(+), 126 deletions(-) create mode 100644 db-abs -- 2.17.1

1 6

[arch-projects] [dbscripts] Expected behavior of db-remove?
by Luke Shumaker 20 Jun '18

20 Jun '18

From: Luke Shumaker <lukeshu(a)parabola.nu> Following is a test-case for db-remove demonstrating a case where I'm not sure what the intended behavior is. Note that the test-case is identical to the existing "remove multiple packages" test-case, except that 'pkg-single-arch' has been added to the pkgs=() array. With pacman 5.0, the test-case would have passed, but with pacman 5.1, the test-case fails. With the pacman 5.1 version of repo-remove, if any of the named packages are not found, the entire transaction is aborted, and *no* packages are removed. With 5.0, it would have said "error", but still proceeded to remove the other named packages. So, in my test-case, because 'pkg-single-arch' is an x86_64 only package (while the others are x86_64 and i686), db-remove succeeds on x86_64, but fails to remove anything on i686 because pkg-single-arch isn't present there. Also note that despite saying "ERROR" and failing to do anything, db-remove has a 0 exit-code; the test-case failure doesn't happen until it calls checkRemovedPackage. So, what's the desired behavior here? Ignore packages that are already missing from the repo, or abort if any of the named packages aren't found? --- test/cases/db-remove.bats | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/test/cases/db-remove.bats b/test/cases/db-remove.bats index fe373bc..d72c9cf 100644 --- a/test/cases/db-remove.bats +++ b/test/cases/db-remove.bats @@ -44,6 +44,27 @@ load ../lib/common done } +@test "remove multiple packages - some single arch" { + local arches=('i686' 'x86_64') + local pkgs=('pkg-simple-a' 'pkg-simple-b' 'pkg-split-a' 'pkg-split-b' 'pkg-simple-epoch' 'pkg-single-arch') + local pkgbase + local arch + + for pkgbase in ${pkgs[@]}; do + releasePackage extra ${pkgbase} + done + + db-update + + for arch in ${arches[@]}; do + db-remove extra ${arch} ${pkgs[@]} + done + + for pkgbase in ${pkgs[@]}; do + checkRemovedPackage extra ${pkgbase} + done +} + @test "remove any packages" { local pkgs=('pkg-any-a' 'pkg-any-b') local pkgbase -- Happy hacking, ~ Luke Shumaker

1 0

[arch-projects] [dbscripts] [GIT] Official repo DB scripts branch pacman-git deleted. 20131102-88-g2c68135
by eschwartz＠archlinux.org 19 Jun '18

19 Jun '18

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 "Official repo DB scripts". The branch, pacman-git has been deleted was 2c68135f4ab9db048db460bc949322ad7bb418eb - Log ----------------------------------------------------------------- 2c68135f4ab9db048db460bc949322ad7bb418eb pacman 5.1 compatibility ----------------------------------------------------------------------- hooks/post-receive -- Official repo DB scripts

1 0

[arch-projects] [dbscripts] [GIT] Official repo DB scripts branch master updated. 20131102-89-g05dd9be
by eschwartz＠archlinux.org 19 Jun '18

19 Jun '18

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 "Official repo DB scripts". The branch, master has been updated via 05dd9be0db06d7f7cea0eff9f9f6f1993eb6d463 (commit) via 2c68135f4ab9db048db460bc949322ad7bb418eb (commit) from 656fd6d5d8f455492b1e51add9e6e1da8f911a7c (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 05dd9be0db06d7f7cea0eff9f9f6f1993eb6d463 Author: Eli Schwartz <eschwartz(a)archlinux.org> Date: Mon May 28 19:45:15 2018 -0400 test: BUILDDIR must be owned by build user pacman 5.1 enforces this restriction. OTOH it is a simpler setup to set this as the user homedir directly in account creation (just like makechrootpkg has always done) than to create an additional, world-writable, directory. dockerfile: don't use tmpfs for /build ----------------------------------------------------------------------- Summary of changes: Makefile | 2 +- test/Dockerfile | 3 +-- test/lib/common.bash | 9 ++++----- 3 files changed, 6 insertions(+), 8 deletions(-) hooks/post-receive -- Official repo DB scripts

1 0

[arch-projects] [dbscripts] [PATCH v2] test: Fix typoed variables
by Luke Shumaker 16 Jun '18

16 Jun '18

From: Luke Shumaker <lukeshu(a)parabola.nu> - ftpdir-cleanup: ${pkg[0]} -> ${pkgs[0]} This mistake was introduced in 7628525156110022fa70ad91e4bc13ee8a3cceb0 - test: common.bash: $pkgarches[@] -> ${pkgarches[@]} This mistake was introduced in 7628525156110022fa70ad91e4bc13ee8a3cceb0 --- Per Eli's request, I've squashed 2 previously separate commits together to form this. test/cases/ftpdir-cleanup.bats | 2 +- test/lib/common.bash | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/test/cases/ftpdir-cleanup.bats b/test/cases/ftpdir-cleanup.bats index 8c713c6..74215d0 100644 --- a/test/cases/ftpdir-cleanup.bats +++ b/test/cases/ftpdir-cleanup.bats @@ -111,7 +111,7 @@ __checkRepoRemovedPackage() { ftpdir-cleanup for arch in ${arches[@]}; do - __checkRepoRemovedPackage extra ${pkg[0]} ${arch} + __checkRepoRemovedPackage extra ${pkgs[0]} ${arch} done checkRemovedPackage extra ${pkgs[0]} diff --git a/test/lib/common.bash b/test/lib/common.bash index 36c735f..b82643e 100644 --- a/test/lib/common.bash +++ b/test/lib/common.bash @@ -273,7 +273,7 @@ checkRemovedPackageDB() { if [[ ${pkgarches[@]} == any ]]; then tarches=(${ARCHES[@]}) else - tarches=($pkgarches[@]) + tarches=(${pkgarches[@]}) fi for db in ${DBEXT} ${FILESEXT}; do -- 2.17.1

1 0