• Re:

    From Drew Parsons@21:1/5 to Alexandre Detiste on Mon Jul 22 13:00:01 2024
    On 2024-07-22 11:40, Alexandre Detiste wrote:
    Hi Nilesh,

    I joined Astro team and took care of matplotlib rdeps there.

    I'm struggling with basemap... I don't understand how
    this multi-package with it's 3 setup.py works.
    It's the very last rdpeps that will block migration later on.

    I think it's the right time to upload to Unstable.
    ---

    matplotlib build is failing right now too.
    Salsa CI logs are truncated & useless.

    dh_sphinxdoc -O--buildsystem=pybuild
    dh_sphinxdoc: error: debian/python-matplotlib-doc/usr/share/doc/python-matplotlib-doc/html/search.html
    does not load searchindex.js
    make: *** [debian/rules:26: binary] Error 25
    dpkg-buildpackage: error: fakeroot debian/rules binary subprocess
    returned exit status 2
    I: copying local configuration
    E: Failed autobuilding of package

    Greetings


    Thanks Alexandre. Certainly I'll be happy to have matplotlib 3.8 (if
    not 3.9) in unstable, if we can live with kicking basemap out of
    testing. scipy-docs will use matplotlib-docs.

    The new basemap has pushed setup.py down into one of the subdirs. I've
    haven't looked into it deeply, but I'm wondering if it might work just
    setting appropriate PYBUILD_* variables in debian to point sourcedir at
    the new subdir containing setup.py? i.e. activating pybuild's --dir
    option. Not sure if that would mean a PYBUILD_DIR variable or something
    else. Depends on whether we can ignore the other new subdirs. I haven't
    checked for correspondence between the new and the old basemap source.

    Drew

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Emmanuel Arias@21:1/5 to Drew Parsons on Mon Jul 22 15:10:02 2024
    On Mon, Jul 22, 2024 at 12:58:49PM +0200, Drew Parsons wrote:
    On 2024-07-22 11:40, Alexandre Detiste wrote:
    Hi Nilesh,

    I joined Astro team and took care of matplotlib rdeps there.

    I'm struggling with basemap... I don't understand how
    this multi-package with it's 3 setup.py works.
    It's the very last rdpeps that will block migration later on.

    I think it's the right time to upload to Unstable.
    ---

    matplotlib build is failing right now too.
    Salsa CI logs are truncated & useless.

    dh_sphinxdoc -O--buildsystem=pybuild
    dh_sphinxdoc: error: debian/python-matplotlib-doc/usr/share/doc/python-matplotlib-doc/html/search.html
    does not load searchindex.js
    make: *** [debian/rules:26: binary] Error 25
    dpkg-buildpackage: error: fakeroot debian/rules binary subprocess
    returned exit status 2
    I: copying local configuration
    E: Failed autobuilding of package

    Greetings


    Thanks Alexandre. Certainly I'll be happy to have matplotlib 3.8 (if not 3.9) in unstable, if we can live with kicking basemap out of testing. scipy-docs will use matplotlib-docs.

    The new basemap has pushed setup.py down into one of the subdirs. I've haven't looked into it deeply, but I'm wondering if it might work just setting appropriate PYBUILD_* variables in debian to point sourcedir at the new subdir containing setup.py? i.e. activating pybuild's --dir option. Not sure if that would mean a PYBUILD_DIR variable or something else. Depends on whether we can ignore the other new subdirs. I haven't checked for correspondence between the new and the old basemap source.
    Yes, new upstream release is different, I plan work on it after DebConf.
    But, do we need remove basemap from testing?

    Drew


    --
    cheers,
    Emmanuel Arias

    ⢀⣴⠾⠻⢶⣦⠀
    ⣾⠁⢠⠒⠀⣿⡁ eamanu@debian.org
    ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: 13796755BBC72BB8ABE2AEB5 FA9DEC5DE11C63F1
    ⠈⠳⣄

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEE3lnVbvHK7ir4q61+p3sXeEcY/EFAmaeWVIACgkQ+p3sXeEc Y/EsoA/+OHfsZNfImYKkhthcQc4WI4izVk4EXe/HhP0wdrnq/8Kv5KiurREYb1sY YBJsNoUX33xYQtqAwjtUndHq/KFdN8o2qnfMcuCrwdtCzRR/hKiNSnaGztKKSjwa Lv7bWIAia3mmmdA92udgH6LsJD32km2XHm3f1xVnUh4Ui9M143r+Zd80Fp/o0agq OknkWuUmpa5xw5RHXjZvG75lnHYK0btNiSv/8lsPh5RswBG4pDc1h0JP5zNw9XEi kR/gw+A2IUmd8LU3Wx9CNS7uPBc6cNmuiZO09PN96xPWa6ydjQc+QSP5w3NyUhAm FrCoEl8IyIU5nOv+HYx9ToEx5vcEbOho37roIKXw2D0UlcvNBtEa4W79UT9QO8rY DbLX0Zo+BtGyYM6fQ0jDyUZvGYUi/N6AfKdeEke/j+Iq4CUUzS3fx+lzgFP2hsqg fbhQiu1SByhZeuLuWCNkffmVYYeQfoN8ACABe8LVzXB0NjZZNR3PRAI7EkpYPt9S sq99ZgvhoogRoGj58/9G5A/cc5yE3gl8Pw8YgysXi9fNXva5lkYhUP66YCRZCOk7 IB2ECWBrnJqfyeR/0KSJdzMbz/VT1y3VIaZhMAu5OJ7GMBkvHTJ7+wkSSRba9rGA wfV0rJieab95bQg+R1/qWM32NrQp1aKK1jX+3DIiOYJQBFn
  • From Blair Noctis@21:1/5 to Emmanuel Arias on Mon Jul 22 15:20:01 2024
    A bit nitpicking, but I hope you have noticed the (lack of) subject. An empty "Re:" feels really weird.

    On 22/07/2024 21:06, Emmanuel Arias wrote:
    On Mon, Jul 22, 2024 at 12:58:49PM +0200, Drew Parsons wrote:
    On 2024-07-22 11:40, Alexandre Detiste wrote:
    Hi Nilesh,

    I joined Astro team and took care of matplotlib rdeps there.

    I'm struggling with basemap... I don't understand how
    this multi-package with it's 3 setup.py works.
    It's the very last rdpeps that will block migration later on.

    I think it's the right time to upload to Unstable.
    ---

    matplotlib build is failing right now too.
    Salsa CI logs are truncated & useless.

    dh_sphinxdoc -O--buildsystem=pybuild
    dh_sphinxdoc: error:
    debian/python-matplotlib-doc/usr/share/doc/python-matplotlib-doc/html/search.html
    does not load searchindex.js
    make: *** [debian/rules:26: binary] Error 25
    dpkg-buildpackage: error: fakeroot debian/rules binary subprocess
    returned exit status 2
    I: copying local configuration
    E: Failed autobuilding of package

    Greetings


    Thanks Alexandre. Certainly I'll be happy to have matplotlib 3.8 (if not
    3.9) in unstable, if we can live with kicking basemap out of testing.
    scipy-docs will use matplotlib-docs.

    The new basemap has pushed setup.py down into one of the subdirs. I've
    haven't looked into it deeply, but I'm wondering if it might work just
    setting appropriate PYBUILD_* variables in debian to point sourcedir at the >> new subdir containing setup.py? i.e. activating pybuild's --dir option. Not >> sure if that would mean a PYBUILD_DIR variable or something else. Depends on >> whether we can ignore the other new subdirs. I haven't checked for
    correspondence between the new and the old basemap source.
    Yes, new upstream release is different, I plan work on it after DebConf.
    But, do we need remove basemap from testing?

    --
    Sdrager,
    Blair Noctis


    -----BEGIN PGP SIGNATURE-----

    iHUEARYKAB0WIQScTWEJ927Sl0a/hB7sV97Kb1Pv6QUCZp5bdAAKCRDsV97Kb1Pv 6UsGAP0TxWQ6Hfh+RQKDlV8c6ODU6YJuWkwXt1nh+HAiB3oJiwEA7k6dDqnGEr/q 8J9JdtLzN55uR7IAt6iDOKaW0boPRAM=
    =9W+3
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)