Yeah, I agree.

On Mon, 4 Sept 2023, 15:16 Marcell Meszaros, <marcell.mesza...@runbox.eu>
wrote:

> Upstream stated they have no intention or capacity to maintain the legacy
> gnuradio 3.8 branch.
>
> This git package does not provide 'gnuradio38' [a], so it has no
> dependents, only the latter does.
>
> But both this and that package fails to build.
>
> The few dependents of 'gnuradio38' are all dead and fail to build as well,
> or some of them actually have upstream updates or third-party forks that
> work with gnuradio 3.10.
>
> So keeping this package is completely superfluous in my view.
>
> [a]: https://aur.archlinux.org/packages/gnuradio38?all_reqs=1#pkgreqs
>
>
> On 13 August 2023 06:46:05 GMT+02:00, "Nick Østergaard" <oe.n...@gmail.com>
> wrote:
>
>> Hi
>>
>> I am not sure that is fair as such, people could be using it for legacy
>> oot modules, and there is someone trying it out at least two weeks ago, see
>> https://github.com/gnuradio/gnuradio/issues/6762
>>
>> I must admit, that I have not touched it in a while.
>>
>> Nick
>>
>> On Sun, 13 Aug 2023 at 01:35, <not...@aur.archlinux.org> wrote:
>>
>>> MarsSeed [1] filed a deletion request for gnuradio-maint38-git [2]:
>>>
>>> gnuradio 3.8 is not maintained since
>>> 2022-03 (last release 2022-01). [a]
>>>
>>> Nothing depends on this VCS package.
>>>
>>> I recommend deletion.
>>>
>>> [a]: https://github.com/gnuradio/gnuradio/commits/maint-3.8
>>>
>>> [1] https://aur.archlinux.org/account/MarsSeed/
>>> [2] https://aur.archlinux.org/pkgbase/gnuradio-maint38-git/
>>
>>

Reply via email to