Re: dchanges-3.0-0: are we not to use this?
> I am in the process of building newer versions of my packages
> (to meet the beta schedule), and dchanges was, umm, problematic. It
> insisted on the new double-hyphen separators (easily fixed), and the
> architecture name as part of the file name (also fixable). Also, the
> usage message does not match internals )overide ps=blah should say
> pri=blah). Should these be bug reports, or have I managed to pick up
> an unsipported version?
Please use it and report bugs. Use -o for old filenames. This is the
first feedback, I will fix these bugs and release a new version that
dosn't know about new filenames - we couldn't decide on what they
should be or if they were really necessary.