Your message dated Wed, 15 Jul 2026 12:32:54 -0500
with message-id <[email protected]>
and subject line Re: RFS: file-kanji/1.1-23 [ITA] -- kanji code checker
has caused the Debian Bug report #1142122,
regarding RFS: file-kanji/1.1-23 [ITA] -- kanji code checker
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.)
--
1142122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1142122
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "file-kanji":
* Package name : file-kanji
Version : 1.1-23
Upstream contact : Norizaku Ito <[email protected]>
* URL : [fill in URL of upstream's web site]
* License : public-domain
* Vcs : https://salsa.debian.org/debian/file-kanji
Section : misc
The source builds the following binary packages:
file-kanji - kanji code checker
To access further information about this package, please visit the
following URL:
https://mentors.debian.net/package/file-kanji/
Alternatively, you can download the package with 'dget' using this
command:
dget -x
https://mentors.debian.net/debian/pool/main/f/file-kanji/file-kanji_1.1-23.dsc
Changes since the last upload:
file-kanji (1.1-23) unstable; urgency=medium
.
* d/control: change maintainer to me (Closes: #897562)
* d/control: upgrade debhelper compatibility to 14
* d/control: remove Rules-Requires-Root: no field
* d/control: remove Priority: optional field
* d/control: upgrade standards version to 4.7.4
* add a lintian override to stop lintian from moaning
Regards,
--
Luke Yasuda
--- End Message ---
--- Begin Message ---
Hello,
With debhelper-compat 14 you can also drop ${shlibs:Depends}.
Additionally, please take a look at this Lintian output and address it on your
next upload:
Running lintian...
N:
I: file-kanji 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:
I: file-kanji source: patch-not-forwarded-upstream
[debian/patches/06-cross.patch]
N:
N: According to the DEP-3 headers, this patch has not been forwarded
N: upstream.
N:
N: Please forward the patch and try to have it included in upstream's version
N: control system. If the patch is not suitable for that, please mention
N: not-needed in the Forwarded field of the patch header.
N:
N: If the patch was actually taken from upstream, please prefix the Origin
N: field information with upstream or backport, as documented in the DEP-3.
N: For example:
N:
N: Origin: upstream,
https://github.com/zim-desktop-wiki/zim-desktop-wiki/commit/d33286c75b623cfb249c627b0c348be62e6377c9.patch
N:
N: Please refer to social contract item 2, Coordination with upstream
N: developers (Section 3.1.4) in the Debian Developer's Reference, Changes to
N: the upstream sources (Section 4.3) in the Debian Policy Manual,
N: Bug#755153, and https://dep-team.pages.debian.net/deps/dep3/ for details.
N:
N: Visibility: info
N: Show-Always: no
N: Check: debian/patches/dep3
N: Renamed from: send-patch
N:
N:
I: file-kanji source: patch-not-forwarded-upstream
[debian/patches/07-hardening-flag.patch]
N:
I: file-kanji source: patch-not-forwarded-upstream
[debian/patches/implicit-int.patch]
N:
I: file-kanji source: patch-not-forwarded-upstream
[debian/patches/missing-prototypes.patch]
N:
P: file-kanji source: maintainer-manual-page [debian/file2.1]
N:
N: The maintainer keeps a manual page in ./debian. Please forward the manual
N: page upstream and ask them to include in their version control system, and
N: in their next release.
N:
N: If the manual page was already forwarded or rejected, or the upstream is
N: gone, please override the tag and annotate it with a suitable comment.
N:
N: Please refer to social contract item 2, Coordination with upstream
N: developers (Section 3.1.4) in the Debian Developer's Reference, and
N: Changes to the upstream sources (Section 4.3) in the Debian Policy Manual
N: for details.
N:
N: Visibility: pedantic
N: Show-Always: no
N: Check: debian/manual-pages
N: Renamed from: maintainer-manpage
N:
N:
P: file-kanji source: no-homepage-field
N:
N: This non-native package lacks a Homepage field. If the package has an
N: upstream home page that contains useful information or resources for the
N: end user, consider adding a Homepage control field to debian/control.
N:
N: Please refer to Homepage (Section 5.6.23) in the Debian Policy Manual for
N: details.
N:
N: Visibility: pedantic
N: Show-Always: no
N: Check: fields/homepage
N:
N:
P: file-kanji 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: file-kanji 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:
I: Lintian run successful (worst tag: info)
Otherwise, enjoy:
$ dput ftp-master ../file-kanji_1.1-23_source.changes
Uploading file-kanji 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 file-kanji_1.1-23.dsc
Uploading file-kanji_1.1.orig.tar.gz
Uploading file-kanji_1.1-23.debian.tar.xz
Uploading file-kanji_1.1-23_source.buildinfo
Uploading file-kanji_1.1-23_source.changes
Best regards,
Simon Quigley
[email protected]
--- End Message ---
