January 2018 - Arch-projects - lists.archlinux.org

[arch-projects] [mkinitcpio] [PATCH] --rsyncable option
by Charles Duffy 16 Dec '18

16 Dec '18

At present, mkinitcpio outputs are not particularly stable: Generating two consecutive initramfs images from the same inputs can generate archives which are quite entirely unlike each other from the perspective of binary diff tools (rsync, casync, rdiff-backup, xdelta, etc). Making some adjustments to compression and archival can greatly reduce the size of this delta. A ticket with a proposed patch (adding a --rsyncable option to mkinitcpio) has been opened at https://bugs.archlinux.org/task/56128 -- however, as the advice there has been to consult this mailing list, it may no longer be open as of this writing. :) The change consists of the following: - Sort the list of files (in the C locale) before passing it to cpio. - When --rsyncable is passed, set all datestamps to the UNIX epoch before generating the cpio archive. - When --rsyncable is passed, pass the --reproducible option to cpio (this creates a dependency on GNU cpio 2.12, prevents device numbers from being included in the archive, and renumbers inode numbers to be consistent when file ordering is unchanged). - When --rsyncable is passed, pass the --rsyncable and --no-name options to gzip (the former tells it to reset the compression table on occasion, sacrificing compression ratio to prevent the effect from changes from cascading throughout too much of the stream; the latter prevents name and timestamp data from being stored in the gzip header itself). A version of the patch squashing together the two commits already present on the ticket is attached.

1 1

[arch-projects] [PATCH] [namcap] Treat all non-tar files as PKGBUILD files, regardless of filename
by Luke Shumaker 16 Apr '18

16 Apr '18

From: Luke Shumaker <lukeshu(a)parabola.nu> https://bugs.archlinux.org/task/57193 If the user mistakenly passes in some other (non-package, non-PKGBUILD) file, instead of refusing to process it (saying "Error: Cannot process ${filename}"), it will now try to parse it as a PKGBUILD, probably encounter and print at least one error, but finally say "Error: ${filename} is not a valid PKGBUILD". This is actually probably *more* helpful to a confused user who passed in the wrong file. --- namcap.py | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/namcap.py b/namcap.py index b62a2fa..fd62d3c 100755 --- a/namcap.py +++ b/namcap.py @@ -248,9 +248,7 @@ for package in packages: if os.path.isfile(package) and tarfile.is_tarfile(package): process_realpackage(package, active_modules) - elif package.endswith('PKGBUILD'): + else: process_pkgbuild(package, active_modules) - else: - print("Error: Cannot process %s" % package) # vim: set ts=4 sw=4 noet: -- 2.15.1

3 3

[arch-projects] [devtools] [GIT] The official devtools repository branch bpiotrowski/debug created. 20171108-13-g73b9f7b
by bpiotrowski＠archlinux.org 29 Jan '18

29 Jan '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 "The official devtools repository". The branch, bpiotrowski/debug has been created at 73b9f7bfccf277e45f921920cc53d1cfb1331ca7 (commit) - Log ----------------------------------------------------------------- commit 73b9f7bfccf277e45f921920cc53d1cfb1331ca7 Author: Bartłomiej Piotrowski <bpiotrowski(a)archlinux.org> Date: Tue Jan 23 09:46:05 2018 +0100 commitpkg: Use printf format strings for messages about debug packages commit 8455bb165969cccbdb823f3023417ad36299e83b Author: Bartłomiej Piotrowski <bpiotrowski(a)archlinux.org> Date: Mon Jan 15 17:28:17 2018 +0100 commitpkg: Warn about missing debug packages commit 1b9cca80d4ca55f7712dbcaa02172e0d920197cc Author: dequis <dx(a)dxzone.com.ar> Date: Sun Mar 12 21:15:49 2017 -0300 commitpkg: Fix typo in debug package check commit c47fd11bab81f34f62e2e067e5e497cd862e434f Author: Allan McRae <allan(a)archlinux.org> Date: Sun Mar 12 19:20:48 2017 -0300 commitpkg: Upload debug packages if available Debug packages are uploaded to staging/$repo-debug ----------------------------------------------------------------------- hooks/post-receive -- The official devtools repository

1 0

[arch-projects] [archweb] Origin of konami.js
by Luke Shumaker 28 Jan '18

28 Jan '18

Hi Dan, I'm sorry to bother you. In archweb commit bec4e79 (2013-02-09), you added `sitestatic/konami.min.js`. It is apparently https://github.com/snaptortoise/konami-js commit ec0f686 run through UglifyJS 2.2, but with a few modifications (below) made first. Would it be correct to assume that you are the author of those modifications? If so, would you consent to re-licensing the modifications to be under the MIT license; reflecting the upstream license change in konami-js?? --- diff a/konami.js b/konami.js --- a/konami.js +++ b/konami.js @@ -56,7 +56,7 @@ load: function(link){ this.orig_keys = this.keys; konami.addEvent(document,"touchmove",function(e){ - if(e.touches.length == 1 && konami.iphone.capture==true){ + if(e.touches.length == 1 && konami.iphone.capture===true){ var touch = e.touches[0]; konami.iphone.stop_x = touch.pageX; konami.iphone.stop_y = touch.pageY; @@ -66,7 +66,7 @@ } }); konami.addEvent(document,"touchend",function(evt){ - if (konami.iphone.tap==true) konami.iphone.check_direction(link); + if (konami.iphone.tap===true) konami.iphone.check_direction(link); },false); konami.addEvent(document,"touchstart", function(evt){ konami.iphone.start_x = evt.changedTouches[0].pageX @@ -76,12 +76,12 @@ }); }, check_direction: function(link){ - x_magnitude = Math.abs(this.start_x-this.stop_x) - y_magnitude = Math.abs(this.start_y-this.stop_y) - x = ((this.start_x-this.stop_x) < 0) ? "RIGHT" : "LEFT"; - y = ((this.start_y-this.stop_y) < 0) ? "DOWN" : "UP"; - result = (x_magnitude > y_magnitude) ? x : y; - result = (this.tap==true) ? "TAP" : result; + var x_magnitude = Math.abs(this.start_x-this.stop_x) + var y_magnitude = Math.abs(this.start_y-this.stop_y) + var x = ((this.start_x-this.stop_x) < 0) ? "RIGHT" : "LEFT"; + var y = ((this.start_y-this.stop_y) < 0) ? "DOWN" : "UP"; + var result = (x_magnitude > y_magnitude) ? x : y; + result = (this.tap===true) ? "TAP" : result; if (result==this.keys[0]) this.keys = this.keys.slice(1,this.keys.length) if (this.keys.length==0) { -- Happy hacking, ~ Luke Shumaker

2 1

[arch-projects] [namcap] possibility to use renamed PKGBUILD files
by ashark＠linuxcomp.ru 25 Jan '18

25 Jan '18

4 8

[arch-projects] [devtools] [PATCH 1/2] Revert "arch-nspawn: Work around pacman master returning file-URLs from the cache"
by Eli Schwartz 23 Jan '18

23 Jan '18

This reverts commit eb6b0e3f11279b6512b1469ff042d2982eaaeef4. This never worked, as pacman-git returns file urls from the cache anyway and pacman stable doesn't have any problem at all. Having useless code which makes people think the issue is solved when it really isn't, is bloat, so remove it. Signed-off-by: Eli Schwartz <eschwartz(a)archlinux.org> --- arch-nspawn.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch-nspawn.in b/arch-nspawn.in index 7a7a274..50ce674 100644 --- a/arch-nspawn.in +++ b/arch-nspawn.in @@ -59,7 +59,7 @@ else fi # shellcheck disable=2016 -host_mirror=$(pacman --cachedir /doesnt/exist -Sddp extra/devtools 2>/dev/null | sed -r 's#(.*/)extra/os/.*#\1$repo/os/$arch#') +host_mirror=$(pacman -Sddp extra/devtools 2>/dev/null | sed -r 's#(.*/)extra/os/.*#\1$repo/os/$arch#') # shellcheck disable=2016 [[ $host_mirror == *file://* ]] && host_mirror_path=$(echo "$host_mirror" | sed -r 's#file://(/.*)/\$repo/os/\$arch#\1#g') -- 2.16.1

1 1

[arch-projects] [devtools] [GIT] The official devtools repository branch master updated. 20171108-9-g38c7a39
by bpiotrowski＠archlinux.org 23 Jan '18

23 Jan '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 "The official devtools repository". The branch, master has been updated via 38c7a391b043547b946a99731a56a233458ba7a2 (commit) via 75ad2aca572d36c4df1b07153e2403534fbd89ed (commit) via aee72cae3231811058d6993d71f97e449e477d8f (commit) via 5ab8f8430a2c865656cd800c03ac21cb17a86d3c (commit) via c9e287e845973e4c04e21fc513caaea4907e604e (commit) via 48b2f8dcc49d88e60bd9e4ee97c92fea8ac90721 (commit) via 3b725b58434b92e93ff90164fae8d76c4761706a (commit) from 7a3c5085017987b6ef934cf9d9b098b4994ba21a (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 38c7a391b043547b946a99731a56a233458ba7a2 Author: Bartłomiej Piotrowski <bpiotrowski(a)archlinux.org> Date: Sun Jan 21 14:18:43 2018 +0100 makechrootpkg: make sure that makepkg.conf is always parsed as text commit 75ad2aca572d36c4df1b07153e2403534fbd89ed Author: Luke Shumaker <lukeshu(a)parabola.nu> Date: Mon Jan 15 17:57:00 2018 +0100 makechrootpkg: Adjust to work properly with `set -e` This worked properly until eab5aba. commit aee72cae3231811058d6993d71f97e449e477d8f Author: Luke Shumaker <lukeshu(a)parabola.nu> Date: Mon Jan 15 17:57:00 2018 +0100 lib/common.sh: Adjust to work properly with `set -u` Support for working with `set -u` was broken by 94160d6. Egg on my face; I'm the one who wants `set -u` support, and I'm the author of that commit! libmakepkg does not work with `set -u`; but mostly because of the include guards! So we just need to temporarily disable `set -u` (nounset) while loading libmakepkg. Instead of introducing a new variable, just store the initial nounset status in _INCLUDE_COMMON_SH; rather than a useless fixed-string "true". While we're at it, disable POSIX-mode (just in case we're running as "sh" instead of "bash"), since libmakepkg uses bash-isms that won't parse in POSIX mode. commit 5ab8f8430a2c865656cd800c03ac21cb17a86d3c Author: Luke Shumaker <lukeshu(a)parabola.nu> Date: Mon Jan 15 17:57:00 2018 +0100 arch-nspawn: Remove pointless $(echo ...) subshell commit c9e287e845973e4c04e21fc513caaea4907e604e Author: Luke Shumaker <lukeshu(a)parabola.nu> Date: Mon Jan 15 17:57:00 2018 +0100 arch-nspawn: make sure that makepkg.conf is always parsed as text https://lists.parabola.nu/pipermail/dev/2017-June/005576.html commit 48b2f8dcc49d88e60bd9e4ee97c92fea8ac90721 Author: Eli Schwartz <eschwartz(a)archlinux.org> Date: Sun Sep 3 03:53:40 2017 -0400 makechrootpkg: Fix anti-pattern when checking for enabled features Don't use error-prone logic e.g. foo=true; if $foo ... This completely fails to act as expected when the variable is unset because of unrelated bugs. While this merely causes the default behavior to be "false" rather than "true" in such cases, it is better to fail to enable explicitly requested behavior (which will be noticed by the user) than to simply upgrade to this behavior for free (which may not seem to have any obvious cause). Signed-off-by: Eli Schwartz <eschwartz(a)archlinux.org> commit 3b725b58434b92e93ff90164fae8d76c4761706a Author: Eli Schwartz <eschwartz(a)archlinux.org> Date: Sun Sep 3 03:53:39 2017 -0400 makechrootpkg: Fix unconditionally running namcap Fixes regression in 2fd5931a8c67289a8a4acd327b3ce99a5d64c8c7 $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 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> ----------------------------------------------------------------------- Summary of changes: arch-nspawn.in | 4 ++-- lib/common.sh | 4 +++- makechrootpkg.in | 10 +++++----- 3 files changed, 10 insertions(+), 8 deletions(-) hooks/post-receive -- The official devtools repository

1 0

[arch-projects] [devtools] [PATCH 0/7] Backports from Parabola v20180103
by Luke Shumaker 21 Jan '18

21 Jan '18

From: Luke Shumaker <lukeshu(a)parabola.nu> These are the commits in Parabola's developer tools v20180103 that are not in upstream devtools that I think are upstreamable. There's no real theme to them. Some of theme have been seen on this mailing list before. (I appologize that I waited 2 weeks to send this; I didn't send it right away, then I forgot.) Eli Schwartz (2): makechrootpkg: Fix unconditionally running namcap makechrootpkg: Fix anti-pattern when checking for enabled features Luke Shumaker (5): arch-nspawn: make sure that makepkg.conf is always parsed as text arch-nspawn: Remove pointless $(echo ...) subshell lib/common.sh: Adjust to work properly with `set -u` makechrootpkg: Adjust to work properly with `set -e` makechrootpkg: Put "keyserver-options auto-key-retrieve" in gpg.conf arch-nspawn.in | 4 ++-- lib/common.sh | 4 +++- makechrootpkg.in | 9 +++++---- 3 files changed, 10 insertions(+), 7 deletions(-) -- Happy hacking, ~ Luke Shumaker

3 15

[arch-projects] [devtools] Rebasing devtools32 to contribute upstream
by Luke Shumaker 20 Jan '18

20 Jan '18

Hi all, As the maintainer of Parabola's devtools, I know that with a merging workflow, it can be a huge pain to rebase out changes to have patchset that you can contribute upstream. If any of the Arch Linux 32 team ever decide that you want to contribute changes from devtools32 into upstream devtools, I expect that you will find the "lukeshu/rebase/archlinux32" branch of https://git.parabola.nu/packages/devtools-par.git/ to be useful. It is simply devtools32's "master" branch, rebased so that it looks like it used a rebasing workflow instead of a merging workflow. I'll generally keep it up-to-date as I keep an eye out for anything that I might want to backport into Parabola. (And indeed, there's already one such change https://lists.archlinux.org/pipermail/arch-projects/2018-January/004704.html ) -- Happy hacking, ~ Luke Shumaker

2 2

[arch-projects] [devtools] [PATCH] makechrootpkg: Do not copy the user keyring into the chroot.
by Eli Schwartz 15 Jan '18

15 Jan '18

Since commit 75fdff1811a0487f82c75b2e260da905102b4eea we no longer run integrity checks inside the chroot anyway, so this is no longer needed and will never be used. Signed-off-by: Eli Schwartz <eschwartz(a)archlinux.org> --- makechrootpkg.in | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/makechrootpkg.in b/makechrootpkg.in index 511e519..9c79171 100644 --- a/makechrootpkg.in +++ b/makechrootpkg.in @@ -180,12 +180,7 @@ prepare_chroot() { printf >>"$copydir/etc/group" 'builduser:x:%d:\n' "$builduser_gid" printf >>"$copydir/etc/passwd" 'builduser:x:%d:%d:builduser:/build:/bin/bash\n' "$builduser_uid" "$builduser_gid" - $install -d "$copydir"/{build,build/.gnupg,startdir,{pkg,srcpkg,src,log}dest} - - for x in .gnupg/pubring.{kbx,gpg}; do - [[ -r $USER_HOME/$x ]] || continue - $install -m 644 "$USER_HOME/$x" "$copydir/build/$x" - done + $install -d "$copydir"/{build,startdir,{pkg,srcpkg,src,log}dest} sed -e '/^MAKEFLAGS=/d' -e '/^PACKAGER=/d' -i "$copydir/etc/makepkg.conf" for x in BUILDDIR=/build PKGDEST=/pkgdest SRCPKGDEST=/srcpkgdest SRCDEST=/srcdest LOGDEST=/logdest \ -- 2.15.1

1 0