Bug#1069620: RFS: lua-mode/20231023~git-1 -- Emacs major-mode for editing Lua programs

2024-08-03 Thread Xiyue Deng
Control: retitle -1 RFS: lua-mode/20221027+git20231023.d074e41-1 -- Emacs 
major-mode for editing Lua programs

Hi Phil,

Phil Wyett  writes:

> [[PGP Signed Part:Undecided]]
> Hi all,
>
> Do we have a consensus as yet on the versioning?
>

I actually lost track of this.  I have now changed to use the version of
the package with git snapshot date plus hash.

New changes pushed to team repo[1] and rebuilt package uploaded to
mentors[2].  PTAL.


> Regards
>
> Phil
>
>
> On Sat, 11 May 2024 10:29:56 -0700 Xiyue Deng  wrote:
>> Hi Tobias,
>> 
>> Tobias Frost  writes:
>> 
>> > Hi Xiyue,
>> >
>> > when packaging a git snapshot, I feel this should be indicated in the
>> > upstream version that it is based on the old one, something like
>> > +
>> >
>> > In your case I'd 20210802+git20231023 as upstream version.
>> >
>> > Long time ago I did something like that for dhewm3, you 
>> > can see the watch file here:
>> >
> https://salsa.debian.org/games-team/dhewm3/-/blob/debian/1.5.0+git20181221+dfsg-1/debian/watch?ref_type=tags
>> >
>> > (not marking moreinfo, as other people might see that differently.)
>> 
>> Thanks for your comments!  I actually also thought about this but ended
>> up not following that idea because it will end up with 3 different
>> versions based on dates:
>> 
>> * 20210802 which is the last tagged version[1],
>> * 20221027 which is specified in the upstream source[2] and will end up
>> in the installed elpa package directory but was never tagged, and
>> * 20231023 which is the date of the latest upstream commit[3] when
>> sending this email.
>> 
>> I think 20210802+git20231023. follows the current practice but
>> will be *very* confusing when user will find that the package is
>> installed at /usr/share/emacs/site-lisp/elpa/lua-mode-20221027.  I chose
>> 20231023~git as a compromise just to avoid having too many dates there,
>> which is still possible to upgrade to 20231023 should that be tagged one
>> day.  I think the next choice could be 20221027+git20231023. just
>> so there is one less date to deal with.
>> 
>> Wdyt?
>> 
>> [1] https://github.com/immerrr/lua-mode/tags
>> [2] https://github.com/immerrr/lua-mode/blob/master/lua-mode.el#L15
>> [3]
> https://github.com/immerrr/lua-mode/commit/d074e4134b1beae9ed4c9b512af741ca0d852ba3
>> 
>> >
>> > --
>> > tobi
>> >
>> > On Sun, Apr 21, 2024 at 10:02:48AM -0700, Xiyue Deng wrote:
>> >> Package: sponsorship-requests
>> >> Severity: normal
>> >> 
>> >> Dear mentors,
>> >> 
>> >> I am looking for a sponsor for my package "lua-mode":
>> >> 
>> >>  * Package name : lua-mode
>> >>    Version  : 20231023~git-1
>> >>    Upstream contact : immerrr 
>> >>  * URL  : https://github.com/immerrr/lua-mode
>> >>  * License  : GPL-3+
>> >>  * Vcs  : https://salsa.debian.org/emacsen-team/lua-mode
>
> -- 
>
> "I play the game for the game’s own sake"
>
> Arthur Conan Doyle - The Adventure of the Bruce-Partington Plans
>
> --
>
> Buy Me A Coffee: https://buymeacoffee.com/kathenasorg
>
> Internet Relay Chat (IRC): kathenas
>
> Matrix: #kathenas:matrix.org
>
> Website: https://kathenas.org
>
> Instagram: https://instagram.com/kathenasorg/
>
> Threads: https://www.threads.net/@kathenasorg


[1] https://salsa.debian.org/emacsen-team/lua-mode
[2] https://mentors.debian.net/package/lua-mode/

-- 
Xiyue Deng


signature.asc
Description: PGP signature


Bug#1069620: RFS: lua-mode/20231023~git-1 -- Emacs major-mode for editing Lua programs

2024-08-03 Thread Phil Wyett
Hi all,

Do we have a consensus as yet on the versioning?

Regards

Phil


On Sat, 11 May 2024 10:29:56 -0700 Xiyue Deng  wrote:
> Hi Tobias,
> 
> Tobias Frost  writes:
> 
> > Hi Xiyue,
> >
> > when packaging a git snapshot, I feel this should be indicated in the
> > upstream version that it is based on the old one, something like
> > +
> >
> > In your case I'd 20210802+git20231023 as upstream version.
> >
> > Long time ago I did something like that for dhewm3, you 
> > can see the watch file here:
> >
https://salsa.debian.org/games-team/dhewm3/-/blob/debian/1.5.0+git20181221+dfsg-1/debian/watch?ref_type=tags
> >
> > (not marking moreinfo, as other people might see that differently.)
> 
> Thanks for your comments!  I actually also thought about this but ended
> up not following that idea because it will end up with 3 different
> versions based on dates:
> 
> * 20210802 which is the last tagged version[1],
> * 20221027 which is specified in the upstream source[2] and will end up
> in the installed elpa package directory but was never tagged, and
> * 20231023 which is the date of the latest upstream commit[3] when
> sending this email.
> 
> I think 20210802+git20231023. follows the current practice but
> will be *very* confusing when user will find that the package is
> installed at /usr/share/emacs/site-lisp/elpa/lua-mode-20221027.  I chose
> 20231023~git as a compromise just to avoid having too many dates there,
> which is still possible to upgrade to 20231023 should that be tagged one
> day.  I think the next choice could be 20221027+git20231023. just
> so there is one less date to deal with.
> 
> Wdyt?
> 
> [1] https://github.com/immerrr/lua-mode/tags
> [2] https://github.com/immerrr/lua-mode/blob/master/lua-mode.el#L15
> [3]
https://github.com/immerrr/lua-mode/commit/d074e4134b1beae9ed4c9b512af741ca0d852ba3
> 
> >
> > --
> > tobi
> >
> > On Sun, Apr 21, 2024 at 10:02:48AM -0700, Xiyue Deng wrote:
> >> Package: sponsorship-requests
> >> Severity: normal
> >> 
> >> Dear mentors,
> >> 
> >> I am looking for a sponsor for my package "lua-mode":
> >> 
> >>  * Package name : lua-mode
> >>    Version  : 20231023~git-1
> >>    Upstream contact : immerrr 
> >>  * URL  : https://github.com/immerrr/lua-mode
> >>  * License  : GPL-3+
> >>  * Vcs  : https://salsa.debian.org/emacsen-team/lua-mode

-- 

"I play the game for the game’s own sake"

Arthur Conan Doyle - The Adventure of the Bruce-Partington Plans

--

Buy Me A Coffee: https://buymeacoffee.com/kathenasorg

Internet Relay Chat (IRC): kathenas

Matrix: #kathenas:matrix.org

Website: https://kathenas.org

Instagram: https://instagram.com/kathenasorg/

Threads: https://www.threads.net/@kathenasorg

--








signature.asc
Description: This is a digitally signed message part


Bug#1069620: RFS: lua-mode/20231023~git-1 -- Emacs major-mode for editing Lua programs

2024-05-11 Thread Xiyue Deng
Hi Tobias,

Tobias Frost  writes:

> Hi Xiyue,
>
> when packaging a git snapshot, I feel this should be indicated in the
> upstream version that it is based on the old one, something like
> +
>
> In your case I'd 20210802+git20231023 as upstream version.
>
> Long time ago I did something like that for dhewm3, you 
> can see the watch file here:
> https://salsa.debian.org/games-team/dhewm3/-/blob/debian/1.5.0+git20181221+dfsg-1/debian/watch?ref_type=tags
>
> (not marking moreinfo, as other people might see that differently.)

Thanks for your comments!  I actually also thought about this but ended
up not following that idea because it will end up with 3 different
versions based on dates:

* 20210802 which is the last tagged version[1],
* 20221027 which is specified in the upstream source[2] and will end up
in the installed elpa package directory but was never tagged, and
* 20231023 which is the date of the latest upstream commit[3] when
sending this email.

I think 20210802+git20231023. follows the current practice but
will be *very* confusing when user will find that the package is
installed at /usr/share/emacs/site-lisp/elpa/lua-mode-20221027.  I chose
20231023~git as a compromise just to avoid having too many dates there,
which is still possible to upgrade to 20231023 should that be tagged one
day.  I think the next choice could be 20221027+git20231023. just
so there is one less date to deal with.

Wdyt?

[1] https://github.com/immerrr/lua-mode/tags
[2] https://github.com/immerrr/lua-mode/blob/master/lua-mode.el#L15
[3] 
https://github.com/immerrr/lua-mode/commit/d074e4134b1beae9ed4c9b512af741ca0d852ba3

>
> --
> tobi
>
> On Sun, Apr 21, 2024 at 10:02:48AM -0700, Xiyue Deng wrote:
>> Package: sponsorship-requests
>> Severity: normal
>> 
>> Dear mentors,
>> 
>> I am looking for a sponsor for my package "lua-mode":
>> 
>>  * Package name : lua-mode
>>Version  : 20231023~git-1
>>Upstream contact : immerrr 
>>  * URL  : https://github.com/immerrr/lua-mode
>>  * License  : GPL-3+
>>  * Vcs  : https://salsa.debian.org/emacsen-team/lua-mode
>>Section  : lisp
>> 
>> The source builds the following binary packages:
>> 
>>   elpa-lua-mode - Emacs major-mode for editing Lua programs
>> 
>> To access further information about this package, please visit the following 
>> URL:
>> 
>>   https://mentors.debian.net/package/lua-mode/
>> 
>> Alternatively, you can download the package with 'dget' using this command:
>> 
>>   dget -x 
>> https://mentors.debian.net/debian/pool/main/l/lua-mode/lua-mode_20231023~git-1.dsc
>> 
>> Changes since the last upload:
>> 
>>  lua-mode (20231023~git-1) unstable; urgency=medium
>>  .
>>* Sync to latest upstream snapshot (d074e41)
>>* Drop the patch applied upstream and reorder the remaining patch
>>* Update upstream license to GPL-3+ following upstream change
>>* Add a missing upstream copyright holder
>> 
>> Regards,
>> -- 
>> Xiyue Deng
>> 

-- 
Xiyue Deng



Bug#1069620: RFS: lua-mode/20231023~git-1 -- Emacs major-mode for editing Lua programs

2024-05-11 Thread Tobias Frost
Hi Xiyue,

when packaging a git snapshot, I feel this should be indicated in the
upstream version that it is based on the old one, something like
+

In your case I'd 20210802+git20231023 as upstream version.

Long time ago I did something like that for dhewm3, you 
can see the watch file here:
https://salsa.debian.org/games-team/dhewm3/-/blob/debian/1.5.0+git20181221+dfsg-1/debian/watch?ref_type=tags

(not marking moreinfo, as other people might see that differently.)

--
tobi

On Sun, Apr 21, 2024 at 10:02:48AM -0700, Xiyue Deng wrote:
> Package: sponsorship-requests
> Severity: normal
> 
> Dear mentors,
> 
> I am looking for a sponsor for my package "lua-mode":
> 
>  * Package name : lua-mode
>Version  : 20231023~git-1
>Upstream contact : immerrr 
>  * URL  : https://github.com/immerrr/lua-mode
>  * License  : GPL-3+
>  * Vcs  : https://salsa.debian.org/emacsen-team/lua-mode
>Section  : lisp
> 
> The source builds the following binary packages:
> 
>   elpa-lua-mode - Emacs major-mode for editing Lua programs
> 
> To access further information about this package, please visit the following 
> URL:
> 
>   https://mentors.debian.net/package/lua-mode/
> 
> Alternatively, you can download the package with 'dget' using this command:
> 
>   dget -x 
> https://mentors.debian.net/debian/pool/main/l/lua-mode/lua-mode_20231023~git-1.dsc
> 
> Changes since the last upload:
> 
>  lua-mode (20231023~git-1) unstable; urgency=medium
>  .
>* Sync to latest upstream snapshot (d074e41)
>* Drop the patch applied upstream and reorder the remaining patch
>* Update upstream license to GPL-3+ following upstream change
>* Add a missing upstream copyright holder
> 
> Regards,
> -- 
> Xiyue Deng
> 



Bug#1069620: RFS: lua-mode/20231023~git-1 -- Emacs major-mode for editing Lua programs

2024-04-21 Thread Xiyue Deng
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "lua-mode":

 * Package name : lua-mode
   Version  : 20231023~git-1
   Upstream contact : immerrr 
 * URL  : https://github.com/immerrr/lua-mode
 * License  : GPL-3+
 * Vcs  : https://salsa.debian.org/emacsen-team/lua-mode
   Section  : lisp

The source builds the following binary packages:

  elpa-lua-mode - Emacs major-mode for editing Lua programs

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/lua-mode/

Alternatively, you can download the package with 'dget' using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/l/lua-mode/lua-mode_20231023~git-1.dsc

Changes since the last upload:

 lua-mode (20231023~git-1) unstable; urgency=medium
 .
   * Sync to latest upstream snapshot (d074e41)
   * Drop the patch applied upstream and reorder the remaining patch
   * Update upstream license to GPL-3+ following upstream change
   * Add a missing upstream copyright holder

Regards,
-- 
Xiyue Deng