Bug#928450: RFS: megadown/0~20190502+git734e46f-1 [RC]
On Sat, May 04, 2019 at 04:08:32PM -0700, Lev Lazinskiy wrote:
> I am looking for a sponsor for my package "megadown"
>
> * Package name : megadown
> Version : 0~20190502+git734e46f-1
> Changes since the last upload:
>
> * New upstream release (Closes: #927462) which is an RC bug.
> * Remove patch series. Upstream swapped out python for jq. Python is no longer
> required
> * Add jq as dependency
Hi!
This is a non-maintainer upload, and you don't seem to have followed the
usual rules. Also, during a freeze, only small targetted fixes are
appropriate -- this is a bulk new upstream version. There are cases when
there's no better way than such a large upload (like Firefox and Chromium
these days), but as the patch fixing #927462 is tiny and obvious (although
I don't know if it's enough), it strongly seems the large upload is not
needed.
Thus, could you please extract (and test) just the fix? Only if that
doesn't work we could debate uploading the whole new upstream version.
Also, although a RC bug that hasn't seen maintainer response within two
weeks is eligible for a 0-day NMU, you'd still need to follow at least parts
of the procedure. Especially, the upload needs to be marked appropriately:
the first line of the changelog should say "Non-maintainer upload.", the
version needs to be .1, etc. NMUs are supposed to be small which is similar
to during-freeze updates.
(Even if such a procedure might seem like an unnecessary hurdle, it doubles
as a way to ensure you are aware what you're doing.)
Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Did ya know that typing "test -j8" instead of "ctest -j8"
⢿⡄⠘⠷⠚⠋⠀ will make your testsuite pass much faster, and fix bugs?
⠈⠳⣄⠀⠀⠀⠀
Reply to: