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:24 jinmei]:
 > I think creating a ticket makes sense.  I don't have a strong opinion
 > about when to work on it; I'm not insisting that should be considered
 > an immediate followup task of this one, but I'd rather see it as a bit
 > longer term task.

 OK, that's second to create on merge of this branch. I think I had some
 kind of document on how it could work already (maybe sometime around the
 previous F2F meeting). I'll have to find it.

 > Is this about that we have python/isc/cc/proto_defs.py under builddir
 > while other .py files under srcdir, and distcheck fails in unittests
 > when importing isc.cc.proto_defs?

 Done, with some minor problems. But it should be solved now.

 > And, on to the latest branch:
 >
 > '''util/python/Makefile.am'''
 >
 > - It's awkward that the new .py's need to be in EXTRA_DIST while
 >   gen_wiredata.py doesn't have to (I've read the commit log, btw).
 >   The latter is located under top_builddir:
 > {{{
 > .spec.wire:
 >       $(PYTHON) $(top_builddir)/src/lib/util/python/gen_wiredata.py -o
 $@ $<
 > }}}
 >   i.e., not under top_srcdir.  Could that be related?

 I don't think it is directly related to this, but I think it is related to
 the fact it is generated from the .in by configure. It may be that all
 these generated files are automatically put into the tarball, while the
 plain ones must be listed somewhere.

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