Source: duplicity Version: 1.2.2-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230925 ftbfs-trixie
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<<PKGBUILDDIR>>' > rm -r --verbose debian/duplicity/usr/share/doc/duplicity-* > removed 'debian/duplicity/usr/share/doc/duplicity-1.2.2/COPYING' > removed 'debian/duplicity/usr/share/doc/duplicity-1.2.2/CONTRIBUTING.md' > removed 'debian/duplicity/usr/share/doc/duplicity-1.2.2/README-LOG.md' > removed 'debian/duplicity/usr/share/doc/duplicity-1.2.2/CHANGELOG.md' > removed 'debian/duplicity/usr/share/doc/duplicity-1.2.2/README-REPO.md' > removed 'debian/duplicity/usr/share/doc/duplicity-1.2.2/README.md' > removed 'debian/duplicity/usr/share/doc/duplicity-1.2.2/README-TESTING.md' > removed directory 'debian/duplicity/usr/share/doc/duplicity-1.2.2' > (cd debian/duplicity/usr \ > && mkdir -p share/doc/duplicity \ > && mv --verbose \ > lib/python*/dist-packages/duplicity/backends/README \ > share/doc/duplicity/README.backends) > mv: cannot stat 'lib/python*/dist-packages/duplicity/backends/README': No > such file or directory > make[1]: *** [debian/rules:27: execute_after_dh_auto_install] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/09/25/duplicity_1.2.2-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230925;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230925&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.