Re: update devel/mspdebug to 0.25

2023-12-22 Thread Lucas de Sena
~ping~ > Update devel/mspdebug from 0.23 to the last commit after 0.25. > > Upstream has not tagged an official release since 0.25 (2017). > Development has continued since then, however, with many fixes > and additions, until last commit in 2022. So I think it is ok > to replace GH_TAGNAME with

Re: update devel/mspdebug to 0.25

2023-12-06 Thread Stuart Henderson
On 2023/12/06 11:44, Lucas de Sena wrote: > On 2023-12-06, Stuart Henderson wrote: > > If 0.25 hasn't actually been released please use pre not pl. pl is for > > something post-release and will need EPOCH should there be a real 0.25 > > sometime. See packages-specs(7). > > v0.25 had already been r

Re: update devel/mspdebug to 0.25

2023-12-06 Thread Lucas de Sena
On 2023-12-06, Stuart Henderson wrote: > If 0.25 hasn't actually been released please use pre not pl. pl is for > something post-release and will need EPOCH should there be a real 0.25 > sometime. See packages-specs(7). v0.25 had already been released by upstream in 2017-07-24, see [1]. But devel

Re: update devel/mspdebug to 0.25

2023-12-06 Thread Stuart Henderson
On 2023/12/04 11:25, Lucas de Sena wrote: > Update devel/mspdebug from 0.23 to the last commit after 0.25. > > Upstream has not tagged an official release since 0.25 (2017). > Development has continued since then, however, with many fixes > and additions, until last commit in 2022. So I think it

update devel/mspdebug to 0.25

2023-12-04 Thread Lucas de Sena
Update devel/mspdebug from 0.23 to the last commit after 0.25. Upstream has not tagged an official release since 0.25 (2017). Development has continued since then, however, with many fixes and additions, until last commit in 2022. So I think it is ok to replace GH_TAGNAME with GH_COMMIT here. Ok