From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] duplicity 1.2.1 incompatible with python3.12
Date: Wed, 11 Oct 2023 17:35:39 +0200 [thread overview]
Message-ID: <20231011153539.6eIETWrYPs6aUIKKOeCwHyfp9JOmsML485I8Wm3bH2E@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46572@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1194 bytes --]
Closed issue by adud on void-packages repository
https://github.com/void-linux/void-packages/issues/46572
Description:
### Is this a new report?
Yes
### System Info
Void 6.5.6_1 x86_64 GenuineIntel uptodate rFFFF
### Package(s) Affected
duplicity-1.2.1_3
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
The package is supposed to do backups
### Actual behaviour
Any call to duplicity results in the following python error
```
Traceback (most recent call last):
File "/usr/bin/duplicity", line 30, in <module>
from future import standard_library
File "/usr/lib/python3.12/site-packages/future/standard_library/__init__.py", line 65, in <module>
import imp
ModuleNotFoundError: No module named 'imp'
```
The bug comes from the [future](https://pypi.org/project/future/) package, which uses the `imp` module (removed in python 3.12). The use of this package has been removed since duplicity 2.0.0 (https://gitlab.com/duplicity/duplicity/-/blob/main/CHANGELOG.md) while dropping python2.7 support
This could explain the failure in #46170
### Steps to reproduce
`duplicity`
prev parent reply other threads:[~2023-10-11 15:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 21:57 [ISSUE] " adud
2023-10-11 15:35 ` Johnnynator [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231011153539.6eIETWrYPs6aUIKKOeCwHyfp9JOmsML485I8Wm3bH2E@z \
--to=johnnynator@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).