Github messages for voidlinux
 help / color / mirror / Atom feed
From: Vinfall <Vinfall@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: bash-completion: update to 2.12.0.
Date: Wed, 08 May 2024 04:47:37 +0200	[thread overview]
Message-ID: <20240508024737.9A14321147@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: 2989 bytes --]

There's a closed pull request on the void-packages repository

bash-completion: update to 2.12.0.
https://github.com/void-linux/void-packages/pull/49589

Description:
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
-->


      parent reply	other threads:[~2024-05-08  2:47 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 ` [PR PATCH] [Updated] " Vinfall
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 ` Vinfall [this message]

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=20240508024737.9A14321147@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).