libffi (3.8.0-2) unstable; urgency=medium
 .
   * Correct symbols file for LIBFFI_CALL_PLAN_8.[45] versioned symbols.
libffi (3.8.0-1) unstable; urgency=medium
 .
   * New upstream version.
   * Update symbols file.
libffi (3.8.0-1~exp1) experimental; urgency=medium
 .
   * New upstream version.

postgresql-18 (18.6-3) unstable; urgency=medium
 .
   * Fix package names used in the Breaks and drop old Breaks against
     dbconfig-common before 2.0.22.
postgresql-18 (18.6-2) unstable; urgency=medium
 .
   * Add Breaks on the packages affected by the output_plugin_libraries change:
     pg-rewrite, pg-squeeze, postgres-decoderbufs, wal2json.
     Also add timescaledb (different reason, TBD).
postgresql-18 (18.6-1) unstable; urgency=medium
 .
   * New upstream version 18.6. (18.5 was never released.)
 .
     + Restrict logical decoding output plugins to the set specified by
       a new server parameter `output_plugin_libraries` (Jacob
       Champion)
 .
       Previously, a replication user could select any loadable library
       for logical decoding, allowing exploits of various sorts. To
       allow locking this down without breaking setups that worked
       before, introduce a whitelist of allowed output plugins.
 .
       By default, only the output plugins shipped as part of
       PostgreSQL (`pgoutput` and `test_decoding`) are included in
       `output_plugin_libraries`. Installations that rely on other
       output plugins must add them after updating the server, for
       example
 .
       output_plugin_libraries = 'pgoutput, test_decoding, my_trusted_decoder'
 .
       Additionally, pg_upgrade --check will fail if the
       `output_plugin_libraries` parameter on the new cluster does not
       permit the plugins of logical replication slots on the old
       cluster, when migrating from versions 17 and later. Make
       necessary additions to the new cluster's setting before
       performing pg_upgrade.
 .
       The PostgreSQL Project thanks Vladimir Tokarev and Yu Kunpeng
       for reporting this problem. (CVE-2026-6471)
 .
     + Fix contrib/pgcrypto's PGP encryption to detect unsupported
       ciphers (Daniel Gustafsson)
 .
       Previously, if OpenSSL rejected the requested cipher (for
       example, because it is running in FIPS mode, or the legacy
       provider hasn't been loaded), pgcrypto failed to notice the
       failure and simply XOR'd the non-encrypted block with the
       plaintext, rendering the "encryption" trivially breakable. This
       will typically occur with deprecated or non-FIPS cipher
       algorithms (cipher-algo=blowfish/bf, twofish, cast5, or 3des).
 .
       By default, pgcrypto will now fail to decrypt any messages that
       were affected in this way. To allow retrieval of such data, a
       new option `ignore-cipher-failure` has been added to
       pgp_pub_decrypt() and pgp_sym_decrypt(). Setting
       `ignore-cipher-failure=1` will restore their previous behavior,
       allowing the faulty encryption wrapper to be stripped off:
 .
       pgp_sym_decrypt(encrypted_column, any key, 'ignore-cipher-failure=1')
 .
       Once the affected messages are identified and stripped of their
       wrappers, they can then be re-encrypted with a modern algorithm.
       It is important however that the behavior of OpenSSL be the same
       as it was when the faulty messages were created: if the set of
       unsupported algorithms is not the same, this approach will not
       work. See the documentation for `ignore-cipher-failure`.
 .
       The PostgreSQL Project thanks Shishir Sharma for reporting this
       problem. (CVE-2026-14663)
 .
     + Fix psql to skip in-line data following a scripted COPY ... FROM
       STDIN command, even if the COPY fails before sending
       `PGRES_COPY_IN` (Tom Lane)
 .
       Previously, if a `COPY` command failed at startup (for instance,
       because the target table doesn't exist) psql would not realize
       that and would proceed to read the following in-line data as SQL
       commands. In the best case that's wrong and in the worst case
       it's a SQL-injection hazard. Teach psql to recognize
       syntactically-valid COPY ... FROM STDIN commands and to skip
       data on its own authority if the server doesn't respond with
       `PGRES_COPY_IN`.
 .
       While this fix is unlikely to affect any production SQL scripts,
       test scripts might intentionally exercise failing COPY ... FROM
       STDIN commands. Those will need to gain a `\.` data terminator
       line after each such command.
 .
       The PostgreSQL Project thanks Alexander Lakhin for reporting
       this problem. (CVE-2026-6464)
 .
     + Cross-check the output row type of a portal running EXECUTE or
       FETCH (Robert Haas)
 .
       EXECUTE and FETCH use two portals: an outer one for the
       statement itself, and an inner one running the query being
       executed on its behalf. It was previously possible to make the
       declared row types of the two portals diverge, leading to server
       memory disclosure and arbitrary code execution.
 .
       The PostgreSQL Project thanks Ben Morris (in collaboration with
       Claude and Anthropic Research) and Peter Geoghegan for reporting
       this problem. (CVE-2026-16239)
 .
     + Fix buffer overrun with long time zone abbreviation in to_char()
       (Tom Lane)
 .
       This can easily crash the server, and exploits leading to
       arbitrary code execution have been reported.
 .
       The PostgreSQL Project thanks Hcamael, Amjad Shahzad, Tan Zhen
       of AntAISecurityLab, Tomer Fichman, Zheng Yu, Amy Burnett
       (OpenAI Codex Security), Rick de Jager, Heewon Song, Sylvie
       Mayer, Aleksander Alekseev, and Hillai Ben Sasson for reporting
       this problem. (CVE-2026-14669)
 .
     + Fix buffer overrun in regexp match/split functions (Masahiko
       Sawada)
 .
       If passed invalidly-encoded data, these functions could write
       past the end of their conversion buffer.
 .
       The PostgreSQL Project thanks Francesco Verardi for reporting
       this problem. (CVE-2026-14664)
 .
     + Harden the ascii() function against invalid input (Michael
       Paquier)
 .
       By supplying invalidly-encoded input, this function could be
       coaxed to read and return a few bytes of data that it shouldn't.
       In assert-enabled builds, its assertions could be triggered too.
 .
       The PostgreSQL Project thanks Hcamael for reporting this
       problem. (CVE-2026-18024)
 .
     + Fix multirange type handling in pg_restore_attribute_stats()
       (OpenAI Security Research Team)
 .
       pg_restore_attribute_stats() treated multirange types just like
       their underlying range type. This works correctly for the bounds
       histogram, but it was wrong for all the other statistics kinds.
 .
       The PostgreSQL Project thanks Amy Burnett (OpenAI Codex
       Security) for reporting this problem. (CVE-2026-16238)
 .
     + Make scalarineqsel() check that a constant it expects to be of
       type tid actually is (Tom Lane)
 .
       This expectation will hold for all the built-in operators that
       use this estimator, but a maliciously-constructed operator could
       violate it, leading to a crash or server memory disclosure.
 .
       The PostgreSQL Project thanks Hcamael for reporting this
       problem. (CVE-2026-14668)
 .
     + Harden tsvector and tsquery code against overly long values
       (both individual lexemes and total vector/query length) (Tom
       Lane)
 .
       The documented limits were not enforced in all code paths.
 .
       The PostgreSQL Project thanks Yuhang Wu, Zhenpeng Lin, Zheng Yu,
       and Hcamael for reporting these problems. (CVE-2026-14662)
 .
     + Fix various places that mistakenly assumed they would not have
       to deal with more than `FUNC_MAX_ARGS` function arguments (Tom
       Lane)
 .
       Notably, the server's actual limit on the number of arguments to
       an aggregate function is `FUNC_MAX_ARGS - 1`, but the parser
       failed to enforce that, creating hazards downstream.
 .
       The PostgreSQL Project thanks Zheng Yu, ylwangtju, and Masahiko
       Sawada for reporting these problems. (CVE-2026-14679)
 .
     + Reject calls from SQL to functions that take or return type
       internal (Tom Lane)
 .
       The existing defenses against doing this have been shown to be
       insufficient, so add more explicit checks.
 .
       The PostgreSQL Project thanks Amy Burnett (OpenAI Codex
       Security) for reporting this problem. (CVE-2026-14680)
 .
     + Preserve the ownership of extended statistics objects when they
       are rebuilt by ALTER TABLE (Masahiko Sawada)
 .
       Previously, the role running ALTER TABLE gained ownership of
       such objects, but that seems inappropriate.
 .
       The PostgreSQL Project thanks Noah Misch for reporting this
       problem. (CVE-2026-6469)
 .
     + When deparsing an EXTRACT() function call, quote the field name
       if needed (Nathan Bossart)
 .
       The parser accepts any string literal as a field name in
       EXTRACT(), deferring validation to execution. If the call is
       stored and deparsed (for example during pg_dump), the string
       body was regurgitated verbatim, allowing SQL injection.
 .
       The PostgreSQL Project thanks Ben Morris (in collaboration with
       Claude and Anthropic Research) for reporting this problem.
       (CVE-2026-15741)
 .
     + Check for `USAGE` privilege on data types in places that
       formerly failed to check that (Nathan Bossart)
 .
       CREATE TYPE AS RANGE did not check, nor did ALTER TABLE OF, nor
       did commands that create stored expressions. These omissions
       allowed roles without `USAGE` privilege to nonetheless create
       objects depending on the type, possibly blocking the type's
       owner from changing the type later.
 .
       The PostgreSQL Project thanks Jingzhou Fu for reporting this
       problem. (CVE-2026-6470)
 .
     + Invalidate role-dependent cached plans after role changes (Ilya
       Staroverov, Shinya Kato, Nathan Bossart)
 .
       Role membership, role attribute, and database ownership changes
       may impact the expected behavior of row-level security policies,
       but previously we'd continue to use cached plans that were made
       according to the old state of affairs.
 .
       The PostgreSQL Project thanks Ilya Staroverov and Shinya Kato
       for reporting this problem. (CVE-2026-14666)
 .
     + Reject GSSEncRequest after direct SSL connection (Michael
       Paquier)
 .
       After establishing a TLS-encrypted connection, the server would
       still accept a request for GSSAPI encryption. If that succeeded,
       the connection would proceed using TLS encryption, but it would
       look like a GSS connection to the pg_hba rules. Thus, a pg_hba
       policy intending to disallow TLS would not be enforced
       correctly.
 .
       The PostgreSQL Project thanks p4p3r for reporting this problem.
       (CVE-2026-14681)
 .
     + Make mock SCRAM authentication secrets more plausible (Nathan
       Bossart)
 .
       If a SCRAM login is attempted against a role that doesn't exist
       or doesn't have a SCRAM secret, we generate a mock secret and
       carry out the authentication handshake anyway, to avoid
       revealing these facts to an attacker. But the mock secret was
       made with a fixed iteration count, which in itself can be an
       observable response discrepancy. Use the configuration setting
       `scram_iterations` instead, to make the mock secret look more
       like the installation's real secrets.
 .
       The PostgreSQL Project thanks Radim Marek for reporting this
       problem. (CVE-2026-14672)
 .
     + Fix out-of-bounds writes in ecpg applications caused by invalid
       bytea data received from the server (Michael Paquier)
 .
       ecpg assumed without checking that any bytea value must begin
       with `\x`. A broken or malicious server might send a string
       shorter than 2 bytes, resulting in memory clobber in the
       application.
 .
       The PostgreSQL Project thanks ylwangtju for reporting this
       problem. (CVE-2026-16241)
 .
     + Do not do backquote expansion on the argument of psql's
       \unrestrict command (Nathan Bossart)
 .
       This oversight in the fix for CVE-2025-8714 allows a malicious
       server to inject shell commands into plain-text dump output that
       will be run at restore time on the machine running psql, the
       exact scenario that CVE-2025-8714 intended to prevent.
 .
       The PostgreSQL Project thanks Lucas Velgus, Filip Janus, and
       Daniel Bakker for reporting this problem. (CVE-2026-18408)
 .
     + Remove pg_dump's assumption that pg_proc.protrftypes cannot have
       more than `FUNC_MAX_ARGS` entries (Tom Lane)
 .
       Since there could be entries for both input and output
       arguments, it's feasible for this array's length to exceed
       `FUNC_MAX_ARGS` (which constrains only input arguments). Even if
       that were not so, pg_dump cannot assume that the server was
       built with the same value of `FUNC_MAX_ARGS` that it has. An
       overrun would lead to a memory clobber inside pg_dump.
 .
       The PostgreSQL Project thanks Masahiko Sawada for reporting this
       problem. (CVE-2026-19385)
 .
     + Harden PL/Perl against "tied" Perl arrays and hashes (Tom Lane)
 .
       A tied object that doesn't behave like a regular one could lead
       to memory overwrite, or to constructing a corrupt result array
       (which would likely cause problems later).
 .
       The PostgreSQL Project thanks Hcamael for reporting this
       problem. (CVE-2026-14670)
 .
     + Fix integer overflows in memory-allocation calculations in
       PL/Perl and PL/Tcl (Heikki Linnakangas)
 .
       This is the same type of problem as CVE-2026-6473, just in a
       different part of the code, and is fixed in the same way.
 .
       The PostgreSQL Project thanks the Tulya Project (Team Dhiutsa,
       Bitecope Technologies Private Ltd) for reporting this problem.
       (CVE-2026-14677)
 .
     + Ensure that contrib/amcheck functions restrict `search_path`
       before executing index expressions (Noah Misch)
 .
       Because amcheck will run such index expressions as the owner of
       their tables, a caller could potentially hijack
       `search_path`-dependent functions to run arbitrary code as the
       table owner. By default this is not a vulnerability because only
       superusers are allowed to call amcheck functions; but if that
       privilege was granted out, it created a larger hazard than the
       documentation suggests.
 .
       The PostgreSQL Project thanks Yuelin Wang and Jacob Brazeal for
       reporting this problem. (CVE-2026-14673)
 .
     + Fix integer overflows in contrib/fuzzystrmatch's levenshtein()
       and levenshtein_less_equal() functions (Nathan Bossart)
 .
       Passing large cost values to these functions could cause integer
       overflows, thereby producing nonsensical results, and even
       causing out-of-bounds writes in some cases.
 .
       The PostgreSQL Project thanks Ben Morris (in collaboration with
       Claude and Anthropic Research) for reporting this problem.
       (CVE-2026-15742)
 .
     + Fix buffer overrun in contrib/pg_stat_statements (Álvaro
       Herrera)
 .
       Query normalization didn't accurately account for the amount of
       space the normalized string would require.
 .
       The PostgreSQL Project thanks Sajeeb Lohani (with TrendAI Zero
       Day Initiative) and Yuelin Wang for reporting this problem.
       (CVE-2026-14676)
 .
     + Fix datatype error in contrib/pg_trgm's GiST picksplit function
       (Heikki Linnakangas)
 .
       This mistake resulted in reading past the end of the buffer,
       typically causing bad split decisions; but a crash could ensue
       if you're very unlucky.
 .
       The PostgreSQL Project thanks Mehmet D. Ince for reporting this
       problem. (CVE-2026-14678)
 .
     + Remove the plan cache in contrib/refint (Ayush Tiwari)
 .
       This caching behavior has several serious bugs, notably that
       check_foreign_key() embeds the new key values in its
       cascade-UPDATE queries, so a cached plan reuses the
       originally-needed values rather than the key values that should
       be used. The simplest solution is to remove it.
 .
       The PostgreSQL Project thanks Hcamael for reporting this
       problem. (CVE-2026-14671)
 .
     + Ensure that parallel GIN index builds update the table's
       pg_class.reltuples value correctly (Jan Nidzwetzki, Tomas
       Vondra)
 .
       A parallel worker could report an uninitialized value for the
       number of rows it processed, leading to a bogus value for
       reltuples, even Infinity or NaN. Such values could lead to
       subsequent autovacuum and autoanalyze operations never deciding
       that the table needs to be processed. If so, the situation will
       not self-heal. A manual ANALYZE command, or creation of another
       index, will be needed to reset reltuples to the correct value.
       If you have any tables with GIN indexes, it's recommended to
       check to see if their reltuples entries look sane. A query such
       as this may be helpful:
 .
         SELECT DISTINCT t.oid::regclass, t.reltuples
         FROM pg_class t
           JOIN pg_index i ON t.oid = i.indrelid
           JOIN pg_class ic ON i.indexrelid = ic.oid
         WHERE t.relhasindex AND ic.relam = 2742;
 .
   * Fix psql -c 'truncate/create table; copy from stdin'.

powa-archivist (5.3.0-1) unstable; urgency=medium
 .
   * New upstream version 5.3.0.

powerman (2.4.4-6) unstable; urgency=medium
 .
   * QA upload.
   * d/changelog
     - remove trailing white space
   * d/control
     - remove default priority
     - bump Standards-Version to 4.7.4
     - correct section of library package
     - bump debhelper-compat to 14
     - remove substvars handled by debhelper at compat 14
   * d/copyright
     - correct path of GPL-2.
   * d/patches
     - add two upstream fixes for const-correctness compilation failures
       (Closes: #1128740)
   * d/s/lintian-overrides
     - unrecognized dh-exec env var is defined in d/rules.
   * d/watch
     - convert to version 5

prefixdate (0.6.1-1) unstable; urgency=medium
 .
   * New upstream release.

prismatic-schema-clojure (1.4.1-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version 1.4.1
   * switch packaging to dh-clojure
   * refresh autopkgtests
   * d/control: bump min version for test.check
   * d/control: drop obsolete test deps
   * d/control: bump dh compat level to 14
   * d/upstream: add metadata
   * d/watch: update to v5 format
   * Remove redundant Priority: optional from source stanza.
   * Update standards version to 4.7.4, no changes needed.
   * Removed Rules-Requires-Root

pybdsf (1.14.1-2) unstable; urgency=medium
 .
   * Make the build reproducible (Closes: #1144409)
pybdsf (1.14.1-1) unstable; urgency=medium
 .
   * New upstream version 1.14.1
   * Drop patches applied upstream
   * Push Standards-Version to 4.7.4; remove redundant Priority: optional
   * Remove rpath from _cbdsm module
pybdsf (1.13.0-3) unstable; urgency=medium
 .
   * Team upload.
   * Add patches for Python 3.14 compatibility (Closes: #1122049):
     - ensure that the boost library for the correct Python interpreter is used
     - use 'fork' rather than 'forkserver' for multiprocessing
pybdsf (1.13.0-2) unstable; urgency=medium
 .
   * Add argument types to function prototypes (Closes: #1114276)
pybdsf (1.13.0-1) unstable; urgency=medium
 .
   * New upstream version 1.13.0. Closes: #1094757, #1095216
   * Rediff patches
   * Push Standards-Version to 4.7.2, no changes needed
   * Add build dependency python3-numpy-dev
pybdsf (1.12.0-1) unstable; urgency=medium
 .
   * New upstream version 1.12.0
   * Rediff patches
pybdsf (1.11.1-2) unstable; urgency=medium
 .
   * Adjust f2py executable name (Closes: #1081693)
pybdsf (1.11.1-1) unstable; urgency=medium
 .
   * Allow prereleases in d/watch
   * New upstream version 1.11.1
   * Rediff patches
pybdsf (1.11.0-1) unstable; urgency=medium
 .
   * New upstream version 1.11.0. Closes: #1076960
   * Rediff patches
   * Update build dependencies
pybdsf (1.10.3-3) unstable; urgency=medium
 .
   * Fix python3.12 build (Closes: #1063407)
   * Push Standards-Version to 4.7.0. No changes needed
pybdsf (1.10.3-2) unstable; urgency=medium
 .
   * Add build time test and autopkgtest (Closes: #1035198)
pybdsf (1.10.3-1) unstable; urgency=medium
 .
   [Bastian Germann]
   * New upstream version 1.10.3
   * Rediff patches
 .
   [ Ole Streicher ]
   * Call dh_numpy
   * Update d/watch
   * Fix build issue with Python 3.11 (Closes: #1024499)
   * Push Standards-Version to 4.6.2. No changes needed
pybdsf (1.10.1-1) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Update watch file format version to 4.
   * Update pattern for GitHub archive URLs.
 .
   [ Ole Streicher ]
   * New upstream version 1.10.1
   * Rediff patches
   * Push Standards-Version to 4.6.0. No changes needed.
pybdsf (1.9.2-3) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Use secure URI in Homepage field
   * Set upstream metadata fields: Bug-Submit, Repository, Repository-Browse
 .
   [ Ole Streicher ]
   * Fix build dependencies (Closes: #972772)
pybdsf (1.9.2-2) unstable; urgency=low
 .
   * Unconditionally add astropy dependency
   * Use system specific multiarch name instead of generic one
pybdsf (1.9.2-1) unstable; urgency=low
 .
   * Initial package (Closes: #959778)
   * Derived from the kernsuite package by Gijs Molenaar

pycdio (2.1.1-1.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add a patch to fix a FTBFS with new Swig 4.5
   * Switch to debhelper-compat 14
   * Rewrite d/rules with newer & shorter syntax
   * Rewrite d/watch in v5 format
   * Add debian/salsa-ci.yml
   * Drop "Rules-Requires-Root: no": it is the default now
   * Bump Standards-Version to 4.7.4, drop Priority: tag

pydata-sphinx-theme (0.17.1+dfsg-4) unstable; urgency=medium
 .
   * Team upload.
   * Fix node-dedent import (closes: #1143361).

pypuppetdb (3.2.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Drop unused dependency on mypy.
   * Standards-Version: 4.7.4 (routine-update)
   * Reorder sequence of d/control fields by cme (routine-update)

python-aioeafm (1.0.0-4) unstable; urgency=medium
 .
   * Team upload.
   * Drop unused build-dependencies on python3-mypy & python3-setuptools
   * Use dh-sequence-python3
   * Set upstream metadata fields: Bug-Submit.
   * Disable useless Salsa CI jobs

python-aiopyarr (23.4.0-3) unstable; urgency=medium
 .
   * Team Upload
   * Use dh-sequence-python3
   * Add debian/salsa-ci.yml
   * Drop unused dependency on python3-mypy
   * Bump Standards-Version to 4.7.4, drop Priority: tag
   * Mark python3-pytest* as <!nocheck>
   * Rewrite d/watch in v5 format
   * Switch to debhelper-compat 14

python-airgradient (0.10.0-1) unstable; urgency=medium
 .
   * New upstream release.
   * Remove debian/gbp.conf, switch to dgit.
   * Remove defaults from debian/control.
   * Update Standards-Version.
   * Update to debhelper compatibility level 14.
   * Add dh-sequence-single-binary.
   * Remove debhelper compat 14 auto-applied substvars.
   * Prefix debhelper files with the binary package name.
   * Update copyright year.
   * Update debian/watch to format version 5.
   * Add debian/salsa-ci.yml.

python-ast-serialize (0.8.0+0gitfc05930-1) unstable; urgency=medium
 .
   * Initial release. (Closes: #1144444)

python-bleak-smlight (1.1.1-1) unstable; urgency=medium
 .
   * Initial release. (Closes: #1144540)

python-bottle-sqlite (0.2.0-7) unstable; urgency=medium
 .
   * Team Upload
   * Tweak d/watch to detected an eventual future version
   * Switch to debhelper-compat 14
   * Use secure URI in Homepage field.
   * Update standards version to 4.7.4, no changes needed.

python-cffi (2.1.1-1) unstable; urgency=medium
 .
   * Team Upload
   * New upstream version 2.1.1
   * Drop build-dep on python3-py (Closes: #1121670)
   * Refresh bundled-wheel-and-setuptools.patch
   * Drop pycparser-3.patch: applied upstream
   * Add debian/salsa-ci.yml
   * Bump Standards-Version to 4.7.4, drop Priority: tag
   * Drop duplicate dependency on dh-python

python-changelogd (0.1.10-2) unstable; urgency=medium
 .
   * Team upload.
   * d/control: remove unused mypy dependency.
   * Standards-Version: 4.7.4 (routine-update)
   * Reorder sequence of d/control fields by cme (routine-update)

python-configshell-fb (1:2.0.3-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version 2.0.3, drop upstream applied patches.
   * Cleanup inactive Uploaders

python-consolekit (1.13.0-6) unstable; urgency=medium
 .
   * Team upload
   * Add debian/salsa-ci.yml
   * Drop unused python3-mypy build-dependency
 .
   [ Bastian Germann ]
   * d/watch: Fix bad values

python-django-adminsortable (2.0.10-5) unstable; urgency=medium
 .
   * Salsa: disable useless BLHC job
   * Update standards version to 4.7.4, no changes needed.
   * Set upstream metadata fields: Repository.
   * Enable Testsuite: autopkgtest-pkg-python
   * Tweak d/watch for new Pypi archive name mangling policy
   * Switch to debhelper-compat 14

python-duet (0.2.9-4) unstable; urgency=medium
 .
   * Team upload.
   * d/control: remove unused dependency on mypy.
   * Standards-Version: 4.7.4 (routine-update)
   * Reorder sequence of d/control fields by cme (routine-update)
   * Update watch file format version to 5.
   * Use GitHub template in watch file instead of explicit
     Source/Matching-Pattern.

python-gnuplotlib (0.47-1) unstable; urgency=medium
 .
   * New upstream version 0.47
     - We don't ask for gnuplot features (and spawn extra gnuplot processes)
       unless necessary
     - .gp files are executable and have a #! only if gnuplot was found
     - Replaced distutils.spawn with shutil

python-hypothesis (6.155.7-1) unstable; urgency=medium
 .
   * New upstream version 6.155.7
     - This is the final pure Python release
   * Migrate to debhelper 14
   * hypothesis-python source dir was renamed to hypothesis
   * Refresh patches (no functional changes)
   * Add test depend on python3-scipy

python-inquirerpy (0.3.4-4) unstable; urgency=medium
 .
   * Team Upload
   * Use versioned copyright format URI.
   * Update standards version to 4.7.4, no changes needed.
   * Add debian/upstream/metadata
   * Add debian/salsa-ci.yml
   * Tweak d/watch to accept new Pypi archive naming mangling policy
   * Switch to debhelper 14

python-levenshtein (0.27.3-1) unstable; urgency=medium
 .
   * New upstream version 0.27.3
   * move to new upstream location:
     https://github.com/rapidfuzz/Levenshtein
   * add gbp.conf
   * add CI/CD config
   * d/control:
     - use Build-Depends-Indep for docs
     - bump S-V to 4.7.4, remove RRR and Priority: optional
     - update required package versions
   * d/copyright: update copyright holders
   * d/patches: disable custom sphinx theme
   * d/watch: migrate to version 5
   * d/rules:
   - make skbuilds verbose
   - skbuild use deterministic build path
   * transition to dh-compat 14
   * adopt package (Closes: #1065327)

python-lsp-server (1.15.0-1) unstable; urgency=medium
 .
   * New upstream version 1.15.0
     - Fixes tests (Closes: #1143368)
   * Port to debhelper 14
   * Bump policy version (no changes)
   * Drop old Breaks (older than oldstable)

python-maxcube-api (0.4.3-1) unstable; urgency=medium
 .
   * Initial release. (Closes: #1144255)

python-moto (5.1.18-5) unstable; urgency=medium
 .
   * Team upload.
   * d/control: remove unused mypy dependency.
   * Standards-Version: 4.7.4 (routine-update)
   * debputy lint --auto-fix (routine-update)
   * watch file standard 4 (routine-update)

python-nameparser (2.1.0-1) unstable; urgency=medium
 .
   * New upstream release.
   * Switch debian/watch to use GitHub instead of PyPI.

python-numpysane (0.45-1) unstable; urgency=medium
 .
   * New upstream version 0.45
python-numpysane (0.44-1) unstable; urgency=medium
 .
   * Added Depends: python3-packaging
   * New upstream version 0.44

python-parsl (2026.07.27+ds-2) unstable; urgency=medium
 .
   * Team upload.
   * d/control: remove unused mypy dependency.
   * Reorder sequence of d/control fields by cme (routine-update)
   * debputy lint --auto-fix (routine-update)

python-plac (1.4.5-3) unstable; urgency=medium
 .
   * Team upload.
   * Add patch for Python 3.14+ compat. Closes: #1140949).
python-plac (1.4.5-2) unstable; urgency=medium
 .
   [ Manuel Guerra ]
   * Team upload.
   * Fix FTBFS. (Closes: #1123289)
   * Remove alien tag Built-Using from debian/control.
   * Remove source lintian-overrides.
   * Bump Standards-Version to 4.7.4, remove "priority" tag.
 .
   [ Michael R. Crusoe ]
   * debputy lint --auto-fix (routine-update)
python-plac (1.4.5-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release.
   * debian/watch: Bump file to version 5, rewrite the source of the files.
   * debian/control: Update to latest conventions
     - Bump Standards-Version to 4.7.2 (no changes needed).
     - Remove unused Rules-Requires-Root.
     - Move python3-pytest to Build-Depends-Indep.
     - Duplicate tests in autopkgtest.
     - Rewrite the text for better reading.
   * debian/copyright: Update stanzas with copyright information
     - Add Manuel Guerra to 'debian/*' stanzas.
     - Add email to upstream author in '*' stanzas.
     - Fit text to a better read.
   * debian/rules: Update the rules implementation
     - Reformulate rules to get reproducibility.
     - Build and install HTML documentation.
   * debian/docs: Update file to prevent installation of entire doc directory
     - Remove installation of entire doc/ directory inside documentation because
       the doc/ directory contains test, examples and documentation files.
     - Install README.md file.
   * debian/install: Install HTML documentation.
   * debian/doc-base: Add doc-base file.
   * debian/clean: Clean generated documentation.
python-plac (1.4.3-2) unstable; urgency=medium
 .
   * Team upload.
   * Use dh-sequence-python3
   * Remove ref. to Python2 from debian/rules
python-plac (1.4.3-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release:
     - Fix for Python 3.13 changing the output formats (closes: #1082249).
python-plac (1.4.1-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version 1.4.1 (Closes: #1040087)
   * Bump Standards-Version to 4.6.2 (no changes needed)
   * Add patch for importing missing module
   * Add manpage for plac_runner
   * Add lintian override for script with extension warning
python-plac (1.3.5-1) unstable; urgency=medium
 .
   * New upstream release.
   * - Removes non-deterministic test (Closes: #1006999)
python-plac (1.3.4-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Ondřej Nový ]
   * Use debhelper-compat instead of debian/compat.
   * d/control: Update Maintainer field with new Debian Python Team
     contact address.
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
     layout.
 .
   [ Debian Janitor ]
   * Set upstream metadata fields: Bug-Database, Bug-Submit.
   * Bump debhelper from old 11 to 13.
     + Drop check for DEB_BUILD_OPTIONS containing "nocheck", since debhelper now
       does this.
 .
   [ Paul Wise ]
   * New upstream release (Closes: #972065)
     - Add new setuptools build dependency
   * Drop build dependency on obsolete unmaintained SQLSoup (Closes: #999639)
   * Wrap and sort Debian packaging information
   * plac moved to a new upstream maintainer, update URLs
   * Stop ignoring the results of the tests
   * Mark the import test as superficial
   * Drop lintian overrides since they are valid
   * Switch the watch file to GitHub tags page
   * Declare compliance with Debian Policy 4.6.0, no changes needed
   * Add more upstream metadata
   * Drop deviation from upstream plac_runner.py naming
   * Copy the doc dir for the tests since the tests are in there
   * Copy the plac_runner the tests since the tests use it
   * Fix package description typos
   * Make the tests print something unless terse mode is enabled
   * Update copyright holders for the Debian packaging
   * Document that the build does not require root
   * Drop doc-base file as the PDF has been removed upstream
     and the HTML version of the documentation isn't built by Debian
python-plac (0.9.6-1.1) unstable; urgency=medium
 .
   * Non maintainer upload by the Reproducible Builds team.
   * No source change upload to rebuild on buildd with .buildinfo files.
python-plac (0.9.6-1) unstable; urgency=low
 .
   * Initial release. (Closes: #901201)

python-pwdlib (0.3.1-1) unstable; urgency=medium
 .
   * New upstream version 0.3.1
   * refresh and drop upstreamed patches
   * d/watch: migrate to version 5
   * d/control:
   - bump S-V to 4.7.4, remove RRR and Priority field
   - add Build-Depends-Indep for docs
   - migrate to dh-compat 14
   * wrap and sort debian dir

python-pyaudio (0.2.14-1) unstable; urgency=medium
 .
   [ Andreas Tille ]
   * New upstream version
   * Maintain in Debian Python team
     Closes: #1127633, #1141846
   * Bump debhelper from old 12 to 13.
   * Fix day-of-week for changelog entry 0.2.8-1.
   * Fix day-of-week for changelog entry 0.2.6-1.
   * Fix day-of-week for changelog entry 0.2.5-1.
   * Remove redundant Priority: optional from source stanza.
   * Trim trailing whitespace.
   * Add debian/watch file, using pypi.
   * Set debhelper-compat version in Build-Depends.
   * Standards-Version: 4.7.4 (routine-update)
   * Testsuite: autopkgtest-pkg-python (routine-update)
   * Build-Depends: pybuild-plugin-pyproject (routine-update)
   * Build-Depends: s/dh-python/dh-sequence-python3/ (routine-update)
   * Drop 'Rules-Requires-Root: no' from d/control (routine-update)
   * Remove field Testsuite on binary package python-pyaudio-doc that duplicates
     source.
   * Fill in Homepage field.
   * Fix installation by setting PYBUILD_NAME=pyaudio
   * Try hard to get test working but pyaudio tests require a functional
     ALSA/PortAudio device, unavailable in the build environment. Leave
     the attempts as comments anyway
 .
   [ Helmut Grohne ]
   * Demote documentation dependencies to Build-Depends-Indep.
     Closes: #941113

python-pyqrcode (1.2.1-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add debian/salsa-ci.yml
   * Use dh-sequence-python3
   * Bump Standards-Version to 4.7.4, drop Priority: tag
   * Rewrite d/watch in v5 format, accept new Pypi archive name mangling
   * Switch to debhelper-compat 14
 .
   [ Debian Janitor ]
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
     Repository-Browse.

python-qtpy (2.4.3-5) unstable; urgency=medium
 .
   * Team upload
   * Add debian/salsa-ci.yml
   * Rewrite d/watch in v5 format
   * Use dh-sequence-python3
   * Bump Standards-Version to 4.7.4, drop Priority: tag
   * Set upstream metadata fields: Security-Contact.

python-reverse-geocode (1.6.6-1) unstable; urgency=medium
 .
   * Initial release. (Closes: #1144256)

python-samplerate (0.2.4-3) unstable; urgency=medium
 .
   [ Pieter Lenaerts ]
   * Revert CMakeLists.txt to unpatched upstream
   * Make CMakeLists.txt patch DEP3 & gbp pq compliant
   * d/rules: Remove manual build flags. Debhelper covers them.
   * d/control:
     - add self to uploaders,
     - bump stds version & compat helper version
     - add pybuild-plugin-pyproject to build deps
     - mark Testsuite: autopkgtest-pkg-python
   * d/salsa-ci.yml: Correct blhc ignore regex
 .
   [ Gianfranco Costamagna ]
   * Proper versioning and run only for default Python3 (Closes: #1143199)

python-technove (2.1.3-1) unstable; urgency=medium
 .
   * New upstream release.
   * Update to debhelper compatibility level 14.
   * Add dh-sequence-single-binary.
   * Remove debhelper compat 14 auto-applied substvars.
   * Prefix debhelper files with the binary package name.
   * Add debian/py3dist-overrides.

python-trezor (0.20.2-1) unstable; urgency=medium
 .
   [ Soren Stoutner ]
   * New upstream release.
   * Add the following files:
     - debian/source/lintian-overrides.
     - debian/python3-trezor.lintian-overrides.
   * debian/changelog:
     - Update upstream copyright for new release.
     - Bump my main copyright years to be 2024-2026.
   * debian/control:
     - Add Build-Depends on pybuild-plugin-pyproject and flit.
     - Bump debhelper-compat from version 13 to 14, removing the now-unnecessary
       ${misc:Depends} and ${python3:Depends}.
     - Bump Standards-Version from 4.7.2 to 4.7.4, removing the now-redundant
       "Priority: optional" field.
     - Remove "Rules-Requires-Root: no".
   * debian/watch:  Refactor from version 4 to version 5.
 .
   [ Manuel Guerra ]
   * Move setuptools to Build-Depends instead of Build-Depends-Indep.

python-ttfautohint-py (0.6.1-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version 0.6.1

python-ttls (1.11.1-1) unstable; urgency=medium
 .
   * New upstream release.
   * Remove debian/gbp.conf, switch to dgit.
   * Update Standards-Version.
   * Update to debhelper compatibility level 14.
   * Add dh-sequence-single-binary.
   * Remove debhelper compat 14 auto-applied substvars.
   * Prefix debhelper files with the binary package name.

python-virustotal-api (1.1.11-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Rewrite d/watch in v5 format
      -> the "[_-]"allow to detect evenutal future version that applies
         the new Pypi archive name mangling policy
   * Use dh-sequence-python3
   * Drop "Rules-Requires-Root: no": it is the default now
   * Add debian/salsa-ci.yml
   * Bump Standards-Version to 4.7.4, drop Priority: tag
 .
   [ Debian Janitor ]
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository-Browse.

yte (1.5.4-1) unstable; urgency=medium
 .
   * New upstream version 1.5.4
yte (1.5.1-2) unstable; urgency=medium
 .
   * Team Upload.
   * source-only upload.
yte (1.5.1-1) unstable; urgency=medium
 .
   * Initial release (Closes: #1055930)



REMOVED: ukui-screensaver 3.0.3.4-1
REMOVED: pyhoca-cli 0.6.1.3-2
REMOVED: lightdm-remote-session-x2go 0.0.2.0-2.1
REMOVED: remmina 1.4.43+dfsg-1