- Package:
- sponsorship-requests
- Source:
- sponsorship-requests
- Submitter:
- Jacob Mealey
- Date:
- 2026-09-13 21:37:01 UTC
- Severity:
- normal
Dear mentors, I am looking for a sponsor for my package "janet": * Package name : janet Version : 1.42.1-1 Upstream contact : Calvin Rose <calsrose@gmail.com> * URL : https://janet-lang.org/ * License : Expat * Vcs : https://salsa.debian.org/jacobmealey/janet Section : interpreters The source builds the following binary packages: janet - Lisp-like programming language for system scripting libjanet-dev - Development files for the Janet programming language libjanet1.42 - Shared libraries for the Janet programming language To access further information about this package, please visit the following URL: https://mentors.debian.net/package/janet/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/j/janet/janet_1.42.1-1.dsc Changes since the last upload: janet (1.42.1-1) unstable; urgency=medium . * Update to Janet 1.42.1 Regards, -- Jacob Mealey
Hi Jacob, Thanks for working on an update for this package! It looks like you dropped a reverse-applicable patch and renamed a binary package. Could you please note these in the changelog? Feel free to re-upload to mentors with the same changelog stanza and version, not a new one. For future reference, it would be good for you to note in the request that a pass through NEW will be needed, so a binary upload is done instead of a source one. Once that's done, feel free to remove the "moreinfo" flag from this bug. You can do that in almost the same way I added it, by starting the body of your message with "Control: tags -1 -moreinfo" I hope this helps. Feel free to CC me on your followup, and I can take another look if I'm available. If you have any questions, just let me know. Best regards, Simon Quigley tsimonq2@debian.org
Thanks for reviewing this, and the advice! I've reuploaded to mentors. Do you have any recomendations for making libjanet have a constant name? upstream changes the soname with every release and so I update the package to reflect the new soname for the library, I largely followed liblua as a reference when working on this package but there may be a better way to handle it.
Then I'm afraid you need to change the binary name too, and do transitions.
Hello, Fortunately, janet has no reverse dependencies, so we won't have to worry about that last part. Andrey is right though, the binary package rename is necessary. Let us know if you need further clarification. Best regards, Simon Quigley tsimonq2@debian.org
Thanks both for the advice, I ended up doing the rename by following [1] and uploaded to mentors. Happy to make any further changes!
... Forgot the link <https://wiki.debian.org/RenamingPackages>