Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod From: Sandro Tosi Newsgroups: linux.debian.maint.python Subject: Re: Making py2dsp/pypi2deb the default tool to create Python-based packages in Debian Date: Fri, 22 Jul 2022 00:00:01 +0200 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Thu Jul 21 21:50:48 2022 Old-Return-Path: X-Amavis-Spam-Status: No, score=-6.409 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DIGITS_LETTERS=1, FOURLA=0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, LDO_WHITELIST=-5, MD5_SHA1_SUM=-1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no X-Policyd-Weight: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .gmail. - helo: .mail-pg1-f179.google. - helo-domain: .google.) FROM/MX_MATCHES_HELO(DOMAIN)=-2; rate: -5.5 X-Gm-Message-State: AJIora/uaKT5IoxMze5+QgYKz+yLAv5Sx8nwbfrDOuKFoyp/s5JWlVGV CcKcihU5ncGcnZuTf/LduIvw25u4NnSDSI4+et934Wkelgg= X-Google-SMTP-Source: AGRyM1suC+dXZ/V7VHwbfRE4CWEBxkM6BeHQAibANrX8639uFbSm3UzSa2H+pr2LfYqpGy64BcT8YXKLXOLogdOkArU= X-Received: by 2002:a05:6a00:22d5:b0:52b:af2:9056 with SMTP id f21-20020a056a0022d500b0052b0af29056mr243301pfj.80.1658440231458; Thu, 21 Jul 2022 14:50:31 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Mailing-List: archive/latest/20097 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/CAB4XWXzPdi2nYF1TEqd6TO2_MW3H2G-zVe=W5_U8syF6PXFeew@mail.gmail.com Approved: robomod@news.nic.it Lines: 15 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Thu, 21 Jul 2022 17:50:05 -0400 X-Original-Message-ID: X-Original-References: Xref: csiph.com linux.debian.maint.python:14263 > Before I've sent my mail I also checked Git HEAD which was no change. there was: https://salsa.debian.org/python-team/tools/pypi2deb/-/commit/f9eda106f1514a1fff83fb3a8324817a91489879 > Are you sure thet the package version 3.20220721 contains the correct > executables? yes, i simply forgot to bump the internal version; what really matters is: does the last release fix the problem you were having? -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi