2006/10/27, Martin Guy <[EMAIL PROTECTED]>:
I am building for the forthcoming armel architecture, and I too needed to add an arch to the control file. Is there any reason not to simply make this "any" rather than have to change it every time a new arch is made? None of the mainline arches are missing, and a huge selection of unofficial ones is present.
I presume the reason is that there is (or was) one architecture for which nbd-client failed to build, and control file syntax does not support e.g. Architecture: any !arm The db4.[234] series gets round lack of java support on arm and others by simply specifying Architecture: any for the packages, modifying the rules file to exclude the impossible builds and letting the final dpackaging harmlessly warn dpkg-genchanges: warning: package libdb4.4-java in control file but not in files list This seems less painful that getting a new bug report every time a new arch is created Bless M -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
