Source: sqlparse
Version: 0.5.5-2
Severity: serious
Justification: unfit for release?
X-Debbugs-Cc: [email protected], [email protected]

Hi

As pointed out in
https://www.openwall.com/lists/oss-security/2026/11/10/20 and more
widely discussed in
https://github.com/andialbrecht/sqlparse/discussions/945 upstream has
declared sqlparse as EOL.

I'm raising this as first as RC level to explore the possiblity that
we can keep sqlparse out of forky or eventually remove. But at this
time there are a couple of problems considering that:

carnil@coccia:~$ dak rm --suite=sid -n -R sqlparse
Will remove the following packages from sid:

python-sqlparse-doc |    0.5.5-2 | all
python3-sqlparse |    0.5.5-2 | all
 sqlformat |    0.5.5-2 | all
  sqlparse |    0.5.5-2 | source

Maintainer: Debian Python Team <[email protected]>

------------------- Reason -------------------

----------------------------------------------

Checking reverse dependencies...
# Broken Depends:
litecli: litecli
mycli: mycli
omnidb: omnidb-common
pgcli: pgcli
python-django: python3-django
python-django-debug-toolbar: python3-django-debug-toolbar
python-pgspecial: python3-pgspecial
yoyo: python3-yoyo

# Broken Build-Depends:
pgcli: python3-sqlparse (0.3 >=)
python-django: python3-sqlparse
python-django-debug-toolbar: python3-sqlparse
python-pgspecial: python3-sqlparse
yoyo: python3-sqlparse

Dependency problem found.

so that would not be immediately possible. What do you think on the
the practical possibility to achieve that goal?

Regards,
Salvatore

Reply via email to