DFSG, Licensing & New Packages Team

debian/copyright check

Command: cme check dpkg-copyright
Exit code: 0

(no output)

licenserecon

Command: licenserecon
Exit code: 0

en: Versions: licenserecon '14.0'  licensecheck '3.3.9-1'

Parsing Source Tree  ....
Reading d/copyright  ....
Running licensecheck ....

No significant differences found

Look for SPDX

Command: grep -r -B1 'SPDX-'
Exit code: 1

(no output)

Lintian

Command: lintian -i -I -v --pedantic
Exit code: 0

N:
I: python-valkey 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: python-valkey source: patch-not-forwarded-upstream [debian/patches/remove-exe-permissions-client-py.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: python3-valkey: synopsis-is-a-sentence "Python interface to the Valkey key-value store."
N: 
N:   The package synopsis (also known as the "short" description, ie. the first
N:   line in the package's "Description:" field) either ends with a full stop
N:   "." character or starts another sentence.
N:   
N:   This is not necessary as the synopsis does not need to be a full sentence.
N:   It is recommended that a single descriptive phrase is used instead.
N:   
N:   Note also that the synopsis is not part of the rest of the "long"
N:   Description: field.
N: 
N:   Please refer to The package synopsis, or short description (Section 6.2.2)
N:   in the Debian Developer's Reference for details.
N: 
N:   Visibility: info
N:   Show-Always: no
N:   Check: fields/description
N:   Renamed from: description-synopsis-might-not-be-phrased-properly
N: 
N:
P: python-valkey source: package-does-not-install-examples [docs/examples/]
N: 
N:   The original source tarball contains the specified examples directory.
N:   However, no examples are installed in any binary packages.
N:   
N:   Please use dh_installexamples to install these to the most relevant
N:   package, for example by adding the directory name followed by a wildcard
N:   to a debian/pkgname.examples file.
N:   
N:   Lintian looks for any directory called examples under /usr/share/doc in
N:   all binary packages.
N: 
N:   Please refer to the dh_installexamples(1) manual page for details.
N: 
N:   Visibility: pedantic
N:   Show-Always: no
N:   Check: examples
N: 
N:   Screen: examples/in-tests
N:     Advocates: "Scott Kitterman" <debian@kitterman.com>
N:     Reason: 
N:             Some sources like python-tomlkit trigger this tag for tests because of files
N:             in ./tests/examples/. They are not examples for tomlkit, however. They are
N:             examples of TOML files used in the tests.
N:             
N:             Overall, the check is probably better off not looking in test
N:             directories.
N:             
N:             Read more in Bug#1005184.
N: 

duck

Command: duck
Exit code: 0

(no output)

look for copyright

Command: egrep -R -i copyright
Exit code: 0

tests/test_asyncio/testdata/titles.csv:copyright law of the netherlands,2
tests/testdata/titles.csv:copyright law of the netherlands,2
LICENSE:Copyright (c) 2022-2023, Redis, inc.
LICENSE:Copyright (c) 2024-present, valkey-py contributors
LICENSE:The above copyright notice and this permission notice shall be included in all
LICENSE:AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
docs/conf.py:copyright = f"{current_year}, Valkey"
docs/conf.py:# If true, "(C) Copyright ..." is shown in the HTML footer. Default is True.
docs/conf.py:# html_show_copyright = True
docs/conf.py:epub_copyright = "2023, Redis Ltd"
util/wait-for-it.sh:# Copyright (c) 2016 Giles Hall
util/wait-for-it.sh:# The above copyright notice and this permission notice shall be included in all
util/wait-for-it.sh:# AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
debian/copyright:Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
debian/copyright:Copyright: 2022-2023, Redis, inc.
debian/copyright:Copyright: 2026 Lena Voytek <lena@voytek.dev>
debian/copyright: The above copyright notice and this permission notice shall be included in
debian/copyright: AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER

look for license

Command: egrep -R -i license
Exit code: 0

LICENSE:MIT License
LICENSE:to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
docs/index.rst:License
docs/index.rst:This project is licensed under the `MIT license <https://github.com/valkey-io/valkey-py/blob/master/LICENSE>`_.
util/wait-for-it.sh:# The MIT License (MIT)
util/wait-for-it.sh:# use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
pyproject.toml:license = { file = "LICENSE" }
pyproject.toml:    "License :: OSI Approved :: MIT License",
debian/copyright:License: Expat
debian/copyright:License: Expat
debian/copyright:License: Expat
debian/copyright: publish, distribute, sublicense, and/or sell copies of the Software,
README.md:[![MIT licensed](https://img.shields.io/badge/license-MIT-blue.svg)](./LICENSE)
CONTRIBUTING.md:all incoming contributions are correctly attributed and licensed. A Developer
CONTRIBUTING.md:    have the right to submit it under the open source license
CONTRIBUTING.md:    source license and I have the right under that license to
CONTRIBUTING.md:    or in part by me, under the same open source license (unless
CONTRIBUTING.md:    I am permitted to submit under a different license), as
CONTRIBUTING.md:    consistent with this project or the open source license(s)