Github messages for voidlinux
 help / color / mirror / Atom feed
From: kruceter <kruceter@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] libgdal: update to 3.5.2
Date: Mon, 31 Oct 2022 02:37:53 +0100	[thread overview]
Message-ID: <20221031013753.ZvNNdnt6ULFDo75OOk4paUA0cKtacdy0jif6iZXyJf8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40225@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1054 bytes --]

New review comment by kruceter on void-packages repository

https://github.com/void-linux/void-packages/pull/40225#discussion_r1008969231

Comment:
@classabbyamp, I could update it to 8.2.0 (did not crosscompile yet), but apparently it hangs with wxPython4 (`ToolBar.AddTool(): arguments did not match any overloaded call: ...`), rendering grass inoperable.

According to https://github.com/OSGeo/grass/issues/2019, this can be solved by updating wxPython4 to the newer version, but here the old version of wxWidgets itself (3.0.5 vs. 3.2.1) makes its appearance:

```
In file included from ../../../../sip/cpp/sip_corewxZoomGestureEvent.cpp:10:
../../../../sip/cpp/sipAPI_core.h:22411:10: fatal error: wx/collheaderctrl.h: No such file or directory
22411 | #include <wx/collheaderctrl.h>
      |          ^~~~~~~~~~~~~~~~~~~~~
compilation terminated.
```

Given how many packages depend on wxWidgets, I suspect that it must be updated in a separate PR along with its reverse dependencies.

Is there a course of action you would recommend?

  parent reply	other threads:[~2022-10-31  1:37 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-30  5:27 [PR PATCH] " kruceter
2022-10-30  6:22 ` [PR PATCH] [Updated] " kruceter
2022-10-30  9:04 ` [PR REVIEW] " classabbyamp
2022-10-30  9:04 ` classabbyamp
2022-10-30 18:09 ` [PR PATCH] [Updated] " kruceter
2022-10-30 18:12 ` [PR REVIEW] " kruceter
2022-10-31  1:37 ` kruceter [this message]
2022-10-31  1:57 ` classabbyamp
2022-10-31 12:51 ` [PR PATCH] [Updated] " kruceter
2022-10-31 12:55 ` kruceter
2022-11-01  6:06 ` kruceter
2022-11-01  6:32 ` kruceter
2022-11-01  6:33 ` kruceter
2022-11-01  6:34 ` [PR REVIEW] " classabbyamp
2022-11-01  7:15 ` kruceter
2022-11-01 11:14 ` kruceter
2022-11-01 11:35 ` [PR PATCH] [Updated] " kruceter
2022-11-01 17:59 ` [PR PATCH] [Updated] libgdal: update to 3.5.3 kruceter
2022-11-02 13:29 ` kruceter
2022-11-03  7:11 ` kruceter
2022-11-03  8:01 ` kruceter
2022-11-03 20:34 ` [PR PATCH] [Updated] " kruceter
2022-11-03 20:40 ` kruceter
2022-11-03 22:51 ` kruceter
2022-11-03 23:05 ` kruceter
2022-11-04  9:05 ` kruceter
2022-11-04 12:36 ` kruceter
2022-11-05  3:23 ` the-maldridge
2022-11-05  3:27 ` [PR PATCH] [Merged]: " classabbyamp

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=20221031013753.ZvNNdnt6ULFDo75OOk4paUA0cKtacdy0jif6iZXyJf8@z \
    --to=kruceter@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).