Comment 9 for bug 934096

If you're running oneiric you should be able to install a more recent bzr from the daily builds ppa:

https://launchpad.net/~bzr/+archive/daily

> About the assumptions of the filename changes. I have looked at the uscan code, and in some (exotic) situations the filename is
> indeed changed (to prevent some illegal filenames). I cannot see a way of getting notified about a filename change. Should we >
> look into adding this information for the XML output (ie modifying uscan), or let bzr-builddeb check all know filename possibilities > (in a correct order)? The first is most robust, but the latter is 'easier' (as we do not have to patch uscan and get it accepted)...
It looks like the <target> element can be used to find the filename that was created locally, so I don't think that would really require patching of uscan.

Another alternative would indeed be to create an empty directory somewhere and then assume that just make uscan put the file there. That seems fairly robust too, but is a bit more ugly than just looking at the --dehs output.

What do you think?