Problem with transport lines in BridgeDB's bridge pool assignment files

There seems to be a problem with BridgeDB writing transport lines to its bridge pool assignment files:

$ grep -c transport *
2013-07-13-00-01-22:123
2013-07-13-00-30-22:200
2013-07-13-01-00-23:275
2013-07-13-01-30-22:44
2013-07-13-02-00-25:121
2013-07-13-02-30-27:198
2013-07-13-03-00-33:281
2013-07-13-03-30-29:73

Numbers shouldn't go up and down so fast.

Also, I saw Isis mention this the other day, but I'm not sure if there's already a ticket for it:

1093d197b5eab404f30806948367483ad5c7482e email ip=4 flag=stable
112f02b648f19502831103fa50715ce31f8a4a2e email ip=4 flag=stable port=443
112f02b648f19502831103fa50715ce31f8a4a2e email ip=4 flag=stable port=443 transport=obfs3,obfs2
11b3a235c05843fbc57f29a848dee6dc6a6be118 unallocated

Note the duplicate entry for 112f02b648f19502831103fa50715ce31f8a4a2e. The first line shouldn't be there, I guess.

Setting priority to major, because the currently produced bridge pool assignments won't be useful for analysis.