Hi Adam

Thanks for your email.

Since one of the conditions is that the version needs to be at least
in testing I think we should wait until Sunday to have version 3.2.0
ported instead of 3.1.7.

And thanks for your offer to help, I will probably need it ;P

Best regards!


On Fri, May 14, 2021 at 8:45 PM Adam Borowski <kilob...@angband.pl> wrote:
>
> Package: ugrep
> Version: 3.2.0+dfsg-1
> Severity: wishlist
>
> Hi!
> Could you please upload a version of ugrep to buster-bpo?
>
> To save you from having to RTFM, here's the procedure:
> * append ~bpo10+1 to version number (+2 on 2nd upload...)
> * set distribution in the new changelog entry to "buster-backports"
> * first upload of a backport needs to go through bpo-NEW, thus binaries
>   need to be included
> * bpo uploads these days go to the same queue as regular uploads
> * a version to be backported needs to be already in testing
>
> I'm not certain if DMs can upload their own packages to bpo-NEW, I think
> they can't.  As there's no requirement for a backporter to be an uploader,
> I can go through all the motions for +1 if you don't wish to bother with
> a sponsored upload the first time.
>
>
> Meow!
> -- System Information:
> Debian Release: 11.0
>   APT prefers testing-security
>   APT policy: (500, 'testing-security'), (500, 'unstable'), (500, 'testing'), 
> (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 5.10.0-6-amd64 (SMP w/4 CPU threads)
> Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
> Shell: /bin/sh linked to /usr/bin/dash
> Init: sysvinit (via /sbin/init)
>
> Versions of packages ugrep depends on:
> ii  libbz2-1.0    1.0.8-4
> ii  libc6         2.31-12
> ii  libgcc-s1     11-20210319-1
> ii  liblz4-1      1.9.3-2
> ii  liblzma5      5.2.5-2
> ii  libpcre2-8-0  10.36-2
> ii  libstdc++6    11-20210319-1
> ii  libzstd1      1.4.8+dfsg-2.1
> ii  zlib1g        1:1.2.11.dfsg-2
>
> ugrep recommends no packages.
>
> ugrep suggests no packages.
>
> -- no debconf information



-- 
Ricardo Ribalda

Reply via email to