Your message dated Wed, 15 Jul 2026 17:47:37 -0500
with message-id <[email protected]>
and subject line Re: RFS: libhtmlunit-csp-java/4.22.0-1 [RFP] -- Library for 
working with Content Security Policy policies
has caused the Debian Bug report #1135717,
regarding RFS: libhtmlunit-csp-java/4.22.0-1 [RFP] -- Library for working with 
Content Security Policy policies
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1135717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1135717
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "libhtmlunit-csp-java":

 * Package name     : libhtmlunit-csp-java
   Version          : 4.22.0-1
   Upstream contact : Ronald Brill <[email protected]>
 * URL              : https://github.com/HtmlUnit/htmlunit-csp
 * License          : Apache-2.0
 * Vcs              : https://salsa.debian.org/java-team/libhtmlunit-csp-java
   Section          : java

The source builds the following binary packages:

  libhtmlunit-csp-java - Library for working with Content Security Policy 
policies

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

  https://mentors.debian.net/package/libhtmlunit-csp-java/

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

  dget -x 
https://mentors.debian.net/debian/pool/main/libh/libhtmlunit-csp-java/libhtmlunit-csp-java_4.22.0-1.dsc

Changes for the initial release:

 libhtmlunit-csp-java (4.22.0-1) unstable; urgency=medium
 .
   * Initial release. (Closes: #1135340)

Regards,

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


--- End Message ---
--- Begin Message ---
Hello,

I adjusted the long description to remove the placeholder at the end: "(Include 
the long description here.)"

Please address this Lintian output on your next upload:

Running lintian...
N:
I: libhtmlunit-csp-java source: older-debian-watch-file-standard 4 
[debian/watch]
N:                                                                              
                                                                                
                                                                                
N:   The version= line in the debian/watch file in this package declares an
N:   older version. Please upgrade when you have a chance.
N: 
N:   Please refer to the uscan(1) manual page for details.
N: 
N:   Visibility: info
N:   Show-Always: no
N:   Check: debian/watch/standard
N: 
N:
P: libhtmlunit-csp-java source: package-uses-old-debhelper-compat-version 13
N: 
N:   This package uses a debhelper compatibility level that is no longer
N:   recommended. Please consider using the recommended level.
N:   
N:   For most packages, the best way to set the compatibility level is to
N:   specify debhelper-compat (= X) as a Build-Depends in debian/control. You
N:   can also use the debian/compat file or export DH_COMPAT in debian/rules.
N:   
N:   If no level is selected debhelper defaults to level 1, which is
N:   deprecated.
N: 
N:   Please refer to the debhelper(7) manual page for details.
N: 
N:   Visibility: pedantic
N:   Show-Always: no
N:   Check: debhelper
N: 
N:
P: libhtmlunit-csp-java source: redundant-priority-optional-field 
[debian/control:3]
N: 
N:   This package currently sets the Priority field in the debian/control file
N:   to "optional".
N:   
N:   As of dpkg version 1.22.13, this field is set to "optional" by default. As
N:   such, in this case the Priority field is redundant and should be removed.
N: 
N:   Visibility: pedantic
N:   Show-Always: no
N:   Check: debian/control/field/priority
N: 
N:
P: libhtmlunit-csp-java source: trailing-whitespace [debian/control:34]
N: 
N:   This file contains lines with trailing whitespace characters.
N:   
N:   Whilst often harmless and unsightly, such extra whitespaces can also cause
N:   tools to interpret the whitespace characters literally. The tool diff(1)
N:   does not like them, either. They are best avoided.
N:   
N:   Some of these problems can be hard to track down.
N:   
N:   Whitespace at the end of lines may be removed with the following:
N:   
N:    $ sed -i -e 's@[[:space:]]*$@@g' debian/control debian/changelog
N:   
N:   If you use Emacs, you can also use "M-x wh-cl" (whitespace-cleanup).
N:   
N:   However, if you wish to only remove trailing spaces and leave trailing
N:   tabs (eg. for Makefiles), you can use the following code snippet:
N:   
N:    $ sed -i -e 's@[ ]*$@@g' debian/rules
N:   
N:   To remove empty lines from the end of a file, you can use:
N:   
N:    $ sed -i -e :a -e '/^\n*$/{$d;N;};/\n$/ba' debian/rules
N: 
N:   Visibility: pedantic
N:   Show-Always: no
N:   Check: debian/trailing-whitespace
N:   Renamed from: file-contains-trailing-whitespace
N: 
N:
P: libhtmlunit-csp-java source: trailing-whitespace [debian/control:7]
N:
P: libhtmlunit-csp-java source: upstream-metadata-file-is-missing
N: 
N:   This source package is not Debian-native but it does not have a
N:   debian/upstream/metadata file.
N:   
N:   The Upstream MEtadata GAthered with YAml (UMEGAYA) project is an effort to
N:   collect meta-information about upstream projects from any source package.
N:   This file is in YAML format and it is used in to feed the data in the
N:   UltimateDebianDatabase. For example, it can contains the way the authors
N:   want their software be cited in publications and some bibliographic
N:   references about the software.
N:   
N:   Please add a debian/upstream/metadata file.
N: 
N:   Please refer to https://dep-team.pages.debian.net/deps/dep12/ and
N:   https://wiki.debian.org/UpstreamMetadata for details.
N: 
N:   Visibility: pedantic
N:   Show-Always: no
N:   Check: debian/upstream/metadata
N: 
N:
X: libhtmlunit-csp-java source: debian-watch-does-not-check-openpgp-signature 
[debian/watch]
N: 
N:   This watch file does not specify a means to verify the upstream tarball
N:   using a cryptographic signature.
N:   
N:   If upstream distributions provides such signatures, please use the
N:   pgpsigurlmangle options in this watch file's opts= to generate the URL of
N:   an upstream OpenPGP signature. This signature is automatically downloaded
N:   and verified against a keyring stored in debian/upstream/signing-key.asc
N:   
N:   Of course, not all upstreams provide such signatures but you could request
N:   them as a way of verifying that no third party has modified the code after
N:   its release (projects such as phpmyadmin, unrealircd, and proftpd have
N:   suffered from this kind of attack).
N: 
N:   Please refer to the uscan(1) manual page for details.
N: 
N:   Visibility: pedantic
N:   Show-Always: no
N:   Check: debian/watch
N:   Renamed from: debian-watch-does-not-check-gpg-signature
N:   debian-watch-may-check-gpg-signature
N:   This tag is experimental.
N: 
N:
X: libhtmlunit-csp-java source: very-long-line-length-in-source-file 519 > 512 
[README.md:49]
N: 
N:   The source file includes a line length that is well beyond the normally
N:   human made code line length.
N:   
N:   This very long line length does not allow Lintian to do correctly some
N:   source file checks.
N:   
N:   This line could also be the result of some text injected by a computer
N:   program, and thus could lead to FTBFS bugs.
N:   
N:   Last but not least, long line in source code could be used to obfuscate
N:   the source code and to hide stuff like backdoors or security problems.
N:   
N:   It could be due to jslint source comments or other build tool comments.
N:   
N:   You may report this issue upstream.
N: 
N:   Visibility: pedantic
N:   Show-Always: no
N:   Check: files/contents/line-length
N:   Renamed from: insane-line-length-in-source-file
N:   This tag is experimental.
N: 
N:   Screen: autotools/long-lines
N:     Advocates: "Russ Allbery" <[email protected]>
N:     Reason: 
N:             Upstream sources using autoconf have traditionally been
N:             distributed with generated ./configure scripts as well as
N:             other third-party m4 macro files such as libtool.
N:             
N:             When paired with automake, there may also be some intermediate
N:             Makefile.in files.
N:             
N:             A lot of sources potentially contain such files, but they are
N:             not actionable by either the Debian distributor or by the
N:             upstream maintainer.
N:             
N:             As a side note, modern Debian build protocols will re-create
N:             many of those files via dh_autoreconf. They are present merely
N:             to aid in bootstrapping systems where the GNU suite may not yet
N:             be available.
N:             
N:             Read more in Bug#996740.
N: 
N:
X: libhtmlunit-csp-java source: very-long-line-length-in-source-file 8169 > 512 
[src/test/resources/csp.txt:266]

I: Lintian run successful (worst tag: info)

Otherwise, enjoy:

$ dput ftp-master ../libhtmlunit-csp-java_4.22.0-1_amd64.changes
Uploading libhtmlunit-csp-java using ftp to ftp-master (host: 
ftp.upload.debian.org; directory: /pub/UploadQueue/)
running allowed-distribution: check whether a local profile permits uploads to 
the target distribution
running protected-distribution: warn before uploading to distributions where a 
special policy applies
running checksum: verify checksums before uploading
running suite-mismatch: check the target distribution for common errors
running gpg: check GnuPG signatures before the upload
Uploading libhtmlunit-csp-java_4.22.0-1.dsc
Uploading libhtmlunit-csp-java_4.22.0.orig.tar.xz
Uploading libhtmlunit-csp-java_4.22.0-1.debian.tar.xz
Uploading libhtmlunit-csp-java_4.22.0-1_all.deb
Uploading libhtmlunit-csp-java_4.22.0-1_amd64.buildinfo
Uploading libhtmlunit-csp-java_4.22.0-1_amd64.changes

It is now in the Debian NEW queue where it can either be accepted or rejected. 
If it is rejected, feel free to CC me on your followup, and if I'm available, I 
can take another look.

Best regards,
Simon Quigley
[email protected]

--- End Message ---

Reply via email to