From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Package 'grass' : GRASS GUI not working
Date: Fri, 20 May 2022 04:11:13 +0200 [thread overview]
Message-ID: <20220520021113.FNkfq3jFdPIabMlF7uT71MwVM33JAOvW6ABqEYlY1NM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29209@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]
Closed issue by nezos on void-packages repository
https://github.com/void-linux/void-packages/issues/29209
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname: Void 5.10.19_1 x86_64 AuthenticAMD uptodate rFFFF
* package: grass-7.6.1_4
### Expected behavior
Executing grass76 should start the GUI of the program
### Actual behavior
Starting GRASS GIS...
WARNING: GRASS GUI not found. Please check your installation.
Switching to text based interface mode.
### Steps to reproduce the behavior
$ sudo xbps-install grass
$ grass76
### Causes
I have found two causes:
a) /usr/bin/grass76 has at line 105 hardcoded a path for the lib files that does not exist as it is different than that of the installation
b) if I understood correctly, it requires wxpython v2
### Probable solution
Upgrade version to the latest, I have found a fork by @Nyx70 https://github.com/Nyx70/void-packages/blob/qgis/srcpkgs/grass/
next prev parent reply other threads:[~2022-05-20 2:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 16:22 [ISSUE] " nezos
2022-05-06 2:08 ` github-actions
2022-05-20 2:11 ` github-actions [this message]
2023-10-19 1:52 ` jcobban
2023-10-19 2:17 ` 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=20220520021113.FNkfq3jFdPIabMlF7uT71MwVM33JAOvW6ABqEYlY1NM@z \
--to=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).