Re: (unfortunately) more BIRD-2.0.0 woes ...