From: foopub <foopub@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: kicad: update to 6.0.1
Date: Sat, 29 Jan 2022 02:12:42 +0100 [thread overview]
Message-ID: <20220129011242.SOg0bzCgv0QxQj8hAcbcen_zt_2AOSaOaa2mHWeaFKo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34917@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 697 bytes --]
New comment by foopub on void-packages repository
https://github.com/void-linux/void-packages/pull/34917#issuecomment-1024793923
Comment:
> For next time, it'd be best to just let CI run. See [bb4b6fb](https://github.com/void-linux/void-packages/commit/bb4b6fb5588eeb2dce6611b89c542f082bd14120)
Seems CI builds fail for all but x86_64 glibc... https://github.com/void-linux/void-packages/actions/runs/1736427514
I tried looking through the build logs but they're too long to view online. Tried to download, but it reached >100mb before I cancelled. Not sure what the issues are, and kicad is the most annoying program to debug in my experience (no runtime logs!) so I gave up at that point.
next prev parent reply other threads:[~2022-01-29 1:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 2:47 [PR PATCH] kicad: update to 6.0.0 PoroCYon
2022-01-07 18:52 ` unspecd
2022-01-07 23:07 ` [PR PATCH] [Updated] " PoroCYon
2022-01-07 23:10 ` PoroCYon
2022-01-16 8:43 ` lemmi
2022-01-16 8:44 ` lemmi
2022-01-16 16:37 ` [PR PATCH] [Updated] " PoroCYon
2022-01-16 16:38 ` PoroCYon
2022-01-16 17:48 ` kicad: update to 6.0.1 PoroCYon
2022-01-16 18:35 ` [PR REVIEW] " ericonr
2022-01-16 18:35 ` ericonr
2022-01-16 18:35 ` ericonr
2022-01-16 23:33 ` PoroCYon
2022-01-16 23:39 ` PoroCYon
2022-01-17 0:55 ` [PR PATCH] [Updated] " PoroCYon
2022-01-17 0:57 ` PoroCYon
2022-01-17 4:47 ` [PR REVIEW] " ericonr
2022-01-17 17:17 ` [PR PATCH] [Updated] " PoroCYon
2022-01-23 22:23 ` PoroCYon
2022-01-26 17:26 ` foopub
2022-01-26 17:34 ` foopub
2022-01-27 0:32 ` PoroCYon
2022-01-27 1:05 ` PoroCYon
2022-01-27 13:53 ` [PR PATCH] [Updated] " PoroCYon
2022-01-28 6:27 ` [PR PATCH] [Closed]: " ericonr
2022-01-28 8:00 ` ericonr
2022-01-29 1:12 ` foopub
2022-01-29 1:12 ` foopub [this message]
2022-01-23 16:33 [PR PATCH] " foopub
2022-01-23 17:38 ` foopub
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=20220129011242.SOg0bzCgv0QxQj8hAcbcen_zt_2AOSaOaa2mHWeaFKo@z \
--to=foopub@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).