-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi,
> On Mon, 2012-11-26 at 13:41 +0100, Dominik George wrote: > > I am looking for a sponsor for my package "couchdb". The upload would fix > > RC bug #692295. > May I ask some things? How is it your package, if you are not listed as > maintainer nor uploader? Ask the person who wrote the RFS template generator. On the other hand, it's the Debian communities package. Maybe it should say "my version xyz of package foo". If you take any offence on this, I really pity you. > Why do you NMU immediately when I'm known for quick reply? First, because I can, second, because that's what the DDs at the BSP told me to do. > Why do you ignore other fixes that I've mentioned to you in > my previous mail? That includes collation with RMs. You did not mention any fixes. You mentioned a pending upload. I thought you were referring to the pending upload of 1.2.0-2 to *wheezy*, which does not include any fix for the issue we are discussing. How about being a bit more specific next time? I also find that you failed to post any details of your fix to the BTS. Even though you may be known for "quick reply", other parties might be interested in how to fix the problem beforehand. You even may want testers for a patch before uploading it. In any case, the BTS report log lacks any hint whatsoever about your fix. > Anyway, I've included your patch in -3, even if I'm not convinced about > it. I think it would have been better to send HUP signal first, then > after a specified time send TERM signal to couchdb. Abusing SIGHUP for shutdown in my opinion is a major violation of well-estabished standards that should be discussed with upstream. In conclusion, Debian is a community-effort. I am very convinced that no single person owns any part of it, so no single person should ever take offence on someone else helping them. If you had e-mailed your own patch for the problem to the BTS right when you wrote it, also mentioning that you are about to upload it, would have both solve the problem you see *and* saved me and the fellows at the BSP quite a few hours of work. Please note that you posted your tiny little hint about some pending upload only *after* you realized that we were doing work on the issue. Please also realize that Frank and I spent almost two full days on the issue, discussing with dpkg and apt developers and shell gurus all possible ways of solving this issue in a way that does *not* violate upstream's ideas of signal handling. Although you included the fix in the end, and although you claim to be *quick* at it, please try to recognize your fellow community members' work and also try to understand if they like to get credits for it. Cheers, Nik -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQFOBAEBAgA4BQJQtHyWMRpodHRwczovL3d3dy5kb21pbmlrLWdlb3JnZS5kZS9n cGctcG9saWN5LnR4dC5hc2MACgkQWfyOHW8qgAHUjAf+MM3xHsT8l4Nv2lChyOxC urmpRYX+dZDI9BKOIBRKZHq42e7h8h6EtdPAiQ7x0wuW01hXhVcbnSmP4YR/Jbao QgaJfXbyJK641MV80tv5qZPN1K13KF3+a4PAwmrIZQpKstC6ekuC5Xm9RsTE3zi5 dzktw6DPxQU4l1v8HDKkECetJmKi2Gf40SZ8bLrW84jHg0hQn9KnEjeV8HstfIvw PKoKfFz53yRXRYH1dLyIOi1/H5TYzFzOSh2g/+ysd+jU8Gk8efspXvJE7gVP6TA/ +0toWjlPgbK8KiQmKtMAmFtq3BKA6fZybMWkXwkXG4tHDuu3r4yKexgZdBsub4mY lA== =e1CH -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
