Your message dated Mon, 02 Oct 2023 09:05:22 +0000
with message-id <[email protected]>
and subject line Bug#1052878: fixed in duplicity 1.2.2-2
has caused the Debian Bug report #1052878,
regarding duplicity: FTBFS: mv: cannot stat 
'lib/python*/dist-packages/duplicity/backends/README': No such file or directory
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.)


-- 
1052878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052878
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: duplicity
Version: 1.2.2-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: [email protected]
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;[email protected]
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230925&[email protected]&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.

--- End Message ---
--- Begin Message ---
Source: duplicity
Source-Version: 1.2.2-2
Done: Alexander Zangerl <[email protected]>

We believe that the bug you reported is fixed in the latest version of
duplicity, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alexander Zangerl <[email protected]> (supplier of updated duplicity package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Mon, 02 Oct 2023 10:39:40 +0200
Source: duplicity
Architecture: source
Version: 1.2.2-2
Distribution: unstable
Urgency: medium
Maintainer: Alexander Zangerl <[email protected]>
Changed-By: Alexander Zangerl <[email protected]>
Closes: 1052878
Changes:
 duplicity (1.2.2-2) unstable; urgency=medium
 .
   * minor build adjustments (closes: #1052878)
Checksums-Sha1:
 9f2f37c2dada33a70c0de8757fdbf45530f9913c 2188 duplicity_1.2.2-2.dsc
 a8e629e7e3f5b1aa28d98e5f0061f8ff62b8206e 16328 duplicity_1.2.2-2.debian.tar.xz
 eba6edac06ad70d3f006100420750cc40df50b19 11298 
duplicity_1.2.2-2_amd64.buildinfo
Checksums-Sha256:
 b77b7e4bf9d23e5a53449f8517b7eb1809b181c4ec0e05cb657f7ffaadc94f21 2188 
duplicity_1.2.2-2.dsc
 69f052339f29bba74d95279ed6e111bb96455cf07857434b705a3c5ac94ed49f 16328 
duplicity_1.2.2-2.debian.tar.xz
 2837bf108550c5e0001334575fc2709450f0621202fa9187692df27f30e2c87e 11298 
duplicity_1.2.2-2_amd64.buildinfo
Files:
 01b1ddb88a55c2c47127266e98afe196 2188 utils optional duplicity_1.2.2-2.dsc
 21fa582b43b82fb3cc8dbf67cc65e798 16328 utils optional 
duplicity_1.2.2-2.debian.tar.xz
 f96d7e63cd66a5ddfa4bd902325593ae 11298 utils optional 
duplicity_1.2.2-2_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJlGoUmAAoJED06g4g30PqNbN4P/Rz1t02EA6YoIr5jZlIwJ7Qh
J6ie6urtvd1ExMniJpXACJnXb6lSUuIQuKwNu9i8d/1BbCnLtK+a9KFo6IcJFd0O
wUOvnz6xJRxFOmaGd1yiJWG6fwWnbHNyuuwQmwCoHh7ClBXygWzFpqOjFpAhQ6rn
/UrJCSITBGq1XF3aOmnQ/VMpgRRbPV1j6INmGDYnRvxtHfCiKPGoFvfoYfneHIxV
WixNZy0MFmBOD2uHT1/rm4iaaymSpWwfQz1S5t0EeVohWxVhAYSkLrcqgCLhlvG5
r4PJ5Ixhs5NwZxk3OOHQygkRhKnvIP1MgtRAXNS4YfXcAl4iC3/7zm27oyuSBIyD
dHQznmJsiClLtywnQeInaVfXw8HTWDq/SNXRpIMcc510O2oGz0IxzB2d3/GlqyKo
fofO8mA9xBOHhDEe+rgNp2I5NX6+LJIByMkBXRdAhnJl7ezcpGB2XCFXvruqvnpl
JKsSab+I34eH2UIktWnr9ckss7daeNJ7DnZTfld3Ghu1Rw2GMZXRHnOfL2Gpq2ai
79Z8QxTTP+Rfx6RyZ3pVK4mWzMn4CipOXxEF7hz3mpvVl+QpEjYZWuObf6isjWq3
rZTkhVB3ydSJ1jjG1Ay3FxtffVd3kLQH+62FjlH0FQIXKm83GOGamJWK/H13k+gN
KuOFz+mYI3SgRJ0sXXGz
=ltFg
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to