Re: Behavior change for Python packages built with CMake

2023-07-27 Thread Timo Röhling
Hi Adrian, * Adrian Bunk [2023-07-27 18:02]: The real problem are the unknown number of packages that are affected but don't FTBFS where this will only have an effect after the next upload or binNMU. I looked at the archive and tried to gauge the number of possibly affected packages. First, I

Re: Behavior change for Python packages built with CMake

2023-07-27 Thread Adrian Bunk
On Thu, Jul 27, 2023 at 01:49:33PM +0200, Timo Röhling wrote: >... > However, a few Debian > packages have also relied on the old, broken behavior, which is > why about 30 packages have been hit by FTBFS bugs from Lucas' latest > archive rebuild ("dh_install: error: missing files, aborting") >...

Re: Behavior change for Python packages built with CMake

2023-07-27 Thread Stefano Rivera
Hi Simon (2023.07.27_13:24:53_+) > Is "deb_system" and not "deb" the canonical thing to use here? The GNOME > team has been using "DEB_PYTHON_INSTALL_LAYOUT = deb" to work around > the corresponding issue with Meson-built packages. Historically it's always been deb. > > The patched sysconfig

Re: Behavior change for Python packages built with CMake

2023-07-27 Thread Simon McVittie
On Thu, 27 Jul 2023 at 16:33:59 +0200, Timo Röhling wrote: > > Would it make sense for debhelper to set this, either unconditionally > > or in a sufficiently new compat level, and either unconditionally or > > for the cmake and meson build systems? > > > Yes, I think that is a good idea. Should t

Re: Behavior change for Python packages built with CMake

2023-07-27 Thread Timo Röhling
* Simon McVittie [2023-07-27 14:24]: The patched sysconfig and distutils.sysconfig modules in Debian have a (somewhat poorly documented) override for package builds: set the DEB_PYTHON_INSTALL_LAYOUT environment variable to "deb_system". This is used internally by pybuild Would it make sense f

Re: Behavior change for Python packages built with CMake

2023-07-27 Thread Timo Röhling
* Enrico Zini [2023-07-27 15:51]: Are we at a situation where we can pick one and document it as an accepted standard, until some build tool will set it by default, in which case it'll only become redundant? Yes, I believe this is the case. Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭─

Re: Behavior change for Python packages built with CMake

2023-07-27 Thread Timo Röhling
* Sebastiaan Couwenberg [2023-07-27 15:30]: On 7/27/23 15:24, Simon McVittie wrote: Is "deb_system" and not "deb" the canonical thing to use here? The GNOME team has been using "DEB_PYTHON_INSTALL_LAYOUT = deb" to work around the corresponding issue with Meson-built packages. It's effectively

Re: Behavior change for Python packages built with CMake

2023-07-27 Thread Enrico Zini
On Thu, Jul 27, 2023 at 01:49:33PM +0200, Timo Röhling wrote: > TL;DR: export DEB_PYTHON_INSTALL_LAYOUT=deb_system in d/rules [...] > N.B. It looks like Meson has been affected in a similar way [2]. I have several affected packages and it wouldn't be a problem to export `DEB_PYTHON_INSTALL_LAYOUT

Re: Behavior change for Python packages built with CMake

2023-07-27 Thread Sebastiaan Couwenberg
On 7/27/23 15:24, Simon McVittie wrote: On Thu, 27 Jul 2023 at 13:49:33 +0200, Timo Röhling wrote: recently there have been two independent changes in the Python and CMake world which conspired to FTBFS a number of packages. TL;DR: export DEB_PYTHON_INSTALL_LAYOUT=deb_system in d/rules Is "de

Re: Behavior change for Python packages built with CMake

2023-07-27 Thread Simon McVittie
On Thu, 27 Jul 2023 at 13:49:33 +0200, Timo Röhling wrote: > recently there have been two independent changes in the Python and > CMake world which conspired to FTBFS a number of packages. > > TL;DR: export DEB_PYTHON_INSTALL_LAYOUT=deb_system in d/rules Is "deb_system" and not "deb" the canonica