From: klarasm <klarasm@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: routinator: update to 0.11.2
Date: Mon, 25 Apr 2022 12:45:47 +0200 [thread overview]
Message-ID: <20220425104547.pWTxis65L-u7WUlJg4-cG1PT2qarLCK9CL5ryXjF5bw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35971@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 714 bytes --]
New comment by klarasm on void-packages repository
https://github.com/void-linux/void-packages/pull/35971#issuecomment-1108401426
Comment:
Seems like github packages is having issues (https://www.githubstatus.com/incidents/b40k7ckrs7sp) which is probably why some builds are failing.
```
Starting job container
/usr/bin/docker --config /home/runner/work/_temp/.docker_500e6f68-fa9e-4be4-a631-8fb3451b5bfe login ghcr.io -u klarasm --password-stdin
/usr/bin/docker --config /home/runner/work/_temp/.docker_500e6f68-fa9e-4be4-a631-8fb3451b5bfe pull ghcr.io/void-linux/xbps-src-masterdir:20210313rc01-x86_64-musl
Error response from daemon: received unexpected HTTP status: 500 Internal Server Error
```
next prev parent reply other threads:[~2022-04-25 10:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 16:59 [PR PATCH] routinator: update to 0.11.0 klarasm
2022-04-10 15:07 ` [PR PATCH] [Updated] " klarasm
2022-04-10 15:08 ` klarasm
2022-04-10 15:10 ` routinator: update to 0.11.1 klarasm
2022-04-24 15:26 ` [PR PATCH] [Updated] " klarasm
2022-04-24 15:28 ` [PR PATCH] [Updated] routinator: update to 0.11.2 klarasm
2022-04-24 15:29 ` klarasm
2022-04-25 9:08 ` [PR REVIEW] " paper42
2022-04-25 9:09 ` paper42
2022-04-25 10:20 ` [PR PATCH] [Updated] " klarasm
2022-04-25 10:26 ` [PR REVIEW] " klarasm
2022-04-25 10:42 ` klarasm
2022-04-25 10:45 ` klarasm [this message]
2022-04-25 11:44 ` [PR PATCH] [Updated] " klarasm
2022-04-25 17:01 ` CameronNemo
2022-07-03 18:48 ` klarasm
2022-07-03 20:16 ` [PR PATCH] [Merged]: " paper42
2022-07-03 21:27 ` CameronNemo
2022-07-04 19:13 ` klarasm
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=20220425104547.pWTxis65L-u7WUlJg4-cG1PT2qarLCK9CL5ryXjF5bw@z \
--to=klarasm@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).