* [ISSUE] duplicity 1.2.1 incompatible with python3.12
@ 2023-10-10 21:57 adud
2023-10-11 15:35 ` [ISSUE] [CLOSED] " Johnnynator
0 siblings, 1 reply; 2+ messages in thread
From: adud @ 2023-10-10 21:57 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1191 bytes --]
New 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`
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-10-11 15:35 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-10-10 21:57 [ISSUE] duplicity 1.2.1 incompatible with python3.12 adud
2023-10-11 15:35 ` [ISSUE] [CLOSED] " Johnnynator
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).