From: Vinfall <Vinfall@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] bash-completion: update to 2.12.0.
Date: Fri, 29 Mar 2024 12:54:23 +0100 [thread overview]
Message-ID: <20240329115423.0B5CD21820@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49589@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 3144 bytes --]
There is an updated pull request by Vinfall against master on the void-packages repository
https://github.com/Vinfall/void-packages master
https://github.com/void-linux/void-packages/pull/49589
bash-completion: update to 2.12.0.
Two backported patches from upstream (i.e. [#688](https://github.com/scop/bash-completion/pull/688) and [#675](https://github.com/scop/bash-completion/pull/675)) are deleted since the new version includes them already.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
This PR FAILS to build on x86_64-musl with the following warnings:
```sh
=> xbps-src: updating repositories for host (x86_64-musl)...
[*] Updating repository `https://repo-default.voidlinux.org/current/musl/bootstrap/x86_64-musl-repodata' ...
[*] Updating repository `https://repo-default.voidlinux.org/current/musl/x86_64-musl-repodata' ...
[*] Updating repository `https://repo-default.voidlinux.org/current/musl/nonfree/x86_64-musl-repodata' ...
[*] Updating repository `https://repo-default.voidlinux.org/current/musl/debug/x86_64-musl-repodata' ...
=> xbps-src: updating software in / masterdir...
=> xbps-src: cleaning up / masterdir...
=> bash-completion-2.12.0_1: removing autodeps, please wait...
=> bash-completion-2.12.0_1: building with [gnu-configure] for x86_64-musl...
[runtime] bash-5.2.21_1: found (https://repo-default.voidlinux.org/current/musl)
=> bash-completion-2.12.0_1: skipping check (XBPS_CHECK_PKGS is disabled) ...
=> bash-completion-2.12.0_1: running pre-pkg hook: 03-rewrite-python-shebang ...
=> bash-completion-2.12.0_1: running pre-pkg hook: 04-generate-runtime-deps ...
=> bash-completion-2.12.0_1: running pre-pkg hook: 05-generate-32bit-runtime-deps ...
=> bash-completion-2.12.0_1: running pre-pkg hook: 90-set-timestamps ...
=> bash-completion-2.12.0_1: setting mtimes to Fri Mar 29 07:05:08 UTC 2024
=> bash-completion-2.12.0_1: running pre-pkg hook: 99-pkglint-subpkgs ...
=> bash-completion-2.12.0_1: running pre-pkg hook: 99-pkglint ...
=> ERROR: bash-completion-2.12.0_1: /etc/bash_completion.d is forbidden. Use /usr/share/bash-completion/completions.
=> ERROR: bash-completion-2.12.0_1: cannot continue with installation!
```
How can I solve the error `/etc/bash_completion.d is forbidden. Use /usr/share/bash-completion/completions.`? I searched a bit but could not find something useful.
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/49589.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-master-49589.patch --]
[-- Type: text/x-diff, Size: 5862 bytes --]
From 57c4c828c2595b80ce2d7904f3d3ce9517579c75 Mon Sep 17 00:00:00 2001
From: Vinfall <neptuniahuai0tc@riseup.net>
Date: Fri, 29 Mar 2024 19:38:40 +0800
Subject: [PATCH] bash-completion: update to 2.12.0.
Two backported patches from upstream (i.e.
https://github.com/scop/bash-completion/pull/688 and
https://github.com/scop/bash-completion/pull/675) are deleted since the
new version includes them already.
---
.../patches/complete-xbps.patch | 24 ------
.../bash-completion/patches/linux-zstd.patch | 75 -------------------
srcpkgs/bash-completion/template | 6 +-
3 files changed, 3 insertions(+), 102 deletions(-)
delete mode 100644 srcpkgs/bash-completion/patches/complete-xbps.patch
delete mode 100644 srcpkgs/bash-completion/patches/linux-zstd.patch
diff --git a/srcpkgs/bash-completion/patches/complete-xbps.patch b/srcpkgs/bash-completion/patches/complete-xbps.patch
deleted file mode 100644
index 3e34ef1d78dacb..00000000000000
--- a/srcpkgs/bash-completion/patches/complete-xbps.patch
+++ /dev/null
@@ -1,24 +0,0 @@
-Complete tar with .xbps files.
-
-Backported from upstream https://github.com/scop/bash-completion/pull/688
-
---- a/completions/tar
-+++ b/completions/tar 2022-01-23 11:42:19.699734913 -0300
-@@ -422,7 +422,7 @@
-
- __tar_detect_ext()
- {
-- local tars='@(@(tar|gem|spkg)?(.@(Z|[bgx]z|bz2|lz?(ma|o)|zst))|t@([abglx]z|b?(z)2|zst))'
-+ local tars='@(@(tar|spkg)?(.@(Z|[bgx]z|bz2|lz?(ma|o)|zst))|t@([abglx]z|b?(z)2|zst)|gem|xbps)'
- ext="$tars"
-
- case "$tar_mode_arg" in
-@@ -430,7 +430,7 @@
- # Should never happen?
- ;;
- ?(-)*[cr]*f)
-- ext='@(tar|gem|spkg)'
-+ ext='@(tar|gem|spkg|xbps)'
- case ${words[1]} in
- *a*) ext="$tars" ;;
- *z*) ext='t?(ar.)gz' ;;
diff --git a/srcpkgs/bash-completion/patches/linux-zstd.patch b/srcpkgs/bash-completion/patches/linux-zstd.patch
deleted file mode 100644
index f230a1c08169b7..00000000000000
--- a/srcpkgs/bash-completion/patches/linux-zstd.patch
+++ /dev/null
@@ -1,75 +0,0 @@
-From 4298bc2760d00c83025680f11a3490403b91ba98 Mon Sep 17 00:00:00 2001
-From: Richard Schütz <richardschuetz@users.noreply.github.com>
-Date: Tue, 28 Dec 2021 20:07:11 +0100
-Subject: [PATCH] feat(_modules): support zstd compressed modules
-
----
- bash_completion | 3 ++-
- 1 file changed, 2 insertions(+), 1 deletion(-)
-
-diff --git a/bash_completion b/bash_completion
-index 3d50b2ae..16523708 100644
---- a/bash_completion
-+++ b/bash_completion
-@@ -1417,7 +1417,8 @@ _modules()
- local modpath
- modpath=/lib/modules/$1
- COMPREPLY=($(compgen -W "$(command ls -RL $modpath 2>/dev/null |
-- command sed -ne 's/^\(.*\)\.k\{0,1\}o\(\.[gx]z\)\{0,1\}$/\1/p')" -- "$cur"))
-+ command sed -ne 's/^\(.*\)\.k\{0,1\}o\(\.[gx]z\)\{0,1\}$/\1/p' \
-+ -e 's/^\(.*\)\.ko\.zst$/\1/p')" -- "$cur"))
- }
-
- # This function completes on installed modules
-From b6a9ed50909224fa6b7887b604e86e4efce8289b Mon Sep 17 00:00:00 2001
-From: Michal Suchánek <msuchanek@suse.de>
-Date: Fri, 1 Oct 2021 21:40:44 +0200
-Subject: [PATCH] feat(insmod,modinfo,modprobe): support zstd compressed
- modules (#614)
-
-Signed-off-by: Michal Suchanek <msuchanek@suse.de>
----
- completions/insmod | 2 +-
- completions/modinfo | 2 +-
- completions/modprobe | 2 +-
- 3 files changed, 3 insertions(+), 3 deletions(-)
-
-diff --git a/completions/insmod b/completions/insmod
-index a59e7535..2f756a99 100644
---- a/completions/insmod
-+++ b/completions/insmod
-@@ -7,7 +7,7 @@ _insmod()
-
- # do filename completion for first argument
- if ((cword == 1)); then
-- _filedir '@(?(k)o?(.[gx]z))'
-+ _filedir '@(?(k)o?(.[gx]z|.zst))'
- else # do module parameter completion
- COMPREPLY=($(compgen -W "$(PATH="$PATH:/sbin" modinfo \
- -p ${words[1]} 2>/dev/null | cut -d: -f1)" -- "$cur"))
-diff --git a/completions/modinfo b/completions/modinfo
-index b2809144..4d4d835c 100644
---- a/completions/modinfo
-+++ b/completions/modinfo
-@@ -43,7 +43,7 @@ _modinfo()
-
- # do filename completion if we're giving a path to a module
- if [[ $cur == @(*/|[.~])* ]]; then
-- _filedir '@(?(k)o?(.[gx]z))'
-+ _filedir '@(?(k)o?(.[gx]z|.zst))'
- else
- _modules $version
- fi
-diff --git a/completions/modprobe b/completions/modprobe
-index 958cd938..799ea197 100644
---- a/completions/modprobe
-+++ b/completions/modprobe
-@@ -80,7 +80,7 @@ _modprobe()
- insert)
- # do filename completion if we're giving a path to a module
- if [[ $cur == @(*/|[.~])* ]]; then
-- _filedir '@(?(k)o?(.[gx]z))'
-+ _filedir '@(?(k)o?(.[gx]z|.zst))'
- elif [[ -n $module ]]; then
- # do module parameter completion
- if [[ $cur == *=* ]]; then
diff --git a/srcpkgs/bash-completion/template b/srcpkgs/bash-completion/template
index e28e00138868a9..a888ecc8df7818 100644
--- a/srcpkgs/bash-completion/template
+++ b/srcpkgs/bash-completion/template
@@ -1,7 +1,7 @@
# Template file for 'bash-completion'
pkgname=bash-completion
-version=2.11
-revision=5
+version=2.12.0
+revision=1
build_style=gnu-configure
make_install_args="profiledir=/etc/bash/bashrc.d"
depends="bash"
@@ -11,7 +11,7 @@ maintainer="skmpz <dem.procopiou@gmail.com>"
license="GPL-2.0-or-later"
homepage="https://github.com/scop/bash-completion"
distfiles="https://github.com/scop/bash-completion/releases/download/${version}/bash-completion-${version}.tar.xz"
-checksum=73a8894bad94dee83ab468fa09f628daffd567e8bef1a24277f1e9a0daf911ac
+checksum=3eb05b1783c339ef59ed576afb0f678fa4ef49a6de8a696397df3148f8345af9
# Summary of tests:
# = 26 failed, 1106 passed, 457 skipped, 14 xfailed, 4 xpassed in 1126.01s (0:18:46) =
next prev parent reply other threads:[~2024-03-29 11:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-29 11:47 [PR PATCH] " Vinfall
2024-03-29 11:54 ` Vinfall [this message]
2024-03-30 8:05 ` dataCobra
2024-03-31 2:47 ` [PR PATCH] [Updated] " Vinfall
2024-03-31 2:52 ` Vinfall
2024-05-08 2:47 ` Vinfall
2024-05-08 2:47 ` [PR PATCH] [Closed]: " Vinfall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240329115423.0B5CD21820@inbox.vuxu.org \
--to=vinfall@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).