#1147095 RFS: imsprog/1.9.1-1 -- Linux chip programmer for CH341A/CH347T/FT232H devices

#1147095#5
Date:
2026-09-07 13:41:36 UTC
From:
To:
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "imsprog":

  * Package name     : imsprog
    Version          : 1.9.1-1
    Upstream contact : Mikhail Medvedev<e-ink-reader@yandex.ru>
  * URL              :https://github.com/bigbigmdm/IMSProg
  * License          : LGPL-2.1+, BSD-1-Clause, GPL-2+, GPL-3+, GFDL-1.3
  * Vcs              :https://github.com/bigbigmdm/IMSProg/tree/debian/latest
    Section          : devel

The source builds the following binary packages:

   imsprog - Linux chip programmer for CH341A/CH347T/FT232H devices

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

https://mentors.debian.net/package/imsprog/

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

   dget -xhttps://mentors.debian.net/debian/pool/main/i/imsprog/imsprog_1.9.1-1.dsc

Changes since the last upload:

  imsprog (1.9.1-1) unstable; urgency=medium
  .
    * New upstream version:
      - Update debian/copyright.
      - Changed depends, description in debian/control (new hardware added).
      - Removed unnecessary debian/*.maintscript file.

Regards,

#1147095#10
Date:
2026-09-08 15:18:09 UTC
From:
To:
Hello,

Please address this Lintian output on your next upload:

Running lintian...
N:
I: imsprog source: unused-override source-is-missing [IMSProg_programmer/other/index.html] [debian/source/lintian-overrides:2]
N:
N:   Your package specifies the named override but there were no tags that
N:   could have been silenced by it.
N:
N:   Maybe you fixed an underlying condition but forgot to remove the override.
N:   It is also possible that the Lintian maintainers fixed a false positive.
N:
N:   If the override is now unused, please remove it.
N:
N:   This tag is similar to mismatched-override except there a tag could have
N:   been silenced if the context had matched.
N:
N:   Sometimes, overrides end up not being used because a tag appears only on
N:   some architectures. In that case, overrides can be equipped with an
N:   architecture qualifier.
N:
N:   Please refer to Architecture specific overrides (Section 2.4.3) in the
N:   Lintian User's Manual for details.
N:
N:   Visibility: info
N:   Show-Always: yes
N:   Check: lintian
N:
N:
P: imsprog 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: imsprog source: trailing-whitespace [debian/control:28]
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:
X: imsprog 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: imsprog: spelling-error-in-binary NAm Name [usr/bin/IMSProg]
N:
N:   Lintian found a spelling error in the given binary. Lintian has a list of
N:   common misspellings that it looks for. It does not have a dictionary like
N:   a spelling checker does.
N:
N:   If the string containing the spelling error is translated with the help of
N:   gettext or a similar tool, please fix the error in the translations as
N:   well as the English text to avoid making the translations fuzzy. With
N:   gettext, for example, this means you should also fix the spelling mistake
N:   in the corresponding msgids in the *.po files.
N:
N:   You can often find the word in the source code by running:
N:
N:    grep -rw <word> <source-tree>
N:
N:   This tag may produce false positives for words that contain non-ASCII
N:   characters due to limitations in strings.
N:
N:   Visibility: pedantic
N:   Show-Always: no
N:   Check: binaries/spelling
N:   This tag is experimental.
N:
N:
X: imsprog source: very-long-line-length-in-source-file 636 > 512 [IMSProg_programmer/dialogabout.ui:90]
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" <rra@debian.org>
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: imsprog source: very-long-line-length-in-source-file 636 > 512 [IMSProg_programmer/language/chipProgrammer_zh_CN.ts:26]
N:
X: imsprog source: very-long-line-length-in-source-file 636 > 512 [IMSProg_programmer/language/chipProgrammer_zh_TW.ts:26]
N:
X: imsprog source: very-long-line-length-in-source-file 651 > 512 [IMSProg_programmer/language/chipProgrammer_it_IT.ts:27]
N:
X: imsprog source: very-long-line-length-in-source-file 661 > 512 [IMSProg_programmer/language/chipProgrammer_pt_BR.ts:27]
N:
X: imsprog source: very-long-line-length-in-source-file 666 > 512 [IMSProg_programmer/language/chipProgrammer_es_ES.ts:27]
N:
X: imsprog source: very-long-line-length-in-source-file 667 > 512 [IMSProg_programmer/language/chipProgrammer_uk_UA.ts:27]
N:
X: imsprog source: very-long-line-length-in-source-file 670 > 512 [IMSProg_programmer/language/chipProgrammer_ru_RU.ts:27]
N:
X: imsprog source: very-long-line-length-in-source-file 676 > 512 [IMSProg_programmer/language/chipProgrammer_de_DE.ts:27]
N:
X: imsprog source: very-long-line-length-in-source-file 676 > 512 [IMSProg_programmer/language/chipProgrammer_hu_HU.ts:27]
N: 0 hints overridden; 1 unused override

I: Lintian run successful (worst tag: info)

Otherwise, enjoy:

$ dput ssh-upload ../imsprog_1.9.1-1_source.changes
Uploading imsprog using sftp to ssh-upload (host: ssh.upload.debian.org; directory: /srv/upload.debian.org/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
Logging into host ssh.upload.debian.org as tsimonq2
Uploading imsprog_1.9.1-1.dsc
Uploading imsprog_1.9.1.orig.tar.gz
Uploading imsprog_1.9.1-1.debian.tar.xz
Uploading imsprog_1.9.1-1_source.buildinfo
Uploading imsprog_1.9.1-1_source.changes

Best regards,
Simon Quigley
tsimonq2@debian.org