Your message dated Fri, 10 Oct 2025 11:30:01 +1000
with message-id <[email protected]_HH.FGUE>
and subject line Re: Bug#1115302: duplicity: Duplicity does not run on Debian
13.1, needs 'future' python module, which is not provided in Trixie
has caused the Debian Bug report #1115302,
regarding duplicity: Duplicity does not run on Debian 13.1, needs 'future'
python module, which is not provided in Trixie
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1115302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1115302
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: duplicity
Version: 3.0.4-1+b1
Severity: important
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.
-- System Information:
Debian Release: 13.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.12.43+deb13-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages duplicity depends on:
ii gnupg 2.4.7-21
ii libc6 2.41-12
ii librsync2t64 2.3.4-1.1+b1
ii python3 3.13.5-1
ii python3-fasteners 0.18-2
ii python3-httplib2 0.22.0-1
ii python3-lxml 5.4.0-1
ii python3-paramiko 3.5.1-3
ii python3-pexpect 4.9-3
ii python3-pkg-resources 78.1.1-0.1
ii python3-psutil 7.0.0-2
ii python3-requests 2.32.3+dfsg-5
Versions of packages duplicity recommends:
ii python3-oauthlib 3.2.2-3
ii python3-urllib3 2.3.0-3
ii rsync 3.4.1+ds1-5
Versions of packages duplicity suggests:
pn lftp <none>
pn ncftp <none>
pn par2 <none>
pn python3-boto3 <none>
ii python3-pip 25.1.1+dfsg-1
pn python3-swiftclient <none>
pn tahoe-lafs <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
On Mon, 06 Oct 2025 08:39:36 +0200, Niels Lammers writes:
>As I cannot reproduce the upgrade itself, I will assume this was a very
>odd individual issue. Sorry about that!
no problem. i'll close that bug for now.
regards
az
--
Alexander Zangerl + GPG Key 2FCCF66BB963BD5F + https://snafu.priv.at/
"So instead, I toil through fields of various OSes, planting applications,
spraying patches to catch the bugs, and watching the databases grow."
-- D. Joseph Creighton
signature.asc
Description: Digital Signature
--- End Message ---
