Bug#706514: RFS: dcraw/9.17-1
2013/7/12 Oliver Sander <sander@igpm.rwth-aachen.de>:
> I kind of knew these rules, but it's good to now the details anyway.
>
> Problem is, I don't understand how much these rules apply to me, since
> the actual upload to unstable will not be done by me. That case is
> not covered by the text.
It does not matter, who "physically" uploads the package e.g. sponsors it.
In this case you are the author of changes. I would upload it into, for example,
14-DAY queue, if:
1) you will continue to maintain it;
2) original maintainer will not react.
3) the package technically be OK.
>> I was thinking, you want to (co-)maintain the package (CC-ing
>> original maintainer again).
>
>
> I do consider doing so, but so far I have not even managed to get
> anything uploaded at all. (no offense)
I usually upload the package, even there are some minor problems,
which would be good to fix. But from my point of view, the current
status of the package is not enough good to be uploaded in Debian.
Please, fix "patch-issues". Patch should be minimal and clear. if you do
not understand, what the patch does - just remove it and check the
package functionality. I pointed already the problems with .badpixels
and gpg_key file.
Also it is very important to decide, whether you want to (co)-maintain
the package. If not - who will fix the possible problems after the uploading
of new version?
@Steve, please, clarify, whether you want to maintain the package further.
Cheers,
Anton
Reply to: