From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: MEGAcmd: update to 1.5.1 and adopt
Date: Thu, 19 Jan 2023 03:01:13 +0100 [thread overview]
Message-ID: <20230119020113.ZJpz8S3OkYoEKHLBActe7dAcEvs4Ytsgtl7emUBHCw0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39733@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1587 bytes --]
There's a closed pull request on the void-packages repository
MEGAcmd: update to 1.5.1 and adopt
https://github.com/void-linux/void-packages/pull/39733
Description:
#### Testing the changes
- I tested the changes in this PR: **briefly**: by running `mega-cmd`, logging in and downloading a file using the `get` command.
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
<!-- I am trying to update `MEGAcmd` to `1.5.1` and `MEGAsdk` to `3.9.11d` (as per the version submoduled in MEGAcmd's repo).
But am I getting a very peculiar issue with the ./configure script.
```
configure: line 22309: syntax error near unexpected token `cat'
configure: line 22309: `cat >confcache <<\_ACEOF'
```
It doesn't really seem like there is a syntax error there.
It runs just fine when manually run outside of the chroot. So I tried the following:
- using `chroot-bash` outside the chroot to run `./configure` and replicated the issue.
- using `bash` outside the chroot to run `./configure` and replicated the issue.
- using `zsh` inside the chroot (by redefining `do_configure` to use `zsh`) which bypasses the issue but creates another issue.
- using `sh` outside the chroot works as expected.
_I don't think using another shell is a real solution._
I don't really know how to continue so I'm making a **broken draft pull request** to ask for help.
What could bash be doing differently so as to cause this issue?
Maybe I messed something up when porting `autotools.patch` to the new version of `MEGAcmd`?-->
prev parent reply other threads:[~2023-01-19 2:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 10:53 [PR PATCH] MEGAcmd: update to 1.5.1 cultab
2022-10-06 9:56 ` cultab
2022-10-06 10:51 ` [PR PATCH] [Updated] " cultab
2022-10-06 10:58 ` cultab
2022-10-06 11:00 ` cultab
2022-10-06 11:05 ` [PR PATCH] [Updated] " cultab
2022-10-06 12:25 ` cultab
2022-10-06 12:35 ` cultab
2022-10-06 12:45 ` cultab
2023-01-05 1:59 ` MEGAcmd: update to 1.5.1 and adopt github-actions
2023-01-19 2:01 ` github-actions [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=20230119020113.ZJpz8S3OkYoEKHLBActe7dAcEvs4Ytsgtl7emUBHCw0@z \
--to=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).