BIND 10 #1924: Msgq undeliverable notifications

[BIND 10 Development]

#1924: Msgq undeliverable notifications
-------------------------------------+-------------------------------------
            Reporter:  vorner        |                        Owner:
                Type:  task          |  jinmei
            Priority:  medium        |                       Status:
           Component:  msgq          |  reviewing
            Keywords:                |                    Milestone:
           Sensitive:  0             |  Sprint-20130219
         Sub-Project:  Core          |                   Resolution:
Estimated Difficulty:  6             |                 CVSS Scoring:
         Total Hours:  0             |              Defect Severity:  N/A
                                     |  Feature Depending on Ticket:  msgq-
                                     |  ng
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Changes (by vorner):

 * owner:  vorner => jinmei


Comment:

 Hello

 Replying to [comment:21 jinmei]:
 > First off, it would be helpful if you refer to other original comments
 > with a response of whether or not it's addressed (and if necessary,
 > why), or at least with a summary sentence that would read "I believe
 > I've addressed all other points".  If none of these were commented, I
 > cannot be sure if the revise is ongoing (but the ticket was returned
 > to me to peek into it) or is supposed to be complete.  Also, I cannot
 > be sure if some points are not addressed it was intentional or just
 > overlooked.

 Sorry for the misunderstanding. I thought such thing is implicit, if the
 comment doesn't say otherwise, everything should have been addressed. So,
 everything not included below should be handled.

 > That said...I expect (or hope) we'll clarify these points and revisit
 > the msgq system at a more fundamental way, and, with that assumption,
 > I wouldn't argue on this point in the context of this ticket.

 I hope we get to it soon too. But I'm not sure at which opportunity. Do
 you think it makes sense to create some kind of ticket for it and try to
 push it to a sprint?

 However, I discovered a problem. The python file is generated into
 builddir in distcheck, which is different than the srcdir. And python
 insists all the files are in the same directory where the `__init__.py`
 file lives. Would you have an idea how to solve this in an elegant way
 (eg. not by copying all the files into the builddir, for example).

-- 
Ticket URL: <http://bind10.isc.org/ticket/1924#comment:23>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development