Next time I would appreciate it if you followed section 5.11.1 of the Developers Reference a bit more closely.

You did submit a bug report, atleast the snmp dependency was one that actually did not already have a report submitted on; however giving less than 24 hours before you uploaded not only the NMU but the patch to the BTS hardly gives time for a response from the developer. Submitting the patch within 24 hours and not uploading the NMU after giving some time for a response would have been better.

   5.11.1 states the following order, please abid by it:

      1) File a bug report *Hurray you did that atleast*
      2) Wait a few days for a response. File a 'patch' if no response
3) Wait a few more days if you get no answer, then mail announcing the intent to NMU 4) Upload your package to DELAYED/7-day (not 3-DAY, not 5-DAY, *7-DAY*)

If you had checked all the other bugs you closed and read them you would have noticed that I was working on the 2.0.9 packaging already as it had been released. I had been working on 2.0.8 when the C++ ABI transition hit the mirrors. You would have also noticed I respond to just about every bug report filed, so not getting a response from a bug filed within 24 hours isn't a problem.

I won't go on about the fact that some of the items in the bugs you closed were not addressed in your NMU to begin with and would have been closed without being addressed.

Checking the QA mia-history would have also showed I wasn't MIA as well; however you made no attempt, other than the one bug report to, contact me prior to doing the NMU.

   Regards,
   Jeremy

Luk Claes wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi

Attached the patch for the version I uploaded to DELAYED-3. If you want
to override this NMU, then please upload a fixed version before this
upload reaches the archive.

Cheers

Luk
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFDOrOv5UTeB5t8Mo0RAroWAKCJJKSp8C0rxiRy5hodedzYL1DUDgCeOEFU
SHa/IFchE6QIA22kbkjHRuQ=
=kq6O
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to