Github messages for voidlinux
 help / color / mirror / Atom feed
From: Jjp137 <Jjp137@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] GZDoom reports its version as "<unknown version>"
Date: Sat, 16 Dec 2023 05:28:36 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47787@inbox.vuxu.org> (raw)

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

New issue by Jjp137 on void-packages repository

https://github.com/void-linux/void-packages/issues/47787

Description:
### Is this a new report?

Yes

### System Info

Void 6.1.67_1 x86_64 GenuineIntel uptodate FFFFFF

### Package(s) Affected

gzdoom-4.11.3_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

GZDoom should display the correct version number (4.11.3 as of this writing) where appropriate, including during startup and within the in-game console.

### Actual behaviour

First few lines of output:
```
$ gzdoom -iwad doom.wad
GZDoom <unknown version> -  - SDL version
Compiled on Nov 18 2023

OS: Void Linux, Linux 6.1.67_1 on x86_64
GZDoom version <unknown version>
```

In-game, `<unknown version>` is shown on the bottom-right corner of the console.

### Steps to reproduce

Run GZDoom from the command line in order to see the terminal output, which is always printed even without an IWAD present.

If an IWAD can be found on your system, after GZDoom starts, open the console (default: ~) and observe that the bottom-right corner says `<unknown version>`.

             reply	other threads:[~2023-12-16  4:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-16  4:28 Jjp137 [this message]
2023-12-16 17:40 ` meator
2023-12-16 18:24 ` meator

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47787@inbox.vuxu.org \
    --to=jjp137@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).