Bug#896428: python3-pytest-runner: ptr fails to import
Package: python3-pytest-runner
Version: 2.11.1-1
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python3-pytest-runner importing the module ptr
into a python interpreter fails with the following error:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/ptr.py", line 18, in
import pkg_resources
ModuleNotFoundError: No module named 'pkg_resources'
The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.
Helmut
Bug#896426: python-brian: brian fails to import
Package: python-brian
Version: 1.4.3-1
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python-brian importing the module brian
into a python interpreter fails with the following error:
/usr/lib/python2.7/dist-packages/brian/__init__.py:46: UserWarning: Couldn't
import pylab.
_warnings.warn("Couldn't import pylab.")
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python2.7/dist-packages/brian/__init__.py", line 51, in
from connections import *
File "/usr/lib/python2.7/dist-packages/brian/connections/__init__.py", line
1, in
from sparsematrix import *
File "/usr/lib/python2.7/dist-packages/brian/connections/sparsematrix.py",
line 1, in
from base import *
File "/usr/lib/python2.7/dist-packages/brian/connections/base.py", line 14,
in
from scipy import weave
ImportError: cannot import name weave
The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.
Helmut
Bug#896424: python3-terminado: terminado fails to import
Package: python3-terminado
Version: 0.8.1-2
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python3-terminado importing the module terminado
into a python interpreter fails with the following error:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/terminado/__init__.py", line 7, in
from .websocket import TermSocket
File "/usr/lib/python3/dist-packages/terminado/websocket.py", line 18, in
import tornado.web
ModuleNotFoundError: No module named 'tornado'
The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.
Helmut
Bug#896417: python3-mplexporter: mplexporter fails to import
Package: python3-mplexporter
Version: 0.0.1+20140921-2
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python3-mplexporter importing the module mplexporter
into a python interpreter fails with the following error:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/mplexporter/__init__.py", line 1, in
from .renderers import Renderer
File "/usr/lib/python3/dist-packages/mplexporter/renderers/__init__.py", line
9, in
from .base import Renderer
File "/usr/lib/python3/dist-packages/mplexporter/renderers/base.py", line 5,
in
import numpy as np
ModuleNotFoundError: No module named 'numpy'
The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.
Helmut
Bug#896421: python3-lasagne: lasagne fails to import
Package: python3-lasagne
Version: 0.1+git20180322.37ca134-1
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python3-lasagne importing the module lasagne
into a python interpreter fails with the following error:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/theano/configdefaults.py", line 1738, in
filter_compiledir
os.makedirs(path, 0o770) # read-write-execute for user and group
File "/usr/lib/python3.6/os.py", line 210, in makedirs
makedirs(head, mode, exist_ok)
File "/usr/lib/python3.6/os.py", line 210, in makedirs
makedirs(head, mode, exist_ok)
File "/usr/lib/python3.6/os.py", line 220, in makedirs
mkdir(name, mode)
PermissionError: [Errno 13] Permission denied: '/nonexistent'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/lasagne/__init__.py", line 12, in
import theano
File "/usr/lib/python3/dist-packages/theano/__init__.py", line 66, in
from theano.compile import (
File "/usr/lib/python3/dist-packages/theano/compile/__init__.py", line 10, in
from theano.compile.function_module import *
File "/usr/lib/python3/dist-packages/theano/compile/function_module.py", line
21, in
import theano.compile.mode
File "/usr/lib/python3/dist-packages/theano/compile/mode.py", line 10, in
import theano.gof.vm
File "/usr/lib/python3/dist-packages/theano/gof/vm.py", line 662, in
from . import lazylinker_c
File "/usr/lib/python3/dist-packages/theano/gof/lazylinker_c.py", line 42, in
location = os.path.join(config.compiledir, 'lazylinker_ext')
File "/usr/lib/python3/dist-packages/theano/configparser.py", line 333, in
__get__
self.__set__(cls, val_str)
File "/usr/lib/python3/dist-packages/theano/configparser.py", line 344, in
__set__
self.val = self.filter(val)
File "/usr/lib/python3/dist-packages/theano/configdefaults.py", line 1745, in
filter_compiledir
" '%s'. Check the permissions." % path)
ValueError: Unable to create the compiledir directory
'/nonexistent/.theano/compiledir_Linux-4.14--amd64-x86_64-with-debian-buster-sid--3.6.5-64'.
Check the permissions.
The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.
Helmut
Bug#896425: python3-django-cors-headers: corsheaders fails to import
Package: python3-django-cors-headers
Version: 2.1.0+github-2
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python3-django-cors-headers importing the module corsheaders
into a python interpreter fails with the following error:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/corsheaders/__init__.py", line 1, in
from .checks import check_settings # noqa: F401
File "/usr/lib/python3/dist-packages/corsheaders/checks.py", line 5, in
from django.core import checks
ModuleNotFoundError: No module named 'django'
The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.
Helmut
Bug#896427: python3-spyder-line-profiler: spyder_line_profiler fails to import
Package: python3-spyder-line-profiler
Version: 0.1.1-1
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python3-spyder-line-profiler importing the module
spyder_line_profiler
into a python interpreter fails with the following error:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/spyder_line_profiler/__init__.py", line
12, in
from .lineprofiler import LineProfiler
File "/usr/lib/python3/dist-packages/spyder_line_profiler/lineprofiler.py",
line 14, in
from spyder.utils.qthelpers import qapplication
File "/usr/lib/python3/dist-packages/spyder/utils/qthelpers.py", line 25, in
from spyder.config.base import get_image_path, running_in_mac_app
File "/usr/lib/python3/dist-packages/spyder/config/base.py", line 221, in
LANG_FILE = get_conf_path('langconfig')
File "/usr/lib/python3/dist-packages/spyder/config/base.py", line 126, in
get_conf_path
xdg_config_home = osp.join(get_home_dir(), '.config')
File "/usr/lib/python3/dist-packages/spyder/config/base.py", line 116, in
get_home_dir
raise RuntimeError('Please define environment variable $HOME')
RuntimeError: Please define environment variable $HOME
The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.
Helmut
Bug#896429: python3-django-tables2: django_tables2 fails to import
Package: python3-django-tables2
Version: 1.14.2-1
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python3-django-tables2 importing the module django_tables2
into a python interpreter fails with the following error:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/django_tables2/__init__.py", line 2, in
from .tables import Table, TableBase
File "/usr/lib/python3/dist-packages/django_tables2/tables.py", line 15, in
from . import columns
File "/usr/lib/python3/dist-packages/django_tables2/columns/__init__.py",
line 8, in
from .jsoncolumn import JSONColumn
File "/usr/lib/python3/dist-packages/django_tables2/columns/jsoncolumn.py",
line 15, in
from django.contrib.postgres.fields import HStoreField, JSONField
File
"/usr/lib/python3/dist-packages/django/contrib/postgres/fields/__init__.py",
line 1, in
from .array import * # NOQA
File
"/usr/lib/python3/dist-packages/django/contrib/postgres/fields/array.py", line
3, in
from django.contrib.postgres import lookups
File "/usr/lib/python3/dist-packages/django/contrib/postgres/lookups.py",
line 4, in
from .search import SearchVector, SearchVectorExact, SearchVectorField
File "/usr/lib/python3/dist-packages/django/contrib/postgres/search.py", line
47, in
class SearchVector(SearchVectorCombinable, Func):
File "/usr/lib/python3/dist-packages/django/contrib/postgres/search.py", line
50, in SearchVector
_output_field = SearchVectorField()
File "/usr/lib/python3/dist-packages/django/db/models/fields/__init__.py",
line 172, in __init__
self.db_tablespace = db_tablespace or settings.DEFAULT_INDEX_TABLESPACE
File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 56, in
__getattr__
self._setup(name)
File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 39, in
_setup
% (desc, ENVIRONMENT_VARIABLE))
django.core.exceptions.ImproperlyConfigured: Requested setting
DEFAULT_INDEX_TABLESPACE, but settings are not configured. You must either
define the environment variable DJANGO_SETTINGS_MODULE or call
settings.configure() before accessing settings.
The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.
Helmut
Bug#896420: python3-winrm: winrm fails to import
Package: python3-winrm
Version: 0.3.0-1
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python3-winrm importing the module winrm
into a python interpreter fails with the following error:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/winrm/__init__.py", line 6, in
from winrm.protocol import Protocol
File "/usr/lib/python3/dist-packages/winrm/protocol.py", line 11, in
from winrm.transport import Transport
File "/usr/lib/python3/dist-packages/winrm/transport.py", line 18, in
from distutils.util import strtobool
ModuleNotFoundError: No module named 'distutils.util'
The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.
Helmut
Bug#896423: python-bcolz: bcolz fails to import
Package: python-bcolz
Version: 1.2.0+ds1-1
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python-bcolz importing the module bcolz
into a python interpreter fails with the following error:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python2.7/dist-packages/bcolz/__init__.py", line 21, in
from pkg_resources import parse_version
ImportError: No module named pkg_resources
The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.
Helmut
Bug#896412: python-napalm-eos: napalm_eos fails to import
Package: python-napalm-eos
Version: 0.6.1-1
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python-napalm-eos importing the module napalm_eos
into a python interpreter fails with the following error:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python2.7/dist-packages/napalm_eos/__init__.py", line 16, in
from napalm_eos.eos import EOSDriver
File "/usr/lib/python2.7/dist-packages/napalm_eos/eos.py", line 39, in
import napalm_base.helpers
File "/usr/lib/python2.7/dist-packages/napalm_base/__init__.py", line 25, in
import pkg_resources
ImportError: No module named pkg_resources
The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.
Helmut
Bug#896415: python-fiat: FIAT fails to import
Package: python-fiat
Version: 2017.2.0.0-2
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python-fiat importing the module FIAT
into a python interpreter fails with the following error:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python2.7/dist-packages/FIAT/__init__.py", line 7, in
import pkg_resources
ImportError: No module named pkg_resources
The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.
Helmut
Bug#896410: python-flask-limiter: flask_limiter fails to import
Package: python-flask-limiter
Version: 0.9.3-1
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python-flask-limiter importing the module flask_limiter
into a python interpreter fails with the following error:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python2.7/dist-packages/flask_limiter/__init__.py", line 8, in
from .errors import RateLimitExceeded
File "/usr/lib/python2.7/dist-packages/flask_limiter/errors.py", line 6, in
from pkg_resources import get_distribution
ImportError: No module named pkg_resources
The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.
Helmut
Bug#896429: [Python-modules-team] Bug#896429: python3-django-tables2: django_tables2 fails to import
Control: severity 896234 normal Control: severity 896242 normal Control: severity 896272 normal Control: severity 896306 normal Control: severity 896307 normal Control: severity 896328 normal Control: severity 896378 normal Control: severity 896396 normal Control: severity 896429 normal On Sat, Apr 21, 2018 at 09:47:59AM +1000, Brian May wrote: > Helmut Grohne <hel...@subdivi.de> writes: > > > django.core.exceptions.ImproperlyConfigured: Requested setting > > DEFAULT_INDEX_TABLESPACE, but settings are not configured. You must > > either define the environment variable DJANGO_SETTINGS_MODULE or call > > settings.configure() before accessing settings. > > I believe this bug report, and several others you filled recently that > contain this same text are false. I went passed the bug list to a few others for review and posted the full list to d-devel (including all tracebacks). Nobody spoke up and Chris Lamb vaguely said that the django ones looked legit to him. I have lowered the severity of the relevant bugs (matching "ImproperlyConfigured") to prevent issues with testing migration. > Like it or not, it is just not possible to import Django libraries > without providing a valid django settings file. This is not a sign that > something is broken. I wonder whether we can draw anything useful from these bugs before closing them. For one thing, you cannot use autopkgtest-pkg-python on these modules as is. Then having them not importable means that e.g, pydoc. That's unfortunate. Often times, modules with non-trivial impact on their environment do not do so at import time, but provide something like an install function such that the user makes a conscious choice. An example would be gbulb.install(). So yeah, for django this may make sense, but this behaviour is still unfortunate from a qa pov. I'd like to hear your opinion on this matter. After the dust has settled, I can follow up on d-devel with a summary that suggests filtering this particular django exception. Helmut
Bug#896379: python-avc: avc fails to import
Control: severity -1 normal On Sat, Apr 21, 2018 at 01:57:22AM +0200, Fabrizio Pollastri wrote: > Since python-avc 0.8.3-1.1 supports different widget toolkits and > the user is normally interested to only one toolkit among these, I > preferred to set them as "suggested" (the list follows) and not as > dependencies. If there is a better way to define this, any help is > appreciated (I am not an expert Debian packager). Since the behaviour is intentional, I am lowering the severity of the bug report. Still, I think the behaviour is improvable. Since python-avc really doesn't work at all without any toolkit, having a dependency seems useful to me. For instance, you could put all the suggested toolkits in as alternatives of a single dependency: Suggests: a, b, c, d Depends: a | b | c | d Even after doing so, the module will fail to import though. That has more implications to be considered. For one thing, you cannot use autopkgtest-pkg-python. Then using pydoc fails. This is both unfortunate. An alternative would be to select the toolkit using a function to be called on the imported module. Examples of other libraries where you need to call something before you can use anything are apt_pkg.init() and gbulb.install(). Not sure whether that is "better", but it is something to consider. The other question would be how to exempt python-avc from such tests in order to avoid future bug reports of this kind. Adding it to a whitelist is certainly possible, but also fragile. Helmut
Bug#896198: python3-slip-dbus: slip.dbus fails to import
Control: severity -1 normal Control: tags -1 = upstream On Sat, Apr 21, 2018 at 08:36:58AM +0200, Michael Biebl wrote: > Afaiu, the idea behind this wrapper is, that it's up to the actual > application to decide which implementation it wants, i.e. glib > (python-gobject-2) or the gi based Glib (python3-gi + gir1.2-glib-2.0) , > and the application should declare the proper dependency. Since this is a concious upstream choice, I am lowering severity. It still seems like a bad idea to me, because the behaviour of the module depends on what happens to be installed. If the choice is up to the developer, a developer should be able to encode her choice into the source. I see tow major techniques to avoid this issue: * Having two (sub)modules for each way of integration. * Having some kind of setup/install function that takes care of setting up the integration. (See e.g. apt_pkg.init() or gbulb.install()) Implementing either of these would be considered an API break, so fixing this certainly requires upstream involvement. > If I add a dependency to python3-slip-dbus (assuming that would be the > correct package and not python3-slip), I wouldn't know if I should add > python-gobject-2 > or > python3-gi, gir1.2-glib-2.0 > Both feels wrong somehow. You could use a dependency alternative. Of course that also means encoding a default choice, but a user would always get a working package. I do wonder though why you list python-gobject-2 here as it is a Python 2 module. That doesn't seem to fit into the picture of a python3 package at all and there is no python-slip-dbus that could be relevant. Helmut
Bug#896303: [Pkg-utopia-maintainers] Bug#896303: python3-blockdev: gi.overrides.BlockDev fails to import
Control: tags -1 - moreinfo Control: severity -1 normal On Sat, Apr 21, 2018 at 08:41:26AM +0200, Michael Biebl wrote: > gi overrides are not supposed to be imported directly. > Those overrides are in effect if the GObject Introspection machinery is > in use, in which case the necessary python packages are already installed. Still it seems that this package is not useful without python3-gi. Thus a dependency seems warranted. It also means that you cannot use pydoc and other tooling. I think adding the dependency is a reasonable compromise. Still lowering severity is a reasonable thing to do as basically everyone will pull python3-gi by other means. This issue has little chance of affecting users practically. Helmut
Bug#896197: python-formalchemy: formalchemy fails to import
On Sat, Apr 21, 2018 at 04:01:46PM +0800, Shell Xu wrote: > I don't use python-formalchemy for years, and even requested for adoption > for years. But I guess I known how this is coming. Thank you for replying anyway. > According to this repo, the latest change is 1.5.3, been committed 3 years > ago. There are no visible activity (commits, response of issues, renew the > domain of project, new post in maillist, ...) after that. This issue > (#896197) has been fixed in the latest version (1.5.3), but I suggest stop > maintaining and remove it directly. The correct course of action for that is sending the following to control@bugs.d.o: retitle 896197 RM: python-formalchemy -- ROM; dead upstream severity 896197 normal reassign 896197 ftp.debian.org python-formalchemy already has no reverse dependencies, so removing it doesn't kick anything else. Helmut
Bug#896313: python-pymediainfo: pymediainfo fails to import
On Sat, Apr 21, 2018 at 08:05:53PM -0400, Antoine Beaupre wrote: > So I don't quite understand how this can possibly happen: setuptools is > required to build the package in the first place, why can't dh-python > figure that out on its own? Thank you for your attention to detail. I admit having little clue about the situation around pkg-resources. I still think that it is a bug to miss a dependency on it, but your case is very convincing for shifting the responsibility to insert it to dh-python or something else. Adding pkg-resources to depends should not be the responsibility of individual packages as that'd be fragile. > It's a little strange to expect upstream to add a install_requires on > setuptools when it's part of the install process itself, ie. if you run > `setup.py install` (which is how dh-python builds the package), isn't it > reasonable from upstream to assume that setuptools will be installed at > that stage? Yeah, having upstream take care of Debian's idiosyncrasies doesn't make much sense. > What should be done here? The issue has come up on debian-python@l.d.o as well: https://lists.debian.org/debian-python/2018/04/msg00067.html I suggest following up there. I'm fairly surprised that this hasn't come up any earlier. Helmut
Bug#895726: python3-gbulb: ModuleNotFoundError: No module named 'gi'
Package: python3-gbulb Version: 0.5.3-2 Severity: serious Justification: missing dependency After installing python3-gbulb, I tried importing it into a python interpreter: | $ python3 | Python 3.6.5 (default, Apr 1 2018, 05:46:30) | [GCC 7.3.0] on linux | Type "help", "copyright", "credits" or "license" for more information. | >>> import gbulb | Traceback (most recent call last): | File "", line 1, in | File "/usr/lib/python3/dist-packages/gbulb/__init__.py", line 1, in | from .glib_events import * | File "/usr/lib/python3/dist-packages/gbulb/glib_events.py", line 8, in | from gi.repository import GLib, Gio | ModuleNotFoundError: No module named 'gi' | >>> | $ It looks like python3-gbulb is missing a dependency on python3-gi. After installing that package, the ModuleNotFoundError goes away. Such dependencies are usually inserted via substitution variables and originate from setup.py. Indeed, gbulb's setup.py lacks any requires assignments. Likely, this bug should be fixed upstream rather than simply adding the dependency in debian/control. Helmut
Bug#895742: python-acidobasic should be named python3-acidobasic
Package: python-acidobasic Version: 2.7-4 Severity: serious Justification: violates python policy 3.3 The package python-acidobasic is wrongly named. It contains a Python 3.x module. Python 2.x packages should carry a python- prefix while Python 3.x packages should carry a python3- prefix. Please rename the package to python3-acidobasic. Helmut
Bug#894295: ca-certificates fails to install: Execution of /usr/bin/c_rehash aborted due to compilation errors
Package: ca-certificates Version: 20170717 Severity: grave Justification: fails to install User: helm...@debian.org Usertags: rebootstrap In a fresh sid amd64 chroot: # apt-get install ca-certificates Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libssl1.1 openssl The following NEW packages will be installed: ca-certificates libssl1.1 openssl 0 upgraded, 3 newly installed, 0 to remove and 22 not upgraded. Need to get 2274 kB of archives. After this operation, 5394 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://ftp.stw-bonn.de/debian sid/main amd64 libssl1.1 amd64 1.1.0h-1 [1352 kB] Get:2 http://ftp.stw-bonn.de/debian sid/main amd64 openssl amd64 1.1.0h-1 [744 kB] Get:3 http://ftp.stw-bonn.de/debian sid/main amd64 ca-certificates all 20170717 [178 kB] Fetched 2274 kB in 2s (1181 kB/s) debconf: delaying package configuration, since apt-utils is not installed Selecting previously unselected package libssl1.1:amd64. (Reading database ... 10089 files and directories currently installed.) Preparing to unpack .../libssl1.1_1.1.0h-1_amd64.deb ... Unpacking libssl1.1:amd64 (1.1.0h-1) ... Selecting previously unselected package openssl. Preparing to unpack .../openssl_1.1.0h-1_amd64.deb ... Unpacking openssl (1.1.0h-1) ... Selecting previously unselected package ca-certificates. Preparing to unpack .../ca-certificates_20170717_all.deb ... Unpacking ca-certificates (20170717) ... Processing triggers for libc-bin (2.27-2) ... Setting up libssl1.1:amd64 (1.1.0h-1) ... Setting up openssl (1.1.0h-1) ... Setting up ca-certificates (20170717) ... Updating certificates in /etc/ssl/certs... Unknown regexp modifier "/b" at /usr/bin/c_rehash line 15, at end of line Unknown regexp modifier "/W" at /usr/bin/c_rehash line 26, at end of line Unknown regexp modifier "/3" at /usr/bin/c_rehash line 26, at end of line Unknown regexp modifier "/2" at /usr/bin/c_rehash line 26, at end of line No such class installdir at /usr/bin/c_rehash line 58, near "Prefix our installdir" (Might be a runaway multi-line // string starting on line 26) syntax error at /usr/bin/c_rehash line 58, near "Prefix our installdir" Can't redeclare "my" in "my" at /usr/bin/c_rehash line 63, near "my" Execution of /usr/bin/c_rehash aborted due to compilation errors. dpkg: error processing package ca-certificates (--configure): installed ca-certificates package post-installation script subprocess returned error exit status 255 Processing triggers for libc-bin (2.27-2) ... Errors were encountered while processing: ca-certificates E: Sub-process /usr/bin/dpkg returned an error code (1) # Helmut
Bug#893426: systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN
Package: systemd Version: 238-2 Severity: serious User: helm...@debian.org Usertags: rebootstrap systemd fails to build from source on amd64. Here is a tail of the build log. | FAILED: journal-core@sta/src_journal_journald-context.c.o | cc -Ijournal-core@sta -I. -I.. -I../ -Isrc/libsystemd-network -I../src/libsystemd-network -I../src/libsystemd/sd-network -I../src/libsystemd/sd-netlink -I../src/libsystemd/sd-id128 -I../src/libsystemd/sd-hwdb -I../src/libsystemd/sd-device -I../src/libsystemd/sd-bus -Isrc/core -I../src/core -Isrc/libudev -I../src/libudev -Isrc/udev -I../src/udev -Isrc/login -I../src/login -Isrc/timesync -I../src/timesync -Isrc/resolve -I../src/resolve -Isrc/journal -I../src/journal -Isrc/systemd -I../src/systemd -Isrc/shared -I../src/shared -Isrc/basic -I../src/basic -flto -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -std=gnu99 -Wextra -Werror=undef -Wlogical-op -Wmissing-include-dirs -Wold-style-definition -Wpointer-arith -Winit-self -Wdeclaration-after-statement -Wfloat-equal -Wsuggest-attribute=noreturn -Werror=missing-prototypes -Werror=implicit-function-declaration -Werror=missing-declarations -Werror=return-type -Werror=incompatible-pointer-types -Werror=format=2 -Wstrict-prototypes -Wredundant-decls -Wmissing-noreturn -Wimplicit-fallthrough=5 -Wshadow -Wendif-labels -Wstrict-aliasing=2 -Wwrite-strings -Werror=overflow -Wdate-time -Wnested-externs -ffast-math -fno-common -fdiagnostics-show-option -fno-strict-aliasing -fvisibility=hidden -fstack-protector -fstack-protector-strong --param=ssp-buffer-size=4 -fPIE -Wno-unused-parameter -Wno-missing-field-initializers -Wno-unused-result -Wno-format-signedness -Wno-error=nonnull -Werror=shadow -ffunction-sections -fdata-sections -include config.h -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -MD -MQ 'journal-core@sta/src_journal_journald-context.c.o' -MF 'journal-core@sta/src_journal_journald-context.c.o.d' -o 'journal-core@sta/src_journal_journald-context.c.o' -c ../src/journal/journald-context.c | In file included from ../src/basic/alloc-util.h:28:0, | from ../src/journal/journald-context.c:25: | ../src/basic/macro.h:423:18: error: expected ‘)’ before ‘__attribute__’ | #define noreturn __attribute__((noreturn)) | ^ | In file included from /usr/include/gcrypt.h:30:0, | from ../src/journal/journal-file.h:26, | from ../src/journal/journald-server.h:31, | from ../src/journal/journald-context.h:30, | from ../src/journal/journald-context.c:33: | /usr/include/x86_64-linux-gnu/gpg-error.h:1545:46: error: expected ‘,’ or ‘;’ before ‘)’ token | void gpgrt_log_bug (const char *fmt, ...)GPGRT_ATTR_NR_PRINTF(1,2); | ^ | In file included from ../src/basic/alloc-util.h:28:0, | from ../src/journal/journald-context.c:25: | ../src/basic/macro.h:423:18: error: expected ‘)’ before ‘__attribute__’ | #define noreturn __attribute__((noreturn)) | ^ | In file included from /usr/include/gcrypt.h:30:0, | from ../src/journal/journal-file.h:26, | from ../src/journal/journald-server.h:31, | from ../src/journal/journald-context.h:30, | from ../src/journal/journald-context.c:33: | /usr/include/x86_64-linux-gnu/gpg-error.h:1546:46: error: expected ‘,’ or ‘;’ before ‘)’ token | void gpgrt_log_fatal (const char *fmt, ...) GPGRT_ATTR_NR_PRINTF(1,2); | ^ | In file included from ../src/basic/alloc-util.h:28:0, | from ../src/journal/journald-context.c:25: | ../src/basic/macro.h:423:18: error: expected ‘)’ before ‘__attribute__’ | #define noreturn __attribute__((noreturn)) | ^ | In file included from /usr/include/gcrypt.h:30:0, | from ../src/journal/journal-file.h:26, | from ../src/journal/journald-server.h:31, | from ../src/journal/journald-context.h:30, | from ../src/journal/journald-context.c:33: | /usr/include/x86_64-linux-gnu/gpg-error.h:1558:43: error: expected ‘,’ or ‘;’ before ‘)’ token | const char *func) GPGRT_ATTR_NORETURN; |^ | [231/1523] /usr/bin/python3 /usr/bin/meson --internal exe /<>/build-deb/meson-private/meson_exe_awk_ec289b1578d245bbf1d8589a5ea437fc6525ccd3.dat | ninja: build stopped: subcommand failed. | dh_auto_build: cd build-deb && LC_ALL=C.UTF-8 ninja -j8 -v returned exit code 1 | make[1]: *** [debian/rules:161: override_dh_auto_build] Error 1 | make[1]: Leaving directory '/<>' | make: *** [debian/rules:294: binary-arch] Error 2 | dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 This issue might be related to the
Bug#893513: libayatana-indicator FTBFS: error: assignment from incompatible pointer type
Source: libayatana-indicator Version: 0.6.1-1 Severity: serious User: helm...@debian.org Usertags: rebootstrap After failing to cross build libayatana-indicator, I tried to build it natively, but it fails the same way: | /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../../libayatana-indicator -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -I/usr/include/libayatana-ido3-0.4 -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -DG_LOG_DOMAIN=\"libayatana-indicator\" -Wall -Werror -Wno-error=deprecated-declarations -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o libayatana_indicator3_la-indicator-ng.lo `test -f 'indicator-ng.c' || echo '../../../libayatana-indicator/'`indicator-ng.c | libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../../libayatana-indicator -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -I/usr/include/libayatana-ido3-0.4 -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -DG_LOG_DOMAIN=\"libayatana-indicator\" -Wall -Werror -Wno-error=deprecated-declarations -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c ../../../libayatana-indicator/indicator-ng.c -fPIC -DPIC -o .libs/libayatana_indicator3_la-indicator-ng.o | ../../../libayatana-indicator/indicator-ng.c: In function 'indicator_ng_init': | ../../../libayatana-indicator/indicator-ng.c:690:21: error: assignment from incompatible pointer type [-Werror=incompatible-pointer-types] |self->entry.label = g_object_ref_sink (gtk_label_new (NULL)); | ^ | ../../../libayatana-indicator/indicator-ng.c:691:21: error: assignment from incompatible pointer type [-Werror=incompatible-pointer-types] |self->entry.image = g_object_ref_sink (gtk_image_new ()); | ^ | ../../../libayatana-indicator/indicator-ng.c:693:20: error: assignment from incompatible pointer type [-Werror=incompatible-pointer-types] |self->entry.menu = g_object_ref_sink (gtk_menu_new ()); | ^ | cc1: all warnings being treated as errors | make[5]: *** [Makefile:770: libayatana_indicator3_la-indicator-ng.lo] Error 1 | make[5]: Leaving directory '/<>/builddir/gtk3/libayatana-indicator' | make[4]: *** [Makefile:520: all] Error 2 | make[4]: Leaving directory '/<>/builddir/gtk3/libayatana-indicator' | make[3]: *** [Makefile:439: all-recursive] Error 1 | make[3]: Leaving directory '/<>/builddir/gtk3' | make[2]: *** [Makefile:370: all] Error 2 | make[2]: Leaving directory '/<>/builddir/gtk3' | dh_auto_build: cd builddir/gtk3 && make -j1 returned exit code 2 | make[1]: *** [debian/rules:33: dobuild-gtk3] Error 2 | make[1]: Leaving directory '/<>' | make: *** [debian/rules:20: build-arch] Error 2 | dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2 Helmut
Bug#893736: glib2.0 FTBFS: ModuleNotFoundError: No module named 'distutils'
Source: glib2.0 Version: 2.56.0-2 Severity: serious User: helm...@debian.org Usertags: rebootstrap sbuild -d sid glib2.0 ends with: | Making all in gio | make[4]: Entering directory '/<>/debian/build/deb/gio' | UNINSTALLED_GLIB_SRCDIR=../../../.. \ | UNINSTALLED_GLIB_BUILDDIR=.. \ | /usr/bin/python3 ../../../../gio/gdbus-2.0/codegen/gdbus-codegen.in \ | --interface-prefix org. \ | --generate-c-code gdbus-daemon-generated \ | --c-namespace _G \ | ../../../../gio/dbus-daemon.xml \ | | Traceback (most recent call last): | File "../../../../gio/gdbus-2.0/codegen/gdbus-codegen.in", line 53, in | from codegen import codegen_main | File "/<>/gio/gdbus-2.0/codegen/codegen_main.py", line 29, in | from . import dbustypes | File "/<>/gio/gdbus-2.0/codegen/dbustypes.py", line 22, in | from . import utils | File "/<>/gio/gdbus-2.0/codegen/utils.py", line 22, in | import distutils.version | ModuleNotFoundError: No module named 'distutils' | make[4]: *** [Makefile:5019: gdbus-daemon-generated.c] Error 1 | make[4]: Leaving directory '/<>/debian/build/deb/gio' | make[4]: *** Waiting for unfinished jobs | make[4]: Entering directory '/<>/debian/build/deb/gio' | UNINSTALLED_GLIB_SRCDIR=../../../.. \ | UNINSTALLED_GLIB_BUILDDIR=.. \ | /usr/bin/python3 ../../../../gio/gdbus-2.0/codegen/gdbus-codegen.in \ | --interface-prefix org. \ | --generate-c-code gdbus-daemon-generated \ | --c-namespace _G \ | ../../../../gio/dbus-daemon.xml \ | | Traceback (most recent call last): | File "../../../../gio/gdbus-2.0/codegen/gdbus-codegen.in", line 53, in | from codegen import codegen_main | File "/<>/gio/gdbus-2.0/codegen/codegen_main.py", line 29, in | from . import dbustypes | File "/<>/gio/gdbus-2.0/codegen/dbustypes.py", line 22, in | from . import utils | File "/<>/gio/gdbus-2.0/codegen/utils.py", line 22, in | import distutils.version | ModuleNotFoundError: No module named 'distutils' | make[4]: *** [Makefile:5019: gdbus-daemon-generated.h] Error 1 | make[4]: Leaving directory '/<>/debian/build/deb/gio' | make[3]: *** [Makefile:1279: all-recursive] Error 1 | make[2]: *** [Makefile:900: all] Error 2 | dh_auto_build: cd debian/build/deb && make -j8 -O returned exit code 2 | make[1]: *** [debian/rules:137: override_dh_auto_build] Error 25 | make[1]: Leaving directory '/<>' | make: *** [debian/rules:24: binary-arch] Error 2 | dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 Possibly some dependency is missing? I guess this is connected to the python3.6/3.6.5~rc1-2 upload. Helmut
Bug#893802: diffoscope: missing Depends: python3-distutils
Package: diffoscope Version: 91 Severity: serious User: helm...@debian.org Usertags: rebootstrap In a fresh sid debootstrap, after apt-get install --no-install-recommends diffoscope, you get: $ diffoscope --help Traceback (most recent call last): File "/usr/bin/diffoscope", line 33, in from diffoscope.main import main File "/usr/lib/python3/dist-packages/diffoscope/main.py", line 32, in from .tools import tool_prepend_prefix, tool_required, OS_NAMES, get_current_os File "/usr/lib/python3/dist-packages/diffoscope/tools.py", line 29, in from distutils.spawn import find_executable ModuleNotFoundError: No module named 'distutils' $ This is due to python3.6/3.6.5~rc1-2 having dropped its dependency on python3-distutils. I guess we need to add disutils to install_requires in setup.py to fix this issue. Helmut
Bug#893538: kbibtex FTBFS: delegate-failed rsvg-convert
Source: kbibtex Version: 0.8~20170819git31a77b27e8e83836e-3 Severity: serious User: helm...@debian.org Usertags: rebootstrap I was trying to cross build kbibtex and wondered why it failed, but to my amazement, the failure simply is a native FTBFS. Hope this helps in diagnosing: | # rebuild icons | rm -rf debian/tmp/usr/share/icons | # build icons cache (build for each arch in order to get more testing) | set -e; for SIZE in 8x8 16x16 22x22 24x24 32x32 36x36 42x42 48x48 64x64 72x72 96x96 128x128 192x192 256x256; do \ | mkdir -p debian/tmp/usr/share/icons/hicolor/$SIZE/apps/ ;\ | echo "Make icons for size $SIZE..."; \ | convert icons/kbibtex.svg \ |-background none -define filter:blur=0.75 -filter Gaussian -resize $SIZE \ |-gravity center -extent $SIZE \ |+set date:create +set date:modify -define png:exclude-chunk=time \ |debian/tmp/usr/share/icons/hicolor/$SIZE/apps/kbibtex.png; \ | echo "Done"; \ | done | Make icons for size 8x8... | convert-im6.q16: delegate failed `'rsvg-convert' -o '%o' '%i'' @ error/delegate.c/InvokeDelegate/1919. | convert-im6.q16: unable to open file `/tmp/magick-29767lUAn6InfQnK3': No such file or directory @ error/constitute.c/ReadImage/544. | convert-im6.q16: no images defined `debian/tmp/usr/share/icons/hicolor/8x8/apps/kbibtex.png' @ error/convert.c/ConvertImageCommand/3258. | make[1]: *** [debian/rules:42: override_dh_auto_install] Error 1 | make[1]: Leaving directory '/<>' | make: *** [debian/rules:26: binary-arch] Error 2 | dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned exit status 2 Helmut
Bug#893898: libprelude FTBFS: missing Build-Depends: python3-distutils
Source: libprelude Version: 4.1.0-4 Severity: serious User: helm...@debian.org Usertags: rebootstrap libprelude fails to build from source: | make[6]: Leaving directory '/<>/bindings/perl' | Making all in docs | Making all in api | make[5]: Nothing to be done for 'all'. | Making all in manpages | make[5]: Nothing to be done for 'all'. | make[5]: Nothing to be done for 'all-am'. | Making all in tests | make[4]: Nothing to be done for 'all'. | cd bindings/python && python2.7 setup.py build | running build | running build_py | running build_ext | cd bindings/python && python3.6 setup.py build | Traceback (most recent call last): | File "setup.py", line 26, in | from distutils.sysconfig import get_python_lib | ModuleNotFoundError: No module named 'distutils.sysconfig' | make[1]: *** [debian/rules:43: build-python3.6] Error 1 | make[1]: Leaving directory '/<>' | make: *** [debian/rules:61: build-arch] Error 2 | dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2 Likely it needs to add python3-distutils to Build-Depends after python3.6 dropped it from Depends. Also please rebuild libprelude against a version of gem2deb that fixes #892131. Helmut
Bug#893888: ldns FTBFS: missing dependency on python3-distutils
Source: ldns Version: 1.7.0-3 Severity: serious User: helm...@debian.org Usertags: rebootstrap ldns fails to build from source. Here is the relevant part from the build log: | checking for python3.6... /usr/bin/python3.6 | checking for a version of Python >= '2.1.0'... yes | checking for a version of Python >= '2.4.0'... yes | checking for the distutils Python package... yes | checking for Python include path... Traceback (most recent call last): | File "", line 1, in | ModuleNotFoundError: No module named 'distutils.sysconfig' | Traceback (most recent call last): | File "", line 1, in | ModuleNotFoundError: No module named 'distutils.sysconfig' | | checking for Python library path... Traceback (most recent call last): | File "", line 4, in | ModuleNotFoundError: No module named 'distutils.sysconfig' | Traceback (most recent call last): | File "", line 3, in | ModuleNotFoundError: No module named 'distutils.sysconfig' | Traceback (most recent call last): | File "", line 2, in | ModuleNotFoundError: No module named 'distutils.sysconfig' | Traceback (most recent call last): | File "", line 1, in | ModuleNotFoundError: No module named 'distutils.sysconfig' | -L -lpython3.6 | checking for Python site-packages path... Traceback (most recent call last): | File "", line 1, in | ModuleNotFoundError: No module named 'distutils.sysconfig' | | checking python extra libraries... Traceback (most recent call last): | File "", line 1, in | ModuleNotFoundError: No module named 'distutils.sysconfig' | | checking python extra linking flags... Traceback (most recent call last): | File "", line 1, in | ModuleNotFoundError: No module named 'distutils.sysconfig' | | checking consistency of all components of python development environment... no | configure: error: in `/<>/build/python-3.6': | configure: error: | Could not link test program to Python. Maybe the main Python library has been | installed in some non-standard library path. If so, pass it to configure, | via the LDFLAGS environment variable. | Example: ./configure LDFLAGS="-L/usr/non-standard-path/python/lib" | |ERROR! |You probably have to install the development version of the Python package |for your distribution. The exact name of this package varies among them. | | | See `config.log' for more details | cd build/python-3.6 && tail -v -n \+0 config.log | ==> config.log <== Likely you need to add python3-distutils to Build-Depends after python3.6 dropped that dependency. Helmut
Bug#911177: dlm: does not trap errors from make
Source: dlm Version: 4.0.7-2 Severity: serious Justification: policy 4.6 Tags: upstream The upstream Makefile runs submakes in a for loop without any error trapping. Thus it continues building even in the presence of failures. Doing so violates the Debian policy section 4.6. The recommended solution is adding "set -e". Helmut
Bug#911406: jsonm FTBFS: dh_installdocs: Cannot find (any matches for) "README" (tried in .)
Source: jsonm Version: 1.0.1-1 Severity: serious Tags: ftbfs jsonm fails to build from source in sbuild on unstable/amd64. A build log ends with: |debian/rules override_dh_auto_install | make[1]: Entering directory '/<>' | mkdir -p '/<>/debian/tmp//usr/lib/ocaml/jsonm' | cp _build/src/jsonm.cmi _build/src/jsonm.cma _build/src/jsonm.a _build/src/jsonm.cmx _build/src/jsonm.cmxa _build/src/jsonm.cmxs pkg/META src/jsonm.mli '/<>/debian/tmp//usr/lib/ocaml/jsonm' | make[1]: Leaving directory '/<>' |debian/rules override_dh_install | make[1]: Entering directory '/<>' | dh_install --fail-missing | dh_install: Compatibility levels before 9 are deprecated (level 8 in use) | dh_install: Please use dh_missing --list-missing/--fail-missing instead | dh_install: This feature will be removed in compat 12. | make[1]: Leaving directory '/<>' |dh_ocamldoc | Warning: Element Pervasives.float_of_string not found | Warning: Element Sys.max_string_length not found | Warning: Element Pervasives.nan not found | Warning: Element Pervasives.infinity not found | Warning: Element Pervasives.neg_infinity not found |dh_installdocs | dh_installdocs: Compatibility levels before 9 are deprecated (level 8 in use) | dh_installdocs: Cannot find (any matches for) "README" (tried in .) | | make: *** [debian/rules:21: binary] Error 2 | dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2 Helmut
Bug#911405: gnocchi FTBFS: error in setup.cfg: command 'build_py' has no such option 'pre_hook.build_config'
Source: gnocchi Version: 4.2.0-5 Severity: serious Tags: ftbfs gnocchi fails to build from source in sbuild on unstable/amd64. A build log ends with: |debian/rules override_dh_install | make[1]: Entering directory '/<>' | pyversions: missing X(S)-Python-Version in control file, fall back to debian/pyversions | pyversions: missing debian/pyversions file, fall back to supported versions | py3versions: no X-Python3-Version in control file, using supported versions | set -e ; for pyvers in 3.7 3.6; do \ | python$pyvers setup.py install --install-layout=deb --root /<>/debian/tmp; \ | done | running install | [pbr] Generating AUTHORS | [pbr] AUTHORS complete (0.0s) | running build | running build_py | error: error in setup.cfg: command 'build_py' has no such option 'pre_hook.build_config' | make[1]: *** [debian/rules:35: override_dh_install] Error 1 | make[1]: Leaving directory '/<>' | make: *** [debian/rules:9: binary] Error 2 | dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2 Helmut
Bug#911554: opencascade FTBFS: symbol errors
Source: opencascade Version: 7.3.0+dfsg1-3 Severity: serious Tags: ftbfs opencascade fails to build from source on amd64 with symbol error. The output is too long to include in a mail. reproducible builds have a log though: https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/opencascade_7.3.0+dfsg1-3.rbuild.log.gz A noticeable symbol is: | - _ZN3BVH11RadixSorter4SortE23NCollection_StlIteratorISt26random_access_iterator_tagN18NCollection_Array1ISt4pairIiiEE8IteratorES5_Lb0EES8_i@Base 7.3.0 | +#MISSING: 7.3.0+dfsg1-3# _ZN3BVH11RadixSorter4SortE23NCollection_StlIteratorISt26random_access_iterator_tagN18NCollection_Array1ISt4pairIiiEE8IteratorES5_Lb0EES8_i@Base 7.3.0 Maybe you need to mark it as optional as well. Helmut
Bug#911550: lavacli FTBFS: python3.7: not found
Source: lavacli
Version: 0.9.2-1
Severity: serious
Tags: ftbfs patch
lavacli fails to build from source in unstable. Here is a build log:
| dpkg-buildpackage: info: source package lavacli
| dpkg-buildpackage: info: source version 0.9.2-1
| dpkg-buildpackage: info: source distribution unstable
| dpkg-buildpackage: info: source changed by Senthil Kumaran S (stylesen)
| dpkg-source --before-build .
| dpkg-buildpackage: info: host architecture amd64
| fakeroot debian/rules clean
| dh clean --with python3 --buildsystem=pybuild
|debian/rules override_dh_auto_clean
| make[1]: Entering directory '/<>'
| rm -f -r lavacli.egg-info/ build/ dist/ .pybuild/ doc/_build
| find . -name '*.pyc' -exec rm -f -f {} +
| find . -name '*.pyo' -exec rm -f -f {} +
| find . -name '*~' -exec rm rm -f {} +
| make[1]: Leaving directory '/<>'
|dh_clean -O--buildsystem=pybuild
| debian/rules build
| dh build --with python3 --buildsystem=pybuild
|dh_update_autotools_config -O--buildsystem=pybuild
|dh_auto_configure -O--buildsystem=pybuild
| I: pybuild base:217: python3.7 setup.py config
| /bin/sh: 1: python3.7: not found
| E: pybuild pybuild:338: configure: plugin distutils failed with: exit
code=127: python3.7 setup.py config
| dh_auto_configure: pybuild --configure --test-pytest -i python{version} -p
"3.7 3.6" returned exit code 13
| make: *** [debian/rules:14: build] Error 25
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
Please remove the "python3" alternative from "python3 | python3-all" in
Build-Depends.
Helmut
Bug#911552: node-mocha FTBFS: in `require': cannot load such file -- bundler (LoadError)
Source: node-mocha Version: 4.1.0+ds1-2 Severity: serious Tags: ftbfs node-mocha fails to build from source in sbuild on unstable/amd64. A build log ends with: |debian/rules override_dh_installdocs | make[1]: Entering directory '/<>' | jekyll build --source ./docs --destination ./docs/_site --config ./docs/_config.yml --safe --drafts | /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require': cannot load such file -- bundler (LoadError) | from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require' | from /usr/lib/ruby/vendor_ruby/jekyll/plugin_manager.rb:48:in `require_from_bundler' | from /usr/bin/jekyll:9:in `' | make[1]: *** [debian/rules:40: override_dh_installdocs] Error 1 | make[1]: Leaving directory '/<>' | make: *** [debian/rules:8: binary] Error 2 | dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2 Helmut
Bug#911555: ovirt-guest-agent FTBFS: pep8 fails
Source: ovirt-guest-agent Version: 1.0.13.dfsg-2 Severity: serious Tags: ftbfs ovirt-guest-agent fails to build from source in unstable, because pep8 started producing failures: | make check-local | make[3]: Entering directory '/<>' | /usr/bin/pep8 --exclude="ovirt-guest-agent/setup.py" --filename '*.py,*.py.in' \ | ovirt-guest-agent/CredServer.py ovirt-guest-agent/GuestAgentLinux2.py ovirt-guest-agent/GuestAgentWin32.py ovirt-guest-agent/LockActiveSession.py ovirt-guest-agent/OVirtAgentLo | ovirt-guest-agent/GuestAgentWin32.py:116:14: W605 invalid escape sequence '\c' | ovirt-guest-agent/GuestAgentWin32.py:625:18: W605 invalid escape sequence '\c' | ovirt-guest-agent/GuestAgentWin32.py:645:18: W605 invalid escape sequence '\c' | ovirt-guest-agent/GuestAgentWin32.py:672:18: W605 invalid escape sequence '\c' | ovirt-guest-agent/GuestAgentWin32.py:724:18: W605 invalid escape sequence '\C' | ovirt-guest-agent/GuestAgentWin32.py:724:32: W605 invalid escape sequence '\D' | make[3]: *** [Makefile:907: check-local] Error 1 | make[3]: Leaving directory '/<>' | make[2]: *** [Makefile:773: check-am] Error 2 | make[2]: Leaving directory '/<>' | make[1]: *** [Makefile:482: check-recursive] Error 1 | make[1]: Leaving directory '/<>' | dh_auto_test: make -j8 check VERBOSE=1 returned exit code 2 | make: *** [debian/rules:24: build] Error 2 | dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 Helmut
Bug#911154: netkit-ntalk misses the generator for configure
Source: netkit-ntalk Version: 0.17-15 Severity: serious Justification: DFSG #2 User: helm...@debian.org Usertags: rebootstrap The configure file in the netkit-ntalk is generated using confgen from MCONFIG.in. However, the generator is missing. No package in unstable contains said confgen tool. Thus configure cannot be regenerated after fixing a bug. That's a violation of DFSG #2. Helmut
Bug#911686: wtf-peewee FTBFS: AttributeError: 'ModelSelect' object has no attribute 'model_class'
Source: wtf-peewee
Version: 0.2.6+dfsg-2
Severity: serious
Tags: ftbfs
wtf-peewee fails to build from source in unstable for multiple
architectures, e.g. i386:
https://tests.reproducible-builds.org/debian/rbuild/unstable/i386/wtf-peewee_0.2.6+dfsg-2.rbuild.log.gz
| ERROR: test_hidden_field_none (wtfpeewee.tests.WTFPeeweeTestCase)
| --
| Traceback (most recent call last):
| File "/build/1st/wtf-peewee-0.2.6+dfsg/wtfpeewee/tests.py", line 479, in
test_hidden_field_none
| 'blog': '',
| File "/usr/lib/python2.7/dist-packages/wtforms/form.py", line 212, in
__call__
| return type.__call__(cls, *args, **kwargs)
| File "/usr/lib/python2.7/dist-packages/wtforms/form.py", line 272, in
__init__
| super(Form, self).__init__(self._unbound_fields, meta=meta_obj,
prefix=prefix)
| File "/usr/lib/python2.7/dist-packages/wtforms/form.py", line 52, in
__init__
| field = meta.bind_field(self, unbound_field, options)
| File "/usr/lib/python2.7/dist-packages/wtforms/meta.py", line 27, in
bind_field
| return unbound_field.bind(form=form, **options)
| File "/usr/lib/python2.7/dist-packages/wtforms/fields/core.py", line 353,
in bind
| return self.field_class(*self.args, **kw)
| File "/build/1st/wtf-peewee-0.2.6+dfsg/wtfpeewee/fields.py", line 319, in
__init__
| self.model = query.model_class
| AttributeError: 'ModelSelect' object has no attribute 'model_class'
|
| --
| Ran 15 tests in 0.055s
|
| FAILED (errors=7)
| E: pybuild pybuild:338: test: plugin distutils failed with: exit code=2:
python2.7 setup.py test
| dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
| make: *** [debian/rules:5: build] Error 25
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
Helmut
Bug#911689: ubuntu-dev-tools FTBFS: AssertionError: flake8 found issues:
Source: ubuntu-dev-tools
Version: 0.165
Severity: serious
Tags: ftbfs
ubuntu-dev-tools fails to build from source in unstable for multiple
architectures, e.g. amd64:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/ubuntu-dev-tools_0.165.rbuild.log.gz
| ==
| FAIL: test_flake8 (ubuntutools.test.test_flake8.Flake8TestCase)
| Test: Run flake8 on Python source code
| --
| Traceback (most recent call last):
| File "/build/1st/ubuntu-dev-tools-0.165/ubuntutools/test/test_flake8.py",
line 44, in test_flake8
| self.assertFalse(out, "flake8 found issues:\n" + out.decode())
| AssertionError: flake8 found issues:
| ubuntutools/sponsor_patch/bugtask.py:46:11: W605 invalid escape sequence '\('
| ubuntutools/sponsor_patch/bugtask.py:62:50: W605 invalid escape sequence '\('
| ubuntutools/sponsor_patch/bugtask.py:62:58: W605 invalid escape sequence '\)'
| setup.py:14:8: W605 invalid escape sequence '\('
| setup.py:14:14: W605 invalid escape sequence '\)'
|
|
| --
| Ran 81 tests in 86.680s
|
| FAILED (failures=1, skipped=1)
| Test failed:
| The old maintainer was: Ubuntu MOTU Developers
| Resetting as: Ubuntu Developers
| error: Test failed:
| E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1:
python2.7 setup.py test
| dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
| make: *** [debian/rules:6: binary] Error 25
| dpkg-buildpackage: error: debian/rules binary subprocess returned exit status
2
Helmut
Bug#911696: profitbricks-sdk-python FTBFS: flake8 fails
Source: profitbricks-sdk-python Version: 4.1.3-1 Severity: serious Tags: ftbfs profitbricks-sdk-python fails to build from source in unstable: https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/profitbricks-sdk-python_4.1.3-1.rbuild.log.gz |debian/rules override_dh_auto_test | make[1]: Entering directory '/build/1st/profitbricks-sdk-python-4.1.3' | python3 -m flake8 --max-line-length=99 examples profitbricks tests setup.py | profitbricks/client.py:69:12: W605 invalid escape sequence '\d' | make[1]: *** [debian/rules:12: override_dh_auto_test] Error 1 | make[1]: Leaving directory '/build/1st/profitbricks-sdk-python-4.1.3' | make: *** [debian/rules:7: build] Error 2 | dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 Helmut
Bug#911697: at-spi2-core FTBFS: gtkdoc-scangobj fails
Source: at-spi2-core
Version: 2.30.0-2
Severity: serious
Tags: ftbfs
at-spi2-core fails to build from source in unstable for multiple
architectures, e.g. amd64:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/at-spi2-core_2.30.0-2.rbuild.log.gz
| ERROR: 'gtkdoc-scangobj' failed with status 1
| libatspi-scan.c: In function ‘output_signals’:
| : error: ‘dbind’ undeclared (first use in this function)
| /usr/include/glib-2.0/glib/gmessages.h:337:32: note: in expansion of macro
‘G_LOG_DOMAIN’
| #define g_warning(...) g_log (G_LOG_DOMAIN, \
| ^~~~
| libatspi-scan.c:194:5: note: in expansion of macro ‘g_warning’
| g_warning ("Couldn't open output file: %s : %s", signals_filename,
g_strerror(errno));
| ^
| : note: each undeclared identifier is reported only once for
each function it appears in
| /usr/include/glib-2.0/glib/gmessages.h:337:32: note: in expansion of macro
‘G_LOG_DOMAIN’
| #define g_warning(...) g_log (G_LOG_DOMAIN, \
| ^~~~
| libatspi-scan.c:194:5: note: in expansion of macro ‘g_warning’
| g_warning ("Couldn't open output file: %s : %s", signals_filename,
g_strerror(errno));
| ^
| libatspi-scan.c: In function ‘output_object_hierarchy’:
| : error: ‘dbind’ undeclared (first use in this function)
| /usr/include/glib-2.0/glib/gmessages.h:337:32: note: in expansion of macro
‘G_LOG_DOMAIN’
| #define g_warning(...) g_log (G_LOG_DOMAIN, \
| ^~~~
| libatspi-scan.c:462:5: note: in expansion of macro ‘g_warning’
| g_warning ("Couldn't open output file: %s : %s", hierarchy_filename,
g_strerror(errno));
| ^
| libatspi-scan.c: In function ‘output_object_interfaces’:
| : error: ‘dbind’ undeclared (first use in this function)
| /usr/include/glib-2.0/glib/gmessages.h:337:32: note: in expansion of macro
‘G_LOG_DOMAIN’
| #define g_warning(...) g_log (G_LOG_DOMAIN, \
| ^~~~
| libatspi-scan.c:521:5: note: in expansion of macro ‘g_warning’
| g_warning ("Couldn't open output file: %s : %s", interfaces_filename,
g_strerror(errno));
| ^
| libatspi-scan.c: In function ‘output_interface_prerequisites’:
| : error: ‘dbind’ undeclared (first use in this function)
| /usr/include/glib-2.0/glib/gmessages.h:337:32: note: in expansion of macro
‘G_LOG_DOMAIN’
| #define g_warning(...) g_log (G_LOG_DOMAIN, \
| ^~~~
| libatspi-scan.c:571:5: note: in expansion of macro ‘g_warning’
| g_warning ("Couldn't open output file: %s : %s", prerequisites_filename,
g_strerror(errno));
| ^
| libatspi-scan.c: In function ‘output_args’:
| : error: ‘dbind’ undeclared (first use in this function)
| /usr/include/glib-2.0/glib/gmessages.h:337:32: note: in expansion of macro
‘G_LOG_DOMAIN’
| #define g_warning(...) g_log (G_LOG_DOMAIN, \
| ^~~~
| libatspi-scan.c:617:5: note: in expansion of macro ‘g_warning’
| g_warning ("Couldn't open output file: %s : %s", args_filename,
g_strerror(errno));
| ^
| 2018-10-17 23:59:21,266:scangobj.py:execute_command:1196:WARNING:Compiling
scanner failed: 1, command: cc
-I/build/1st/at-spi2-core-2.30.0/obj-x86_64-linux-gnu/.
-I/build/1st/at-spi2-core-2.30.0/. -I/usr/include/dbus-1.0
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -DG_LOG_DOMAIN=dbind -g -O2
-ffile-prefix-map=/build/1st/at-spi2-core-2.30.0=. -fstack-protector-strong
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -c -o
libatspi-scan.o libatspi-scan.c
...
| Running custom install script '/usr/bin/meson --internal gtkdoc
--sourcedir=/build/1st/at-spi2-core-2.30.0
--builddir=/build/1st/at-spi2-core-2.30.0/obj-x86_64-linux-gnu
--subdir=doc/libatspi
--headerdirs=/build/1st/at-spi2-core-2.30.0/atspi@@/build/1st/at-spi2-core-2.30.0/obj-x86_64-linux-gnu/atspi
--mainfile=libatspi-docs.sgml --modulename=libatspi --mode=auto
--scanargs=--rebuild-types
--gobjects-types-file=/build/1st/at-spi2-core-2.30.0/doc/libatspi/libatspi.types
--fixxrefargs=--html-dir=/usr/share/gtk-doc/html@@--extra-dir=/usr/share/gtk-doc/html/glib@@--extra-dir=/usr/share/gtk-doc/html/gobject
--mkdbargs=--sgml-mode@@--output-format=xml --content-files= --cc=cc --ld=cc
--cflags=-I/build/1st/at-spi2-core-2.30.0/obj-x86_64-linux-gnu/.
-I/build/1st/at-spi2-core-2.30.0/. -I/usr/include/dbus-1.0
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -DG_LOG_DOMAIN="dbind" -g -O2
-ffile-prefix-map=/build/1st/at-spi2-core-2.30.0=. -fstack-protector-strong
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2
--ldflags=-L/build/1st/at-spi2-core-2.30.0/obj-x86_64-linux-gnu/atspi
Bug#911688: willow FTBFS: ModuleNotFoundError: No module named 'cv2'
Source: willow
Version: 1.1-3
Severity: serious
Tags: ftbfs
willow fails to build from source in unstable for multiple
architectures, e.g. amd64:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/willow_1.1-3.rbuild.log.gz
| ==
| ERROR: test_has_animation (tests.test_opencv.TestOpenCVOperations)
| --
| Traceback (most recent call last):
| File
"/build/1st/willow-1.1/.pybuild/cpython3_3.7_willow/build/willow/plugins/opencv.py",
line 10, in _cv2
| import cv2
| ModuleNotFoundError: No module named 'cv2'
|
| During handling of the above exception, another exception occurred:
|
| Traceback (most recent call last):
| File
"/build/1st/willow-1.1/.pybuild/cpython3_3.7_willow/build/tests/test_opencv.py",
line 16, in setUp
| colour_image = OpenCVColorImage.from_buffer_rgb(buffer_rgb)
| File
"/build/1st/willow-1.1/.pybuild/cpython3_3.7_willow/build/willow/plugins/opencv.py",
line 58, in from_buffer_rgb
| cv2 = _cv2()
| File
"/build/1st/willow-1.1/.pybuild/cpython3_3.7_willow/build/willow/plugins/opencv.py",
line 12, in _cv2
| from cv import cv2
| ModuleNotFoundError: No module named 'cv'
|
| --
| Ran 96 tests in 2.393s
|
| FAILED (errors=5, expected failures=7)
| E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd
/build/1st/willow-1.1/.pybuild/cpython3_3.7_willow/build; python3.7 -m unittest
discover -v
| dh_auto_test: pybuild --test -i python{version} -p "3.7 3.6" returned exit
code 13
| make: *** [debian/rules:6: build] Error 25
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
Helmut
Bug#911690: vmdb2 FTBFS: tests fail
Source: vmdb2 Version: 0.13.2-1 Severity: serious Tags: ftbfs vmdb2 fails to build from source in unstable for multiple architectures, e.g. amd64: https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/vmdb2_0.13.2-1.rbuild.log.gz |debian/rules override_dh_auto_test | make[1]: Entering directory '/build/1st/vmdb2-0.13.2' | ./check | | | OK | 14 excluded statements | 21 excluded modules | Time: 0.2 s | * Module vmdb.step_list | vmdb/step_list.py:22:0: R0205: Class 'StepRunnerInterface' inherits from object, can be safely removed from bases in python3 (useless-object-inheritance) | vmdb/step_list.py:53:0: R0205: Class 'StepRunnerList' inherits from object, can be safely removed from bases in python3 (useless-object-inheritance) | * Module vmdb.state | vmdb/state.py:19:0: R0205: Class 'State' inherits from object, can be safely removed from bases in python3 (useless-object-inheritance) | * Module vmdb.spec | vmdb/spec.py:40:4: R1705: Unnecessary "elif" after "return" (no-else-return) | | --- | Your code has been rated at 9.94/10 | | make[1]: *** [debian/rules:10: override_dh_auto_test] Error 8 | make[1]: Leaving directory '/build/1st/vmdb2-0.13.2' | make: *** [debian/rules:6: build] Error 2 | dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 Helmut
Bug#911695: golang-github-abh-geoip-dev FTBFS: rm: cannot remove '/<>/debian/golang-github-abh-geoip-dev/usr/share/gocode/src/github.com/abh/geoip/test-db': No such file or directory
Source: golang-github-abh-geoip-dev Version: 0.0~git20150611-3 Severity: serious Tags: ftbfs golang-github-abh-geoip-dev fails to build from source in unstable for multiple architectures, e.g. amd64: https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/golang-github-abh-geoip-dev_0.0~git20150611-3.rbuild.log.gz | fakeroot debian/rules binary | dh binary --buildsystem=golang --with=golang |dh_testroot -O--buildsystem=golang |dh_prep -O--buildsystem=golang |dh_installdirs -O--buildsystem=golang |debian/rules override_dh_auto_install | make[1]: Entering directory '/build/1st/golang-github-abh-geoip-dev-0.0~git20150611' | dh_auto_install -O--buildsystem=golang | cd obj-x86_64-linux-gnu && mkdir -p /build/1st/golang-github-abh-geoip-dev-0.0\~git20150611/debian/golang-github-abh-geoip-dev/usr | cd obj-x86_64-linux-gnu && cp -r bin /build/1st/golang-github-abh-geoip-dev-0.0\~git20150611/debian/golang-github-abh-geoip-dev/usr | # remove the demo binary | rm -r /build/1st/golang-github-abh-geoip-dev-0.0~git20150611/debian/golang-github-abh-geoip-dev/usr/bin | # remove the demo sources | rm -r /build/1st/golang-github-abh-geoip-dev-0.0~git20150611/debian/golang-github-abh-geoip-dev/usr/share/gocode/src/github.com/abh/geoip/ex | # remove the broken test-db symlink | rm /build/1st/golang-github-abh-geoip-dev-0.0~git20150611/debian/golang-github-abh-geoip-dev/usr/share/gocode/src/github.com/abh/geoip/test-db | rm: cannot remove '/build/1st/golang-github-abh-geoip-dev-0.0~git20150611/debian/golang-github-abh-geoip-dev/usr/share/gocode/src/github.com/abh/geoip/test-db': No such file or directory | make[1]: *** [debian/rules:30: override_dh_auto_install] Error 1 | make[1]: Leaving directory '/build/1st/golang-github-abh-geoip-dev-0.0~git20150611' | make: *** [debian/rules:17: binary] Error 2 | dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2 Helmut
Bug#911710: rkward FTBFS: debian/rules has a fi too much
Source: rkward Version: 0.7.0b-1 Severity: serious Tags: ftbfs rkward fails to build from source in unstable since dash fixed #550756. debian/rules has a "fi" too much in the last line and now dash does not like that anymore. | # unfortunately, the r-base-core dependency can not be found by dh_shlibdeps, so we need to get at the version manually | /bin/sh: 10: Syntax error: "fi" unexpected | make[1]: *** [debian/rules:47: override_dh_shlibdeps] Error 2 | make[1]: Leaving directory '/<>' | make: *** [debian/rules:19: binary] Error 2 | dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2 Helmut
Bug#911711: svgwrite FTBFS: tests fail
Source: svgwrite
Version: 1.1.8-2
Severity: serious
Tags: ftbfs
svgwrite fails to build from source in unstable e.g. on amd64:
https://tests.reproducible-builds.org/debian/rbuild/unstable/i386/svgwrite_1.1.8-2.rbuild.log.gz
| ==
| FAIL: test_is_number_optional_number
(tests.test_full11_typechecker.TestFull11TypeChecker)
| --
| Traceback (most recent call last):
| File
"/build/1st/svgwrite-1.1.8/.pybuild/cpython3_3.7_svgwrite/build/tests/test_full11_typechecker.py",
line 177, in test_is_number_optional_number
| self.assertTrue(self.checker.is_number_optional_number(' 1, 2'))
| AssertionError: False is not true
|
| --
| Ran 455 tests in 0.191s
|
| FAILED (failures=1, errors=6)
| E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd
/build/1st/svgwrite-1.1.8/.pybuild/cpython3_3.7_svgwrite/build; python3.7 -m
unittest discover -v
| dh_auto_test: pybuild --test -i python{version} -p "3.7 3.6" returned exit
code 13
| make: *** [debian/rules:9: build] Error 25
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
Helmut
Bug#911712: tigervnc FTBFS: missing Build-Depends: libunwind-dev
Source: tigervnc Version: 1.9.0+dfsg-1 Severity: serious Tags: ftbfs tigervnc passes --enable-libunwind to ./configure, but does not list libunwind-dev in Build-Depends. Consequently it fails to build: | checking for LIBUNWIND... no | configure: error: libunwind requested but not installed. | make: *** [debian/rules:219: obj-x86_64-linux-gnu/unix/xserver/configure.stamp] Error 1 | dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 Helmut
Bug#911713: sdcc FTBFS: tex failure during documentation build
Source: sdcc
Version: 3.7.0+dfsg2-0.1
Severity: serious
Tags: ftbfs
sdcc fails to build from source in unstable.
| LaTeX Warning: Reference `subsec:Search-Paths' on page 32 undefined on input
li
| ne 2261.
|
| [32]
|
| ! LaTeX Error: File `MCS51_named' not found.
|
| See the LaTeX manual or LaTeX Companion for explanation.
| Type H for immediate help.
| ...
|
| l.2283 \includegraphics{MCS51_named}
|
| ?
| ! Emergency stop.
| ...
|
| l.2283 \includegraphics{MCS51_named}
|
| Output written on sdccman.dvi (33 pages, 170988 bytes).
| Transcript written on sdccman.log.
| make[1]: *** [Makefile:67: sdccman.dvi] Error 1
| make[1]: Leaving directory '/<>/doc'
| make: *** [debian/rules:71: build-indep-stamp] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
Supposedly, this was fixed in #909995, but the issue persists.
This time around the traceback looks a little different:
| +Read the file doc/LaTeXConfig.lyx for more information.
| LyX: Done!
| Traceback (most recent call last):
| File "/usr/share/lyx/scripts/convertDefault.py", line 38, in
| output = output.decode()
| AttributeError: 'str' object has no attribute 'decode'
| support/Systemcall.cpp (294): Systemcall: 'python3 -tt
"/usr/share/lyx/scripts/convertDefault.py" svg
"/tmp/lyx_tmpdir.hxwECXKtFDVu/lyx_tmpbuf0/1_build_sdcc-KkmAiE_sdcc-3_7_0+dfsg2_doc_MCS51_named.svg"
eps
"/tmp/lyx_tmpdir.hxwECXKtFDVu/lyx_tmpbuf0/1_build_sdcc-KkmAiE_sdcc-3_7_0+dfsg2_doc_MCS51_named.eps"'
finished with exit code 1
| Error: Cannot convert file
|
| No information for converting svg format files to eps.
| Define a converter in the preferences.
| latex sdccman.tex
Helmut
Bug#911714: serf FTBFS: ssl tests fail
Source: serf Version: 1.3.9-6 Severity: serious Tags: ftbfs serf fails to build from source in unstable e.g. on i386: https://tests.reproducible-builds.org/debian/rbuild/unstable/i386/serf_1.3.9-6.rbuild.log.gz | There were 14 failures: | 1) test_ssl_trust_rootca: test/test_util.c:456: expected <0> but was <120199> | 2) test_ssl_certificate_chain_with_anchor: test/test_util.c:456: expected <0> but was <120199> | 3) test_ssl_certificate_chain_all_from_server: test/test_util.c:456: expected <0> but was <120199> | 4) test_ssl_no_servercert_callback_allok: test/test_util.c:456: expected <0> but was <120170> | 5) test_ssl_large_response: test/test_util.c:456: expected <0> but was <120170> | 6) test_ssl_large_request: test/test_util.c:456: expected <0> but was <120170> | 7) test_ssl_client_certificate: test/test_util.c:456: expected <0> but was <120170> | 8) test_ssl_future_server_cert: test/test_util.c:456: expected <0> but was <120199> | 9) test_setup_ssltunnel: test/test_util.c:456: expected <0> but was <120170> | 10) test_ssltunnel_basic_auth: test/test_context.c:2138: expected <0> but was <120170> | 11) test_ssltunnel_basic_auth_server_has_keepalive_off: test/test_context.c:2138: expected <0> but was <120170> | 12) test_ssltunnel_basic_auth_proxy_has_keepalive_off: test/test_context.c:2138: expected <0> but was <120170> | 13) test_ssltunnel_basic_auth_proxy_close_conn_on_200resp: test/test_context.c:2138: expected <0> but was <120170> | 14) test_ssltunnel_digest_auth: test/test_util.c:456: expected <0> but was <120170> | | !!!FAILURES!!! | Runs: 66 Passes: 52 Fails: 14 | | == Testing test/testcases/deflate.response == | == Testing test/testcases/chunked.response == | == Testing test/testcases/chunked-trailers.response == | == Testing test/testcases/chunked-empty.response == | == Testing test/testcases/simple.response == | == Running the unit tests == | ERROR: test(s) failed in test_all | scons: *** [check] Error 1 | scons: building terminated because of errors. | make[1]: *** [debian/rules:26: override_dh_auto_test-arch] Error 2 | make[1]: Leaving directory '/build/1st/serf-1.3.9' | make: *** [debian/rules:18: binary] Error 2 | dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Helmut
Bug#911715: ros-rosdep FTBFS: flake8 failure
Source: ros-rosdep
Version: 0.12.2-2
Severity: serious
Tags: ftbfs
ros-rosdep fails to build from source in unstable:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/ros-rosdep_0.12.2-2.rbuild.log.gz
| ==
| ERROR: test.test_flake8.test_flake8
| --
| Traceback (most recent call last):
| File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
| self.test(*self.arg)
| File
"/build/1st/ros-rosdep-0.12.2/.pybuild/cpython2_2.7_rosdep2/build/test/test_flake8.py",
line 63, in test_flake8
| 'flake8 reported {report.total_errors} errors'
| AttributeError: 'str' object has no attribute 'format_map'
| >> begin captured stdout << -
|
| 8 W504 line break after binary operator
|
| - >> end captured stdout << --
| >> begin captured logging <<
...
| - >> end captured logging << -
|
| --
| Ran 151 tests in 24.045s
|
| FAILED (errors=1)
| E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd
/build/1st/ros-rosdep-0.12.2/.pybuild/cpython2_2.7_rosdep2/build; python2.7 -m
nose -v test
| dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 returned
exit code 13
| make: *** [debian/rules:7: binary] Error 25
| dpkg-buildpackage: error: debian/rules binary subprocess returned exit status
2
Helmut
Bug#911685: yade FTBFS: ... has no member named 'move_point'; did you mean 'Bare_point'
Source: yade
Version: 2018.02b-4
Severity: serious
Tags: ftbfs
yade fails to build from source in unstable/amd64.
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/yade_2018.02b-4.rbuild.log.gz
| [ 59%] Building CXX object
CMakeFiles/yade.dir/pkg/dem/TesselationWrapper.cpp.o
| /usr/bin/c++ -DBOOST_MATH_DISABLE_FLOAT128=1 -DNDEBUG -DQT_CORE_LIB
-DQT_GUI_LIB -DQT_NO_DEBUG -DQT_OPENGL_LIB -DQT_WIDGETS_LIB -DQT_XML_LIB
-DSUITESPARSE_VERSION_4 -DYADE_ODEINT -DYADE_SPH -DYADE_VTK6 -Dyade_EXPORTS
-I/build/1st/yade-2018.02b/debian/build/yade_autogen/include
-I/build/1st/yade-2018.02b
-I/usr/lib/python2.7/dist-packages/numpy/core/include -I/usr/include/python2.7
-I/usr/include/eigen3 -I/usr/include/vtk-6.3 -I/usr/include/x86_64-linux-gnu
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include
-I/usr/include/suitesparse -I/build/1st/yade-2018.02b/debian/build
-I/build/1st/yade-2018.02b/debian/build/pkg/pfv -isystem
/usr/include/x86_64-linux-gnu/qt5 -isystem
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem
/usr/include/x86_64-linux-gnu/qt5/QtCore -isystem
/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem
/usr/include/x86_64-linux-gnu/qt5/QtXml -isystem
/usr/include/x86_64-linux-gnu/qt5/QtOpenGL -g -O2
-ffile-prefix-map=/build/1st/yade-2018.02b=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -O2
--param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security
-Wall -std=c++11 -DYADE_VTK -DYADE_OPENMP -fopenmp -DYADE_GTS
-DQGLVIEWER_FOUND -DYADE_OPENGL -DYADE_QT5 -DYADE_CGAL -DFLOW_ENGINE
-DTWOPHASEFLOW -DLINSOLV -DFLOW_ENGINE -DYADE_GL2PS -DLBM_ENGINE -fPIC
-ftrack-macro-expansion=0 -save-temps -fstack-protector-strong
-DEIGEN_DONT_VECTORIZE -DEIGEN_DONT_ALIGN
-DEIGEN_DISABLE_UNALIGNED_ARRAY_ASSERT -DCGAL_DISABLE_ROUNDING_MATH_CHECK
-frounding-math -fPIC -std=gnu++11 -o
CMakeFiles/yade.dir/pkg/dem/TesselationWrapper.cpp.o -c
/build/1st/yade-2018.02b/pkg/dem/TesselationWrapper.cpp
| In file included from
/usr/lib/python2.7/dist-packages/numpy/core/include/numpy/ndarraytypes.h:1816,
| from
/usr/lib/python2.7/dist-packages/numpy/core/include/numpy/ndarrayobject.h:18,
| from
/usr/lib/python2.7/dist-packages/numpy/core/include/numpy/arrayobject.h:4,
| from /build/1st/yade-2018.02b/lib/pyutil/numpy_boost.hpp:40,
| from
/build/1st/yade-2018.02b/pkg/dem/TesselationWrapper.cpp:15:
|
/usr/lib/python2.7/dist-packages/numpy/core/include/numpy/npy_1_7_deprecated_api.h:15:2:
warning: #warning "Using deprecated NumPy API, disable it by " "#defining
NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-Wcpp]
| #warning "Using deprecated NumPy API, disable it by " \
| ^~~
| In file included from
/build/1st/yade-2018.02b/lib/triangulation/Tesselation.h:202,
| from
/build/1st/yade-2018.02b/pkg/dem/TesselationWrapper.hpp:15,
| from
/build/1st/yade-2018.02b/pkg/dem/TesselationWrapper.cpp:12:
| /build/1st/yade-2018.02b/lib/triangulation/Tesselation.ipp: In instantiation
of 'CGT::_Tesselation::VertexHandle CGT::_Tesselation::move(CGT::Real,
CGT::Real, CGT::Real, CGT::Real, unsigned int) [with TT =
CGT::TriangulationTypes;
CGT::_Tesselation::VertexHandle =
CGAL::internal::CC_iterator >,
CGAL::Boolean_tag, CGAL::Boolean_tag >,
CGAL::Alpha_shape_cell_base_3 >,
CGAL::Boolean_tag, CGAL::Boolean_tag >, CGAL::Sequential_tag> > >
>, CGAL::Boolean_tag, CGAL::Boolean_tag >, CGAL::Default,
CGAL::Default, CGAL::Default>, false>; CGT::Real = double]':
| /build/1st/yade-2018.02b/pkg/dem/TesselationWrapper.cpp:186:28: required
from here
| /build/1st/yade-2018.02b/lib/triangulation/Tesselation.ipp:78:12: error:
'CGT::_Tesselation >::RTriangulation' {aka 'class
CGAL::Regular_triangulation_3 >,
CGAL::Boolean_tag, CGAL::Boolean_tag >,
CGAL::Alpha_shape_cell_base_3 >,
CGAL::Boolean_tag, CGAL::Boolean_tag >, CGAL::Sequential_tag>,
CGAL::Default>'} has no member named 'move_point'; did you mean 'Bare_point'?
| Vh = Tri->move_point ( vertexHandles[id], Sphere ( Point ( x,y,z ),pow (
rad,2 ) ) );
|~^~
|Bare_point
| In file included from
/usr/lib/python2.7/dist-packages/numpy/core/include/numpy/ndarrayobject.h:27,
| from
/usr/lib/python2.7/dist-packages/numpy/core/include/numpy/arrayobject.h:4,
| from /build/1st/yade-2018.02b/lib/pyutil/numpy_boost.hpp:40,
| from
/build/1st/yade-2018.02b/pkg/dem/TesselationWrapper.cpp:15:
|
/usr/lib/python2.7/dist-packages/numpy/core/include/numpy/__multiarray_api.h:1463:1:
warning: 'int _import_array()' defined but not used [-Wunused-function]
| _import_array(void)
| ^
| make[3]: *** [CMakeFiles/yade.dir/build.make:1496:
CMakeFiles/yade.dir/pkg/dem/TesselationWrapper.cpp.o] Error 1
| make[3]: Leaving directory
Bug#911692: pysmi FTBFS: pysmi.error.PySmiReaderFileNotFoundError: source MIB testC not found
Source: pysmi
Version: 0.2.2-1
Severity: serious
Tags: ftbfs
pysmi fails to build from source in unstable on multiple architectures,
e.g. amd64:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/pysmi_0.2.2-1.rbuild.log.gz
| ==
| ERROR: testGetDataFromFile (tests.test_zipreader.ZipReaderTestCase)
| --
| Traceback (most recent call last):
| File
"/build/1st/pysmi-0.2.2/.pybuild/cpython3_3.7_pysmi/build/tests/test_zipreader.py",
line 180, in testGetDataFromFile
| mibinfo, data = zipReader.getData('testA')
| File
"/build/1st/pysmi-0.2.2/.pybuild/cpython3_3.7_pysmi/build/pysmi/reader/zipreader.py",
line 166, in getData
| raise error.PySmiReaderFileNotFoundError('source MIB %s not found' %
mibname, reader=self)
| pysmi.error.PySmiReaderFileNotFoundError: source MIB testA not found
|
| ==
| ERROR: testGetInnerZipData (tests.test_zipreader.ZipReaderTestCase)
| --
| Traceback (most recent call last):
| File
"/build/1st/pysmi-0.2.2/.pybuild/cpython3_3.7_pysmi/build/tests/test_zipreader.py",
line 200, in testGetInnerZipData
| mibinfo, data = zipReader.getData('testC')
| File
"/build/1st/pysmi-0.2.2/.pybuild/cpython3_3.7_pysmi/build/pysmi/reader/zipreader.py",
line 166, in getData
| raise error.PySmiReaderFileNotFoundError('source MIB %s not found' %
mibname, reader=self)
| pysmi.error.PySmiReaderFileNotFoundError: source MIB testC not found
|
| --
| Ran 108 tests in 16.268s
|
| FAILED (errors=2)
| E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd
/build/1st/pysmi-0.2.2/.pybuild/cpython3_3.7_pysmi/build; python3.7 -m unittest
discover -v
| dh_auto_test: pybuild --test -i python{version} -p "3.7 3.6" returned exit
code 13
| make: *** [debian/rules:5: build] Error 25
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
Helmut
Bug#911693: librabbitmq FTBFS: setup_connection_and_channel: Assertion `rc == AMQP_STATUS_OK' failed.
Source: librabbitmq Version: 0.9.0-0.1 Severity: serious Tags: ftbfs librabbitmq fails to build from source in unstable on the official buildds: https://buildd.debian.org/status/fetch.php?pkg=librabbitmq=arm64=0.9.0-0.1=1538400732=0 | Running tests... | /usr/bin/ctest --force-new-ctest-process -j1 | Test project /<>/obj-aarch64-linux-gnu | Start 1: parse_url | 1/7 Test #1: parse_url Passed0.00 sec | Start 2: tables | 2/7 Test #2: tables ... Passed0.00 sec | Start 3: hostcheck | 3/7 Test #3: hostcheck Passed0.00 sec | Start 4: status_enum | 4/7 Test #4: status_enum .. Passed0.00 sec | Start 5: basic | 5/7 Test #5: basic ***Exception: Child aborted 0.01 sec | test_basic: /<>/tests/test_basic.c:54: setup_connection_and_channel: Assertion `rc == AMQP_STATUS_OK' failed. | | Start 6: sasl_mechanism | 6/7 Test #6: sasl_mechanism ... Passed0.00 sec | Start 7: merge_capabilities | 7/7 Test #7: merge_capabilities ... Passed0.00 sec | | 86% tests passed, 1 tests failed out of 7 | | Total Test time (real) = 0.03 sec | | The following tests FAILED: |5 - basic (Child aborted) | Errors while running CTest | make[1]: *** [Makefile:98: test] Error 8 | make[1]: Leaving directory '/<>/obj-aarch64-linux-gnu' | dh_auto_test: cd obj-aarch64-linux-gnu && make -j1 test ARGS\+=-j1 returned exit code 2 | make: *** [debian/rules:4: build-arch] Error 2 | dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2 Helmut
Bug#911782: python-cryptography FTBFS: openssl test fails
Source: python-cryptography
Version: 2.3-1
Severity: serious
Tags: ftbfs
python-cryptography fails to build from source in unstable. The same
version builds fine in testing. This indicates that a dependency (e.g.
openssl) is the cause.
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/python-cryptography_2.3-1.rbuild.log.gz
| === FAILURES
===
| TestOpenSSL.test_openssl_assert_error_on_stack
|
| self =
|
| def test_openssl_assert_error_on_stack(self):
| b = Binding()
| b.lib.ERR_put_error(
| b.lib.ERR_LIB_EVP,
| b.lib.EVP_F_EVP_ENCRYPTFINAL_EX,
| b.lib.EVP_R_DATA_NOT_MULTIPLE_OF_BLOCK_LENGTH,
| b"",
| -1
| )
| with pytest.raises(InternalError) as exc_info:
| _openssl_assert(b.lib, False)
|
| error = exc_info.value.err_code[0]
| > assert error.code == 101183626
| E AssertionError: assert 337146240L == 101183626
| E+ where 337146240L = _OpenSSLErrorWithText(code=337146240L, lib=20,
func=391, reason=384, reason_text='error:14187180:SSL
routines:ssl_do_config:bad value').code
|
| ../../../tests/hazmat/bindings/test_openssl.py:98: AssertionError
| === warnings summary
===
...
| = 1 failed, 96853 passed, 4186 skipped, 25 warnings in 443.73 seconds
==
| E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd
/build/1st/python-cryptography-2.3/.pybuild/cpython2_2.7_cryptography/build;
python2.7 -m pytest {dir}/tests/
| dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
| make: *** [debian/rules:17: build] Error 25
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
Helmut
Bug#911716: python-urllib3 FTBFS: ssl tests fail
Source: python-urllib3
Version: 1.22-1
Severity: serious
Tags: ftbfs
python-urllib3 fails to build from source in unstable. Building the
experimental version succeeds. A build ends with:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/python-urllib3_1.22-1.rbuild.log.gz
| === FAILURES
===
| _ TestConnection.test_match_hostname_mismatch
__
|
| self =
|
| def test_match_hostname_mismatch(self):
| cert = {'subjectAltName': [('DNS', 'foo')]}
| asserted_hostname = 'bar'
| try:
| with mock.patch('urllib3.connection.log.error') as mock_log:
| > _match_hostname(cert, asserted_hostname)
|
| test/test_connection.py:39:
| _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_
|
| cert = {'subjectAltName': [('DNS', 'foo')]}, asserted_hostname = 'bar'
|
| def _match_hostname(cert, asserted_hostname):
| try:
| > match_hostname(cert, asserted_hostname)
|
| urllib3/connection.py:356:
| _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_
|
| cert = {'subjectAltName': [('DNS', 'foo')]}, hostname = 'bar'
|
| def match_hostname(cert, hostname):
| """Verify that *cert* (in decoded format as returned by
| SSLSocket.getpeercert()) matches the *hostname*. RFC 2818 and RFC
6125
| rules are followed.
|
| The function matches IP addresses rather than dNSNames if hostname is
a
| valid ipaddress string. IPv4 addresses are supported on all platforms.
| IPv6 addresses are supported on platforms with IPv6 support (AF_INET6
| and inet_pton).
|
| CertificateError is raised on failure. On success, the function
| returns nothing.
| """
| if not cert:
| raise ValueError("empty or no certificate, match_hostname needs a
"
| "SSL socket or SSL context with either "
| "CERT_OPTIONAL or CERT_REQUIRED")
| try:
| host_ip = _inet_paton(hostname)
| except ValueError:
| # Not an IP address (common case)
| host_ip = None
| dnsnames = []
| san = cert.get('subjectAltName', ())
| for key, value in san:
| if key == 'DNS':
| if host_ip is None and _dnsname_match(value, hostname):
| return
| dnsnames.append(value)
| elif key == 'IP Address':
| if host_ip is not None and _ipaddress_match(value, host_ip):
| return
| dnsnames.append(value)
| if not dnsnames:
| # The subject is only checked when there is no dNSName entry
| # in subjectAltName
| for sub in cert.get('subject', ()):
| for key, value in sub:
| # XXX according to RFC 2818, the most specific Common Name
| # must be used.
| if key == 'commonName':
| if _dnsname_match(value, hostname):
| return
| dnsnames.append(value)
| if len(dnsnames) > 1:
| raise CertificateError("hostname %r "
| "doesn't match either of %s"
| % (hostname, ', '.join(map(repr, dnsnames
| elif len(dnsnames) == 1:
| raise CertificateError("hostname %r "
| "doesn't match %r"
| > % (hostname, dnsnames[0]))
| E ssl.SSLCertVerificationError: ("hostname 'bar' doesn't match
'foo'",)
|
| /usr/lib/python3.7/ssl.py:327: SSLCertVerificationError
|
| During handling of the above exception, another exception occurred:
|
| self =
|
| def test_match_hostname_mismatch(self):
| cert = {'subjectAltName': [('DNS', 'foo')]}
| asserted_hostname = 'bar'
| try:
| with mock.patch('urllib3.connection.log.error') as mock_log:
| _match_hostname(cert, asserted_hostname)
| except CertificateError as e:
| > assert str(e) == "hostname 'bar' doesn't match 'foo'"
| E assert '("hostname \...ch \'foo\'",)' == "hostname 'bar...t match
'foo'"
| E - ("hostname 'bar' doesn't match 'foo'",)
| E ? -- ---
| E + hostname 'bar' doesn't match 'foo'
|
| test/test_connection.py:41: AssertionError
| === 1 failed, 545 passed, 51 skipped, 1 deselected in 11.58 seconds
| /usr/lib/python3/dist-packages/_pytest/assertion/rewrite.py:6:
DeprecationWarning: the imp module is deprecated in favour of importlib; see
the module's documentation for alternative uses
| import imp
| /usr/lib/python3/dist-packages/pkg_resources/_vendor/pyparsing.py:943:
DeprecationWarning: Using or
Bug#911717: ruby2.5 FTBFS: missing Build-Depends: tzdata
Source: ruby2.5 Version: 2.5.1-6 Severity: serious Tags: ftbfs ruby2.5 fails to build from source in unstable. The time zone tests fail unless tzdata is installed. On the buildds, tzdata is installed, because its Priority is required and debootstrap happens to install required packages. tzdata is not essential nor build-essential though. You must depend on it if you use it. E.g. | 1) Failure: | TestTimeTZ#test_america_los_angeles [/<>/test/ruby/test_time_tz.rb:107]: | TZ=America/Los_Angeles Time.local(2007, 3, 11, 2, 0, 0). | <"2007-03-11 03:00:00 -0700"> expected but was | <"2007-03-11 02:00:00 +">. Helmut
Bug#911955: putty FTBFS due to -Werror=format-overflow
Source: putty Version: 0.70-4 Severity: serious Tags: ftbfs putty fails to build from source in unstable. -Werror=format-overflow triggers: | pscp.c: In function 'scp_send_filename': | pscp.c:886:22: error: '%s' directive writing up to 39 bytes into a region of size 34 [-Werror=format-overflow=] | sprintf(buf, "C%04o %s ", (int)(permissions & 0), sizestr); | ^~~~~ | In file included from /usr/include/stdio.h:862, | from pscp.c:16: | /usr/include/x86_64-linux-gnu/bits/stdio2.h:33:10: note: '__builtin___sprintf_chk' output between 8 and 47 bytes into a destination of size 40 |return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1, | ^~ |__bos (__s), __fmt, __va_arg_pack ()); |~ Helmut
Bug#911947: glance FTBFS: tests fail: RecursionError: maximum recursion depth exceeded while calling a Python object
Source: glance Version: 2:17.0.0-2 Severity: serious Tags: ftbfs glance fails to build from source in unstable. It has many test failures. A fair number of "RecursionError: maximum recursion depth exceeded while calling a Python object" are among them. See e.g.: https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/glance_17.0.0-2.rbuild.log.gz Most include this: | File "/build/1st/glance-17.0.0/glance/domain/__init__.py", line 316, in keys | return dict(self).keys() | File "/build/1st/glance-17.0.0/glance/domain/__init__.py", line 316, in keys | return dict(self).keys() | File "/build/1st/glance-17.0.0/glance/domain/__init__.py", line 316, in keys | return dict(self).keys() | RecursionError: maximum recursion depth exceeded while calling a Python object Helmut
Bug#911953: librabbitmq-dev missing Depends: libssl-dev
Package: librabbitmq-dev Version: 0.9.0-0.1 Severity: serious Tags: ftbfs Control: affects -1 + src:pmacct pmacct fails to build from source. This is caused by a bug in librabbitmq-dev. After installing librabbitmq-dev, the .pc file is dysfunctional: $ pkg-config librabbitmq --cflags Package openssl was not found in the pkg-config search path. Perhaps you should add the directory containing `openssl.pc' to the PKG_CONFIG_PATH environment variable Package 'openssl', required by 'librabbitmq', not found $ The .pc file has | Requires.private: openssl but the package misses a dependency on libssl-dev. Either remove openssl from requires or add libssl-dev to Depends. Helmut
Bug#911945: breezy FTBFS: Build-Depends on unavailable python-lzma-dbg
Source: breezy Version: 3.0.0~bzr7141-1 Severity: serious Tags: ftbfs breezy Build-Depends on python-lzma-dbg. Since version 0.5.3-4, python-lzma no longer builds that package. Thus breezy's Build-Depends are permanently unsatisfiable. If you really need python-lzma-dbg, please: reassign -1 python-lzma retitle -1 reintroduce python-lzma-dbg affects -1 + src:breezy Helmut
Bug#911941: mpgrafic FTBFS on amd64: tests fail: unexpected additional output line
Source: mpgrafic Version: 0.3.15-1 Severity: serious Tags: ftbfs mpgrafic fails to build from source in unstable on amd64. Here is a reproducible log: https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/mpgrafic_0.3.15-1.rbuild.log.gz | | See ./test-suite.log | | make[5]: *** [Makefile:705: test-suite.log] Error 1 | make[5]: Leaving directory '/build/1st/mpgrafic-0.3.15' | make[4]: *** [Makefile:813: check-TESTS] Error 2 | make[4]: Leaving directory '/build/1st/mpgrafic-0.3.15' | make[3]: *** [Makefile:1041: check-am] Error 2 | make[3]: Leaving directory '/build/1st/mpgrafic-0.3.15' | make[2]: *** [Makefile:590: check-recursive] Error 1 | make[2]: Leaving directory '/build/1st/mpgrafic-0.3.15' | dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2 | +++regression test diagnostic+++ | ARCH_DEFAULT_MPI_IMPL=openmpi | diff: | --- Output.stdout.np32 2017-08-18 09:19:38.0 -1200 | +++ Output.stdout.np32.tmp 2019-11-19 03:54:55.398906633 -1200 | @@ -1,3 +1,4 @@ | +profitbricks-build15-amd64.52873hfi_wait_for_device: The /dev/hfi1_0 device failed to appear after 15.0 seconds: Connection timed out | | Will generate initial conditions on grid of size 32 32 32 | | Linux profitbricks-build15-amd64 4.18.0-0.bpo.1-amd64 #1 SMP Debian 4.18.6-1~bpo9+1 (2018-09-13) x86_64 GNU/Linux | Processors on this machine: | processor : 0 | processor : 1 | processor : 2 | processor : 3 | processor : 4 | processor : 5 | processor : 6 | processor : 7 | processor : 8 | processor : 9 | processor : 10 | processor : 11 | processor : 12 | processor : 13 | processor : 14 | processor : 15 | +++/regression test diagnostic+++ | make[1]: *** [debian/rules:33: override_dh_auto_test] Error 1 | make[1]: Leaving directory '/build/1st/mpgrafic-0.3.15' | make: *** [debian/rules:16: build] Error 2 | dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 On reproducible ci, it seems to only happen on amd64 and not for armhf, arm64 or i386. It seems to only happen in unstable and not in testing. Building it locally in sbuild, I can see that it fails reliably. Helmut
Bug#911154: netkit-ntalk misses the generator for configure
Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9 -10 -11 -12 -13 -14 -15 Control: reassign -2 src:biff Control: retitle -2 biff misses the generator for configure Control: reassign -3 src:bsd-finger Control: retitle -3 bsd-finger misses the generator for configure Control: reassign -4 src:linux-ftpd Control: retitle -4 linux-ftpd misses the generator for configure Control: reassign -5 src:linux-ftpd-ssl Control: retitle -5 linux-ftpd-ssl misses the generator for configure Control: reassign -6 src:netkit-bootparamd Control: retitle -6 netkit-bootparamd misses the generator for configure Control: reassign -7 src:netkit-ftp Control: retitle -7 netkit-ftp misses the generator for configure Control: reassign -8 src:netkit-ftp-ssl Control: retitle -8 netkit-ftp-ssl misses the generator for configure Control: reassign -9 src:netkit-rsh Control: retitle -9 netkit-rsh misses the generator for configure Control: reassign -10 src:netkit-rusers Control: retitle -10 netkit-rusers misses the generator for configure Control: reassign -11 src:netkit-rwall Control: retitle -11 netkit-rwall misses the generator for configure Control: reassign -12 src:netkit-rwho Control: retitle -12 netkit-rwho misses the generator for configure Control: reassign -13 src:netkit-telnet Control: retitle -13 netkit-telnet misses the generator for configure Control: reassign -14 src:netkit-telnet-ssl Control: retitle -14 netkit-telnet-ssl misses the generator for configure Control: reassign -15 src:netkit-tftp Control: retitle -15 netkit-tftp misses the generator for configure On Sun, Oct 28, 2018 at 11:19:47AM +0100, Christoph Biedl wrote: > Still you have a practical point as mentioned in #873085: The generated > configure has bugs, even some more (bashisms, reported outside Debian), > and it's way better to fix this in the generator than in some 15 > packages. I think this is the sticking point. The requirement for source is there to make modifications feasible. Of course we can patch bugs in binary files, but it becomes prohibitively expensive. The same is true for fixing the same bug in 15 packages. For this reason, I think that we do violate the DFSG here. > It seems however the mentioned confgen program is lost in the void. > I've been looking around quite a lot, but no avail. So I've contacted > David A. Holland[1], asking for advice. As a plan B, I might as well > re-implement that confgen program and make it part of the build > process. But I'd do that only as a last resort only: At least some of > the packages have a significant popcon count, so RM isn't an option. It seems fairly obvious now that we'll have to touch all those 15 packages one way or another. Whether we add confgen or replace the build system altogether is an open question, but both involve changing all affected source packages. Given this, I'll clone the respective bugs. That in turn means that reducing the scope using RM bugs (for some) sounds useful. I'm not sure that adding our own confgen is maintainable in the long run. We already have very many build systems in Debian. We've learned the hard way that supporting many different build and packaging tools is expensive. Nowadays, most packages use debhelper and that kind of centralization bears benefits in modifiability. So I wonder whether outright replacing confgen usage (effectively reimplementing the build system for <= 15 packages) would be more maintainable in the long run. Most likely, that would make cross building just work. On the other hand, we'd have to extend the prospective confgen to support that use case. I'm suggesting that rewriting all those build systems using one of the standard tools (e.g. autotools, cmake, meson, maybe not qmake, ...) could mean less work. Helmut
Bug#912274: ruby-clockwork FTBFS: Mocha::NotInitializedError: Mocha methods cannot be used outside the context of a test
Source: ruby-clockwork Version: 1.2.0-3 Severity: serious Tags: ftbfs ruby-clockwork fails to build from source in unstable. | 1) Error: | Clockwork::Event::#thread?::manager config thread option set to true#test_0001_is true: | Mocha::NotInitializedError: Mocha methods cannot be used outside the context of a test | /<>/test/event_test.rb:12:in `block (4 levels) in ' | | 2) Error: | Clockwork::Event::#thread?::manager config thread option set to true#test_0002_is false when event thread option set: | Mocha::NotInitializedError: Mocha methods cannot be used outside the context of a test | /<>/test/event_test.rb:12:in `block (4 levels) in ' | | 3) Error: | Clockwork::Manager#test_0013_exceptions still set the last timestamp to avoid spastic error loops: | Mocha::NotInitializedError: Mocha methods cannot be used outside the context of a test | /<>/test/manager_test.rb:131:in `block (2 levels) in ' | | 4) Error: | Clockwork#test_0006_support module re-open style: | Mocha::NotInitializedError: Mocha methods cannot be used outside the context of a test | /<>/test/clockwork_test.rb:80:in `block (2 levels) in ' | | 5) Error: | Clockwork#test_0001_should run events with configured logger: | Mocha::NotInitializedError: Mocha methods cannot be used outside the context of a test | /<>/test/clockwork_test.rb:24:in `block (2 levels) in ' | | 6) Error: | Clockwork#test_0002_should log event correctly: | Mocha::NotInitializedError: Mocha methods cannot be used outside the context of a test | /<>/test/clockwork_test.rb:37:in `block (2 levels) in ' | | 7) Error: | Clockwork#test_0004_should not run anything after reset: | Mocha::NotInitializedError: Mocha methods cannot be used outside the context of a test | /<>/test/clockwork_test.rb:62:in `block (2 levels) in ' | | 8) Error: | Clockwork#test_0003_should pass event without modification to handler: | Mocha::NotInitializedError: Mocha methods cannot be used outside the context of a test | /<>/test/clockwork_test.rb:50:in `block (2 levels) in ' | | 9) Error: | Clockwork#test_0005_should pass all arguments to every: | Mocha::NotInitializedError: Mocha methods cannot be used outside the context of a test | /<>/test/clockwork_test.rb:69:in `block (2 levels) in ' | | 10) Error: | Clockwork::Event::#thread?::manager config thread option not set#test_0001_is true if event thread option is true: | Mocha::NotInitializedError: Mocha methods cannot be used outside the context of a test | /<>/test/event_test.rb:28:in `block (4 levels) in ' | | 11) Error: | Clockwork::Manager::max_threads#test_0001_should warn when an event tries to generate threads more than max_threads: | Mocha::NotInitializedError: Mocha methods cannot be used outside the context of a test | /<>/test/manager_test.rb:276:in `block (3 levels) in ' | | 12) Error: | Clockwork::Manager::max_threads#test_0002_should not warn when thread is managed by others: | Mocha::NotInitializedError: Mocha methods cannot be used outside the context of a test | /<>/test/manager_test.rb:291:in `block (3 levels) in ' | | 85 runs, 139 assertions, 0 failures, 12 errors, 0 skips | rake aborted! | Command failed with status (1): [ruby -w -I"test" "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/at_test.rb" "test/clockwork_test.rb" "test/database_events/sync_performer_test.rb" "test/event_test.rb" "test/manager_test.rb" "test/database_events/test_helpers.rb" -v] | | Tasks: TOP => default | (See full trace by running task with --trace) | ERROR: Test "ruby2.5" failed. Exiting. | dh_auto_install: dh_ruby --install /<>/debian/ruby-clockwork returned exit code 1 | make: *** [debian/rules:6: binary] Error 1 | dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2 Helmut
Bug#912272: staden-io-lib FTBFS: dh_installdocs: Cannot find (any matches for) "README" (tried in .)
Source: staden-io-lib Version: 1.14.9-4 Severity: serious Tags: ftbfs staden-io-lib fails to build from source in unstable. This smells a bit like a debhelper regression, but I'm not sure actually. In any case, it fails to build reliably. |dh_installdocs -O--no-parallel | dh_installdocs: Cannot find (any matches for) "README" (tried in .) | | make: *** [debian/rules:11: binary] Error 2 | dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2 Helmut
Bug#911938: libhttp-daemon-ssl-perl FTBFS: tests fail: Connection refused
Source: libhttp-daemon-ssl-perl Version: 1.05-01-1 Severity: serious Tags: ftbfs libhttp-daemon-ssl-perl fails to build from source in unstable. https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/libhttp-daemon-ssl-perl_1.05-01-1.rbuild.log.gz | # Failed test 'got request object' | # at t/testpost.t line 88. | Can't call method "method" on an undefined value at t/testpost.t line 89. | # Looks like your test exited with 255 just after 5. | | # Failed test 'posted small request' | # at t/testpost.t line 55. | # 500 | # Server closed connection without sending any data back | | # Failed test 'posted 66k request' | # at t/testpost.t line 62. | # 500 | # Can't connect to 127.0.0.1:39653 (Connection refused) | | # Failed test 'posted 67k request' | # at t/testpost.t line 68. | # 500 | # Can't connect to 127.0.0.1:39653 (Connection refused) | | # Failed test 'posted 500k request' | # at t/testpost.t line 74. | # 500 | # Can't connect to 127.0.0.1:39653 (Connection refused) | t/testpost.t | 1..20 | ok - made test server | ok - server init port=39653 | ok - server fileno | ok - accepted first post | not ok - got request object | not ok - posted small request | not ok - posted 66k request | not ok - posted 67k request | not ok - posted 500k request | Dubious, test returned 255 (wstat 65280, 0xff00) | Failed 16/20 subtests | | Test Summary Report | --- | t/testpost.t (Wstat: 65280 Tests: 9 Failed: 5) | Failed tests: 5-9 | Non-zero exit status: 255 | Parse errors: Bad plan. You planned 20 tests but ran 9. | Files=4, Tests=26, 34 wallclock secs ( 0.06 usr 0.03 sys + 1.09 cusr 0.25 csys = 1.43 CPU) | Result: FAIL | Failed 1/4 test programs. 5/26 subtests failed. | make[2]: *** [Makefile:829: test_dynamic] Error 255 | make[2]: Leaving directory '/build/1st/libhttp-daemon-ssl-perl-1.05-01' | dh_auto_test: make -j1 test TEST_VERBOSE=1 returned exit code 2 | make[1]: *** [debian/rules:20: override_dh_auto_test] Error 2 | make[1]: Leaving directory '/build/1st/libhttp-daemon-ssl-perl-1.05-01' | make: *** [debian/rules:4: build] Error 2 | dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 According to reproducible builds ci, it also happens for i386, armhf and arm64. That indicates that it is architecture-independent. The same version seems to build fine in testing. Some dependency likely is the cause. It also fails in sbuild (reproducible uses pbuilder). Helmut
Bug#911943: openhft-compiler FTBFS: missing Build-Depends: libeasymock-java
Source: openhft-compiler Version: 2.2.4-1 Severity: serious Tags: ftbfs patch openhft-compiler fails to build from source in unstable: https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/openhft-compiler_2.2.4-1.rbuild.log.gz | [ERROR] Failed to execute goal on project compiler: Could not resolve dependencies for project net.openhft:compiler:bundle:2.2.4: Cannot access sonatype-nexus-staging (https://oss.sonatype.org/content/repositories/staging) in offline mode and the artifact org.easymock:easymock:jar:debian has not been downloaded from it before. -> [Help 1] Please add "libeasymock-java" to Build-Depends. That makes it build successfully. Helmut
Bug#911944: neovim FTBFS: tests fail
Source: neovim Version: 0.3.1-1 Severity: serious Tags: ftbfs neovim fails to build from source in unstable. | [ ERROR ] 6 errors, listed below: | [ ERROR ] test/functional/helpers.lua @ 743: after_each | test/helpers.lua:289: crash detected (see above) | | stack traceback: | test/helpers.lua:289: in function 'check_cores' | test/functional/helpers.lua:748: in function | | [ ERROR ] test/functional/helpers.lua @ 743: after_each | test/helpers.lua:289: crash detected (see above) | | stack traceback: | test/helpers.lua:289: in function 'check_cores' | test/functional/helpers.lua:748: in function | | [ ERROR ] test/functional/helpers.lua @ 743: after_each | test/helpers.lua:289: crash detected (see above) | | stack traceback: | test/helpers.lua:289: in function 'check_cores' | test/functional/helpers.lua:748: in function | | [ ERROR ] test/functional/helpers.lua @ 743: after_each | test/helpers.lua:289: crash detected (see above) | | stack traceback: | test/helpers.lua:289: in function 'check_cores' | test/functional/helpers.lua:748: in function | | [ ERROR ] test/functional/helpers.lua @ 743: after_each | test/helpers.lua:289: crash detected (see above) | | stack traceback: | test/helpers.lua:289: in function 'check_cores' | test/functional/helpers.lua:748: in function | | [ ERROR ] test/functional/helpers.lua @ 743: after_each | test/helpers.lua:289: crash detected (see above) | | stack traceback: | test/helpers.lua:289: in function 'check_cores' | test/functional/helpers.lua:748: in function | | | 18 SKIPPED TESTS | 6 ERRORS | -- Output to stderr: ... | ninja: build stopped: subcommand failed. | make[1]: *** [debian/rules:77: override_dh_auto_test-arch] Error 1 | make[1]: Leaving directory '/<>' | make: *** [debian/rules:39: binary] Error 2 | dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Looking to reproducible builds, the failure pattern looks quite random: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/neovim.html However, in local builds for unstable/amd64 in sbuild, I didn't get a single successful build. Helmut
Bug#911858: controlsfx FTBFS: error: package javafx.scene does not exist
Source: controlsfx Version: 8.40.14-1 Severity: serious Tags: ftbfs controlsfx fails to build from source in unstable. https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/controlsfx_8.40.14-1.rbuild.log.gz | All input files are considered out-of-date for incremental task ':controlsfx:compileJava'. | :controlsfx:compileJava - is not incremental (e.g. outputs have changed, no previous execution, etc.). | Compiling with JDK Java compiler API. | Generating pom file /build/1st/controlsfx-8.40.14/controlsfx-samples/build/debian/controlsfx-samples.pom | :controlsfx-samples:debianMavenPom (Thread[Daemon worker,5,main]) completed. Took 0.183 secs. | /build/1st/controlsfx-8.40.14/fxsampler/src/main/java/fxsampler/model/SampleTree.java:6: error: package javafx.scene.control does not exist | import javafx.scene.control.TreeItem; |^ | /build/1st/controlsfx-8.40.14/fxsampler/src/main/java/fxsampler/model/WelcomePage.java:30: error: package javafx.scene does not exist | import javafx.scene.Node; |^ Helmut
Bug#911873: python-transitions FTBFS: tests fail with Python 3.7: RuntimeError: generator raised StopIteration
Source: python-transitions
Version: 0.6.7-1
Severity: serious
Tags: ftbfs
python-transitions fails to build from source. Its test suite has lots
of these:
| ==
| ERROR: test_use_machine_as_model
(tests.test_states.TestStatesDiagramsLockedNested)
| --
| Traceback (most recent call last):
| File
"/<>/.pybuild/cpython3_3.7_transitions/build/transitions/extensions/diagrams.py",
line 376, in _get_graph
| return self.model_graphs[model] if not show_roi else
self._graph_roi(model)
| KeyError:
|
| During handling of the above exception, another exception occurred:
|
| Traceback (most recent call last):
| File "/usr/lib/python3/dist-packages/pygraphviz/agraph.py", line 1093, in
subgraphs_iter
| raise StopIteration
| StopIteration
|
| The above exception was the direct cause of the following exception:
|
| Traceback (most recent call last):
| File
"/<>/.pybuild/cpython3_3.7_transitions/build/tests/test_states.py",
line 169, in setUp
| super(TestStatesDiagramsLockedNested, self).setUp()
| File
"/<>/.pybuild/cpython3_3.7_transitions/build/tests/test_graphing.py",
line 290, in setUp
| super(TestDiagramsLockedNested, self).setUp()
| File
"/<>/.pybuild/cpython3_3.7_transitions/build/tests/test_graphing.py",
line 222, in setUp
| super(TestDiagramsNested, self).setUp()
| File
"/<>/.pybuild/cpython3_3.7_transitions/build/tests/test_graphing.py",
line 89, in setUp
| self.stuff = Stuff(machine_cls=self.machine_cls)
| File
"/<>/.pybuild/cpython3_3.7_transitions/build/tests/utils.py", line
20, in __init__
| self.machine = machine_cls(*args, **kwargs)
| File
"/<>/.pybuild/cpython3_3.7_transitions/build/transitions/extensions/diagrams.py",
line 363, in __init__
| model.get_graph()
| File
"/<>/.pybuild/cpython3_3.7_transitions/build/transitions/extensions/diagrams.py",
line 378, in _get_graph
| return self._get_graph(model, title, force_new=True, show_roi=show_roi)
| File
"/<>/.pybuild/cpython3_3.7_transitions/build/transitions/extensions/diagrams.py",
line 373, in _get_graph
| self.model_graphs[model] = self.graph_cls(self).get_graph(title if title
is not None else self.title)
| File
"/<>/.pybuild/cpython3_3.7_transitions/build/transitions/extensions/diagrams.py",
line 179, in get_graph
| self._add_edges(self.machine.events.copy(), fsm_graph)
| File
"/<>/.pybuild/cpython3_3.7_transitions/build/transitions/extensions/diagrams.py",
line 222, in _add_edges
| for sub in container.subgraphs_iter():
| RuntimeError: generator raised StopIteration
|
| --
| Ran 981 tests in 15.914s
|
| FAILED (errors=323)
| E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd
/<>/.pybuild/cpython3_3.7_transitions/build; python3.7 -m nose -v
tests
| dh_auto_test: pybuild --test -i python{version} -p "3.7 3.6" returned exit
code 13
| make: *** [debian/rules:10: build] Error 25
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
Likely this is due to Python 3.7 having become a supported Python
version and Python 3.7 having changed behaviour wrt. generators.
Helmut
Bug#911861: python-hbmqtt FTBFS with Python 3.7
Source: python-hbmqtt
Version: 0.9.2-2
Severity: serious
Tags: ftbfs
python-hbmqtt fails to build from source with Python 3.7 as it tries to
use "async" as a variable name:
| ==
| ERROR: Failure: SyntaxError (invalid syntax (manager.py, line 16))
| --
| Traceback (most recent call last):
| File "/usr/lib/python3/dist-packages/nose/failure.py", line 39, in runTest
| raise self.exc_val.with_traceback(self.tb)
| File "/usr/lib/python3/dist-packages/nose/loader.py", line 417, in
loadTestsFromName
| addr.filename, addr.module)
| File "/usr/lib/python3/dist-packages/nose/importer.py", line 47, in
importFromPath
| return self.importFromDir(dir_path, fqname)
| File "/usr/lib/python3/dist-packages/nose/importer.py", line 94, in
importFromDir
| mod = load_module(part_fqname, fh, filename, desc)
| File "/usr/lib/python3.7/imp.py", line 234, in load_module
| return load_source(name, filename, file)
| File "/usr/lib/python3.7/imp.py", line 171, in load_source
| module = _load(spec)
| File "", line 696, in _load
| File "", line 677, in _load_unlocked
| File "", line 728, in exec_module
| File "", line 219, in _call_with_frames_removed
| File
"/<>/.pybuild/cpython3_3.7_hbmqtt/build/tests/plugins/test_persistence.py",
line 10, in
| from hbmqtt.plugins.manager import BaseContext
| File
"/<>/.pybuild/cpython3_3.7_hbmqtt/build/hbmqtt/plugins/manager.py",
line 16
| from asyncio import async as ensure_future
| ^
| SyntaxError: invalid syntax
|
| --
| Ran 38 tests in 0.056s
|
| FAILED (errors=3)
| E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd
/<>/.pybuild/cpython3_3.7_hbmqtt/build; python3.7 -m nose -v -I
test_manager.py
| dh_auto_test: pybuild --test -i python{version} -p "3.7 3.6" returned exit
code 13
| make: *** [debian/rules:13: build] Error 25
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
Helmut
Bug#911869: ruby-sinatra-contrib FTBFS: tests fail during dh_ruby --install
Source: ruby-sinatra-contrib
Version: 1.4.7-1
Severity: serious
Tags: ftbfs
ruby-sinatra-contrib fails to build from source. Apparently it runs
tests during dh_ruby --install and fails doing so:
| Failures:
|
| 1) Sinatra::Cookies include? checks response cookies
| Failure/Error: jar.should include(:foo)
|
|expected {"foo" => "bar"} to include :foo
|Diff:
|@@ -1,2 +1,2 @@
|-[:foo]
|+"foo" => "bar",
| # ./spec/cookies_spec.rb:553:in `block (3 levels) in '
|
| Deprecation Warnings:
|
| Using `should` from rspec-expectations' old `:should` syntax without
explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or
explicitly enable `:should` with `config.expect_with(:rspec) { |c| c.syntax =
:should }` instead. Called from
/build/1st/ruby-sinatra-contrib-1.4.7/spec/capture_spec.rb:26:in `block (3
levels) in '.
|
| `failure_message_for_should` is deprecated. Use `failure_message` instead.
Called from /build/1st/ruby-sinatra-contrib-1.4.7/spec/decompile_spec.rb:10:in
`block in '.
|
|
| If you need more of the backtrace for any of these deprecations to
| identify where to make the necessary changes, you can configure
| `config.raise_errors_for_deprecations!`, and it will turn the
| deprecation warnings into errors, giving you the full backtrace.
|
| 2 deprecation warnings total
|
| Finished in 5.13 seconds (files took 1.41 seconds to load)
| 837 examples, 1 failure
|
| Failed examples:
|
| rspec ./spec/cookies_spec.rb:550 # Sinatra::Cookies include? checks response
cookies
|
| /usr/bin/ruby2.5 /usr/bin/rspec --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb
failed
| ERROR: Test "ruby2.5" failed. Exiting.
| dh_auto_install: dh_ruby --install
/build/1st/ruby-sinatra-contrib-1.4.7/debian/ruby-sinatra-contrib returned exit
code 1
| make: *** [debian/rules:4: binary] Error 1
| dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned
exit status 2
Helmut
Bug#911856: python-transliterate FTBFS with multiple supported python versions
Source: python-transliterate
Version: 1.10.1-1
Severity: serious
Tags: ftbfs
python-transliterate fails to build from source when multiple versions
of Python are supported.
|debian/rules override_dh_auto_test
| make[1]: Entering directory '/<>'
| cp runtests.py /<>/.pybuild/cpython3_3.7_transliterate/build
/<>/.pybuild/cpython3_3.6_transliterate/build
| cp: -r not specified; omitting directory
'/<>/.pybuild/cpython3_3.7_transliterate/build'
| make[1]: *** [debian/rules:22: override_dh_auto_test] Error 1
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:6: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
When multiple versions are supported, pybuild --print '{build_dir}'
yields multiple directories, but cp needs one target.
Helmut
Bug#911878: libosinfo FTBFS: tests fail: ERROR:test-isodetect.c:406:test_one: assertion failed (shortid == info->shortid): ("win10" == "win8")
Source: libosinfo
Version: 1.2.0-1
Severity: serious
Tags: ftbfs
libosinfo fails to build from source in unstable:
| /isodetect/windows: **
| ERROR:test-isodetect.c:406:test_one: assertion failed (shortid ==
info->shortid): ("win10" == "win8")
| FAIL test-isodetect (exit status: 134)
|
|
| Testsuite summary for libosinfo 1.2.0
|
| # TOTAL: 16
| # PASS: 15
| # SKIP: 0
| # XFAIL: 0
| # FAIL: 1
| # XPASS: 0
| # ERROR: 0
|
| See tests/test-suite.log
| Please report to libosi...@redhat.com
|
| make[4]: *** [Makefile:1289: test-suite.log] Error 1
| make[4]: Leaving directory '/<>/tests'
| make[3]: *** [Makefile:1397: check-TESTS] Error 2
| make[3]: Leaving directory '/<>/tests'
| make[2]: *** [Makefile:1587: check-am] Error 2
| make[2]: Leaving directory '/<>/tests'
| make[1]: *** [Makefile:594: check-recursive] Error 1
| make[1]: Leaving directory '/<>'
| dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2
| make: *** [debian/rules:23: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
Helmut
Bug#911879: meson fails again: AttributeError: 'list' object has no attribute 'absolute_path'
Package: meson Version: 0.48.1-1 Severity: serious Tags: ftbfs Control: affects -1 + src:gnome-initial-setup In #909851, an AttributeError was fixed. Building gnome-initial setup, I get a surprisingly similar one with the version that fixed #909851: | Traceback (most recent call last): | File "/usr/lib/python3/dist-packages/mesonbuild/mesonmain.py", line 364, in run | app.generate() | File "/usr/lib/python3/dist-packages/mesonbuild/mesonmain.py", line 136, in generate | self._generate(env) | File "/usr/lib/python3/dist-packages/mesonbuild/mesonmain.py", line 165, in _generate | intr.run() | File "/usr/lib/python3/dist-packages/mesonbuild/interpreter.py", line 3836, in run | super().run() | File "/usr/lib/python3/dist-packages/mesonbuild/interpreterbase.py", line 380, in run | self.evaluate_codeblock(self.ast, start=1) | File "/usr/lib/python3/dist-packages/mesonbuild/interpreterbase.py", line 404, in evaluate_codeblock | raise e | File "/usr/lib/python3/dist-packages/mesonbuild/interpreterbase.py", line 398, in evaluate_codeblock | self.evaluate_statement(cur) | File "/usr/lib/python3/dist-packages/mesonbuild/interpreterbase.py", line 409, in evaluate_statement | return self.function_call(cur) | File "/usr/lib/python3/dist-packages/mesonbuild/interpreterbase.py", line 705, in function_call | return func(node, posargs, kwargs) | File "/usr/lib/python3/dist-packages/mesonbuild/interpreterbase.py", line 273, in wrapped | return f(*wrapped_args, **wrapped_kwargs) | File "/usr/lib/python3/dist-packages/mesonbuild/interpreterbase.py", line 162, in wrapped | return f(*wrapped_args, **wrapped_kwargs) | File "/usr/lib/python3/dist-packages/mesonbuild/interpreter.py", line 3422, in func_subdir | self.evaluate_codeblock(codeblock) | File "/usr/lib/python3/dist-packages/mesonbuild/interpreterbase.py", line 404, in evaluate_codeblock | raise e | File "/usr/lib/python3/dist-packages/mesonbuild/interpreterbase.py", line 398, in evaluate_codeblock | self.evaluate_statement(cur) | File "/usr/lib/python3/dist-packages/mesonbuild/interpreterbase.py", line 413, in evaluate_statement | return self.method_call(cur) | File "/usr/lib/python3/dist-packages/mesonbuild/interpreterbase.py", line 741, in method_call | return obj.method_call(method_name, args, kwargs) | File "/usr/lib/python3/dist-packages/mesonbuild/interpreter.py", line 1622, in method_call | value = fn(state, args, kwargs) | File "/usr/lib/python3/dist-packages/mesonbuild/interpreterbase.py", line 219, in wrapped | return f(*wrapped_args, **wrapped_kwargs) | File "/usr/lib/python3/dist-packages/mesonbuild/interpreterbase.py", line 162, in wrapped | return f(*wrapped_args, **wrapped_kwargs) | File "/usr/lib/python3/dist-packages/mesonbuild/modules/i18n.py", line 92, in merge_file | ifile_abs = inputfile.absolute_path(state.environment.source_dir, | AttributeError: 'list' object has no attribute 'absolute_path' Helmut
Bug#911874: python-pyfaidx FTBFS: tests fail with Python 3.7: RuntimeError: generator raised StopIterationj
Source: python-pyfaidx
Version: 0.5.4-1
Severity: serious
Tags: ftbfs
python-pyfaidx fails to build from source in unstable. Its test suite
has lots of these:
| ==
| ERROR: test_reverse_iter (test_FastaRecord_iter.TestFastaRecordIter)
| --
| Traceback (most recent call last):
| File "/<>/pyfaidx/__init__.py", line 808, in __iter__
| raise StopIteration
| StopIteration
|
| The above exception was the direct cause of the following exception:
|
| Traceback (most recent call last):
| File "/<>/tests/test_FastaRecord_iter.py", line 30, in
test_reverse_iter
| expect = list(chain(*([line[::-1] for line in record][::-1] for record in
Fasta('data/genes.fasta', as_raw=True
| File "/<>/tests/test_FastaRecord_iter.py", line 30, in
| expect = list(chain(*([line[::-1] for line in record][::-1] for record in
Fasta('data/genes.fasta', as_raw=True
| File "/<>/tests/test_FastaRecord_iter.py", line 30, in
| expect = list(chain(*([line[::-1] for line in record][::-1] for record in
Fasta('data/genes.fasta', as_raw=True
| RuntimeError: generator raised StopIteration
|
| Name Stmts Miss Cover Missing
| ---
| pyfaidx/__init__.py 69914080% 14-15, 165, 170, 293, 336-343,
346, 356-363, 373-377, 385, 389, 414-415, 440, 443, 479, 481, 487, 540-541,
579, 586-589, 654-657, 700, 729, 744-755, 761, 786, 793, 833, 876-887, 910,
922, 926, 928, 930, 935, 990, 998-999, 1002, 1037, 1044, 1066-1105, 1108,
1117-1137, 1181-1186, 1194-1195, 1233, 1241, 1247-1248
| pyfaidx/cli.py 25712850% 22-25, 31-36, 47-50, 78, 80,
91-106, 120-140, 181-182, 186, 190, 192, 195, 203, 208-214, 228, 231, 237-239,
248-250, 256, 265-278, 282, 286-287, 290-293, 308-315, 321-328, 334-342,
348-358, 361
| ---
| TOTAL 95626872%
| --
| Ran 134 tests in 9.432s
|
| FAILED (SKIP=36, errors=2)
| E: pybuild pybuild:338: test: plugin custom failed with: exit code=1: set -e;
\
| python3.7 -m "nose" --with-coverage --cover-package=pyfaidx
| dh_auto_test: pybuild --test --test-nose -i python{version} -p "3.7 3.6"
--test --system=custom "--test-args=set -e; \\\
| {interpreter} -m \"nose\" --with-coverage
--cover-package=pyfaidx" returned exit code 13
| make[1]: *** [debian/rules:18: override_dh_auto_test] Error 25
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:10: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
Looks like this has started failing, because Python 3.7 has become a
supported Python version and Python 3.7 is stricter about generators.
Helmut
Bug#911877: crossroads: package build vulnerable to /tmp
Source: crossroads Version: 2.81-2 Severity: serious Tags: security crossroads's xr/Makefile has: | $(BINDIR)/xr: $(BIN) | cp $(BIN) $(TMPXR) | install $(TMPXR) $(BINDIR)/xr | rm -f $(TMPXR) where | TMPXR = /tmp/xr-$(shell whoami) Jakub Wilk observed that a malicious user could create /tmp/xr-root as a directory with mode 777 and replace the directory with an arbitrary file after the cp (via inotify) thus injecting an arbitrary binary into the build. Helmut
Bug#911876: asyncpg FTBFS: tests fail
Source: asyncpg
Version: 0.17.0-1
Severity: serious
Tags: ftbfs
asyncpg fails to build from source in unstable:
| === FAILURES
===
| ___ TestCodecsLargeOIDs.test_custom_codec_large_oid
|
| self =
|
| async def test_custom_codec_large_oid(self):
| await self.con.execute('CREATE DOMAIN test_domain_t AS int')
| try:
| oid = await self.con.fetchval('''
| SELECT oid FROM pg_type WHERE typname = 'test_domain_t'
| ''')
| > self.assertEqual(oid, 2147483648)
| E AssertionError: 2147483649 != 2147483648
|
| tests/test_codecs.py:1611: AssertionError
| Captured stdout setup
-
| module 'ctypes' has no attribute 'util'
| 1 failed, 236 passed, 2 skipped, 1 deselected in 52.57 seconds
| E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd
/<>/.pybuild/cpython3_3.7_asyncpg/build; python3.7 -m pytest
-k-test_flake8
| dh_auto_test: pybuild --test --test-pytest -i python{version} -p "3.7 3.6"
returned exit code 13
| make: *** [debian/rules:8: build] Error 25
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
Also on reproducible builds:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/asyncpg_0.17.0-1.rbuild.log.gz
https://tests.reproducible-builds.org/debian/rbuild/unstable/arm64/asyncpg_0.17.0-1.rbuild.log.gz
Helmut
Bug#912035: pymongo FTBFS: pymongo.errors.ConfigurationError: Private key doesn't match certificate: [SSL: CA_MD_TOO_WEAK] ca md too weak (_ssl.c:2779)
Source: pymongo Version: 3.7.1-1 Severity: serious Tags: ftbfs pymongo fails to build from source in unstable (but not yet in testing): | I: pybuild base:217: python2.7 setup.py test | running test | running egg_info | creating pymongo.egg-info | writing requirements to pymongo.egg-info/requires.txt | writing pymongo.egg-info/PKG-INFO | writing top-level names to pymongo.egg-info/top_level.txt | writing dependency_links to pymongo.egg-info/dependency_links.txt | writing manifest file 'pymongo.egg-info/SOURCES.txt' | reading manifest file 'pymongo.egg-info/SOURCES.txt' | reading manifest template 'MANIFEST.in' | writing manifest file 'pymongo.egg-info/SOURCES.txt' | running build_ext | building 'bson._cbson' extension | x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Ibson -I/usr/include/python2.7 -c bson/_cbsonmodule.c -o build/temp.linux-amd64-2.7/bson/_cbsonmodule.o | x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Ibson -I/usr/include/python2.7 -c bson/time64.c -o build/temp.linux-amd64-2.7/bson/time64.o | x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Ibson -I/usr/include/python2.7 -c bson/buffer.c -o build/temp.linux-amd64-2.7/bson/buffer.o | x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Ibson -I/usr/include/python2.7 -c bson/encoding_helpers.c -o build/temp.linux-amd64-2.7/bson/encoding_helpers.o | x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-z,relro -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -Wdate-time -D_FORTIFY_SOURCE=2 -g -fdebug-prefix-map=/build/python2.7-A8UpPM/python2.7-2.7.15=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 build/temp.linux-amd64-2.7/bson/_cbsonmodule.o build/temp.linux-amd64-2.7/bson/time64.o build/temp.linux-amd64-2.7/bson/buffer.o build/temp.linux-amd64-2.7/bson/encoding_helpers.o -o /<>/bson/_cbson.so | building 'pymongo._cmessage' extension | x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Ibson -I/usr/include/python2.7 -c pymongo/_cmessagemodule.c -o build/temp.linux-amd64-2.7/pymongo/_cmessagemodule.o | x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Ibson -I/usr/include/python2.7 -c bson/buffer.c -o build/temp.linux-amd64-2.7/bson/buffer.o | x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-z,relro -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -Wdate-time -D_FORTIFY_SOURCE=2 -g -fdebug-prefix-map=/build/python2.7-A8UpPM/python2.7-2.7.15=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 build/temp.linux-amd64-2.7/pymongo/_cmessagemodule.o build/temp.linux-amd64-2.7/bson/buffer.o -o /<>/pymongo/_cmessage.so | Traceback (most recent call last): | File "setup.py", line 405, in | **extra_opts | File "/usr/lib/python2.7/dist-packages/setuptools/__init__.py", line 140, in setup | return distutils.core.setup(**attrs) | File "/usr/lib/python2.7/distutils/core.py", line 151, in setup | dist.run_commands() | File "/usr/lib/python2.7/distutils/dist.py", line 953, in run_commands | self.run_command(cmd) | File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command | cmd_obj.run() | File "setup.py", line 130, in run | result = runner.run(suite) | File "/<>/test/__init__.py", line 708, in run | setup() | File "/<>/test/__init__.py", line 691, in setup | client_context.init() | File "/<>/test/__init__.py", line 307, in init | self._init_client() | File "/<>/test/__init__.py", line 216, in _init_client | self.client = self._connect(host, port, **_SSL_OPTIONS) | File
Bug#912034: python-tblib FTBFS with python3.7: doctests fail
Source: python-tblib
Version: 1.3.2-2
Severity: serious
Tags: ftbfs
python-tblib fails to build from source in unstable. A doctest fails
when run under python3.7:
| I: pybuild base:217: cd /<>/.pybuild/cpython3_3.7_tblib/build;
python3.7 -m pytest -vv tests /<>/README.rst
| = test session starts
==
| platform linux -- Python 3.7.1, pytest-3.6.4, py-1.6.0, pluggy-0.6.0 --
/usr/bin/python3.7
| cachedir: ../../../.pytest_cache
| rootdir: /<>, inifile: setup.cfg
| collecting ... collected 1 item
|
| ../../../README.rst::README.rst FAILED
[100%]
|
| === FAILURES
===
| _ [doctest] README.rst
_
| 155 ...
| 156 >>> len(s3) > 1
| 157 True
| 158
| 159 Unpickling
| 160 ~~
| 161
| 162 ::
| 163
| 164 >>> pickle.loads(s1)
| Expected:
| (<...Exception'>, Exception('fail',), )
| Got:
| (, Exception('fail'), )
|
| /<>/README.rst:164: DocTestFailure
| === short test summary info
| FAIL ../../../README.rst::README.rst
| === 1 failed in 0.01 seconds
===
| E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd
/<>/.pybuild/cpython3_3.7_tblib/build; python3.7 -m pytest -vv
tests {dir}/README.rst
| dh_auto_test: pybuild --test -i python{version} -p "3.7 3.6" returned exit
code 13
| make[1]: *** [debian/rules:11: override_dh_auto_test] Error 25
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:8: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
Helmut
Bug#873085: bsd-finger does not trap errors from ./configure
Hi Christoph, On Fri, Oct 26, 2018 at 06:29:50PM +0200, Christoph Biedl wrote: > Helmut Grohne wrote... > > > The debian policy section 4.6 requires that when build commands fail, > > the build should abort. In case bsd-finger's ./configure aborts, the > > error is ignored and the build attempts to continue potentially > > resulting in a broken package. Adding "set -e; " (as suggested by the > > policy) before the conditional fixes this issue. > > I doubt this is sufficient. There are squences like > > |echo 'no' > |echo 'Compiler '"$CC"' does not exist or cannot compile C; try > another.' > |rm -f __conftest* > +exit > > that rather should exit nonzero as fixed in > > https://sources.debian.org/patches/netkit-tftp/0.17-21/875885.patch/ The link is presently 500, but I agree with the overall idea. > Also I reckon all packages that use a configure "This file was generated > by confgen version 2" are affected from this issue. Do you agree this > applies to > > biff > linux-ftpd > linux-ftpd-ssl > netkit-bootparamd > netkit-ftp > netkit-ftp-ssl > netkit-ntalk > netkit-rsh > netkit-rusers > netkit-rwall > netkit-rwho > netkit-telnet > netkit-telnet-ssl > > as well? > > Greetings from the Karlsruhe BSP, I actually wanted to *de*crease the RC > bug count ... I actually think the issue is even worse than you project it. There also is #911154 (netkit-ntalk misses the generator for configure). I not only agree that the policy 4.6 violation affects all these, but that the dfsg violation likely affects all of these. Now given the dfsg violation, I think the best path forward would be generating these scripts from source (fixing the dfsg violation) and then fixing the generator (fixing the policy 4.6 violation once rather than 13 times). I think we can ensure that the Karlsruhe BSP does not run out of rc bugs now. Helmut
Bug#912679: libmagickcore-6.q16-dev missing Depends: libmagickcore-6-arch-config
Package: libmagickcore-6.q16-dev Version: 8:6.9.10.14+dfsg-5 Severity: serious Justification: missing dependency Control: affects -1 + src:gem libmagickcore-6.q16-dev does not depend on libmagickcore-6-arch-config. It does depend on libmagickcore-6-headers, which depends on libmagickcore-6-arch-config, but libmagickcore-6-headers is Multi-Arch: foreign. So you get some libmagickcore-6-arch-config and not necessarily one with matching architecture. The dependency is too weak. When building gem, this can become fatal: | /bin/bash ../../libtool --tag=CXX --mode=compile aarch64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I../../src -I../../src -Wdate-time -D_FORTIFY_SOURCE=2 -DGEM_VERSION_CODENAME='""Debian/1:0.93.3-18""' -DPD -I/usr/include/pd -fopenmp -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -fopenmp -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -fopenmp -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -I/usr/include/aarch64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 -I/usr/include/aarch64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 -I/usr/include/aarch64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -freg-struct-return -O3 -falign-loops -falign-functions -falign-jumps -funroll-loops -ffast-math -c -o gem_imageMAGICK_la-imageMAGICK.lo `test -f 'imageMAGICK.cpp' || echo './'`imageMAGICK.cpp | libtool: compile: aarch64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I../../src -I../../src -Wdate-time -D_FORTIFY_SOURCE=2 -DGEM_VERSION_CODENAME=\"\"Debian/1:0.93.3-18\"\" -DPD -I/usr/include/pd -fopenmp -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -fopenmp -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -fopenmp -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -I/usr/include/aarch64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 -I/usr/include/aarch64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 -I/usr/include/aarch64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -freg-struct-return -O3 -falign-loops -falign-functions -falign-jumps -funroll-loops -ffast-math -c imageMAGICK.cpp -fPIC -DPIC -o .libs/gem_imageMAGICK_la-imageMAGICK.o | In file included from /usr/include/ImageMagick-6/Magick++/Include.h:14, | from /usr/include/ImageMagick-6/Magick++.h:10, | from imageMAGICK.cpp:21: | /usr/include/ImageMagick-6/magick/magick-config.h:21:10: fatal error: magick/magick-baseconfig.h: No such file or directory | #include "magick/magick-baseconfig.h" | ^~~~ | compilation terminated. | make[3]: *** [Makefile:613: gem_imageMAGICK_la-imageMAGICK.lo] Error 1 | make[3]: Leaving directory '/<>/plugins/imageMAGICK' | make[2]: *** [Makefile:489: all-recursive] Error 1 | make[2]: Leaving directory '/<>/plugins' | make[1]: *** [Makefile:598: all-recursive] Error 1 | make[1]: Leaving directory '/<>' | dh_auto_build: make -j1 returned exit code 2 | make: *** [debian/rules:82: binary-arch] Error 2 | dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 The dependency from libmagickcore-6-headers on libmagickcore-6-arch-config should be removed. It is always too week and needs to be lifted to a higher level. What can be done though is flipping the dependency. Have libmagickcore-6-arch-config depend on libmagickcore-6-headers and then replace any dependency on libmagickcore-6-headers with one on libmagickcore-6-arch-config. That should be fine, because both packages are considered implementation detail and do not have any reverse dependencies outside imagemagick. Helmut
Bug#911912: golang-github-gin-gonic-gin FTBFS: missing Build-Depends: tzdata
Source: golang-github-gin-gonic-gin Version: 1.3.0+dfsg1-2 Severity: serious Tags: ftbfs patch golang-github-gin-gonic-gin fails to build from source when tzdata is not present in the chroot. While our autobuilders do install it (due to debootstrap installing Priority: required), it is neither essential nor build-essential. If it goes missing, tests fail: | --- FAIL: TestBindingFormForTime (0.00s) | binding_test.go:729: | Error Trace:binding_test.go:729 | binding_test.go:241 | Error: Received unexpected error: | open /usr/lib/go-1.10/lib/time/zoneinfo.zip: no such file or directory | Test: TestBindingFormForTime | binding_test.go:730: | Error Trace:binding_test.go:730 | binding_test.go:241 | Error: Not equal: | expected: 1510675200 | actual : -62135596800 | Test: TestBindingFormForTime | binding_test.go:731: | Error Trace:binding_test.go:731 | binding_test.go:241 | Error: Not equal: | expected: "Asia/Chongqing" | actual : "UTC" | | Diff: | --- Expected | +++ Actual | @@ -1 +1 @@ | -Asia/Chongqing | +UTC | Test: TestBindingFormForTime Please add "tzdata " to Build-Depends. Helmut
Bug#912239: ruby-httparty FTBFS: SSL_CTX_use_certificate: ee key too small
Source: ruby-httparty
Version: 0.16.2+dfsg1-1
Severity: serious
Tags: ftbfs
ruby-httparty fails to build from source in unstable:
|
GEM_PATH=debian/ruby-httparty/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
ruby2.5 -e gem\ \"httparty\"
|
|
┌──┐
| │ Run tests for ruby2.5 from debian/ruby-tests.rake
│
|
└──┘
|
| RUBYLIB=/<>/debian/ruby-httparty/usr/lib/ruby/vendor_ruby:.
GEM_PATH=debian/ruby-httparty/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
ruby2.5 -S rake -f debian/ruby-tests.rake
| /usr/bin/ruby2.5 /usr/bin/rspec --pattern spec/\*\*/\*_spec.rb
| /<>/spec/httparty/request/body_spec.rb:3: warning: setting
Encoding.default_external
| Run options: include {:focus=>true}
|
| All examples were filtered out; ignoring {:focus=>true}
|
| Randomized with seed 46039
|
*.#>/spec/support/ssl_test_server.rb:34
run> terminated with exception (report_on_exception is true):
| /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `initialize':
SSL_CTX_use_certificate: ee key too small (OpenSSL::SSL::SSLError)
| from /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `new'
| from /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `accept'
| from /<>/spec/support/ssl_test_server.rb:56:in
`thread_main'
| from /<>/spec/support/ssl_test_server.rb:34:in `block (2
levels) in start'
|
.#>/spec/support/ssl_test_server.rb:34
run> terminated with exception (report_on_exception is true):
| /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `initialize':
SSL_CTX_use_certificate: ee key too small (OpenSSL::SSL::SSLError)
| from /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `new'
| from /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `accept'
| from /<>/spec/support/ssl_test_server.rb:56:in
`thread_main'
| from /<>/spec/support/ssl_test_server.rb:34:in `block (2
levels) in start'
|
.#>/spec/support/ssl_test_server.rb:34
run> terminated with exception (report_on_exception is true):
| /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `initialize':
SSL_CTX_use_certificate: ee key too small (OpenSSL::SSL::SSLError)
| from /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `new'
| from /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `accept'
| from /<>/spec/support/ssl_test_server.rb:56:in
`thread_main'
| from /<>/spec/support/ssl_test_server.rb:34:in `block (2
levels) in start'
|
F#>/spec/support/ssl_test_server.rb:34
run> terminated with exception (report_on_exception is true):
| /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `initialize':
SSL_CTX_use_certificate: ee key too small (OpenSSL::SSL::SSLError)
| from /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `new'
| from /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `accept'
| from /<>/spec/support/ssl_test_server.rb:56:in
`thread_main'
| from /<>/spec/support/ssl_test_server.rb:34:in `block (2
levels) in start'
|
F#>/spec/support/ssl_test_server.rb:34
run> terminated with exception (report_on_exception is true):
| /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `initialize':
SSL_CTX_use_certificate: ee key too small (OpenSSL::SSL::SSLError)
| from /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `new'
| from /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `accept'
| from /<>/spec/support/ssl_test_server.rb:56:in
`thread_main'
| from /<>/spec/support/ssl_test_server.rb:34:in `block (2
levels) in start'
|
.#>/spec/support/ssl_test_server.rb:34
run> terminated with exception (report_on_exception is true):
| /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `initialize':
SSL_CTX_use_certificate: ee key too small (OpenSSL::SSL::SSLError)
| from /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `new'
| from /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `accept'
| from /<>/spec/support/ssl_test_server.rb:56:in
`thread_main'
| from /<>/spec/support/ssl_test_server.rb:34:in `block (2
levels) in start'
|
F#>/spec/support/ssl_test_server.rb:34
run> terminated with exception (report_on_exception is true):
| /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `initialize':
SSL_CTX_use_certificate: ee key too small (OpenSSL::SSL::SSLError)
| from /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `new'
| from /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `accept'
Bug#912241: uuagc FTBFS: error: Repeated declaration of synthesized attribute copy of nonterminal Pattern.
Source: uuagc Version: 0.9.52.1-2 Severity: serious Tags: ftbfs uuagc fails to build from source in unstable on the official buildds for any arch tried thus far: https://buildd.debian.org/status/fetch.php?pkg=uuagc=amd64=0.9.52.1-2=1538622922=0 | src-ag/Patterns.ag:22:23: error: Repeated declaration of synthesized attribute copy of nonterminal Pattern. | First definition: "src-ag/Patterns.ag"(line 22, column 23). | Other definition: "src-ag/Patterns.ag"(line 22, column 23). | src-ag/Patterns.ag:22:23: error: Repeated declaration of synthesized attribute copy of nonterminal Patterns. | First definition: "src-ag/Patterns.ag"(line 22, column 23). | Other definition: "src-ag/Patterns.ag"(line 22, column 23). ... | make: *** [/usr/share/cdbs/1/class/hlibrary.mk:147: build-ghc-stamp] Error 1 | dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 Helmut
Bug#912245: ruby-nio4r FTBFS: SSL_CTX_use_certificate: ee key too small
Source: ruby-nio4r Version: 1.2.1-1 Severity: serious Tags: ftbfs ruby-nio4r fails to build in unstable with the current openssl: | Failures: | | 1) OpenSSL::SSL::SSLSocket behaves like an NIO selectable selects readable objects | Failure/Error: ssl_peer = OpenSSL::SSL::SSLSocket.new(peer, ssl_server_context) | | OpenSSL::SSL::SSLError: |SSL_CTX_use_certificate: ee key too small | Shared Example Group: "an NIO selectable" called from ./spec/nio/selectables/ssl_socket_spec.rb:160 | # ./spec/nio/selectables/ssl_socket_spec.rb:36:in `initialize' | # ./spec/nio/selectables/ssl_socket_spec.rb:36:in `new' | # ./spec/nio/selectables/ssl_socket_spec.rb:36:in `block (2 levels) in ' | # /usr/lib/ruby/vendor_ruby/rspec/core/memoized_helpers.rb:298:in `block (2 levels) in let' | # /usr/lib/ruby/vendor_ruby/rspec/core/memoized_helpers.rb:157:in `block (3 levels) in fetch_or_store' | # /usr/lib/ruby/vendor_ruby/rspec/core/memoized_helpers.rb:157:in `fetch' | # /usr/lib/ruby/vendor_ruby/rspec/core/memoized_helpers.rb:157:in `block (2 levels) in fetch_or_store' | # /usr/lib/ruby/vendor_ruby/rspec/support/reentrant_mutex.rb:23:in `synchronize' | # /usr/lib/ruby/vendor_ruby/rspec/core/memoized_helpers.rb:156:in `block in fetch_or_store' | # /usr/lib/ruby/vendor_ruby/rspec/core/memoized_helpers.rb:155:in `fetch' | # /usr/lib/ruby/vendor_ruby/rspec/core/memoized_helpers.rb:155:in `fetch_or_store' | # /usr/lib/ruby/vendor_ruby/rspec/core/memoized_helpers.rb:298:in `block in let' | # ./spec/support/selectable_examples.rb:5:in `block (2 levels) in ' | # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:254:in `instance_exec' | # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:254:in `block in run' | # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:500:in `block in with_around_and_singleton_context_hooks' | # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:457:in `block in with_around_example_hooks' | # /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:464:in `block in run' | # /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:602:in `run_around_example_hooks_for' | # /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:464:in `run' | # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:457:in `with_around_example_hooks' | # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:500:in `with_around_and_singleton_context_hooks' | # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:251:in `run' | # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:629:in `block in run_examples' | # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:625:in `map' | # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:625:in `run_examples' | # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:591:in `run' | # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:592:in `block in run' | # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:592:in `map' | # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:592:in `run' | # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:116:in `block (3 levels) in run_specs' | # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:116:in `map' | # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:116:in `block (2 levels) in run_specs' | # /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1989:in `with_suite_hooks' | # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:111:in `block in run_specs' | # /usr/lib/ruby/vendor_ruby/rspec/core/reporter.rb:74:in `report' | # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:110:in `run_specs' | # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:87:in `run' | # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:71:in `run' | # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:45:in `invoke' | # /usr/bin/rspec:4:in `' | | 2) OpenSSL::SSL::SSLSocket behaves like an NIO selectable does not select unwritable objects | Failure/Error: ssl_peer = OpenSSL::SSL::SSLSocket.new(peer, ssl_server_context) | | OpenSSL::SSL::SSLError: |SSL_CTX_use_certificate: ee key too small | Shared Example Group: "an NIO selectable" called from ./spec/nio/selectables/ssl_socket_spec.rb:160 | # ./spec/nio/selectables/ssl_socket_spec.rb:99:in `initialize' | # ./spec/nio/selectables/ssl_socket_spec.rb:99:in `new' | # ./spec/nio/selectables/ssl_socket_spec.rb:99:in `block (2 levels) in ' | # /usr/lib/ruby/vendor_ruby/rspec/core/memoized_helpers.rb:298:in `block (2 levels) in let' | # /usr/lib/ruby/vendor_ruby/rspec/core/memoized_helpers.rb:157:in `block (3 levels) in fetch_or_store' | # /usr/lib/ruby/vendor_ruby/rspec/core/memoized_helpers.rb:157:in `fetch' | # /usr/lib/ruby/vendor_ruby/rspec/core/memoized_helpers.rb:157:in `block (2 levels) in fetch_or_store' | #
Bug#912246: ruby-cheffish FTBFS: uses unavailable default cipher DES-EDE3-CBC
Source: ruby-cheffish Version: 13.1.0-1 Severity: serious Tags: ftbfs ruby-cheffish fails to build from source in unstable: | An error occurred while loading ./spec/unit/recipe_run_wrapper_spec.rb. | Failure/Error: property :cipher, OpenSSL::Cipher.ciphers, default: "DES-EDE3-CBC" | | Chef::Exceptions::ValidationFailed: | Property cipher must be one of: "aes-128-cbc", "aes-128-cbc-hmac-sha1", "aes-128-cbc-hmac-sha256", "aes-128-ccm", "aes-128-cfb", "aes-128-cfb1", "aes-128-cfb8", "aes-128-ctr", "aes-128-ecb", "aes-128-gcm", "aes-128-ocb", "aes-128-ofb", "aes-128-xts", "aes-192-cbc", "aes-192-ccm", "aes-192-cfb", "aes-192-cfb1", "aes-192-cfb8", "aes-192-ctr", "aes-192-ecb", "aes-192-gcm", "aes-192-ocb", "aes-192-ofb", "aes-256-cbc", "aes-256-cbc-hmac-sha1", "aes-256-cbc-hmac-sha256", "aes-256-ccm", "aes-256-cfb", "aes-256-cfb1", "aes-256-cfb8", "aes-256-ctr", "aes-256-ecb", "aes-256-gcm", "aes-256-ocb", "aes-256-ofb", "aes-256-xts", "aes128", "aes128-wrap", "aes192", "aes192-wrap", "aes256", "aes256-wrap", "aria-128-cbc", "aria-128-ccm", "aria-128-cfb", "aria-128-cfb1", "aria-128-cfb8", "aria-128-ctr", "aria-128-ecb", "aria-128-gcm", "aria-128-ofb", "aria-192-cbc", "aria-192-ccm", "aria-192-cfb", "aria-192-cfb1", "aria-192-cfb8", "aria-192-ctr", "aria-192-ecb", "aria-192-gcm", "aria-192-ofb", "aria-256-cbc", "aria-256-ccm", "aria-256-cfb", "aria-256-cfb1", "aria-256-cfb8", "aria-256-ctr", "aria-256-ecb", "aria-256-gcm", "aria-256-ofb", "aria128", "aria192", "aria256", "bf", "bf-cbc", "bf-cfb", "bf-ecb", "bf-ofb", "blowfish", "camellia-128-cbc", "camellia-128-cfb", "camellia-128-cfb1", "camellia-128-cfb8", "camellia-128-ctr", "camellia-128-ecb", "camellia-128-ofb", "camellia-192-cbc", "camellia-192-cfb", "camellia-192-cfb1", "camellia-192-cfb8", "camellia-192-ctr", "camellia-192-ecb", "camellia-192-ofb", "camellia-256-cbc", "camellia-256-cfb", "camellia-256-cfb1", "camellia-256-cfb8", "camellia-256-ctr", "camellia-256-ecb", "camellia-256-ofb", "camellia128", "camellia192", "camellia256", "cast", "cast-cbc", "cast5-cbc", "cast5-cfb", "cast5-ecb", "cast5-ofb", "chacha20", "chacha20-poly1305", "des", "des-cbc", "des-cfb", "des-cfb1", "des-cfb8", "des-ecb", "des-ede", "des-ede-cbc", "des-ede-cfb", "des-ede-ecb", "des-ede-ofb", "des-ede3", "des-ede3-cbc", "des-ede3-cfb", "des-ede3-cfb1", "des-ede3-cfb8", "des-ede3-ecb", "des-ede3-ofb", "des-ofb", "des3", "des3-wrap", "desx", "desx-cbc", "id-aes128-CCM", "id-aes128-GCM", "id-aes128-wrap", "id-aes128-wrap-pad", "id-aes192-CCM", "id-aes192-GCM", "id-aes192-wrap", "id-aes192-wrap-pad", "id-aes256-CCM", "id-aes256-GCM", "id-aes256-wrap", "id-aes256-wrap-pad", "id-smime-alg-CMS3DESwrap", "rc2", "rc2-128", "rc2-40", "rc2-40-cbc", "rc2-64", "rc2-64-cbc", "rc2-cbc", "rc2-cfb", "rc2-ecb", "rc2-ofb", "rc4", "rc4-40", "rc4-hmac-md5", "seed", "seed-cbc", "seed-cfb", "seed-ecb", "seed-ofb", "sm4", "sm4-cbc", "sm4-cfb", "sm4-ctr", "sm4-ecb", "sm4-ofb"! You passed "DES-EDE3-CBC". | # ./lib/chef/resource/private_key.rb:34:in `' | # ./lib/chef/resource/private_key.rb:8:in `' | # ./lib/chef/resource/private_key.rb:7:in `' | # ./lib/chef/resource/private_key.rb:6:in `' | # ./lib/cheffish/recipe_dsl.rb:25:in `' | # ./lib/cheffish.rb:130:in `' | # ./spec/support/spec_support.rb:3:in `' | # ./spec/unit/recipe_run_wrapper_spec.rb:1:in `' | | Finished in 0.00014 seconds (files took 0.78209 seconds to load) | 0 examples, 0 failures, 16 errors occurred outside of examples | | /usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format documentation failed | ERROR: Test "ruby2.5" failed. Exiting. | dh_auto_install: dh_ruby --install /<>/debian/ruby-cheffish returned exit code 1 | make[1]: *** [debian/rules:11: override_dh_auto_install] Error 1 | make[1]: Leaving directory '/<>' | make: *** [debian/rules:7: binary] Error 2 | dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2 Looks like ruby-cheffish expects openssl to provide DES-EDE3-CBC, but that one is only available in lower case. Helmut
Bug#912247: starman FTBFS: ssl tests fail
Source: starman Version: 0.4014-2 Severity: serious Tags: ftbfs starman fails to build from source in unstable. Presumably openssl broke it: | t/ssl.t .. | Dubious, test returned 111 (wstat 28416, 0x6f00) | No subtests run | 2018/10/29-15:24:42 Starman::Server (type Net::Server::PreFork) starting! pid(13247) | Resolved [localhost]:46413 to [127.0.0.1]:46413, IPv4 | Binding to SSL port 46413 on host 127.0.0.1 with IPv4 | 2018/10/29-15:24:42 Cannot connect to SSL port 46413 on 127.0.0.1 [No such file or directory] | at line 105 in file /usr/share/perl5/Net/Server/Proto/SSL.pm | 2018/10/29-15:24:42 Received QUIT. Running a graceful shutdown | 2018/10/29-15:24:42 Worker processes cleaned up | 2018/10/29-15:24:42 Server closing! | cannot open port: 127.0.0.1:46413 at /usr/share/perl5/Test/TCP.pm line 53. | t/ssl_largebody.t | Dubious, test returned 111 (wstat 28416, 0x6f00) | No subtests run | 2018/10/29-15:24:59 Starman::Server (type Net::Server::PreFork) starting! pid(13283) | Binding to TCP port 35767 on host 127.0.0.1 with IPv4 | Setting gid to "1000 1000 4 24 29 44 111 114 115 136 142 1000" | 2018/10/29-15:24:59 Server closing! ... | Test Summary Report | --- | t/ssl.t(Wstat: 28416 Tests: 0 Failed: 0) | Non-zero exit status: 111 | Parse errors: No plan found in TAP output | t/ssl_largebody.t (Wstat: 28416 Tests: 0 Failed: 0) | Non-zero exit status: 111 | Parse errors: No plan found in TAP output | Files=13, Tests=111, 34 wallclock secs ( 0.04 usr 0.01 sys + 0.95 cusr 0.22 csys = 1.22 CPU) | Result: FAIL | dh_auto_test: perl Build test --verbose 1 returned exit code 1 | make: *** [debian/rules:7: build] Error 2 | dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 Helmut
Bug#912249: ruby-file-tail FTBFS: test_tail_change2(FileTailTest) fails
Source: ruby-file-tail Version: 1.1.1-2 Severity: serious Tags: ftbfs ruby-file-tail fails to build from source in unstable. | Failure: test_tail_change2(FileTailTest) | /<>/tests/file_tail_test.rb:353:in `test_tail_change2' | 350: end | 351: appender.join | 352: logger.join | => 353: assert_equal(110, lines.size) | 354: assert reopened | 355: assert_equal 10, @in.lineno | 356: end | <110> expected but was | <20> | | diff: | ? 110 | ? 2 | === | | Finished in 24.813629151 seconds. | --- | 20 tests, 70 assertions, 1 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications | 95% passed | --- | 0.81 tests/s, 2.82 assertions/s | ERROR: Test "ruby2.5" failed. Exiting. | dh_auto_install: dh_ruby --install /<>/debian/ruby-file-tail returned exit code 1 | make: *** [debian/rules:16: binary] Error 1 | dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2 Helmut
Bug#912253: ruby-protected-attributes: FTBFS reliably (failing tests)
Source: ruby-protected-attributes Version: 1.1.3-2 Severity: serious Tags: ftbfs ruby-protected-attributes fails to build from source reliably now. On my system as well as on reproducible builds, I consistently see the very same three failures: | Finished in 0.447334s, 453.7994 runs/s, 1629.6540 assertions/s. | | 1) Error: | AccessibleParamsWrapperTest#test_accessible_wrapped_keys_from_matching_model: | Mocha::NotInitializedError: Mocha methods cannot be used outside the context of a test | /<>/test/accessible_params_wrapper_test.rb:67:in `test_accessible_wrapped_keys_from_matching_model' | | 2) Error: | AccessibleParamsWrapperTest#test_derived_wrapped_keys_from_matching_model: | Mocha::NotInitializedError: Mocha methods cannot be used outside the context of a test | /<>/test/accessible_params_wrapper_test.rb:41:in `test_derived_wrapped_keys_from_matching_model' | | 3) Error: | AccessibleParamsWrapperTest#test_derived_wrapped_keys_from_specified_model: | Mocha::NotInitializedError: Mocha methods cannot be used outside the context of a test | /<>/test/accessible_params_wrapper_test.rb:54:in `block in test_derived_wrapped_keys_from_specified_model' | /<>/test/accessible_params_wrapper_test.rb:9:in `with_default_wrapper_options' | /<>/test/accessible_params_wrapper_test.rb:53:in `test_derived_wrapped_keys_from_specified_model' | | 203 runs, 729 assertions, 0 failures, 3 errors, 0 skips | rake aborted! | Command failed with status (1): [ruby -w -I"test" "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/accessible_params_wrapper_test.rb" "test/attribute_sanitization_test.rb" "test/mass_assignment_security/black_list_test.rb" "test/mass_assignment_security/permission_set_test.rb" "test/mass_assignment_security/sanitizer_test.rb" "test/mass_assignment_security/strong_parameters_fallback_test.rb" "test/mass_assignment_security/white_list_test.rb" "test/mass_assignment_security_test.rb" "test/test_helper.rb" -v] | | Tasks: TOP => default | (See full trace by running task with --trace) | ERROR: Test "ruby2.5" failed. Exiting. | dh_auto_install: dh_ruby --install /<>/debian/ruby-protected-attributes returned exit code 1 | make: *** [debian/rules:6: binary] Error 1 | dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2 Helmut
Bug#912236: ruby-ffi-rzmq FTBFS: SSL_CTX_use_certificate: ee key too small
Source: ruby-ffi-rzmq Version: 2.0.6-1 Severity: serious Tags: ftbfs ruby-ffi-rzmq fails to build from source in unstable (but not in testing): | Failures: | | 1) ZMQ::Poller poll works with SSLSocket | Failure/Error: server = OpenSSL::SSL::SSLSocket.new(s, ctx) | | OpenSSL::SSL::SSLError: |SSL_CTX_use_certificate: ee key too small | # ./spec/poll_spec.rb:254:in `initialize' | # ./spec/poll_spec.rb:254:in `new' | # ./spec/poll_spec.rb:254:in `block (3 levels) in ' | | Finished in 2.72 seconds (files took 0.12738 seconds to load) | 443 examples, 1 failure | | Failed examples: | | rspec ./spec/poll_spec.rb:240 # ZMQ::Poller poll works with SSLSocket | | ERROR: Test "ruby2.5" failed. Exiting. | dh_auto_install: dh_ruby --install /<>/debian/ruby-ffi-rzmq returned exit code 1 | make: *** [debian/rules:15: binary] Error 1 | dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2 Looks like more openssl fallout. Helmut
Bug#912255: python-asdf FTBFS if some webserver is listening to localhost:80
Source: python-asdf
Version: 2.1.0-1
Severity: serious
Tags: ftbfs
python-asdf fails to build from source if some webserver is listening to
localhost:80. The Debian policy prohibits doing so in section 4.9. The
access is only legitimate if python-asdf starts the web server.
| === FAILURES
===
| _ test_invalid_source
__
|
| small_tree = {'not_shared': array([10, 9, 8, 7, 6, 5, 4, 3, 2, 1],
dtype=uint8), 'science_data': array([0., 1., 2., 3., 4., 5., 6., 7., 8., 9.]),
'skipping': array([0., 2., 4., 6., 8.]), 'subset': array([3., 4., 5., 6.])}
|
| def test_invalid_source(small_tree):
| buff = io.BytesIO()
|
| ff = asdf.AsdfFile(small_tree)
| ff.write_to(buff)
|
| buff.seek(0)
| with asdf.AsdfFile.open(buff) as ff2:
| ff2.blocks.get_block(0)
|
| with pytest.raises(ValueError):
| ff2.blocks.get_block(2)
|
| with pytest.raises(IOError):
| > ff2.blocks.get_block("http://127.0.0.1/;)
|
| asdf/tests/test_low_level.py:141:
| _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_
| asdf/block.py:643: in get_block
| source, do_not_fill_defaults=True)
| asdf/asdf.py:364: in open_external
| do_not_fill_defaults=do_not_fill_defaults)
| asdf/asdf.py:778: in open
| ignore_missing_extensions=ignore_missing_extensions)
| _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_
|
| cls =
| self = , fd = 'http://127.0.0.1/'
| uri = None, mode = 'r', validate_checksums = False, do_not_fill_defaults =
True
| _get_yaml_content = False, _force_raw_types = False
| strict_extension_check = False, ignore_missing_extensions = False
|
| @classmethod
| def _open_impl(cls, self, fd, uri=None, mode='r',
|validate_checksums=False,
|do_not_fill_defaults=False,
|_get_yaml_content=False,
|_force_raw_types=False,
|strict_extension_check=False,
|ignore_missing_extensions=False):
| """Attempt to open file-like object as either AsdfFile or
AsdfInFits"""
| if not is_asdf_file(fd):
| try:
| # TODO: this feels a bit circular, try to clean up. Also
| # this introduces another dependency on astropy which may
| # not be desireable.
| from . import fits_embed
| return fits_embed.AsdfInFits._open_impl(fd, uri=uri,
| validate_checksums=validate_checksums,
|
ignore_version_mismatch=self._ignore_version_mismatch,
| extensions=self._extensions,
| strict_extension_check=strict_extension_check,
|
ignore_missing_extensions=ignore_missing_extensions,
| _extension_metadata=self._extension_metadata)
| except ValueError:
| pass
| raise ValueError(
| > "Input object does not appear to be ASDF file or FITS with " +
| "ASDF extension")
| E ValueError: Input object does not appear to be ASDF file or FITS
with ASDF extension
|
| asdf/asdf.py:682: ValueError
| - Captured stdout call
-
| Downloading http://127.0.0.1/ [Done]
| === warnings summary
===
|
.pybuild/cpython3_3.7_asdf/build/asdf/tests/test_suite.py::test_reference_file[reference_files/1.0.0/complex.asdf]
| /usr/lib/python3/dist-packages/numpy/core/numeric.py:2321: RuntimeWarning:
overflow encountered in absolute
| return less_equal(abs(x-y), atol + rtol * abs(y))
|
| -- Docs: http://doc.pytest.org/en/latest/warnings.html
| === 1 failed, 319 passed, 12 skipped, 4 xfailed, 1 warnings in 4.60 seconds
| E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd
/<>/.pybuild/cpython3_3.7_asdf/build; python3.7 -m pytest
| dh_auto_test: pybuild --test --test-pytest -i python{version} -p "3.7 3.6"
returned exit code 13
| make: *** [debian/rules:8: build] Error 25
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
Helmut
Bug#911944: neovim FTBFS: tests fail
Hi James, On Sat, Nov 10, 2018 at 09:29:42AM -0500, James McCoy wrote: > On Fri, Oct 26, 2018 at 03:30:54PM +0200, Helmut Grohne wrote: > > neovim fails to build from source in unstable. > > > > | [ ERROR ] 6 errors, listed below: > > | [ ERROR ] test/functional/helpers.lua @ 743: after_each > > | test/helpers.lua:289: crash detected (see above) > > | > > | stack traceback: > > | test/helpers.lua:289: in function 'check_cores' > > | test/functional/helpers.lua:748: in function > > > > I haven't seen these on the buidds or locally. The only issue I've been > seeing, aside from some flaky tests, I've filed upstream[0]: > > [ RUN ] mbyte utf_char2bytes: FAIL > test/unit/helpers.lua:731: (string) ' > not enough memory' > > stack traceback: > test/unit/helpers.lua:747: in function 'itp_parent' > test/unit/helpers.lua:774: in function > > [0]: https://github.com/neovim/neovim/issues/9212 Thank you for looking into this. I've no clue what the error is supposed to mean either. In any case, I just retried and I can still reliably reproduce the failure. > > Looking to reproducible builds, the failure pattern looks quite random: > > > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/neovim.html > > I'm not actually sure what's happening in the most recent builds there. > I don't see any explicit error output, just the testing stopping earlier > than it should. That looks quite different now. Earlier, I've seen the same errors there. > The armhf & ppc64el buildd failures I can't reproduce on the > porterboxes, although the latter is likely another flaky test. armhf likely needs to be retried as the build timed out. > > However, in local builds for unstable/amd64 in sbuild, I didn't get a > > single successful build. > > If it's not any of the mentioned failures, then some more information > would be useful, as I have quite the opposite behavior locally. What information are you interested in? I also tried in pbuilder and there I only got the utf_char2bytes failure, not the ones with check_cores. This hints that something about my build environment is fishy. If I understand correctly, my user's resource limits "leak" through sbuild while they don't pass through pbuilder. Would limiting the number of processes or virtual memory be a plausible explanation for the failures? So it might be useful to reduce the scope of this bug to the utf_char2bytes failure and the armhf/ppc64el buildd failures. Helmut
Bug#913500: cargo FTBFS: rustc segfaults
Source: cargo Version: 0.31.0-3 Severity: serious Tags: ftbfs rustc segfauls while building cargo. For instance on amd64: https://buildd.debian.org/status/fetch.php?pkg=cargo=amd64=0.31.0-3=1541763110=0 | process didn't exit successfully: `rustc --crate-name build_script_build /<>/vendor/serde/build.rs --color never --crate-type bin --emit=dep-info,link -C debuginfo=2 --cfg 'feature="default"' --cfg 'feature="std"' -C metadata=b12582fccfc6f2bd -C extra-filename=-b12582fccfc6f2bd --out-dir /<>/target/debug/build/serde-b12582fccfc6f2bd -L dependency=/<>/target/debug/deps --cap-lints warn` (signal: 11, SIGSEGV: invalid memory reference) Helmut
Bug#910307: elixir-lang FTBFS: tests fail: Killed
Source: elixir-lang
Version: 1.6.5-1
Severity: serious
Tags: ftbfs
elixir-lang fails to build from source in sbuild on unstable/amd64. A
build log ends with:
| 5) test translates :supervisor_bridge progress (Logger.TranslatorTest)
| test/logger/translator_test.exs:751
| Assertion with =~ failed
| code: assert capture_log(:info, fn ->
| trap = Process.flag(:trap_exit, true)
| {:ok, pid} = :supervisor_bridge.start_link(MyBridge, :normal)
| receive() do
| {:EXIT, ^pid, _} ->
| :ok
| end
| Process.flag(:trap_exit, trap)
| end) =~ ~r"\\[info\\] Child of Supervisor
#PID<\\d+\\.\\d+\\.\\d+> \\(Logger\\.TranslatorTest\\.MyBridge\\) started\nPid:
#PID<\\d+\\.\\d+\\.\\d+>\nStart Call:
Logger.TranslatorTest.MyBridge.init\\(:normal\\)\n"
| left: ""
| right: ~r/\[info\] Child of Supervisor #PID<\d+\.\d+\.\d+>
\(Logger\.TranslatorTest\.MyBridge\) started\nPid: #PID<\d+\.\d+\.\d+>\nStart
Call: Logger.TranslatorTest.MyBridge.init\(:normal\)\n/
| stacktrace:
|test/logger/translator_test.exs:752: (test)
|
| =INFO REPORT 4-Oct-2018::17:13:59.511859 ===
| application: logger
| exited: stopped
| type: temporary
| .
|
| Finished in 0.7 seconds (0.3s on load, 0.4s on tests)
| 1 doctest, 109 tests, 5 failures
|
| Randomized with seed 183795
| make[2]: *** [Makefile:92: test_logger] Error 1
| make[2]: Leaving directory '/<>'
| dh_auto_test: make -j18 test returned exit code 2
| epmd: Thu Oct 4 17:13:59 2018: got KILL_REQ - terminates normal
|
| Killed
| make[1]: *** [debian/rules:12: override_dh_auto_test] Error 2
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:9: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
It also fails on the reproducible builds infrastructure:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/elixir-lang_1.6.5-1.rbuild.log.gz
Helmut
Bug#910316: erlang-ranch FTBFS: src/ranch_ssl.erl:128: ssl:ssl_accept/2: deprecated; use ssl:handshake/2 instead
Source: erlang-ranch Version: 1.3.0-1 Severity: serious Tags: ftbfs erlang-ranch fails to build from source using sbuild on unstable/amd64. A build log ends with: |debian/rules override_dh_auto_build | make[1]: Entering directory '/<>' | make SKIP_DEPS=yes | make[2]: Entering directory '/<>' | DEPEND ranch.d | ERLC ranch.erl ranch_acceptor.erl ranch_acceptors_sup.erl ranch_app.erl ranch_conns_sup.erl ranch_listener_sup.erl ranch_protocol.erl ranch_server.erl ranch_ssl.erl ranch_sup.erl ranch_tcp.erl ranch_transport.erl | compile: warnings being treated as errors | src/ranch_ssl.erl:128: ssl:ssl_accept/2: deprecated; use ssl:handshake/2 instead | make[3]: *** [erlang.mk:5069: ebin/ranch.app] Error 1 | make[2]: *** [erlang.mk:4872: app] Error 2 | make[2]: Leaving directory '/<>' | make[1]: *** [debian/rules:10: override_dh_auto_build] Error 2 | make[1]: Leaving directory '/<>' | make: *** [debian/rules:7: build] Error 2 | dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 This is also seen by reproducible builds: https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/erlang-ranch_1.3.0-1.rbuild.log.gz Helmut
Bug#910318: factory-boy FTBFS: RuntimeError: generator raised StopIteration
Source: factory-boy
Version: 2.8.1-2
Severity: serious
Tags: ftbfs
factory-boy fails to build from source in sbuild on unstable/amd64. A
build ends with:
| ==
| ERROR: test_reset_after_end (tests.test_utils.ResetableIteratorTestCase)
| --
| Traceback (most recent call last):
| File "/<>/factory/utils.py", line 158, in __iter__
| value = next(self.iterator)
| StopIteration
|
| The above exception was the direct cause of the following exception:
|
| Traceback (most recent call last):
| File "/<>/tests/test_utils.py", line 343, in
test_reset_after_end
| self.assertRaises(StopIteration, next, iterator)
| File "/usr/lib/python3.7/unittest/case.py", line 743, in assertRaises
| return context.handle('assertRaises', args, kwargs)
| File "/usr/lib/python3.7/unittest/case.py", line 178, in handle
| callable_obj(*args, **kwargs)
| RuntimeError: generator raised StopIteration
|
| --
| Ran 381 tests in 0.311s
|
| FAILED (errors=2, skipped=30)
| Test failed:
| Creating test database for alias 'default'...
| Creating test database for alias 'replica'...
| Destroying test database for alias 'default'...
| Destroying test database for alias 'replica'...
| Creating test database for alias 'default'...
| Creating test database for alias 'replica'...
| Destroying test database for alias 'default'...
| Destroying test database for alias 'replica'...
| Creating test database for alias 'default'...
| Creating test database for alias 'replica'...
| Destroying test database for alias 'default'...
| Destroying test database for alias 'replica'...
| Creating test database for alias 'default'...
| Creating test database for alias 'replica'...
| Destroying test database for alias 'default'...
| Destroying test database for alias 'replica'...
| error: Test failed:
| make[1]: *** [debian/rules:33: override_dh_auto_test] Error 1
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:12: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
Wild guess: It didn't test on Python 3.7 earlier.
Helmut
Bug#910306: electrum FTBFS: mv: cannot stat 'debian/python3-electrum/usr/share/applications': No such file or directory
Source: electrum Version: 3.1.3-1 Severity: serious electrum fails to build from source in sbuild on unstable/amd64. A build ends with: | mkdir -p debian/electrum/usr/bin debian/electrum/usr/share | mv debian/python3-electrum/usr/bin debian/electrum/usr | mv debian/python3-electrum/usr/share/applications \ |debian/electrum/usr/share | mv: cannot stat 'debian/python3-electrum/usr/share/applications': No such file or directory | make[1]: *** [debian/rules:22: override_dh_auto_install] Error 1 | make[1]: Leaving directory '/<>' | make: *** [debian/rules:9: binary] Error 2 | dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2 Helmut
Bug#910305: easyloggingpp FTBFS: configure: error: cannot find install-sh, install.sh, or shtool in build-aux ".."/build-aux
Source: easyloggingpp
Version: 9.96.5+dfsg-1
Severity: serious
Tags: ftbfs
easyloggingpp fails to build from source in unstable. The build log
essentially looks like this:
| dpkg-buildpackage: info: source package easyloggingpp
| dpkg-buildpackage: info: source version 9.96.5+dfsg-1
| dpkg-buildpackage: info: source distribution unstable
| dpkg-buildpackage: info: source changed by Stephen Kitt
| dpkg-source --before-build .
| dpkg-buildpackage: info: host architecture amd64
| debian/rules clean
| dh clean
|dh_clean
| debian/rules binary
| dh binary
|dh_update_autotools_config
|dh_autoreconf
|debian/rules override_dh_auto_configure
| make[1]: Entering directory '/<>'
| mkdir gtest-build
| cp -a /usr/src/googletest/googletest gtest-source
| dh_auto_configure -Dgtest-source -Bgtest-build
| cd gtest-build && ../gtest-source/configure --build=x86_64-linux-gnu
--prefix=/usr --includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking
| configure: WARNING: unrecognized options: --disable-maintainer-mode
| configure: error: cannot find install-sh, install.sh, or shtool in build-aux
".."/build-aux
| cd gtest-build && tail -v -n \+0 config.log
| ==> config.log <==
| ...
| dh_auto_configure: cd gtest-build && ../gtest-source/configure
--build=x86_64-linux-gnu --prefix=/usr --includedir=\${prefix}/include
--mandir=\${prefix}/share/man --infodir=\${prefix}/share/info --sysconfdir=/etc
--localstatedir=/var --disable-silent-rules
--libdir=\${prefix}/lib/x86_64-linux-gnu
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking returned exit code 1
| make[1]: *** [debian/rules:13: override_dh_auto_configure] Error 2
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:7: binary] Error 2
| dpkg-buildpackage: error: debian/rules binary subprocess returned exit status
2
This looks like some dependency changed possibly debhelper or autoconf
or something.
It's also seen by reproducible builds, but only in unstable:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/easyloggingpp_9.96.5+dfsg-1.rbuild.log.gz
Helmut
Bug#910311: elpy FTBFS randomly: test elpy-promise-wait-should-return-early-for-resolved-promise fails
Source: elpy
Version: 1.24.0-1
Severity: serious
Tags: ftbfs
elpy fails to build from source randomly. A build log contains:
| Test elpy-promise-wait-should-return-early-for-resolved-promise backtrace:
| (if (unwind-protect (setq value-774 (apply fn-772 args-773)) (setq f
| (let (form-description-776) (if (unwind-protect (setq value-774 (app
| (let ((value-774 (quote ert-form-evaluation-aborted-775))) (let (for
| (let ((fn-772 (function elpy-promise-resolved-p)) (args-773 (list pr
| (let ((start-time (current-time)) (promise (elpy-promise nil))) (run
| (progn (let ((start-time (current-time)) (promise (elpy-promise nil)
| (progn (setq elpy-rpc-timeout 100) (progn (let ((start-time (current
| (unwind-protect (progn (setq elpy-rpc-timeout 100) (progn (let ((sta
| (save-current-buffer (set-buffer temp-buffer) (unwind-protect (progn
| (let ((temp-buffer (generate-new-buffer " *temp*"))) (save-current-b
| (progn (let ((temp-buffer (generate-new-buffer " *temp*"))) (save-cu
| (unwind-protect (progn (let ((temp-buffer (generate-new-buffer " *te
| (let ((old-process-list (process-list)) (old-buffer-list (buffer-lis
| (lambda nil (let ((old-process-list (process-list)) (old-buffer-list
| ert--run-test-internal([cl-struct-ert--test-execution-info [cl-struc
| ert-run-test([cl-struct-ert-test elpy-promise-wait-should-return-ear
| ert-run-or-rerun-test([cl-struct-ert--stats t [[cl-struct-ert-test e
| ert-run-tests(t #[385 "\306^B\307\"\203G^@\211\211G\310U\203^T^@\211@\20
| ert-run-tests-batch(nil)
| ert-run-tests-batch-and-exit()
| eval((ert-run-tests-batch-and-exit))
| command-line-1(("-l" "package" "--eval" "(add-to-list 'package-direc
| command-line()
| normal-top-level()
| Test elpy-promise-wait-should-return-early-for-resolved-promise condition:
| (ert-test-failed
| ((should
|(elpy-promise-resolved-p promise))
| :form
| (elpy-promise-resolved-p
|[*elpy-promise* nil nil # nil])
| :value nil))
|FAILED 222/362 elpy-promise-wait-should-return-early-for-resolved-promise
This happened in sbuild on unstable/amd64.
The reproducible builds folks encountered the same failure in one out of
two builds using pbuilder:
https://tests.reproducible-builds.org/debian/logs/unstable/amd64/elpy_1.24.0-1.build2.log.gz
https://tests.reproducible-builds.org/debian/rbuild/unstable/arm64/elpy_1.24.0-1.rbuild.log.gz
https://tests.reproducible-builds.org/debian/rbuild/unstable/armhf/elpy_1.24.0-1.rbuild.log.gz
For amd64, only the second build failed. When I tried it locally in
sbuild, three builds succeeded. I have no clue how the failure is
caused, but it is evident that it is not broken infrastructure.
Helmut
Bug#910312: erlang-jose FTBFS: erlang:get_stacktrace/0: deprecated; use the new try/catch syntax for retrieving the stack backtrace
Source: erlang-jose
Version: 1.8.4-3
Severity: serious
Tags: ftbfs
erlang-jose fails to build from source in sbuild on unstable/amd64. A
build log ends with:
| Compiled src/jose_server.erl
| Compiled src/jose_jwt.erl
| Compiled src/jose_sha3_keccakf1600_nif.erl
| Compiled src/jose_jwk_kty_oct.erl
| Compiled src/jose_jwk_kty_okp_ed448.erl
| src/jose_public_key.erl:44: erlang:get_stacktrace/0: deprecated; use the new
try/catch syntax for retrieving the stack backtrace
| src/jose_public_key.erl:60: erlang:get_stacktrace/0: deprecated; use the new
try/catch syntax for retrieving the stack backtrace
| src/jose_public_key.erl:84: erlang:get_stacktrace/0: deprecated; use the new
try/catch syntax for retrieving the stack backtrace
| src/jose_public_key.erl:107: erlang:get_stacktrace/0: deprecated; use the new
try/catch syntax for retrieving the stack backtrace
| src/jose_public_key.erl:122: erlang:get_stacktrace/0: deprecated; use the new
try/catch syntax for retrieving the stack backtrace
| src/jose_public_key.erl:234: erlang:get_stacktrace/0: deprecated; use the new
try/catch syntax for retrieving the stack backtrace
| Compiling src/jose_public_key.erl failed:
| DEBUG: Worker compilation failed: {{error,
| {error,[],
| [["src/jose_public_key.erl:44:
erlang:get_stacktrace/0: deprecated; use the new try/catch syntax for
retrieving the stack backtrace\n",
|"src/jose_public_key.erl:60:
erlang:get_stacktrace/0: deprecated; use the new try/catch syntax for
retrieving the stack backtrace\n",
|"src/jose_public_key.erl:84:
erlang:get_stacktrace/0: deprecated; use the new try/catch syntax for
retrieving the stack backtrace\n",
|"src/jose_public_key.erl:107:
erlang:get_stacktrace/0: deprecated; use the new try/catch syntax for
retrieving the stack backtrace\n",
|"src/jose_public_key.erl:122:
erlang:get_stacktrace/0: deprecated; use the new try/catch syntax for
retrieving the stack backtrace\n",
|"src/jose_public_key.erl:234:
erlang:get_stacktrace/0: deprecated; use the new try/catch syntax for
retrieving the stack backtrace\n"]]}},
|{source,"src/jose_public_key.erl"}}
| ERROR: compile failed while processing /<>: rebar_abort
| make[1]: *** [/usr/share/dh-rebar/make/dh-rebar.Makefile:126: rebar_compile]
Error 1
| dh_auto_build: make --no-print-directory -f
/usr/share/dh-rebar/make/dh-rebar.Makefile build returned exit code 2
| make: *** [debian/rules:11: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
Helmut
