From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] common/travis/fetch_upstream.sh: fix CI for new git version
Date: Sat, 16 Apr 2022 20:49:50 +0200 [thread overview]
Message-ID: <20220416184950.Dg-Rrz_OIKnbG55V9qdULQYE32HDPwp7NgX85tcUJWc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36725@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1553 bytes --]
There is an updated pull request by classabbyamp against master on the void-packages repository
https://github.com/classabbyamp/void-packages common/fix-ci-git
https://github.com/void-linux/void-packages/pull/36725
common/travis/fetch_upstream.sh: fix CI for new git version
The newest git versions require [safe.directory](https://git-scm.com/docs/git-config/2.35.2#Documentation/git-config.txt-safedirectory) to work properly for repos owned by others.
#### Testing the changes
- I tested the changes in this PR: **YES**
Tested by temporarily adding a commit that changed a package to this PR, and [it succeeded](https://github.com/void-linux/void-packages/actions/runs/2177619018).
<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->
<!-- 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/36725.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-common/fix-ci-git-36725.patch --]
[-- Type: text/x-diff, Size: 840 bytes --]
From c7f983702c1ff12cb048a456b445bd11ba30e714 Mon Sep 17 00:00:00 2001
From: classabbyamp <dev@placeviolette.net>
Date: Sat, 16 Apr 2022 14:39:39 -0400
Subject: [PATCH] common/travis/fetch_upstream.sh: fix CI for new git version
---
common/travis/fetch_upstream.sh | 3 +++
1 file changed, 3 insertions(+)
diff --git a/common/travis/fetch_upstream.sh b/common/travis/fetch_upstream.sh
index 45315563e0b1..5c0256fdbe17 100755
--- a/common/travis/fetch_upstream.sh
+++ b/common/travis/fetch_upstream.sh
@@ -8,5 +8,8 @@ elif command -v git >/dev/null 2>&1; then
GIT_CMD=$(command -v git)
fi
+# required by git 2.35.2+
+$GIT_CMD config --global --add safe.directory /__w/void-packages/void-packages
+
/bin/echo -e '\x1b[32mFetching upstream...\x1b[0m'
$GIT_CMD fetch --depth 200 https://github.com/void-linux/void-packages.git master
next prev parent reply other threads:[~2022-04-16 18:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-16 18:46 [PR PATCH] " classabbyamp
2022-04-16 18:47 ` [PR PATCH] [Updated] " classabbyamp
2022-04-16 18:49 ` classabbyamp [this message]
2022-04-16 18:51 ` [PR PATCH] [Merged]: " the-maldridge
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=20220416184950.Dg-Rrz_OIKnbG55V9qdULQYE32HDPwp7NgX85tcUJWc@z \
--to=classabbyamp@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).