Debian NEW: automated review of petsc 3.26.1+dfsg1-1exp1

dfsg-team at debian.org dfsg-team at debian.org
Sun Nov 15 20:03:46 GMT 2026


Hi,

Your upload of petsc 3.26.1+dfsg1-1exp1 to the NEW queue has had an automated review: an LLM-based check of its licensing and packaging, run by the DFSG team using the Debian Inference service. It is not a decision on the package, and - like other LLM-based work - it can be wrong.

It found 3 blocker, 0 important, 5 minor issues:

  - [blocker] [licensing] Files: * declares the bundled browser JavaScript/CSS BSD-2/UChicago although clipboard.min.js states MIT (c) Zeno Rocha, and KaTeX/sphinx-design/pydata-theme JS has no stanza at all
  - [blocker] [licensing] include/petsc/private/valgrind/{valgrind.h,memcheck.h} carry a four-clause BSD-style licence but are declared BSD-3-clause with Sandia's three-clause text
  - [blocker] [licensing] src/benchmarks/daemon.py carries Chad J. Schroeder's copyright but grants no licence, and is declared BSD-2 by Files: *
  - [minor] [licensing] Files: * does not name the Sphinx team, holder of docs/_static/{basic.css,doctools.js,language_data.js,searchtools.js}
  - [minor] [packaging] libpetsc64-real3.26-dbg depends on libpetsc-real3.26-dev, the 32-bit-index development package
  - [minor] [packaging] 64-bit complex dev/dbg packages depend on libptscotch-64-dev, but the build links and records the -64i variant
  - [minor] [packaging] libpetsc64-complex3.26-dev.postinst tests for libpets64c_complex.so, so its cleanup of the misnamed alternative never runs
  - [minor] [packaging] None of the ten patches has a DEP-3 header

You can read the full review here:

    https://dfsg-new-queue.debian.org/reviews/petsc#assistant-report

Please look at it, and respond by visiting the link below (you'll be asked to authenticate with Salsa first):

    https://dfsg-new-queue.debian.org/llm-review/gWUMtwv8BP--DVpvaJHHjpE2AQ66YW7w

There you may choose to reject the upload yourself, while you fix issues and re-upload, or add comments to clarify or dispute the review.

Your comments are for the DFSG team member who reviews the package, not for the LLM: it will not read them or reply. Tell the reviewer where you think the automated review is right or wrong, and why. Comments are public and shown with the review; you may use markdown, e.g. to link to clarifying information.

If you have any questions, please reply to this e-mail and someone from the
team will respond.

If you would rather not be e-mailed about these reviews, log in at https://dfsg-new-queue.debian.org
and say so on your profile page.

Thanks!



More information about the debian-science-maintainers mailing list