Github messages for voidlinux
 help / color / mirror / Atom feed
* [ISSUE] SDRPlusPlus has switched to a "rolling release" model
@ 2024-10-08 18:24 agausmann
  2024-10-09  8:26 ` tranzystorekk
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: agausmann @ 2024-10-08 18:24 UTC (permalink / raw)
  To: ml

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

New 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 on maintainers on what direction you all would prefer:

- **Adding an `SDRPlusPlus-git` package** that follows the nightly tag (Note for clarity: of course `version=<sha>` would be put in the package template, not `version=nightly`)
- **Updating the `SDRPlusPlus` package** to follow the nightly tag (same note)
- **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.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: SDRPlusPlus has switched to a "rolling release" model
  2024-10-08 18:24 [ISSUE] SDRPlusPlus has switched to a "rolling release" model agausmann
@ 2024-10-09  8:26 ` tranzystorekk
  2024-10-09 12:19 ` classabbyamp
                   ` (3 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: tranzystorekk @ 2024-10-09  8:26 UTC (permalink / raw)
  To: ml

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

New comment by tranzystorekk on void-packages repository

https://github.com/void-linux/void-packages/issues/52568#issuecomment-2401674978

Comment:
We generally don't allow nightlies, betas, `-git` etc. Working on a fix for 1.0.4 is preferable (aside from maybe convincing upstream to cut releases every now and then?)

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: SDRPlusPlus has switched to a "rolling release" model
  2024-10-08 18:24 [ISSUE] SDRPlusPlus has switched to a "rolling release" model agausmann
  2024-10-09  8:26 ` tranzystorekk
@ 2024-10-09 12:19 ` classabbyamp
  2024-10-09 12:19 ` classabbyamp
                   ` (2 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: classabbyamp @ 2024-10-09 12:19 UTC (permalink / raw)
  To: ml

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

New comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/issues/52568#issuecomment-2402163494

Comment:
it would also be good to tell upstream we (and other distros) won't be updating the sw

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: SDRPlusPlus has switched to a "rolling release" model
  2024-10-08 18:24 [ISSUE] SDRPlusPlus has switched to a "rolling release" model 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 ` [ISSUE] [CLOSED] " github-actions
  4 siblings, 0 replies; 6+ messages in thread
From: classabbyamp @ 2024-10-09 12:19 UTC (permalink / raw)
  To: ml

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

New comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/issues/52568#issuecomment-2402163494

Comment:
it would also be good to tell upstream we (and other distros) won't be updating the sw

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: SDRPlusPlus has switched to a "rolling release" model
  2024-10-08 18:24 [ISSUE] SDRPlusPlus has switched to a "rolling release" model agausmann
                   ` (2 preceding siblings ...)
  2024-10-09 12:19 ` classabbyamp
@ 2025-01-08  1:59 ` github-actions
  2025-01-23  1:57 ` [ISSUE] [CLOSED] " github-actions
  4 siblings, 0 replies; 6+ messages in thread
From: github-actions @ 2025-01-08  1:59 UTC (permalink / raw)
  To: ml

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

New comment by github-actions[bot] on void-packages repository

https://github.com/void-linux/void-packages/issues/52568#issuecomment-2576555610

Comment:
Issues become stale 90 days after last activity and are closed 14 days after that.  If this issue is still relevant bump it or assign it.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [ISSUE] [CLOSED] SDRPlusPlus has switched to a "rolling release" model
  2024-10-08 18:24 [ISSUE] SDRPlusPlus has switched to a "rolling release" model agausmann
                   ` (3 preceding siblings ...)
  2025-01-08  1:59 ` github-actions
@ 2025-01-23  1:57 ` github-actions
  4 siblings, 0 replies; 6+ messages in thread
From: github-actions @ 2025-01-23  1:57 UTC (permalink / raw)
  To: ml

[-- 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.

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2025-01-23  1:57 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-10-08 18:24 [ISSUE] SDRPlusPlus has switched to a "rolling release" model 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 ` [ISSUE] [CLOSED] " github-actions

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).