From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] .github/workflows/cycles.yml: update masterdir
Date: Sat, 28 May 2022 21:58:33 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37335@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 451 bytes --]
There is a new pull request by classabbyamp against master on the void-packages repository
https://github.com/classabbyamp/void-packages fix/cycle-masterdir
https://github.com/void-linux/void-packages/pull/37335
.github/workflows/cycles.yml: update masterdir
same change as 8fe764cd87081a676e1c119cfd21938d2ace3ab1, but applied to the cycle check workflow
A patch file from https://github.com/void-linux/void-packages/pull/37335.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-fix/cycle-masterdir-37335.patch --]
[-- Type: text/x-diff, Size: 789 bytes --]
From ea66ca02044a4c85a0dc208c9e3af4228ba470be Mon Sep 17 00:00:00 2001
From: classabbyamp <dev@placeviolette.net>
Date: Sat, 28 May 2022 15:57:28 -0400
Subject: [PATCH] .github/workflows/cycles.yml: update masterdir
---
.github/workflows/cycles.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/.github/workflows/cycles.yml b/.github/workflows/cycles.yml
index d57976cbeed2..0bd148e77f0a 100644
--- a/.github/workflows/cycles.yml
+++ b/.github/workflows/cycles.yml
@@ -8,7 +8,7 @@ jobs:
cycles:
runs-on: ubuntu-latest
container:
- image: 'ghcr.io/void-linux/xbps-src-masterdir:20210313rc01-x86_64-musl'
+ image: 'ghcr.io/void-linux/xbps-src-masterdir:20220527RC01-x86_64-musl'
steps:
- name: Prepare container
run: |
next reply other threads:[~2022-05-28 19:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-28 19:58 classabbyamp [this message]
2022-05-28 21:29 ` [PR PATCH] [Merged]: " ericonr
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37335@inbox.vuxu.org \
--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).