Am Sonntag, den 13.04.2014, 21:49 +0100 schrieb Barry Drake: > On 13/04/14 20:40, Wookey wrote: > > So the simple fix is to update your pbuilder chroot, or build with > > sbuild instead (which probably involves running sbuild-createchroot to > > set up an unstable chroot for it to use (and running sbuild-update > > --keygen once to make some keys for apt to use). Each build gives you > > a nice log file showing exactly what was installed to satisfy the > > build deps, so you shoul dbe able to see which libicu version was > > installed. I've not checked anything, so it could be more subtle than > > this, but that's my first guess. > > Thanks for such an amazingly quick reply guys. I've re-initilised the > chroot environment, with no difference. My source is at: > https://www.dropbox.com/sh/urhm7iekss5a6a4/I7FveejRSd > and the packages it built are at: > https://www.dropbox.com/sh/s748z00c3zxiupp/-SdnD2xcHR > > Regards, Barry.
First remark (as you seem somehow associated with upstream): in the orig.tarball there is a .svn directory.. A good upstream does not ship them in their tarballs ;-) BTW, the changelog misses "-1" (The Debian revision). This is weird as my pbuilder refuses to build non-native packages with a native version, but yours seems more forgiving in this case... You should check if your're really on unstable :) (My pbuilder is at 0.215) (My pbuilder builds also against libicu52; so it's not the source) Best regards, Tobi > > -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1397426886.20086.9.ca...@ithilien.loewenhoehle.ip
