Package: python3-dateutil
Version: 2.8.1-6
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: cross-satisfiability
Control: affects -1 + src:389-ds-base src:abinit src:amp src:ariba src:arpys
src:astropy src:astropy-healpix src:astropy-regions src:astroscrappy
src:basemap src:beancount src:bioxtasraw src:borgbackup src:bornagain src:brian
src:cadabra2 src:calibre src:casa-formats-io src:cctbx src:cfgrib src:cnvkit
src:cpl-plugin-amber src:cpl-plugin-fors src:cpl-plugin-giraf
src:cpl-plugin-hawki src:cpl-plugin-muse src:cpl-plugin-naco
src:cpl-plugin-uves src:cpl-plugin-vimos src:cpl-plugin-visir
src:cpl-plugin-xshoo src:deap src:dioptas src:dipy src:direnv src:epigrass
src:facet-analyser src:fast-histogram src:fence-agents src:fiona src:freeart
src:freecad src:freesas src:galpy src:gammapy src:gensim src:genx src:gpaw
src:gpsd src:gr-radar src:graph-tool src:gudhi src:guiqwt src:healpy src:hinge
src:hkl src:htseq src:hyperspy src:imexam src:iminuit src:intake src:kallisto
src:libcxx-serial src:lmod src:matplotlib src:mdanalysis src:mdtraj src:meep
src:mlpack src:mrpt src:mypaint src:nipy src:numpy src:opendrop
src:openstructure src:pandas src:paraview src:photutils src:picard src:pikepdf
src:promod3 src:psd-tools src:psi4 src:pybdsf src:pycorrfit src:pydevd
src:pyerfa src:pyfai src:pygac src:pykwalify src:pymatgen src:pymca src:pyraf
src:pyregion src:pyresample src:pyrle src:pyrsistent src:pyscanfcs src:pysolid
src:pysynphot src:python-argon2 src:python-biom-format src:python-biopython
src:python-cartopy src:python-cdo src:python-clevercsv
src:python-clickhouse-driver src:python-cobra src:python-cogent src:python-cpl
src:python-cryptography src:python-csa src:python-cython-blis src:python-datrie
src:python-dicompylercore src:python-drizzle src:python-escript
src:python-fabio src:python-feather-format src:python-geotiepoints
src:python-ltfatpy src:python-memprof src:python-nacl src:python-pomegranate
src:python-pyani src:python-pybedtools src:python-pygraphviz src:python-pyproj
src:python-questplus src:python-shapely src:python-skbio src:python-sqt
src:python-thinc src:python-wordcloud src:python-xmlsec src:python-zstandard
src:pywavelets src:pyxrd src:q2-cutadapt src:q2-dada2 src:q2-metadata src:qgis
src:qiskit-terra src:qutip src:rasterio src:rdkit src:reproject src:rocketcea
src:ros-actionlib src:ros-bond-core src:ros-class-loader src:ros-collada-urdf
src:ros-common-msgs src:ros-diagnostics src:ros-dynamic-reconfigure
src:ros-geometric-shapes src:ros-geometry src:ros-geometry2
src:ros-image-common src:ros-image-pipeline src:ros-interactive-markers
src:ros-kdl-parser src:ros-laser-geometry src:ros-message-runtime
src:ros-navigation-msgs src:ros-nodelet-core src:ros-opencv-apps
src:ros-pcl-msgs src:ros-perception-pcl src:ros-random-numbers
src:ros-resource-retriever src:ros-robot-state-publisher src:ros-ros
src:ros-ros-comm src:ros-ros-comm-msgs src:ros-rosconsole
src:ros-rosconsole-bridge src:ros-roscpp-core src:ros-rospack src:ros-rviz
src:ros-std-msgs src:ros-urdf src:ros-vision-opencv src:ros2-ament-cmake
src:ros2-ament-index src:ros2-osrf-testing-tools-cpp
src:ros2-performance-test-fixture src:ros2-rcpputils src:ros2-rcutils
src:ros2-rosidl src:rpy2 src:sagemath src:sasmodels src:sasview src:scamp
src:scikit-learn src:sep src:sfepy src:silx src:skimage src:sncosmo
src:specutils src:statsmodels src:sunpy src:synphot src:tiledb-py
src:tnseq-transit src:tycho2 src:unifrac src:veusz src:vtk7 src:vtk9
src:weechat-matrix src:xrayutilities src:yade src:yt
The affected packages cannot satisfy their cross Build-Depends, because
their transitive dependency on python3-dateutil is not satisfiable. In
general, Architecture: all packages can never satisfy cross
Build-Depends unless marked Multi-Arch: foreign or annotated :native. In
this case, I think that the foreign marking is a reasonable compromise.
dateutil is a pure Python module that does not depend on any Python
extensions. Its interpreter dependency is already annotated :any and its
only module dependency (six) is already marked Multi-Arch: foreign.
Technically, the byte compiled objects are architecture-dependent, but a
foreign interpreter can import modules that lack them. Therefore, one
can argue that interfacing with python3-dateutil is entirely
architecture-independent and the foreign marking is warranted. I'm
attaching a patch for your convenience.
Helmut
diff --minimal -Nru python-dateutil-2.8.1/debian/changelog
python-dateutil-2.8.1/debian/changelog
--- python-dateutil-2.8.1/debian/changelog 2021-07-16 10:51:20.000000000
+0200
+++ python-dateutil-2.8.1/debian/changelog 2022-09-10 13:06:04.000000000
+0200
@@ -1,3 +1,10 @@
+python-dateutil (2.8.1-6.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Mark python3-dateutils Multi-Arch: foreign (Closes: #-1)
+
+ -- Helmut Grohne <hel...@subdivi.de> Sat, 10 Sep 2022 13:06:04 +0200
+
python-dateutil (2.8.1-6) unstable; urgency=medium
[ Bastian Germann ]
diff --minimal -Nru python-dateutil-2.8.1/debian/control
python-dateutil-2.8.1/debian/control
--- python-dateutil-2.8.1/debian/control 2021-07-11 01:24:07.000000000
+0200
+++ python-dateutil-2.8.1/debian/control 2022-09-10 13:06:01.000000000
+0200
@@ -16,6 +16,7 @@
Package: python3-dateutil
Architecture: all
Depends: ${python3:Depends}, ${misc:Depends}, tzdata
+Multi-Arch: foreign
XB-Python-Version: ${python3:Version}
Breaks: khal (<< 1:0.9.10-0.1~),
python3-icalendar (<< 4.0.3-2~),
