Debian 13 Trixie upgrade errors on RPi 4 - - installing flasks and requests

Troubleshooting
1

Creating a bug report/issue

I have searched the existing open and closed issues

Required Information

  • DietPi version | v9.18.2
  • Distro version | trixie 0
  • Kernel version | Linux DietPi 6.12.47+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.12.47-1+rpt1 (2025-09-16) aarch64 GNU/Linux
  • Architecture | arm64
  • SBC model | RPi 4 Model B (aarch64)
  • Power supply used | (EG: 5V 1A RAVpower)
  • SD card used | SD card

Additional Information (if applicable)

  • Software title | (EG: Nextcloud)
  • Was the software title installed freshly or updated/migrated?
  • Can this issue be replicated on a fresh installation of DietPi?
    ← If you sent a “dietpi-bugreport”, please paste the ID here →
  • Bug report ID | b58d0114-3d49-4795-9684-45fcf817f316

Steps to reproduce

  1. Ran Debian 13 Trixie upgrade script several times with the same result, stopping with the same error messages each time.
    Trixie upgrade appears successful, but I receive the same error message regarding “pip3 install -U flask requests” when updating DietPi Software elements.
  2. …

Expected behaviour

  • …

Actual behaviour

  • Error messages during DietPi Software updates following a Debian Trixie upgrade from Bookworm. Fails at: pip3 install -U flasks requests
  "Installing collected packages: requests, markupsafe, itsdangerous, click, blinker, werkzeug, jinja2, flask

  │ Attempting uninstall: requests

  │ Found existing installation: requests 2.32.3

  │ error: uninstall-no-record-file

  │

  │ × Cannot uninstall requests 2.32.3

  │ ╰─> The package's contents are unknown: no RECORD file was found for requests.

  │

  │ hint: The package was installed by debian. You should check if it can uninstall the package.”

Extra details

This RPi 4 Model B is used solely as an ADSB feeder using the ADSB.im Docker package installed via DietPi-Software. The feeder appears to still work after the upgrade to Trixie, but I can no longer access any ADSB.im configuration pages.

I had ensured the previous Bookworm installation was up to date, to include the ADSB.im pacakges.

2

Trying the upgrade script again and taking a fresh look at the console error messages, it appears the upgrade stops when trying to delete an old version of Python requests (v 2.32.3).

So, I manually deleted the requests folder in /usr/lib/python3/dist-packages. I then re-ran the Trixie upgrade script and all DietPi updates were installed successfully with no error messages.

System appears to function normally after reboot and I can now access the config page for the adsb.im feeder.

3

Yes starting Debian Trixie, there is a conflict between pure python packages and python apt packages. Because of this, we might move to individual pyenv per application to avoid this conflict in future