Your message dated Fri, 21 Jul 2023 09:55:42 +0000
with message-id <e1qmmro-00ghud...@fasolo.debian.org>
and subject line Bug#1040853: fixed in python-lockfile 1:0.12.2-3
has caused the Debian Bug report #1040853,
regarding python-lockfile autopkg test fail with setuptools 68
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 ow...@bugs.debian.org
immediately.)


-- 
1040853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040853
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-lockfile
Version: 1:0.12.2-2.2
Severity: serious
Tags: sid trixie

see
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-lockfile/35654871/log.gz

[...]
32s autopkgtest [23:39:35]: test smoke-python3: - - - - - - - - - - results - - - - - - - - - - 32s smoke-python3 FAIL stderr: /tmp/autopkgtest-lxc.37ggweuu/downtmp/build.QlD/src/debian/tests/smoke_test.py:27: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html 32s autopkgtest [23:39:35]: test smoke-python3: - - - - - - - - - - stderr - - - - - - - - - - 32s /tmp/autopkgtest-lxc.37ggweuu/downtmp/build.QlD/src/debian/tests/smoke_test.py:27: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html
 32s   import pkg_resources

--- End Message ---
--- Begin Message ---
Source: python-lockfile
Source-Version: 1:0.12.2-3
Done: Ben Finney <bign...@debian.org>

We believe that the bug you reported is fixed in the latest version of
python-lockfile, 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 1040...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Finney <bign...@debian.org> (supplier of updated python-lockfile 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 ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Fri, 21 Jul 2023 19:03:46 +1000
Source: python-lockfile
Architecture: source
Version: 1:0.12.2-3
Distribution: unstable
Urgency: medium
Maintainer: Ben Finney <bign...@debian.org>
Changed-By: Ben Finney <bign...@debian.org>
Closes: 1040853
Changes:
 python-lockfile (1:0.12.2-3) unstable; urgency=medium
 .
   * Specify current VCS for Debian packaging work.
   * Grant license in Debian packaging files under terms of GNU GPL 3 or later.
   * debian/gbp.conf:
     * Update for current packaging source maintenance workflow.
   * Document the current packaging source maintenance workflow.
   * Override false positive Lintian check for VCS-* field names.
   * Declare conformance to “Standards-Version: 4.6.2”.
   * Declare Debhelper compatibility level 13.
   * debian/compat:
     * Remove obsolete configuration file.
   * debian/watch:
     * Update UScan configuration format to version 4.
   * Remove ‘get-orig-source’ and ‘get-packaged-orig-source’ targets.
     These are no longer mentioned in Debian Policy 4.1.4 and later.
   * debian/tests/:
     * Remove AutoPkgTest for Python 2 package.
   * Stop building the Python 2 package.
   * Explicitly declare build system for PyBuild.
   * Remove specification of ancient minimum Python version.
   * Specify the package build system does not require root privilege.
   * Declare upstream metadata in DEP-12 format.
   * Explicitly mark a superficial AutoPkgTest case.
   * Use only supported Python versions in the AutoPkgTest.
   * Use external package ‘python3-package-smoke-test’ for AutoPkgTest.
     Closes: bug#1040853. Thanks to Matthias Klose for the report.
   * debian/tests/smoke_test.py:
     * Remove unused test helper module, now migrated to external package.
Checksums-Sha1:
 a9bed5472efa038f7162a46ae984d84a9446341f 2186 python-lockfile_0.12.2-3.dsc
 788ebe1fb3b74e082ebf592eeb8b8ff066764c28 9568 
python-lockfile_0.12.2-3.debian.tar.xz
 71ec135d6a02f7f0672a3ded62da0e92c30fb0d9 8307 
python-lockfile_0.12.2-3_amd64.buildinfo
Checksums-Sha256:
 a127b059046f404712145ada8b9b9263fc92c3e91f82abb58496199f522ac03e 2186 
python-lockfile_0.12.2-3.dsc
 49e1968bc9cf919b7102919413e204f9d607e7fce31ab44e43103d5d3788534c 9568 
python-lockfile_0.12.2-3.debian.tar.xz
 102e0886002476ac14d3af03fd8520fe1ea871841b795cf28b3e28061bfccc44 8307 
python-lockfile_0.12.2-3_amd64.buildinfo
Files:
 607be94d835dd0d15d631b157251f59a 2186 python optional 
python-lockfile_0.12.2-3.dsc
 62ebdc562c10df445c51dc52c85b142d 9568 python optional 
python-lockfile_0.12.2-3.debian.tar.xz
 7de4e79a59e47ff2bd8ced32f991f41f 8307 python optional 
python-lockfile_0.12.2-3_amd64.buildinfo

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

iQIzBAEBCAAdFiEEYVng8p4vpBLgeVxz+bRqrIRCDIIFAmS6S2oACgkQ+bRqrIRC
DIKGiQ//TH4Rj4AryAOVkXNLAXl4g+F/Z9lb+w0JinkIiLSb0k7p+p9JmfK/jlK3
egWMIaMk2I+AANT2clixbvI4l9URoPneGoYLakK4Gots8i9BJQVVuet6svCs5KCX
wOgMrRZbye7VPPU00imEprM47OuxfaAqg52gdZDJQ/5t0JUrXxp9iHjPL/6grpGE
vhJUHWwGFF8e5HkjtSJdpmglCAg9WEIrpqjohpGsq3w4LRtkmaHDnaVnXmsNebml
7duJkxiFOo2rGRAl4E8sT534JP++9i0IgrRXAt/h7iqvSwVsuONLf0me5f92Uc8J
wYMiX8HiBMrPdeGFIbKkkdbmttU9qSkfr6uXLKjyPHYJSqosVD4G43EER+HxryZe
hEmowHO/xZ45I34EZscCKST1DD6hbsewfuW73VqWL3kK8ijv1AQb1K6G2yT7qa76
yBiJEvwmvfs1u6IfLy1Fw/KHgYtDcoaWzC1t/jNd0jApjKmSRk8/wapiYCLhAMQq
yhX/poS3k4hOrgcJPZ3E9FEIsYNJE7vQX6+19S1G/7yfXsz5RinlM7ZJ61gFxjxh
/jzLAgfDYq7uBwlxzMtI+BdOXXbPkb/J2jOr9jreUkT3NfFVxYzX+Qa3gQrivgP/
/FVGQMn90vIqBrADgZCKsvKx+K78Fnxkte/gDF0zRukMkF6VGMM=
=jiai
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to