[Pkg-shinken-maint] Comments regarding shinken-mod-auth-cfg-password_2.0.1-1_amd64.changes
Mathieu Parent (Debian)
sathieu at debian.org
Mon Sep 15 09:52:37 UTC 2014
2014-09-15 9:47 GMT+02:00 Thorsten Alteholz <alteholz at debian.org>:
> Hi Mathieu,
> On Sun, 14 Sep 2014, Mathieu Parent (Debian) wrote:
>> Going this way will break our current workflow (and also, uscan and
>> git-buildpackage don't support well multiple orig-tarballs). The
>> schedule of those modules are not coordinated.
> hmm, this is sad.
>> Also, can you show us, which nodejs package is combined? I took a
>> random one which is rather small (node-which, 3.5kB).
> Recently node-ms, node-prr, node-mv and some others have been rejected
> because of their size.
> There has been some discussion about regrouping in . I think currently
> work on combined node-packages is still in progress so none has passed NEW
I also prefer regrouping when possible.
Can you explain what are the exact requirements? no small source
packages or no small binary packages? What are the reasons?
I've read the thread. Nothing shows a solution to multiple upstreams
and gbp workflow. See also what Andrew Kelley said .
I already maintain 141 packages, I can't do things manually.
So please, don't block those packages, until
- uscan supports for multiple tarballs (#531321)
- git-import-orig supports for multiple tarballs (#561071, and
- uscan status shown well in qa page and Debian maintainer dashboard
- optionaly #561072 for git-import-dsc
More information about the Pkg-shinken-maint