Your message dated Wed, 19 Feb 2025 21:58:27 +0000
with message-id <[email protected]>
and subject line Bug#1090166: fixed in ripe-atlas-tools 3.1.0-0.1
has caused the Debian Bug report #1090166,
regarding ripe-atlas-tools: FTBFS: ERROR: Invalid value `None` in
intersphinx_mapping['http://docs.python.org/']. Expected a two-element tuple or
list.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1090166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1090166
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:ripe-atlas-tools
Version: 2.3.0-3
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
--------------------------------------------------------------------------------
[...]
debian/rules build
dh build --with=python3,sphinxdoc --buildsystem=pybuild
dh_update_autotools_config -O--buildsystem=pybuild
dh_autoreconf -O--buildsystem=pybuild
dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:311: python3.13 setup.py config
/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:261: UserWarning:
Unknown distribution option: 'tests_require'
warnings.warn(msg)
/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:261: UserWarning:
Unknown distribution option: 'test_suite'
warnings.warn(msg)
/usr/lib/python3/dist-packages/setuptools/dist.py:694:
SetuptoolsDeprecationWarning: The namespace_packages parameter is deprecated.
!!
********************************************************************************
[... snipped ...]
creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe
copying ripe/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe
creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas
copying ripe/atlas/__init__.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas
creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools
copying ripe/atlas/tools/cache.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools
copying ripe/atlas/tools/streaming.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools
copying ripe/atlas/tools/__init__.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools
copying ripe/atlas/tools/filters.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools
copying ripe/atlas/tools/exceptions.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools
copying ripe/atlas/tools/ipdetails.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools
copying ripe/atlas/tools/version.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools
running egg_info
writing ripe.atlas.tools.egg-info/PKG-INFO
writing dependency_links to ripe.atlas.tools.egg-info/dependency_links.txt
writing namespace_packages to ripe.atlas.tools.egg-info/namespace_packages.txt
writing requirements to ripe.atlas.tools.egg-info/requires.txt
writing top-level names to ripe.atlas.tools.egg-info/top_level.txt
reading manifest file 'ripe.atlas.tools.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
adding license file 'LICENSE'
writing manifest file 'ripe.atlas.tools.egg-info/SOURCES.txt'
/usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning:
Package 'ripe.atlas.tools.aggregators' is absent from the `packages`
configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'ripe.atlas.tools.aggregators' as an importable
package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to
distribute this
package, please make sure that 'ripe.atlas.tools.aggregators' is
explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation
page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'ripe.atlas.tools.aggregators' to be distributed and
are
already explicitly excluding 'ripe.atlas.tools.aggregators' via
`find_namespace_packages(...)/find_namespace` or
`find_packages(...)/find`,
you can try to use `exclude_package_data`, or
`include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools
documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning:
Package 'ripe.atlas.tools.commands' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'ripe.atlas.tools.commands' as an importable
package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to
distribute this
package, please make sure that 'ripe.atlas.tools.commands' is
explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation
page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'ripe.atlas.tools.commands' to be distributed and are
already explicitly excluding 'ripe.atlas.tools.commands' via
`find_namespace_packages(...)/find_namespace` or
`find_packages(...)/find`,
you can try to use `exclude_package_data`, or
`include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools
documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning:
Package 'ripe.atlas.tools.commands.measure' is absent from the `packages`
configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'ripe.atlas.tools.commands.measure' as an importable
package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to
distribute this
package, please make sure that 'ripe.atlas.tools.commands.measure' is
explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation
page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'ripe.atlas.tools.commands.measure' to be distributed
and are
already explicitly excluding 'ripe.atlas.tools.commands.measure' via
`find_namespace_packages(...)/find_namespace` or
`find_packages(...)/find`,
you can try to use `exclude_package_data`, or
`include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools
documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning:
Package 'ripe.atlas.tools.helpers' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'ripe.atlas.tools.helpers' as an importable
package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to
distribute this
package, please make sure that 'ripe.atlas.tools.helpers' is explicitly
added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation
page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'ripe.atlas.tools.helpers' to be distributed and are
already explicitly excluding 'ripe.atlas.tools.helpers' via
`find_namespace_packages(...)/find_namespace` or
`find_packages(...)/find`,
you can try to use `exclude_package_data`, or
`include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools
documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning:
Package 'ripe.atlas.tools.probes' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'ripe.atlas.tools.probes' as an importable
package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to
distribute this
package, please make sure that 'ripe.atlas.tools.probes' is explicitly
added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation
page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'ripe.atlas.tools.probes' to be distributed and are
already explicitly excluding 'ripe.atlas.tools.probes' via
`find_namespace_packages(...)/find_namespace` or
`find_packages(...)/find`,
you can try to use `exclude_package_data`, or
`include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools
documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning:
Package 'ripe.atlas.tools.renderers' is absent from the `packages`
configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'ripe.atlas.tools.renderers' as an importable
package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to
distribute this
package, please make sure that 'ripe.atlas.tools.renderers' is
explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation
page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'ripe.atlas.tools.renderers' to be distributed and are
already explicitly excluding 'ripe.atlas.tools.renderers' via
`find_namespace_packages(...)/find_namespace` or
`find_packages(...)/find`,
you can try to use `exclude_package_data`, or
`include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools
documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning:
Package 'ripe.atlas.tools.renderers.templates.reports' is absent from the
`packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'ripe.atlas.tools.renderers.templates.reports' as an
importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to
distribute this
package, please make sure that
'ripe.atlas.tools.renderers.templates.reports' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation
page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'ripe.atlas.tools.renderers.templates.reports' to be
distributed and are
already explicitly excluding
'ripe.atlas.tools.renderers.templates.reports' via
`find_namespace_packages(...)/find_namespace` or
`find_packages(...)/find`,
you can try to use `exclude_package_data`, or
`include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools
documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning:
Package 'ripe.atlas.tools.settings' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'ripe.atlas.tools.settings' as an importable
package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to
distribute this
package, please make sure that 'ripe.atlas.tools.settings' is
explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation
page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'ripe.atlas.tools.settings' to be distributed and are
already explicitly excluding 'ripe.atlas.tools.settings' via
`find_namespace_packages(...)/find_namespace` or
`find_packages(...)/find`,
you can try to use `exclude_package_data`, or
`include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools
documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning:
Package 'ripe.atlas.tools.settings.templates' is absent from the `packages`
configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'ripe.atlas.tools.settings.templates' as an
importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to
distribute this
package, please make sure that 'ripe.atlas.tools.settings.templates' is
explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation
page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'ripe.atlas.tools.settings.templates' to be
distributed and are
already explicitly excluding 'ripe.atlas.tools.settings.templates' via
`find_namespace_packages(...)/find_namespace` or
`find_packages(...)/find`,
you can try to use `exclude_package_data`, or
`include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools
documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
creating
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/aggregators
copying ripe/atlas/tools/aggregators/__init__.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/aggregators
copying ripe/atlas/tools/aggregators/base.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/aggregators
creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/commands
copying ripe/atlas/tools/commands/__init__.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/commands
copying ripe/atlas/tools/commands/alias.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/commands
copying ripe/atlas/tools/commands/base.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/commands
copying ripe/atlas/tools/commands/configure.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/commands
copying ripe/atlas/tools/commands/go.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/commands
copying ripe/atlas/tools/commands/measurement_info.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/commands
copying ripe/atlas/tools/commands/measurement_search.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/commands
copying ripe/atlas/tools/commands/probe_info.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/commands
copying ripe/atlas/tools/commands/probe_search.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/commands
copying ripe/atlas/tools/commands/report.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/commands
copying ripe/atlas/tools/commands/shibboleet.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/commands
copying ripe/atlas/tools/commands/stream.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/commands
creating
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/commands/measure
copying ripe/atlas/tools/commands/measure/__init__.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/commands/measure
copying ripe/atlas/tools/commands/measure/base.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/commands/measure
copying ripe/atlas/tools/commands/measure/dns.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/commands/measure
copying ripe/atlas/tools/commands/measure/http.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/commands/measure
copying ripe/atlas/tools/commands/measure/ntp.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/commands/measure
copying ripe/atlas/tools/commands/measure/ping.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/commands/measure
copying ripe/atlas/tools/commands/measure/sslcert.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/commands/measure
copying ripe/atlas/tools/commands/measure/traceroute.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/commands/measure
creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/helpers
copying ripe/atlas/tools/helpers/__init__.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/helpers
copying ripe/atlas/tools/helpers/colours.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/helpers
copying ripe/atlas/tools/helpers/rendering.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/helpers
copying ripe/atlas/tools/helpers/sanitisers.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/helpers
copying ripe/atlas/tools/helpers/validators.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/helpers
creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/probes
copying ripe/atlas/tools/probes/__init__.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/probes
creating
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/renderers
copying ripe/atlas/tools/renderers/__init__.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/renderers
copying ripe/atlas/tools/renderers/aggregate_ping.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/renderers
copying ripe/atlas/tools/renderers/base.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/renderers
copying ripe/atlas/tools/renderers/dns.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/renderers
copying ripe/atlas/tools/renderers/dns_compact.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/renderers
copying ripe/atlas/tools/renderers/dst_asn.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/renderers
copying ripe/atlas/tools/renderers/http.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/renderers
copying ripe/atlas/tools/renderers/ntp.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/renderers
copying ripe/atlas/tools/renderers/ping.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/renderers
copying ripe/atlas/tools/renderers/raw.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/renderers
copying ripe/atlas/tools/renderers/ssl_consistency.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/renderers
copying ripe/atlas/tools/renderers/sslcert.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/renderers
copying ripe/atlas/tools/renderers/traceroute.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/renderers
copying ripe/atlas/tools/renderers/traceroute_aspath.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/renderers
creating
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/renderers/templates/reports
copying ripe/atlas/tools/renderers/templates/reports/aggregate_ping.txt ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/renderers/templates/reports
copying ripe/atlas/tools/renderers/templates/reports/dns.txt ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/renderers/templates/reports
copying ripe/atlas/tools/renderers/templates/reports/ssl_consistency.txt ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/renderers/templates/reports
copying ripe/atlas/tools/renderers/templates/reports/sslcert.txt ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/renderers/templates/reports
creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/settings
copying ripe/atlas/tools/settings/__init__.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/settings
creating
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/settings/templates
copying ripe/atlas/tools/settings/templates/base.yaml ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/ripe/atlas/tools/settings/templates
running build_scripts
creating build/scripts-3.12
copying and adjusting scripts/aping -> build/scripts-3.12
copying and adjusting scripts/atraceroute -> build/scripts-3.12
copying and adjusting scripts/adig -> build/scripts-3.12
copying and adjusting scripts/asslcert -> build/scripts-3.12
copying and adjusting scripts/ahttp -> build/scripts-3.12
copying and adjusting scripts/antp -> build/scripts-3.12
copying and adjusting scripts/ripe-atlas -> build/scripts-3.12
changing mode of build/scripts-3.12/aping from 644 to 755
changing mode of build/scripts-3.12/atraceroute from 644 to 755
changing mode of build/scripts-3.12/adig from 644 to 755
changing mode of build/scripts-3.12/asslcert from 644 to 755
changing mode of build/scripts-3.12/ahttp from 644 to 755
changing mode of build/scripts-3.12/antp from 644 to 755
changing mode of build/scripts-3.12/ripe-atlas from 644 to 755
/usr/bin/make -C docs html
make[2]: Entering directory '/<<PKGBUILDDIR>>/docs'
sphinx-build -b html -d _build/doctrees . _build/html
Running Sphinx v8.1.3
loading translations [en]... done
making output directory... done
Converting `source_suffix = '.rst'` to `source_suffix = {'.rst':
'restructuredtext'}`.
ERROR: Invalid value `None` in intersphinx_mapping['http://docs.python.org/'].
Expected a two-element tuple or list.
Configuration error:
Invalid `intersphinx_mapping` configuration (1 error).
make[2]: *** [Makefile:53: html] Error 2
make[2]: Leaving directory '/<<PKGBUILDDIR>>/docs'
make[1]: *** [debian/rules:15: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:10: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
--------------------------------------------------------------------------------
The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:
https://people.debian.org/~sanvila/build-logs/202412/
About the archive rebuild: The build was made on virtual machines from AWS,
using sbuild and a reduced chroot with only build-essential packages.
If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.
If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.
Thanks.
--- End Message ---
--- Begin Message ---
Source: ripe-atlas-tools
Source-Version: 3.1.0-0.1
Done: Alexandre Detiste <[email protected]>
We believe that the bug you reported is fixed in the latest version of
ripe-atlas-tools, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Alexandre Detiste <[email protected]> (supplier of updated ripe-atlas-tools
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Wed, 19 Feb 2025 21:59:39 +0100
Source: ripe-atlas-tools
Architecture: source
Version: 3.1.0-0.1
Distribution: unstable
Urgency: medium
Maintainer: Apollon Oikonomopoulos <[email protected]>
Changed-By: Alexandre Detiste <[email protected]>
Closes: 1018615 1090166
Changes:
ripe-atlas-tools (3.1.0-0.1) unstable; urgency=medium
.
* Non-maintainer Upload.
* Switch to DebHelper 13
* Fix watchfile for new GitHub API
* New upstream version 3.1.0
* Replace python3-nose by python3-pytest, enable most tests
(Closes: #1018615)
* Set Rules-Requires-Root: no
* Disable InterSphinx example (Closes: #1090166)
Checksums-Sha1:
8c1054430f05816c7201889fa2e205812bea8093 2269 ripe-atlas-tools_3.1.0-0.1.dsc
5598fffab16952c63b459854ce58579d4c5c224c 489188
ripe-atlas-tools_3.1.0.orig.tar.gz
3d8bd225c1b80da8421d8b1a82bb4f71d32afc09 4620
ripe-atlas-tools_3.1.0-0.1.debian.tar.xz
4a7e1a78fc44281c86e728787bab37c4838160ad 9188
ripe-atlas-tools_3.1.0-0.1_source.buildinfo
Checksums-Sha256:
4a0bb0069509c078d88bbf9ac1e7d0087a164b2d5e01d2214aa95d582cfe39ad 2269
ripe-atlas-tools_3.1.0-0.1.dsc
769dc5066f36e31bf25c4b37576489565221f89615739b3cbf91f1c25cea400a 489188
ripe-atlas-tools_3.1.0.orig.tar.gz
a3f327cb4703348110057bee0490b4b62c03bee9f2791d1a211da032e05f743d 4620
ripe-atlas-tools_3.1.0-0.1.debian.tar.xz
d761b94e01c2c55a64ff623523052db1730df6409a02d9daec3e649206c231d8 9188
ripe-atlas-tools_3.1.0-0.1_source.buildinfo
Files:
789b73677ddc126b1a05ecc6dc13fd52 2269 net optional
ripe-atlas-tools_3.1.0-0.1.dsc
fbe9dda11edb63a79de4b7a9c4b6b9e8 489188 net optional
ripe-atlas-tools_3.1.0.orig.tar.gz
7fcf863cc4b731fad650865cdd4c8c9c 4620 net optional
ripe-atlas-tools_3.1.0-0.1.debian.tar.xz
f01947d521d8faccd9802c0f93fca4bb 9188 net optional
ripe-atlas-tools_3.1.0-0.1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCgAvFiEEj23hBDd/OxHnQXSHMfMURUShdBoFAme2T20RHHRjaGV0QGRl
Ymlhbi5vcmcACgkQMfMURUShdBrIJg//SSA8fVdmAxbKhNZaqbO6U82+lz+umxXW
2xKUKYrwKxe2OwnZseZ/tdBY3XMlN80yy2xuKXmIqEt8H694OgTWLBgdcQuyCQwW
ElOD0iq0WI8j+stNSkQXBvwlRf7T8HyYTRB7yPv7FVbGXT5S9FmXVkO5vLZAY3Co
aA4AEyGH9LpKPRKBd9ysRt1Oer7gZovxHM/e7jOgZekFxbCDE0iISOnKCiYqd5TJ
JOe/94NcbqKHN3dlZrT7swH1oo65trdKnHiyvjNcWKuduiDJBAF3iQL+LegwaPqY
bkRiIucktQSleUY0nf4+9JIYI6yfsmNoDimUO/RRsnzSMQOFCZ5sD9PHhs28wIQR
YbPG5Acp4OyrSzDuPxhvQPTbIlIGUZadsITtVR/qCJhc+e//M591/mzLIUN/i9P1
c0s1qXNJBHeUvpo7vh/qiv1sGsgZqcfjshBmiIS2J7zDzPbyQs8CSjcAoMOJezDk
Sxmndd8SyodFByqbpS1QQ2nwmcwoo5Eh4SPUEmlZmpUyxdlf61geMMHarWgM/xDW
kWC4utatMKvIwY+pr4t/X3dpgnRWizwusJd2TUxRrDz7NWROOnjSpwPCUXd1yOV0
f2Ryv46e6n1rrSnmEAQVBKaLxJP9zedjQjrd+NtZJl0zZDE8mMPMvPLJoLvvXEpN
RrbzfJsojUE=
=lIHf
-----END PGP SIGNATURE-----
pgpzckz0eYX9k.pgp
Description: PGP signature
--- End Message ---
