rachis-cli 2026.10.0-1
Package Information
| Description | Click-based command line interface for QIIME 2 QIIME 2 is a powerful, extensible, and decentralized microbiome analysis package with a focus on data and analysis transparency. QIIME 2 enables researchers to start an analysis with raw DNA sequence data and finish with publication-quality figures and statistical results. Key features: * Integrated and automatic tracking of data provenance * Semantic type system * Plugin system for extending microbiome analysis functionality * Support for multiple types of user interfaces (e.g. API, command line, graphical) QIIME 2 is a complete redesign and rewrite of the QIIME 1 microbiome analysis pipeline. QIIME 2 will address many of the limitations of QIIME 1, while retaining the features that makes QIIME 1 a powerful and widely-used analysis pipeline. QIIME 2 currently supports an initial end-to-end microbiome analysis pipeline. New functionality will regularly become available through QIIME 2 plugins. You can view a list of plugins that are currently available on the QIIME 2 plugin availability page. The future plugins page lists plugins that are being developed. |
|---|---|
| Maintainer | Debian Med Packaging Team <debian-med-packaging@lists.alioth.debian.org> |
| Changed By | Andreas Tille <tille@debian.org> |
| Sponsor | tille@debian.org |
| Distribution | experimental |
| Architecture | all |
| VCS | git: https://salsa.debian.org/med-team/q2cli.git (browse) |
| Tracker | https://tracker.debian.org/pkg/rachis-cli |
| Uploaded | 2 hours ago |
New Package Report
.changes
| Date | Mon, 16 Nov 2026 22:45:00 +0100 |
|---|---|
| Source | rachis-cli |
| Version | 2026.10.0-1 |
| Changed-By | Andreas Tille <tille@debian.org> |
| Architecture | source all |
| Distribution | experimental |
Changelog
rachis-cli (2026.10.0-1) experimental; urgency=medium
.
* Team upload.
* New upstream version renamed from q2cli to rachis-cli
* d/watch: version=5
* Standards-Version: 4.7.4 (routine-update)
* Update versioned dependency from rachis
* Build-Depends: dh-sequence-single-binary
* Reflow Uploaders field (cme)
* Build-Depends: pybuild-plugin-pyproject (routine-update)
* Reformat the Last-Update date as ISO YYYY-MM-DD.
* Replace FSF postal address with a reference to
https://www.gnu.org/licenses/.
* Set upstream metadata fields: Repository, Repository-Browse.
* Run the upstream test suite during the build for every supported Python
* Skip the two tests that shell out to the `rachis` executable when it is
not in PATH
* Fix compatibility with click 8.3 in unstable
* Update the autopkgtest for the CLI rename to `rachis`
* Rename manpage.dsc
| Package-List | rachis-cli deb science optional arch=all |
|---|---|
| Section | science |
| Priority | optional |
| Component | main |
debian/copyright
Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: rachis-cli
Source: https://github.com/rachis-org/rachis-cli
Files: *
Copyright: 2016-2026 QIIME 2 development team
License: BSD-3-clause
Files: rachis_cli/click/*
Copyright: 2001-2006 Gregory P. Ward
2002-2006 Python Software Foundation
2014 by the Pallets team.
2016-2026 QIIME 2 development team
License: BSD-3-clause
Files: debian/*
Copyright: 2019 Liubov Chuprikova <chuprikovalv@gmail.com>
2019-2026 Andreas Tille <tille@debian.org>
License: BSD-3-clause
License: BSD-3-clause
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
.
1. Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
.
2. Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.
.
3. Neither the name of the copyright holder nor the names of its
contributors may be used to endorse or promote products derived from this
software without specific prior written permission.
.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
DFSG Assistant LLM REVIEW 0 blocker, 1 important, 2 minor
This is an LLM based review using a Debian Inference based workflow. It was not written by a member of the DFSG team and has not been checked by one. It is not a decision on the package: it may be wrong, and it may have missed things.
Reviewed 1 hour ago.
Report
DFSG NEW review for rachis-cli version 2026.10.0-1
Summary
- Licensing is DFSG-compliant and
debian/copyrightis accurate: Yes - Packaging is of good quality: No
- Issues: 0 blocker, 1 important, 2 minor
- debian/watch: version 5
- debian/copyright: machine-readable
- Scan before the review: 4 found
Licensing
The whole tree is BSD-3-Clause: the top-level LICENSE (QIIME 2 development team, 2016-2026) matches the Files: * stanza word for word, and every Python file carries the QIIME 2 BSD header. rachis_cli/click/* is QIIME 2 code derived from click 8.3 (Pallets) and optparse (Gregory P. Ward, Python Software Foundation); those holders are named in their own stanza and the full click notice ships at rachis_cli/click/licenses/click.LICENSE.rst. debian/copyright is DEP-5, includes the full licence text, needs no Files-Excluded, and no other licence is present to conflict with it.
Packaging
Mostly clean Med-team packaging (debhelper compat 14, dh-sequence-single-binary, pybuild, DEP-3 patches, autopkgtest, current Standards-Version), but the build never pins the version: pyproject.toml requires versioningit, which is in no Build-Depends and exists nowhere in Debian, so rachis info/--version fall back to 0.0.0(+notfound). Two smaller defects come from the q2cli-to-rachis rename: the installed man page still names the old qiime command and a wrong completion path, and rachis tools view serves a vendored web app that the package does not ship.
Issues
important packaging 1. Build requirement versioningit is undeclared and unpackaged, so the package reports version 0.0.0 instead of 2026.10.0 ◂
-
Files:
pyproject.toml:9,24-29,45-46,rachis_cli/__init__.py:10-13,debian/control:10-23 -
Basis: inferred from what was read, not seen directly
-
Evidence:
[project] dynamic = ["version"] ... [build-system] requires = [ "setuptools", "versioningit", "wheel" ] ... [tool.versioningit.write] file = "rachis_cli/_version.py"try: from ._version import __version__ except ModuleNotFoundError: __version__ = '0.0.0+notfound' -
Problem: The version comes exclusively from versioningit, which writes rachis_cli/_version.py during the PEP 517 build.
versioningitis not in Build-Depends, andapt-cache showfinds neitherversioningitnorpython3-versioningitin unstable/experimental nor among the uploads in NEW. pybuild runspython3 -m build --skip-dependency-check --no-isolation --wheel(/usr/share/dh-python/dhpython/build/plugin_pyproject.py:147), so the build-system requires are not installed: no _version.py is written and the installed package takes the fallback, reportingrachis-cli version: 0.0.0+notfoundfromrachis info(builtin/info.py:25) and cache keys ofrachis_cli==0.0.0+notfound(core/cache.py:145); the wheel metadata carries the unset default 0.0.0, which is whatrachis --versionprints. (If the backend instead refuses to build without a version, the result is an FTBFS.) Either way the version of this Debian package is never 2026.10.0. -
Fix: Make the version determinable at build time: package versioningit and add it to Build-Depends, or add a small Debian patch that sets the version statically (e.g. write rachis_cli/_version.py with
__version__ = '2026.10.0', or replaced pyproject.toml's dynamic version with a literal one) and drop the versioningit build requirement from pyproject.toml. Verify withrachis --versionandrachis infothat 2026.10.0 is reported.
minor
packaging
2. debian/rachis.1 is the old q2cli page: SYNOPSIS says qiime and the zsh completion path is misspelled
◂
-
Files:
debian/rachis.1:2,6,18,debian/rules:22-24 -
Basis: checked, in the package or with a reference tool
-
Evidence:
.TH RACHIS-CLI "1" "March 2019" "rachis-cli version 2026.10.0"
.B qiime
autoload bashcompinit && bashcompinit && source \fI\,/usr/share/bashcompletion/completions/rachis\/\fP
while debian/rules installs the completion atusr/share/bash-completion/completions/rachis -
Problem: The file was renamed with the package but never regenerated: it is installed as rachis.1, yet its SYNOPSIS documents a command
qiimethat this package does not provide (pyproject.toml installsrachis), its .TH title and date are the old page's, and the zsh instructions point at /usr/share/bashcompletion/completions/rachis, which is not the path the package creates, so following the man page gives a source error. -
Fix: Regenerate the page with help2man from
rachis --help(fixing the program name and .TH title), or correct it by hand: SYNOPSISrachis, .THRACHIS, and/usr/share/bash-completion/completions/rachis.
minor
packaging
3. rachis tools view serves rachis_cli/assets/view, which the package does not ship
◂
-
Files:
rachis_cli/builtin/tools.py:689-690,705,Makefile:13-16,q2view/ -
Basis: inferred from what was read, not seen directly
-
Evidence:
VENDOR_PATH = os.path.join(MODULE_BASE_DIR, 'assets', 'view')
('localhost', port), lambda *_: Handler(*_, directory=VENDOR_PATH),
Makefile:vendor-view: ... git submodule update && cd q2view && npm install --no-save && npm run vendor --VENDOR_DIR=../rachis_cli/assets/view -
Problem: The view subcommand is built around a web app that must be generated by
make vendor-viewfrom the q2view git submodule with npm. That never happens in a Debian build:q2view/in the tarball is empty (the submodule is not in it), rachis_cli/assets/ does not exist, and nothing in debian/rules generates it. The only URL the command opens ishttp://localhost:port/?file=..., whose root falls through to SimpleHTTPRequestHandler serving that non-existent directory, so the user gets a 404/blank page. The defect is inherited from q2cli and survives because the autopkgtest never exercises view (see the TODO in debian/tests/run-unit-test). -
Fix: Ship the view app: include the q2view sources in the source package (also needed for DFSG compliance if the built JS is shipped) and build rachis_cli/assets/view during the package build with the npm toolchain, or change
tools viewto detect the missing vendored app and exit with an explicit error/document the limitation instead of starting an empty server.
Verified ◂
- Inventory: ~54 upstream files outside debian/ and .pc/; every .py (rachis_cli/, builtin/, core/, click/, tests/) carries the
Copyright (c) 2016-2026, QIIME 2 development team/ Modified BSD header. - LICENSE is the BSD-3-Clause text of the QIIME 2 development team, 2016-2026; debian/copyright
Files: *reproduces it and the holder exactly. - rachis_cli/click/{command,parser,option,type}.py are QIIME 2 files derived from click 8.3; the
Copyright (c) 2014 by the Pallets teamnotices and the optparse (Gregory P. Ward 2001-2006, PSF 2002-2006) notice in rachis_cli/click/licenses/click.LICENSE.rst are all named in theFiles: rachis_cli/click/*stanza, and that licence text ships in the binary via setuptools package-data. Not a copy of Debian's python3-click: these files import click and add local mixins/parser subclasses. - The four .qza archives the scan listed -- rachis_cli/tests/data/concatenated_ints.qza, rachis_cli/tests/data/rarefied_table.qza, rachis_cli/tests/data/parse_dir_test/left_ints.qza and rachis_cli/tests/data/parse_dir_test/inner/right_ints.qza -- are QIIME 2 Result fixtures used by rachis_cli/tests (13-81 KB); they are data, not built artefacts, installed with the Python package as test data, and carry no separate copyright notice.
- .github/rubric.png is a PNG referenced only by .github/SUPPORT.md; it is not installed into the binary, is covered by
Files: *, and carries no third-party notice. - rachis_cli/core/assets/copyright_note.txt is a notice to users about copyright in their own analysis results, not a licence term for the software; rachis_cli/core/assets/cli_howto.txt and hooks/50_activate_rachis_cli_tab_completion.sh are ordinary QIIME 2 text/scripts covered by Files: *.
- The prescan's holder check agrees: every copyright holder found in the tree is named in debian/copyright, and no other LICENSE/COPYING/NOTICE/AUTHORS file exists beyond LICENSE and rachis_cli/click/licenses/click.LICENSE.rst.
- debian/copyright is DEP-5 with the correct Format URL, a
Files: *, a click and a debian/* stanza in that override order, one stand-alone BSD-3-clause paragraph, and no Files-Excluded; BSD-3-Clause is the only licence, so nothing incompatible is combined. - All six patches in debian/patches/series are applied, are Debian-only (test skips for absent CLI/q2templates assets, click 8.3 API compatibility, python3 instead of python, no shebang in completion, zsh instructions) and carry DEP-3 Description/Author/Forwarded/Last-Update headers.
- Standards-Version 4.7.4 equals the current Policy version (Debian Policy A10.2); debhelper-compat 14; the <!nocheck> Build-Depends are all test-only and dh skips the test target under nocheck at compat >= 13; ${misc:Depends}/${python3:Depends} are present and dh_gencontrol would add them anyway.
- debian/rules: dh-sequence-single-binary installs into debian/rachis-cli/, and override_dh_install moves usr/bin/tab-rachis to usr/share/bash-completion/completions/rachis and clears its executable bit; debian/manpages installs debian/*.1; debian/tests/control runs the installed test suite plus CLI smoke tests; salsa-ci and upstream/metadata are present.
Provides: q2clialongside the still-existing q2cli binary is permitted by Policy 7.5 (a package may provide a concrete package's name) and the two packages share no file paths.- uscan found the packaged version as the newest upstream release (upstream
2026.10.0, packaged2026.10.0).
Not confirmed ◂
- The renamed core package
rachisis not in unstable/experimental nor in the NEW queue, andq2-feature-tableis only 2024.5.0+dfsg-1 there, so the Build-Dependsrachis (>= 2026.10)and the Dependsq2-feature-table (>= 2026.10)cannot be satisfied yet; if the sibling rename uploads are not in NEW, this package cannot build or install. A build in a chroot with the declared Build-Depends would show it. - Whether setuptools aborts or falls back to 0.0.0 when a pyproject-declared dynamic version has no provider (setuptools is not installed on the reviewing system, so the exact build outcome could not be reproduced).
- One autopkgtest data source, /usr/lib/python3/dist-packages/q2_sample_classifier/tests/data/vaw.qza, was assumed to exist in q2-sample-classifier (the archive's version was not unpacked here).
- The four .qza archives were not opened (binary), so their internal provenance/citation contents were not inspected.
Proposed changes ◂
None.
Uploader's response to the LLM review
Issue 2 is fixed in Git - all others are no issues.
— Andreas Tille (tille), 0 hours ago