Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod From: Paul Wise Newsgroups: linux.debian.maint.python Subject: Re: Where can I find packages that need a maintainer? Date: Mon, 24 Feb 2020 08:30:01 +0100 Message-ID: References: X-Original-To: Pablo Mestre X-Mailbox-Line: From debian-python-request@lists.debian.org Mon Feb 24 07:24:30 2020 Old-Return-Path: X-Amavis-Spam-Status: No, score=-6.5 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, LDO_WHITELIST=-5, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001] 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-wr1-f67.google. - helo-domain: .google.) FROM/MX_MATCHES_HELO(DOMAIN)=-2; rate: -5.5 X-Google-Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=9OH9PKsa/6q3WMl2Xv1z8B/g472vFsNa4afR7PhQlTk=; b=suaqjQ1L5Ya+gYfug+Vy0OfnaBnzapwvK/51Kcl/ocOCIdgBSHB9xgZydihaqNBR3N XSjFSvugy1fyIRSorfBtg0owRM+YvP/2FzV9FP/ef2Vfrlqr4UvMJPuM1bdHoPXWg79t rrZSBlBViDHd7Npr49K1VUgHnov/582tq+Xs8Og51TLKqOScZffydRetmTSxp9HyQrwJ gyZKADOtaGOs4cdH+y3cFom/7nbs6gupEyfvhBkUKnTRPhgQAxzVqogNT+ynERw01BVe NO/8Mu05Bp8ACw3Q0xWZZUYlwsExSZigLkM+q2fYqWneCYjtWaXr0WQFFFC4y+i9+jIu /XRw== X-Gm-Message-State: APjAAAVipLs3YwxUOnoowEUBc4Dt33PPrlU9pdiLO/6rrrJnpLZScfGg i0g/mV/C0SdzaonPiUg6elaxSF8Ufa4hVaCOerpEw4LG X-Google-SMTP-Source: APXvYqwkzEggi6dl+/PhbF6eNo4aILBxJGN3NjBWd8ShYQtk+uc9W9KANImr0Y5emZVWKrk+Mcr9j+G5HAY6TJx/dGw= X-Received: by 2002:adf:d4c7:: with SMTP id w7mr66925781wrk.101.1582529056957; Sun, 23 Feb 2020 23:24:16 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Mailing-List: archive/latest/17958 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/CAKTje6HRMm=C3jAKMUjX__s3=GZ29xxtFMKW0ap+Nj-ByGYZhg@mail.gmail.com Approved: robomod@news.nic.it Lines: 38 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-python@lists.debian.org X-Original-Date: Mon, 24 Feb 2020 07:24:05 +0000 X-Original-Message-ID: X-Original-References: Xref: csiph.com linux.debian.maint.python:12324 On Thu, Feb 13, 2020 at 1:25 AM Pablo Mestre wrote: > I recently started as a maintainer of a package for Debian which is > currently awaiting approval to be reintroduced into the repositories. [1] In case you weren't aware, there are some extra steps when reintroducing packages: https://www.debian.org/doc/manuals/developers-reference/pkgs.html#reintroducing-pkgs Principally this is about reopening bugs closed by the removal and then triaging them and closing any fixed in the new version. https://www.debian.org/Bugs/Developer#closing Last time I needed to do this, I ran this hacky shell one-liner: bts $(for bug in $(curl 'https://bugs.debian.org/cgi-bin/pkgreport.cgi?archive=both;src=colortest-python' | pandoc -f html -t plain --wrap none | grep -B1 -F +rm | grep -o \#[0-9]\\+ | tr -d \#) ; do echo -n "unarchive $bug , reopen $bug , "; done) For your package it gives this command: bts unarchive 753281 , reopen 753281 , unarchive 936320 , reopen 936320 , unarchive 782208 , reopen 782208 , unarchive 890074 , reopen 890074 , See-also this request for making it easier to do this: https://bugs.debian.org/949125 -- bye, pabs https://wiki.debian.org/PaulWise