From: Wesley-Chan <Wesley-Chan@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: goocanvas: update to 3.0.0.
Date: Mon, 03 Oct 2022 11:38:37 +0200 [thread overview]
Message-ID: <20221003093837.IN7HF4NGX9ss-ix7Nl5o5u_UEIzqozw1qxHh8mHoPQs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39647@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 788 bytes --]
New comment by Wesley-Chan on void-packages repository
https://github.com/void-linux/void-packages/pull/39647#issuecomment-1265185515
Comment:
The failure in CI is due to this package: gpredict
It specifically requires goocanvas 2 in configure.ac, but as discussed in [this issue](https://github.com/csete/gpredict/issues/246), gpredict can use goocanvas 3 as well. [Changes to adapt to it](https://github.com/csete/gpredict/blob/master/configure.ac#L52-L65) was also merged into its master but gpredict has no new version released after that change.
In our case, it is one package that is blocking our advancement. Is the normal way to resolve conflicts to make a newer version of goocanvas in Void Linux, or make custom patch to gpredict?
Please advice. Thank you very much.
next prev parent reply other threads:[~2022-10-03 9:38 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 1:36 [PR PATCH] " Wesley-Chan
2022-10-03 1:49 ` [PR PATCH] [Updated] " Wesley-Chan
2022-10-03 9:38 ` Wesley-Chan [this message]
2022-10-03 11:10 ` classabbyamp
2022-10-03 13:11 ` [PR PATCH] [Updated] " Wesley-Chan
2022-10-03 13:24 ` classabbyamp
2022-10-03 13:24 ` classabbyamp
2022-10-03 13:35 ` Wesley-Chan
2022-10-03 13:47 ` classabbyamp
2023-01-02 1:57 ` github-actions
2023-01-02 5:31 ` newbluemoon
2023-04-04 1:53 ` github-actions
2023-04-19 1:54 ` [PR PATCH] [Closed]: " github-actions
-- strict thread matches above, loose matches on Subject: below --
2021-05-28 4:30 [PR PATCH] " reback00
2021-05-28 4:50 ` reback00
2021-05-28 7:03 ` newbluemoon
2021-05-28 10:50 ` reback00
2021-05-28 10:55 ` reback00
2021-05-28 10:56 ` reback00
2021-05-28 12:17 ` newbluemoon
2021-05-28 12:56 ` newbluemoon
2021-05-28 13:03 ` newbluemoon
2021-05-28 13:13 ` newbluemoon
2021-05-28 13:25 ` newbluemoon
2021-05-28 17:31 ` newbluemoon
2021-05-28 17:37 ` reback00
2021-05-28 17:50 ` newbluemoon
2021-05-28 17:50 ` reback00
2022-05-20 2:12 ` github-actions
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=20221003093837.IN7HF4NGX9ss-ix7Nl5o5u_UEIzqozw1qxHh8mHoPQs@z \
--to=wesley-chan@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).