From: github-actions [bot] <"github-actions [bot]"@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] SDRPlusPlus has switched to a "rolling release" model
Date: Thu, 23 Jan 2025 02:57:44 +0100 [thread overview]
Message-ID: <20250123015744.21CF4213D0@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-52568@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1629 bytes --]
Closed issue by agausmann on void-packages repository
https://github.com/void-linux/void-packages/issues/52568
Description:
The latest named version of SDR++ is 1.0.4, which is from 2021. However, it is still in development in "rolling release", where releases are not named, and a `nightly` tag is updated periodically from the main branch.
This hasn't been a problem on Void until recently, where for me, version 1.0.4 has started crashing at launch with the message `Failed to initialize OpenGL loader!`. I built the latest commit of SDR++ locally, and it does not have the same issue.
I would like to work on fixing this, but I am asking for input from maintainers on what direction you all would prefer:
- **Add an `SDRPlusPlus-git` package** that follows the nightly tag
- **Update the `SDRPlusPlus` package** to follow the nightly tag
- **Keep v1.0.4 and investigate the cause of the issue there.** (Maybe it just needs a rebuild, or worst case it might need a patch.)
The last option is there because of this language in the void-packages CONTRIBUTING:
> Software need to be used in version announced by authors as ready to use by the general public - usually called releases. Betas, arbitrary VCS revisions, templates using tip of development branch taken at build time and releases created by the package maintainer won't be accepted.
I'm not sure whether the nightly tag would be allowed. The SDR++ author recommends the main branch and the `nightly` builds, implying that it is continually "ready for use." But I'm open to working on 1.0.4 instead, if updating is not an option for packaging.
prev parent reply other threads:[~2025-01-23 1:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 18:24 [ISSUE] " agausmann
2024-10-09 8:26 ` tranzystorekk
2024-10-09 12:19 ` classabbyamp
2024-10-09 12:19 ` classabbyamp
2025-01-08 1:59 ` github-actions
2025-01-23 1:57 ` github-actions [this message]
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=20250123015744.21CF4213D0@inbox.vuxu.org \
--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).