Bug#1066043: RFS: lem/2022-12-10+dfsg-1 [ITP] -- Tool merging math and logic for executable definitions (tool)

[Bo YU]

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: debian-ocaml-***@lists.debian.org

Dear mentors,

I am looking for a sponsor for my package "lem":

* Package name : lem
Version : 2022-12-10+dfsg-1
Upstream contact : Lem Devs <cl-lem-***@lists.cam.ac.uk>
* URL : https://github.com/rems-project/lem
* License : GPL-2, BSD-3-clause
* Vcs : https://salsa.debian.org/ocaml-team/lem
Section : ocaml

The source builds the following binary packages:

lem - Tool merging math and logic for executable definitions (tool)
liblem-ocaml-dev - Tool merging math and logic for executable definitions (development)

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

https://mentors.debian.net/package/lem/

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

dget -x https://mentors.debian.net/debian/pool/main/l/lem/lem_2022-12-10+dfsg-1.dsc

Changes for the initial release:

lem (2022-12-10+dfsg-1) UNRELEASED; urgency=low
.
* Initial release. (Closes: #1065658)

[Bo YU]

Hi philip!

Hi Bo,
Bringing onto RFS now and for all reviews in the future as was requested on IRC.

Many thanks for it. I was just missing the message to fail to notice
it and any review on IRC(if have), please tell me any issue again if I
did not response to in time.

Bo, As was discussed on the mentors webite. The package review has taken place
and I believe this package is now ready for entry into Debian. Many thanks for
creating this package for Debian.
Note: If any other mentors/developers would like to offer constructive criticism
on the package it would be gratefully received.

Yeah, thanks again. I eagerly hope to receive any reviews that can
improve it and please let me know any issues.

BR,
Bo

Regards
Phil
--
Website: https://kathenas.org
Instagram: https://instagram.com/kathenasorg/
Buy Me A Coffee: https://buymeacoffee.com/kathenasorg

[Bo YU]

Hi Philip,

Thanks for reviewing the package again.

Post by Bo YU
Hi philip!

Hi Bo,
Bringing onto RFS now and for all reviews in the future as was requested on IRC.

Many thanks for it. I was just missing the message to fail to notice
it and any review on IRC(if have), please tell me any issue again if I
did not response to in time.

Bo, As was discussed on the mentors webite. The package review has taken place
and I believe this package is now ready for entry into Debian. Many thanks for
creating this package for Debian.
Note: If any other mentors/developers would like to offer constructive criticism
on the package it would be gratefully received.

May I know the status of the review for the package? Sorry if I am not
polite to ask about the progress of this. I wonder if something is
forgetten in case.

The package is main blocker for linksem[0] and may need more time to
review it for Debian, So I'm going to take the liberty of asking.

Sorry again.

BR,
Bo

[0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067819

Post by Bo YU
Yeah, thanks again. I eagerly hope to receive any reviews that can
improve it and please let me know any issues.
BR,
Bo

Regards
Phil
--
Website: https://kathenas.org
Instagram: https://instagram.com/kathenasorg/
Buy Me A Coffee: https://buymeacoffee.com/kathenasorg

[Bo YU]

Hi philip,

Good night.:)

Morning Bo,
Build after successful build is good.
Skimming through the files.
1. You may want to disable 'export DH_VERBOSE = 1' in 'debian/rules'.
For your notepad for future. :-)

Done and will be kept in mind.:)

1. 'debian/control', Update 'Standards-Version' to latest.

Done.

2. This package release was 2022. The files section in 'debian/copyright' is up
to 2020. A check if anything new has been added, removed or other etc. The usual
fun with making sure the copyright file is accurate.

Yeah, this also confuses me also. Because from upstream's copyright,
it was flagged 2010-2020[0]. But after 2020, there are obviously many
update for codebase, so I think it is okay to extern the year of
copyright of upstream to 2024. Please correct me if I'm wrong.

Other than that, I think a DD from mentors or the OCaml team can look at the
package for possible sponsorship.

\o/.

Do you mind me asking for help from my previous OCaml package mentor
to sponsor it?

Thanks again,

BR,
Bo
[0]: https://github.com/rems-project/lem/blob/master/LICENSE#L3

Regards
Phil
--
Internet Relay Chat (IRC): kathenas
Website: https://kathenas.org
Instagram: https://instagram.com/kathenasorg/
Buy Me A Coffee: https://buymeacoffee.com/kathenasorg

[Bo YU]

Hi,

Post by Bo YU
[0]: https://github.com/rems-project/lem/blob/master/LICENSE#L3

Hi Bo,
I would be more pragmatic here and leave the copyright year for now and enquire
upstream if year and copyrights are correct or due for update. They are the
ultimate source and will give the best data.

Okay, I agree with this also. I have reported this to upsteam[0] also.
But for my change[1] about it, I would like to keep it first and then
to see the upstream's response or sponsor's suggestions.

By sponsor you mean Gianfranco? I think we can see if he has a little free time
once you get information back from upstream and if any additional changes need
be made. Maybe another DD could offer insight here and would maybe now sponsor
the package now and copyright modifications if any can be done in a near future
upload? I will always take sage advise from others, as every day is a school
day!

Yeah, thanks.

Here I am ccing Gianfranco(sorry if I disturbed Gianfranco). So hi
Gianfranco, could you have a look at the package in your free time? I
believe Philip who has helped me to improve it a lot, but maybe we did
not notice something else. Please let me any issues.

Thanks all again.

BR,
Bo

Phil

[0]: https://github.com/rems-project/lem/issues/35
[1]: https://salsa.debian.org/ocaml-team/lem/-/commit/fb4464430c30cc07f3cd23ebfeecd45e78c7529f

--