Github messages for voidlinux
 help / color / mirror / Atom feed
From: kruceter <kruceter@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: proj: update to 9.1.1
Date: Sat, 14 Jan 2023 21:10:04 +0100	[thread overview]
Message-ID: <20230114201004.V-MViqHmTA0GWo2J6lBRjRtLmvHtfkyt2r14alQ4-ck@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40347@inbox.vuxu.org>

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

New comment by kruceter on void-packages repository

https://github.com/void-linux/void-packages/pull/40347#issuecomment-1382643933

Comment:
There is no way to disable GUI using build arguments, their old manual misled me.

Rebase and apply this patch (and change version in the commit message too):

[0001-fixup-grass-update-to-7.8.7-rebuild-for-proj-9.1.txt](https://github.com/void-linux/void-packages/files/10418752/0001-fixup-grass-update-to-7.8.7-rebuild-for-proj-9.1.txt)

There is nothing we can do about broken gui at present time, so leave it be.

If GUI does not work, grass falls back to the text mode. We can live with it at least until wxPython is updated. If you are interested in enforcing the text mode, add the following block to the template:

```sh
post_install() {
	# This package is broken with wxPython4 (<=4.0.7),
	# hence the GUI is compulsorily disabled.
	vsed -i "${DESTDIR}/usr/bin/grass" -e "s/\(default_gui =\).*/\1 \"text\"/"
}
```

Aside from grass I think this pull request can be merged.

  parent reply	other threads:[~2023-01-14 20:10 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-05 15:37 [PR PATCH] Update proj to 7.2.1 ar-jan
2022-11-05 16:58 ` proj: update " nezos
2022-11-05 17:20 ` ar-jan
2022-11-05 18:31 ` [PR REVIEW] " classabbyamp
2022-11-05 18:43 ` ar-jan
2022-11-06 11:51 ` ar-jan
2022-11-06 19:58 ` [PR PATCH] [Updated] " ar-jan
2022-11-06 21:50 ` [PR REVIEW] " kruceter
2022-11-07 11:33 ` ar-jan
2022-11-08 13:24 ` [PR PATCH] [Updated] " ar-jan
2022-11-08 15:29 ` kruceter
2022-11-08 16:09 ` ar-jan
2022-11-08 17:00 ` [PR PATCH] [Updated] " ar-jan
2022-11-08 17:00 ` kruceter
2022-11-08 17:04 ` kruceter
2022-11-08 17:13 ` kruceter
2022-11-08 17:14 ` kruceter
2022-11-08 17:32 ` ar-jan
2022-11-08 17:39 ` kruceter
2022-11-08 17:40 ` kruceter
2022-11-08 23:15 ` nezos
2022-11-08 23:17 ` nezos
2022-11-08 23:29 ` ar-jan
2022-11-09  1:43 ` kruceter
2022-11-09  1:46 ` kruceter
2022-11-09 13:45 ` nezos
2022-11-09 15:53 ` kruceter
2022-11-09 17:26 ` ar-jan
2022-11-10  0:06 ` ar-jan
2022-11-10  0:10 ` ar-jan
2022-11-10  0:20 ` ar-jan
2022-11-15 16:57 ` [PR PATCH] [Updated] " ar-jan
2022-11-15 17:02 ` proj: update to 9.1.0 ar-jan
2022-11-15 17:12 ` [PR PATCH] [Updated] " ar-jan
2022-11-20 17:23 ` ar-jan
2022-11-20 18:41 ` ar-jan
2022-12-03 23:14 ` ar-jan
2022-12-03 23:17 ` ar-jan
2022-12-03 23:22 ` ar-jan
2022-12-03 23:22 ` ar-jan
2022-12-04 13:43 ` [PR PATCH] [Updated] " ar-jan
2022-12-04 21:38 ` [PR REVIEW] proj: update to 9.1.1 classabbyamp
2022-12-04 21:38 ` classabbyamp
2022-12-04 21:38 ` classabbyamp
2022-12-04 21:38 ` classabbyamp
2022-12-04 22:10 ` ar-jan
2022-12-04 22:15 ` classabbyamp
2022-12-04 22:18 ` ar-jan
2022-12-04 22:36 ` ar-jan
2022-12-04 22:41 ` [PR PATCH] [Updated] " ar-jan
2022-12-04 22:41 ` [PR REVIEW] " classabbyamp
2022-12-04 22:44 ` classabbyamp
2022-12-04 22:44 ` ar-jan
2022-12-04 23:02 ` [PR PATCH] [Updated] " ar-jan
2022-12-04 23:09 ` [PR REVIEW] " classabbyamp
2023-01-09  0:42 ` kruceter
2023-01-11 21:38 ` [PR PATCH] [Updated] " ar-jan
2023-01-11 21:39 ` [PR REVIEW] " ar-jan
2023-01-12 20:29 ` ar-jan
2023-01-12 23:30 ` ar-jan
2023-01-13  1:00 ` kruceter
2023-01-14  2:58 ` kruceter
2023-01-14 20:10 ` kruceter [this message]
2023-01-15 12:00 ` ar-jan
2023-01-16  9:29 ` nezos
2023-01-16  9:34 ` classabbyamp
2023-01-16  9:50 ` alexjarosch
2023-01-22 15:45 ` [PR PATCH] [Updated] " ar-jan
2023-01-22 15:52 ` ar-jan
2023-01-22 20:51 ` [PR PATCH] [Merged]: " Johnnynator
2023-01-23  6:36 ` kruceter

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=20230114201004.V-MViqHmTA0GWo2J6lBRjRtLmvHtfkyt2r14alQ4-ck@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).