Bug#1029186: RFS: libcommons-validator-java/1:1.7-1 [Team] -- ease and speed development and maintenance of validation rules
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "libcommons-validator-java": * Package name : libcommons-validator-java Version : 1:1.7-1 Upstream contact : http://commons.apache.org/validator/ * URL : https://commons.apache.org/proper/commons-validator/ * License : Apache-2.0 * Vcs : https://salsa.debian.org/java-team/libcommons-validator-java Section : java The source builds the following binary packages: libcommons-validator-java - ease and speed development and maintenance of validation rules libcommons-validator-java-doc - API documentation for Commons Validator To access further information about this package, please visit the following URL: https://mentors.debian.net/package/libcommons-validator-java/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/libc/libcommons-validator-java/libcommons-validator-java_1.7-1.dsc Changes since the last upload: libcommons-validator-java (1:1.7-1) UNRELEASED; urgency=medium
Bug#1029033: RFS: ruby-mdl/0.12.0-2 -- Markdown lint tool
@Bastian The point you addressed has been forwarded to the subscribers of the Debian Ruby list. The root of the thread is https://lists.debian.org/debian-ruby/2023/01/msg00032.html Regards, Norwid
merge in vendor branch after "gbp import-orig --no-merge"
Hello, On my repo (on salsa) I usually run gbp import-orig --uscan --pristine I would like to be able to update both pristine and upstream branch when there is a new upstream version but not the debian/latest branch. Reason is that /latest branches an debian/latest branches may have a different update pace. So I found we could run: gbp import-orig --uscan --pristine --no-merge Now my question is: How to update the vendor branches individually with the latest upstream branch (or a given upstream version) and have the same result as a call without '-- no-merge' (which would do a --merge-mode=replace" in my case? There is "git merge upstream/" but the result is not equally the same, at least in the log messages, as when runing gbp import-orig with merge enabled (merge-mode is auto, which in my case becomes 'replace'). (Please, leave me in copy of your answer). Thanks Fab
Bug#1029128: RFS: scm/5f3-4 [RC] [Team] -- Scheme language interpreter
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "scm": * Package name : scm Version : 5f3-4 Upstream contact : [fill in name and email of upstream] * URL : https://people.csail.mit.edu/jaffer/SCM.html * License : GFDL-1.3+, LGPL-3+, GPL-3+ * Vcs : https://salsa.debian.org/scheme-team/scm Section : interpreters The source builds the following binary packages: scm - Scheme language interpreter libscm-dev - Embeddable library for SCM Scheme language interpreter To access further information about this package, please visit the following URL: https://mentors.debian.net/package/scm/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/s/scm/scm_5f3-4.dsc Changes since the last upload: scm (5f3-4) unstable; urgency=medium . * Team upload. * Fix ftbfs on mipsel. Closes: #1029122 * Use libncurses-dev instead of libncurses5-dev -- Regards, -- Bo YU signature.asc Description: PGP signature
