Thanks, i will take a look...
El 2/24/20 a las 4:24 AM, Paul Wise escribió:
> 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
>
