Your message dated Thu, 14 Mar 2024 07:37:51 +0100
with message-id <[email protected]>
and subject line Closing manually
has caused the Debian Bug report #1046569,
regarding python-cryptography: Fails to build source after successful build
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.)
--
1046569: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1046569
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: python-cryptography
Version: 38.0.4-4
Severity: minor
Tags: trixie sid ftbfs
User: [email protected]
Usertags: ftbfs-sab-20230813 ftbfs-source-after-build
User: [email protected]
Usertags: qa-doublebuild
Hi,
This package fails to build a source package after a successful build
(dpkg-buildpackage ; dpkg-buildpackage -S).
This is probably a clear violation of Debian Policy section 4.9 (clean target),
but this is filed as severity:minor for now, because a discussion on
debian-devel showed that we might want to revisit the requirement of a working
'clean' target.
More information about this class of issues, included common problems and
solutions, is available at
https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild
Relevant part of the build log:
> cd /<<PKGBUILDDIR>> && runuser -u user42 -- dpkg-buildpackage --sanitize-env
> -us -uc -rfakeroot -S
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
> dpkg-buildpackage: info: source package python-cryptography
> dpkg-buildpackage: info: source version 38.0.4-4
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Nicolas Dandrimont
> <[email protected]>
> dpkg-source --before-build .
> dpkg-source: info: using options from
> python-cryptography-38.0.4/debian/source/options:
> --extend-diff-ignore=(^|/)(.*\.egg-info/(PKG-INFO|SOURCES\.txt|requires\.txt))$
> debian/rules clean
> dh clean --buildsystem=pybuild
> rm -f debian/python-cryptography-doc.debhelper.log
> debian/python3-cryptography.debhelper.log
> debian/rules override_dh_auto_clean
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> dh_auto_clean
> pybuild --clean -i python{version} -p 3.11
> rm -rf .pybuild/
> find . -name \*.pyc -exec rm {} \;
> rm -rf src/rust/target
> rm -rf debian/cargo_registry
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> dh_autoreconf_clean -O--buildsystem=pybuild
> dh_clean -O--buildsystem=pybuild
> rm -f debian/debhelper-build-stamp
> rm -rf debian/.debhelper/
> rm -f -- debian/python3-cryptography.substvars
> debian/python3-cryptography.postinst.debhelper
> debian/python3-cryptography.prerm.debhelper
> debian/python-cryptography-doc.substvars debian/files
> rm -fr -- debian/python3-cryptography/ debian/tmp/
> debian/python-cryptography-doc/
> find . \( \( \
> \( -path .\*/.git -o -path .\*/.svn -o -path .\*/.bzr -o -path
> .\*/.hg -o -path .\*/CVS -o -path .\*/.pc -o -path .\*/_darcs \) -prune -o
> -type f -a \
> \( -name '#*#' -o -name '.*~' -o -name '*~' -o -name DEADJOE \
> -o -name '*.orig' -o -name '*.rej' -o -name '*.bak' \
> -o -name '.*.orig' -o -name .*.rej -o -name '.SUMS' \
> -o -name TAGS -o \( -path '*/.deps/*' -a -name '*.P' \) \
> \) -exec rm -f {} + \) -o \
> \( -type d -a -name autom4te.cache -prune -exec rm -rf {} + \)
> \)
> dpkg-source -b .
> dpkg-source: info: using options from
> python-cryptography-38.0.4/debian/source/options:
> --extend-diff-ignore=(^|/)(.*\.egg-info/(PKG-INFO|SOURCES\.txt|requires\.txt))$
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: verifying ./python-cryptography_38.0.4.orig.tar.gz.asc
> gpgv: Signature made Sun Nov 27 19:02:46 2022 UTC
> gpgv: using RSA key 05FD9FA16CF757350D91A560235AE5F129F9ED98
> gpgv: Note: signatures using the SHA1 algorithm are rejected
> gpgv: Can't check signature: Bad public key
> dpkg-source: warning: cannot verify upstream tarball signature for
> ./python-cryptography_38.0.4.orig.tar.gz: no acceptable signature found
> dpkg-source: info: building python-cryptography using existing
> ./python-cryptography_38.0.4.orig.tar.gz
> dpkg-source: info: building python-cryptography using existing
> ./python-cryptography_38.0.4.orig.tar.gz.asc
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: local changes detected, the modified files are:
> python-cryptography-38.0.4/src/rust/Cargo.lock
> dpkg-source: error: aborting due to unexpected upstream changes, see
> /tmp/python-cryptography_38.0.4-4.diff.pGOTRa
> dpkg-source: info: Hint: make sure the version in debian/changelog matches
> the unpacked source tree
> dpkg-source: info: you can integrate the local changes with dpkg-source
> --commit
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
>
> E: Command 'cd /<<PKGBUILDDIR>> && runuser -u user42 -- dpkg-buildpackage
> --sanitize-env -us -uc -rfakeroot -S' failed to run.
The full build log is available from:
http://qa-logs.debian.net/2023/08/13/python-cryptography_38.0.4-4_unstable.log
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 ---
This bug was closed in recent upload but the closes statement
was missing in changelog thus closing manually.
--
http://fam-tille.de
--- End Message ---
