Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod From: Dirk Eddelbuettel Newsgroups: linux.debian.maint.python Subject: Need a hand with tiledb-python Date: Tue, 10 May 2022 13:20:01 +0200 Message-ID: X-Mailbox-Line: From debian-python-request@lists.debian.org Tue May 10 11:13:52 2022 Old-Return-Path: X-Amavis-Spam-Status: No, score=-6.292 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.248, LDO_WHITELIST=-5, MURPHY_DRUGS_REL8=0.02, RCVD_IN_DNSWL_NONE=-0.0001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -5.5 X-Gm-Message-State: AOAM532kkyEvZHfkf8a4wBGBk5GQub3jjNB4NLCIR9lFvPenAOUbL/m/ IEDn3xo/d9R9vmNp7S6fM46AqJkih54= X-Google-SMTP-Source: ABdhPJyGhFGuBKWuIibZSnZSqJaRjzIuKQk/VYZYQWUlWyJAcRxWyqpxGYFOtBhSMF5RGNibQrR+ZA== X-Received: by 2002:a05:620a:371d:b0:6a0:237c:abb with SMTP id de29-20020a05620a371d00b006a0237c0abbmr15141026qkb.685.1652181214751; Tue, 10 May 2022 04:13:34 -0700 (PDT) Sender: robomod@news.nic.it MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: VM 8.2.0b under 27.1 (x86_64-pc-linux-gnu) X-Mailing-List: archive/latest/19922 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/25210.18653.837226.804742@rob.eddelbuettel.com Approved: robomod@news.nic.it Lines: 32 Organization: linux.* mail to news gateway X-Original-Cc: Dirk Eddelbuettel , Adam Cecile X-Original-Date: Tue, 10 May 2022 06:13:33 -0500 X-Original-Message-ID: <25210.18653.837226.804742@rob.eddelbuettel.com> X-Original-Sender: Dirk Eddelbuettel Xref: csiph.com linux.debian.maint.python:14097 Hi all, I look after the 'tiledb' (a C++ library) package and the 'tiledb-r' package. I also effectively maintain 'tiledb-python' but I am running into some issues there. I do know a little bit of Python and have (co-)maintained two or three packages there for decades but this one stumps me. Larger context is that that upstream is fairly heavy user of Conda and used to a lot of explicit version pinning. This creates issues for us here as the build wants to leave the chroot/pbuilder to match those pins. Adam (CC'ed) who set this up initially already patched some calls out (for example sphinx docs are now local). The 'delicate' bit is that I actually work at TileDB ;-) and don't want to have a fight over the upstream choice (so I didn't bug my colleague yet). Upstream use is upstream use, but Debian packaging also has its rules. The packaging is at https://salsa.debian.org/python-team/packages/tiledb-py (and for historical reasons I also have one at https://salsa.debian.org/edd/tiledb-py which it is behind) and I would *really* appreciate it if someone could take a look. I tried patching requirements_dev.txt and misc/requirements_wheel.txt but am apparently out of my depth here. I reached out to Adam (CC'ed) but he is busy too. We all know how it goes. Please CC me on follow-ups as I am not subscribed to debian-python. Thanks, Dirk -- dirk.eddelbuettel.com | @eddelbuettel | edd@debian.org