Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   Upgrade to Debian Trixie (13.1)
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   Tried to install python3-future package to make duplicity work, but
   found out it is not provided in Trixie (at least that's what it looks
   like..).
   * What was the outcome of this action?
   See previous.
   * What outcome did you expect instead?
   Clear dependency of duplicity on 'future' module and having it
   provided in Trixie.

tags 1115302 + unreproducible moreinfo
severity 1115302 minor
thanks

On Mon, 15 Sep 2025 13:53:35 +0200, Niels Lammers writes:
...
...
package that depends on python3-future: the deb in trixie doesn't
have such a dependency. it installs just fine in a brand-new
trixie chroot, including all the recommended packages.

file name is duplicity_3.0.4-1+b1_amd64.deb, sha256sum
is f1f5497210e15c3db3e04695ad459123fb5247fcb28708e2c9807c65400344a8,
and the stated dependencies are

Depends: libc6 (>= 2.4), librsync2t64 (>= 1.0.0), python3 (<< 3.14),
 python3 (>= 3.13~), python3-fasteners, python3-httplib2, python3-lxml,
 python3-paramiko, python3-pexpect, python3-pkg-resources,
 python3-psutil, python3-requests, python3:any (>= 3.7~), gnupg | gnupg1
Recommends: rsync, python3-urllib3, python3-oauthlib

Hi,

I upgraded to Trixie (not a brand-new install), so my guess is something
must have happened there.
The trixie package in clean environment does work like expected.
As I cannot reproduce the upgrade itself, I will assume this was a very
odd individual issue. Sorry about that!

Thanks for the response and your work.

cheers,
./Niels