From: kawaiiamber <kawaiiamber@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] jamulus: update to 3.8.2
Date: Sun, 27 Feb 2022 16:23:01 +0100 [thread overview]
Message-ID: <20220227152301.kg4IqWZD9GYh-kNIGQHdTCUrUeYHNvcm0qUhAB3tDQo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35867@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 774 bytes --]
New comment by kawaiiamber on void-packages repository
https://github.com/void-linux/void-packages/pull/35867#issuecomment-1053587617
Comment:
> > I'll skip CI and tag WIP until it's resolved. I figured I would make the PR just in case anyone was curious about the status of updating to 3.8.2.
>
> This happened more than a month ago, so the issue is on your side. Remove the CI skip, update your local void-packages and remove old packages (libxml, harfbuzz, etc.) from hostdir/binpkgs.
This persists even after:
```
./xbps-src zap
git pull --rebase upstream master
./xbps-src binary-bootstrap
./xbps-src pkg jamuslus
```
zap ensures that hostdir is clean. Updating and cleaning hostdir was obviously the first thing I tried. I'll remove the CI skip anyway.
next prev parent reply other threads:[~2022-02-27 15:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-26 15:16 [PR PATCH] " kawaiiamber
2022-02-26 15:26 ` [PR PATCH] [Updated] " kawaiiamber
2022-02-27 10:30 ` paper42
2022-02-27 15:23 ` kawaiiamber [this message]
2022-02-27 15:23 ` [PR PATCH] [Updated] " kawaiiamber
2022-02-27 15:27 ` kawaiiamber
2022-02-27 17:41 ` kawaiiamber
2022-02-27 18:57 ` paper42
2022-02-27 18:58 ` [PR PATCH] [Merged]: " paper42
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=20220227152301.kg4IqWZD9GYh-kNIGQHdTCUrUeYHNvcm0qUhAB3tDQo@z \
--to=kawaiiamber@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).