I don't think this removal was such a good idea. Certainly, cleaning up the archive is a valid goal, but breaking dozens of packages along the way is not. The submitter of this bug did not offer the affected packages any upgrade path. Some of the affected packages have reached maintenance stages where it's unreasonable for the upstream maintainer to make a new release just to upgrade automake. Note that re-automaking all the affected packages as part of the packaging is likely to create larger diffs and will thus increase the size of the archives, perhaps more than what is saved by removing automake1.6.
automake1.6 did not have any bugs and did not burden anyone (except the maintainer?), but he did not respond to my offer to orphan the package first. I suggest that to unbreak the situation automake1.6 be reuploaded and removed after all build dependencies are gone. Would this be acceptable? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
