[PKG-Openstack-devel] Bug#839342: python-glance-store: FTBFS: Tests failures

Lucas Nussbaum lucas at debian.org
Sat Oct 1 08:44:20 UTC 2016


Source: python-glance-store
Version: 0.13.1-1
Severity: serious
Tags: stretch sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20160930 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>   File "/<<PKGBUILDDIR>>/glance_store/tests/unit/test_opts.py", line 46, in _test_entry_point
>     list_fn = ep.load()
>   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2263, in load
>     self.require(*args, **kwargs)
>   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2280, in require
>     items = working_set.resolve(reqs, env, installer)
>   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 856, in resolve
>     raise DistributionNotFound(req, requirers)
> pkg_resources.DistributionNotFound: The 'enum34' distribution was not found and is required by the application
> 
> 
> ----------------------------------------------------------------------
> Ran 344 tests in 4.380s
> 
> FAILED (failures=1)
> debian/rules:36: recipe for target 'override_dh_auto_test' failed

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

The full build log is available from:
   http://aws-logs.debian.net/2016/09/30/python-glance-store_0.13.1-1_unstable.log

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!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



More information about the Openstack-devel mailing list