| | --7iMSBzlTiPOCCT2k | Content-Type: text/plain; charset=us-ascii | Content-Disposition: inline | Content-Transfer-Encoding: quoted-printable | | On Thu, Mar 02, 2006 at 07:27:04PM +0200, Jari Aalto wrote: | > Package: svn-buildpackage | > Version: 0.6.14 | > Severity: serious | | > Given situation: | | > # svn-buildpackage .... =20 | > ... | > dh_clean=20 | > make[1]: Leaving directory `/usr/src/net/deb/debian/bbweather/bbweath= | er' | > E: Resolve them manually before continueing | | > E: found unresolved issues:=20 | | > ? .pc/bbweather.cpp | > ? debian/.pc | | > The files marked with (?) should not be considered a fatal error and | > interrupt the build process. Many times there are extra files used | > by the developer to arrange the build as he sees fit for several tools | > like: | | > - Another version control software for temporary chnages | > (mixing svn with distributed VCS) | > - Using patch tools like quilt | > - Making random changes like backup copies to *.orig *.bak etc. | | > The error condition prevents using all these measures to help the | > developer to constrct the debian package. | | So use the --svn-ignore-new option to svn-buildpackage.
Hi steve, I'm wondering if there is reasoning why this is the other way round? In compilers, the rope is tightened with options like -Wall for more restrictive checks. Perhaps it could be option: --svn-exit-unknown instead? Jari -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
