From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] xbps-src throws errors on bash
Date: Wed, 26 Jul 2023 03:00:36 +0200 [thread overview]
Message-ID: <20230726010036.nR5YFDQqyQ869UoMuoDEVFBYz6KBOuorgDX04tIMnx8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45239@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2021 bytes --]
Closed issue by Anachron on void-packages repository
https://github.com/void-linux/void-packages/issues/45239
Description:
### Is this a new report?
Yes
### System Info
Void 6.3.10_1 x86_64 GenuineIntel uptodate rrFFFFFFF
### Package(s) Affected
xbps-src
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
No.
### Expected behaviour
I expect `LANG=C ./xbps-src update-check bsdtar` to throw no errors on bash.
### Actual behaviour
```bash
# LANG=C ./xbps-src update-check bsdtar
/home/lap/var/bldr/gitsrc/common/environment/setup/sourcepkg.sh: line 31: unset: `BASH_FUNC_filew%%': not a valid identifier
/home/lap/var/bldr/gitsrc/common/environment/setup/sourcepkg.sh: line 31: unset: `BASH_FUNC_timer_handle%%': not a valid identifier
/home/lap/var/bldr/gitsrc/common/environment/setup/sourcepkg.sh: line 31: unset: `BASH_FUNC_welcome_prompt_handle%%': not a valid identifier
/home/lap/var/bldr/gitsrc/common/environment/setup/sourcepkg.sh: line 31: unset: `BASH_FUNC_vimw%%': not a valid identifier
/home/lap/var/bldr/gitsrc/common/environment/setup/sourcepkg.sh: line 31: unset: `BASH_FUNC_directory_not_found_handle%%': not a valid identifier
/home/lap/var/bldr/gitsrc/common/environment/setup/sourcepkg.sh: line 31: unset: `BASH_FUNC_shell_prompt_handle%%': not a valid identifier
/home/lap/var/bldr/gitsrc/common/environment/setup/sourcepkg.sh: line 31: unset: `BASH_FUNC_gitw%%': not a valid identifier
/home/lap/var/bldr/gitsrc/common/environment/setup/sourcepkg.sh: line 31: unset: `BASH_FUNC_cdw%%': not a valid identifier
/home/lap/var/bldr/gitsrc/common/environment/setup/sourcepkg.sh: line 31: unset: `BASH_FUNC_command_not_found_handle%%': not a valid identifier
libarchive-3.6.2 -> libarchive-3.7.0
```
### Steps to reproduce
Run `LANG=C ./xbps-src update-check bsdtar` with shell functions inside bashs env.
Issue is because of https://github.com/void-linux/void-packages/commit/6174bd6afde26fbcdf80437ab1653c6dab34099b
@sgn
next prev parent reply other threads:[~2023-07-26 1:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 7:50 [ISSUE] " Anachron
2023-07-25 7:52 ` Anachron
2023-07-25 8:21 ` sgn
2023-07-25 8:26 ` Anachron
2023-07-25 8:41 ` Anachron
2023-07-25 18:39 ` Anachron
2023-07-26 1:00 ` sgn
2023-07-26 1:00 ` sgn [this message]
2023-07-26 6:38 ` Anachron
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=20230726010036.nR5YFDQqyQ869UoMuoDEVFBYz6KBOuorgDX04tIMnx8@z \
--to=sgn@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).