From: HadetTheUndying <HadetTheUndying@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: osg: update to 3.6.5
Date: Wed, 29 Dec 2021 02:51:03 +0100 [thread overview]
Message-ID: <20211229015103.ANPaiUpI5SNHQTz7wy1yKBNUEbBYe7I1-1KdQjLrXmM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34729@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 820 bytes --]
New comment by HadetTheUndying on void-packages repository
https://github.com/void-linux/void-packages/pull/34729#issuecomment-1002357439
Comment:
Okay so I've set `make_check=no` in `sumo` for the time being. It looks like we are a considerable number of releases behind from the upstream and I will address this once the PR is merged. As Prior to `1.9.0 `sumo` did not support python3 properly and this was not spotted during the python-3.10 revbump which the check also fails on. I know this is a little messy but as this package is so many version out of date, and I don't regularly use it, I would prefer to revbump it and then get it back up to date with the upstream after we get `osg` updated. This is my first PR that effects multiple packages like this so I appreciate everyone that's been helping me learn.
next prev parent reply other threads:[~2021-12-29 1:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-28 9:08 [PR PATCH] " HadetTheUndying
2021-12-28 20:01 ` HadetTheUndying
2021-12-28 22:42 ` paper42
2021-12-29 0:01 ` HadetTheUndying
2021-12-29 1:46 ` [PR PATCH] [Updated] " HadetTheUndying
2021-12-29 1:51 ` HadetTheUndying [this message]
2021-12-29 21:32 ` HadetTheUndying
2021-12-29 21:32 ` HadetTheUndying
2022-01-01 18:58 ` paper42
2022-01-09 11:46 ` 4ricci
2022-01-09 20:06 ` HadetTheUndying
2022-03-10 14:27 ` 4ricci
2022-03-12 1:35 ` HadetTheUndying
2022-06-20 2:13 ` github-actions
2022-07-04 2:15 ` [PR PATCH] [Closed]: " github-actions
2022-12-30 1:12 [PR PATCH] " r-ricci
2023-01-07 21:47 ` abenson
2023-01-20 0:54 ` r-ricci
2023-01-21 19:49 ` r-ricci
2023-01-22 22:32 ` Johnnynator
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=20211229015103.ANPaiUpI5SNHQTz7wy1yKBNUEbBYe7I1-1KdQjLrXmM@z \
--to=hadettheundying@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).