• Re: basemap

    From Emmanuel Arias@21:1/5 to Alexandre Detiste on Sat Aug 3 01:30:02 2024
    Hi,

    On Thu, Aug 01, 2024 at 09:14:01AM +0200, Alexandre Detiste wrote:
    Le lun. 22 juil. 2024, 12:59, Drew Parsons <dparsons@debian.org> a crit :

    On 2024-07-22 11:40, Alexandre Detiste

    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.


    Done.

    matplotlib 3.9 can be uploaded to experimental to see what next breaks elsewhere.


    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


    If the upstream tarball is really 3 projects duct-taped together we could maybe import it in 3 different sources packages. The mk-orig-tgz would be a tad complicated, but build would be easy again. That needs checking.
    It could be a good option. I will take it after DebConf24 + 1w. I spent
    some time here trying to fix both RC bugs, but seems it's better package
    new upstream release version, but it will need some effort.

    If someone made some work or is doing it, please let me know to
    duplicate effort.

    Thanks!

    Cheers,
    Emmanuel

    Greetings

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

    iQIzBAABCgAdFiEEE3lnVbvHK7ir4q61+p3sXeEcY/EFAmataoAACgkQ+p3sXeEc Y/H5tg/+M78ja/d64o788yzbxLoGvCO2lahoI2IY+jJ6F2GeKCggyOr6cTcsVcOz RmL+QDc9gi7snY08QaD4kWwyF8s9Bcc0iWZCt1lWZgfR2clOFG/4oaBQ1WAIvl9u b26dzC8lBH2cyPr+JcRxgJ/YL+VRd9LztJRWYwtEdYXjU+vhrcY20iF7/pfRJ+AT LugXsGeDwgt4T2BPmPx1Oer46bG/0GPmVfvIXjc1EIJAHqQNOQrNScHhLR8hJ9ZD AiiKqqzvT4vYEuaB8S94j+uSmBnk+bM5CjQWUcC0ERK+JHtgvWwEqYXFXoelQKe5 fE7PAiVfUNbD2aGosH0RJut3pCi9TvSzNKrJPUEskdGGrbFBn7KG8FrEDT53Rl5/ /5yMk1GAkzGLaO/egSrNYeObRj9PnY1xHQIRUfEr5jubdsqku+HJT/6csz5nZazr xDljeI+2+5bMwlDk4pwJgJAB3UQ1/fi1UJDfb+v5ptUQd2POU+CEEURkOOo6E/LK 9KDabRLIMD2C5p0FAw3OCfxhCL5TITRuFED88rUxVu8R9IqdwbXMCAhu40rtABsU CKgPVaUXIbhSp87KjUOOd9sqab6z6d7TtrrzcyazB3fOFnc4Uxw1fETLwmzROUIc sj5j1YFa/VygFl7nOSdh01k/Fj4bfvjeGspDc5Da5SSxe0mL9pw=
    =LM7P
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andreas Tille@21:1/5 to All on Fri Aug 16 16:40:01 2024
    Am Thu, Aug 01, 2024 at 09:14:01AM +0200 schrieb Alexandre Detiste:
    If the upstream tarball is really 3 projects duct-taped together we could maybe import it in 3 different sources packages. The mk-orig-tgz would be a tad complicated, but build would be easy again. That needs checking.

    Sorry for my late reply - I did not read this list for some time.
    I think the mk-orig-tgz does not need to be that complicated. I imagine
    we could add
    Files-Excluded: OTHER_PROJECT1_DIR
    OTHER_PROJECT2_DIR
    into each d/copyright and by doing so excluding stuff we do not want.

    I havn't checked the actual package but wanted to throw in that idea.

    Kind regards
    Andreas.

    --
    https://fam-tille.de

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Emmanuel Arias@21:1/5 to Andreas Tille on Fri Aug 30 19:10:01 2024
    Just to let you know I started to work on this

    In debian/experimental branch [0]

    [0] https://salsa.debian.org/python-team/packages/basemap/-/tree/debian/experimental?ref_type=heads


    On Fri, Aug 16, 2024 at 04:30:37PM GMT, Andreas Tille wrote:
    Am Thu, Aug 01, 2024 at 09:14:01AM +0200 schrieb Alexandre Detiste:
    If the upstream tarball is really 3 projects duct-taped together we could maybe import it in 3 different sources packages. The mk-orig-tgz would be a tad complicated, but build would be easy again. That needs checking.

    Sorry for my late reply - I did not read this list for some time.
    I think the mk-orig-tgz does not need to be that complicated. I imagine
    we could add
    Files-Excluded: OTHER_PROJECT1_DIR
    OTHER_PROJECT2_DIR
    into each d/copyright and by doing so excluding stuff we do not want.

    I havn't checked the actual package but wanted to throw in that idea.

    Kind regards
    Andreas.

    --
    https://fam-tille.de


    --
    cheers,
    Emmanuel Arias

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

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

    iQIzBAABCgAdFiEEE3lnVbvHK7ir4q61+p3sXeEcY/EFAmbR/I4ACgkQ+p3sXeEc Y/E9sw/8DIGrqU9SxceBaCHqQyy9MFYy5yC69TYpAT/8PJWj+q5hN2VeNOnhzUpc 0vF53mEaPcouVPxwN4JiO3DvHRjjorfE9jX1NdGnlqvHOwDon2mGrT/xSU4eiFJj BHYmjtPsoTKuJklnt6FV5ZmZ+MWzZENcboYIN65GGHUBHBHRvd4YOXKRB0QtiFMg f+5XCt1a9dsgs++BPmL3pKDj856jdlGU7Ic/ik4vLhLtgQA0EUHGfi7V8CntmP/0 YO7LWavB4lZK91QHWSGZCPHCfl4Avj8R9KGGykd0M8Nz270aFmNUxIxEEzLTb2Sn FGzoLZCFSv3IdCMQfRnoc4iVIOu53btjMyO2bI9Y0g5lnIpKU5aGM8lVaZEw6/R3 bhuEmXFlBWn/UeBA4szUKeN2hvElyEOU3LITZKSn3w7CMcKV8tcUavosCq1HdhxK +MCZbaEjzcAPLuqMAuma2GW4UxBTPUa3m7XhicSrHFsuZJg4Z2AfF0Nv2JsD3J5j oYN3gpaT72kn5NuHEaXn5FqojRzt+iWRpfSuWIbF9gV7f0kR3MjswEWXs5Euqrz2 FvM/SrM/K/jxQNKEsjxrq7Hw+NbZNoN+NBksPtVIS/xP9yKfsyjigC50SM5ntOU0 bwRWzPep2apFPinlfo+LtqofDe6KEVDkeb/zc9QMr5yahR4