Bug#1031123: reply: Bug#1031123: RFS: libcommons-collections4-java/4.4-1 [Team] -- Apache Commons Collections - Extended Collections API for Java
Hi, Pierre Gruet: Thanks for your kind advice. > I think it is really fine to care for this package now, but as we are in > the soft freeze period, I would upload to experimental: I used > japi-compliance-checker to see the differences between the jars in > version 4.2-1 and in (your candidate) 4.4-1, and there has been a small > number of (upstream) return types changes. The number of > reverse-dependencies is too large to be tested with ratt at home. All the warnings are solved and please see Upload #3. But for the ratt, it’s really a headache for me too. Could I leave it for the Debian CI ? Please tell me if there are any issues still need to be fixed. Best !
Bug#1031123: RFS: libcommons-collections4-java/4.4-1 [Team] -- Apache Commons Collections - Extended Collections API for Java
Hi, Hilmar Preuße, and tony: Thanks for you guide! I will keep the distribution tag "UNRELEASED" as it is for the sponsor. The debian/watch was modified to direct to apache archive site ,because: 1.Tag names from github are not well defined[1]. 2.Some github release even introduces nonexisted files[2]. I think the apache site will do a little more strict check before archiving. I uploaded again, please refer to mentors.debian.(Upload #2.) [1]https://github.com/apache/commons-collections/tags [2]https://lists.debian.org/debian-java/2023/01/msg00029.html [3]https://mentors.debian.net/package/libcommons-collections4-java/
Bug#1031123: RFS: libcommons-collections4-java/4.4-1 [Team] -- Apache Commons Collections - Extended Collections API for Java
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "libcommons-collections4-java": * Package name : libcommons-collections4-java Version : 4.4-1 Upstream contact : [fill in name and email of upstream] * URL : http://commons.apache.org/collections/ * License : Apache-2.0 * Vcs : https://salsa.debian.org/java-team/libcommons-collections4-java Section : java The source builds the following binary packages: libcommons-collections4-java - Apache Commons Collections - Extended Collections API for Java libcommons-collections4-java-doc - Documentation for Commons Collections 4 To access further information about this package, please visit the following URL: https://mentors.debian.net/package/libcommons-collections4-java/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/libc/libcommons-collections4-java/libcommons-collections4-java_4.4-1.dsc Changes since the last upload: libcommons-collections4-java (4.4-1) UNRELEASED; urgency=medium . * Team upload. * New upstream release. * Update debian/watch. * Update maven.compiler.release to java 9. Regards, -- sun min
Bug#1029186: reply: RFS: libcommons-validator-java/1:1.7-1 [Team] -- ease and speed development and maintenance of validation rules
> Hello Min Sun, > > is there a particular reason why you opt for / stick to distribution > `UNRELEASED` for a package already monitored by the tracker?[1] It is the > entry e.g., `dch -i` puts into file `/debian/changelog` when you start to work > on a new version (increment) of a package. After all other other work on your > side is done, an eventual change to the string `unstable` (then lower case > only) is one of the keys necessary to let results of your work enter branch > `unstable`, and later `testing`, etc. Thanks for your clarification, Tony, I did not mean to specify it as `UNRELEASE`, the ‘uscan and uupdate” tools insert this keyword to debian/changelog. I am not clear about the internal mechanism from `UNRELEASED` to `testing` and later stage. I need learn more about Debian policy along with your guideline. All the best.
Bug#1029186: reply: RFS: libcommons-validator-java/1:1.7-1 [Team] -- ease and speed development and maintenance of validation rules
Hi mentors! I packaged new version of libcommons-validator [1] and uploaded again to debian mentors[2], please refer to Upload #2 . The below line from debian/maven.properties was omitted to ensure all the tests get passed. maven.test.failure.ignore=true In fact all the test cases should get passed. But the DomainValidatorStartupTest depends on a package not available in Debian, which breaks the building. I plan to skip it during the testing but have no ways . And finally I decide to remove it entirely through adding a new patch. I’d appreciate for your further sponsorship. [1] https://archive.apache.org/dist/commons/validator/source/commons-validator-1.7-src.tar.gz [2] https://mentors.debian.net/package/libcommons-validator-java/
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 . * Team upload. * New upstream release. * Add commons-csv-java as new dependency. * Skip running the tests. This new version needs a test dependency called junit-clptr which is not ported to debian currently, I don’t know how to handle this issue and just ignore it,and have to skip the test. I tried to enable the test and build locally with bellow command: dpkg-buildpackage -us -uc The test results shows that : [WARNING] Tests run: 25, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.025 s - in org.apache.commons.validator.routines.EmailValidatorTest [WARNING] Tests run: 576, Failures: 0, Errors: 0, Skipped: 1 I think it is harmless to disable the test for now. I’m not familiar with java packaging and any suggestion or advice is welcome. Regards, -- sun min
Bug#1028536: RFS: doxia/1.12.0-1 [Team] -- Doxia content generation framework (core)
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "doxia": This is the newest tagged version of upstream. * Package name : doxia Version : 1.12.0-1 Upstream contact : [fill in name and email of upstream] * URL : http://maven.apache.org/doxia/ * License : Apache-2.0 * Vcs : https://salsa.debian.org/java-team/doxia Section : java The source builds the following binary packages: libdoxia-java - Doxia content generation framework (modules) libdoxia-core-java - Doxia content generation framework (core) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/doxia/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/d/doxia/doxia_1.12.0-1.dsc Changes since the last upload: doxia (1.12.0-1) UNRELEASED; urgency=medium . * Team upload. * New upstream release. Regards, -- sun min
Bug#1028193: RFS: libcommons-validator-java/1:1.6-3 [NMU] -- 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.6-3 Upstream contact : http://commons.apache.org/validator/ * URL : http://commons.apache.org/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.6-3.dsc Changes since the last upload: libcommons-validator-java (1:1.6-3) UNRELEASED; urgency=medium . * Update upstream repo url and vcs-git url * Update upstream tar script Regards, -- sun min
Bug#1020988: ITP: golang-github-monochromegane-go-gitignore -- A fast gitignore matching library for Go
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020988 * Package name: golang-github-monochromegane-go-gitignore Version : 0.0~git20200626.205db1a-1 Upstream Author : monochromegane * URL : https://github.com/monochromegane/go-gitignore * License : Expat Programming Lang: Go Description : A fast gitignore matching library for Go. go-gitignore Build Status (https://travis-ci.org/monochromegane/go- gitignore) Live for truth,goodness and beauty
