-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi,
I've just had a report of a build error (for amaya-5.3-2) which I've been unable to to reproduce. (No idea why it won't build, but that's not relevant here). I think I've solved it with a minor change to the patch file, but my question is - should it now be amaya-5.3-3? It seems the right thing to do, however for all those people who never experienced the problem it will mean an unnecessary rebuild - which is tedious. Nothing has changed except for build process. Any comments? My view is that the rebuild will have to happen, since the version number has to change. But I think it's an interesting case. Damian Steer -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (Darwin) Comment: Processed by Mailcrypt 3.5.6 and Gnu Privacy Guard <http://www.gnupg.org/> iD8DBQE8quf9AyLCB+mTtykRAsrvAKC1AZCsLfFAzgQ5sOw5zpS19G+psACcD4t1 0nmyQzvG4eB1Qc/yVGZBs7U= =Y/Aa -----END PGP SIGNATURE----- _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
