Bug#1084044: RFS: elpher/3.6.3-1 [Team] -- friendly gopher and gemini client
Sean Whitton <spwhitton@spwhitton.name> writes:
> Hello,
>
> On Sat 05 Oct 2024 at 05:24pm -07, Xiyue Deng wrote:
>
>> Hi Sean,
>>
>> Sean Whitton <spwhitton@spwhitton.name> writes:
>>
>>> Hello Xiyue,
>>>
>>> Upstream haven't pushed a v3.6.3 tag. Are you sure that this isn't
>>> 3.6.3~git... instead, then?
>>>
>>
>> As a matter of fact the latest tag on the official Git repo is v3.6.0,
>> while on nongnu ELPA the latest version is now 3.6.3[1], so I manually
>> merged the commit e3760df in "debian/upstream"[2] which had the commit
>> message "Version bump" and tagged the merged commit as upstream/3.6.3.
>> Hope that is acceptable.
>
> I don't think we can assume that, without a tag. I think it should use
> a 3.6.3~gitYYYYMMDD... version number.
>
Make sense. Though I am kinda sure that commit was what upstream used
for the tarball of version 3.6.3, using a snapshot version format is
safer. Just pushed another commit[1] to fix the version accordingly and
reuploaded to mentors. PTAL.
> --
> Sean Whitton
[1] https://salsa.debian.org/emacsen-team/elpher/-/commit/759981adbb1a715f9a6c54ac7562d892ca77d1a7
--
Xiyue Deng
Reply to: