[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Real newbie ....



On 13/04/14 23:08, Tobias Frost wrote:
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

Thanks again for all your help. I deleted the pbuilder directory from /var/cache and re-created the environment. I also used dpkg -l to see what was installed. libicu48 is not in my system, but was downloaded and installed in the chroot environment during the build. It is not in the pbuilder base.tgz file. I assume the dependency was plucked out of a sword file, so I purged both of the out-of-date sword packages and dpkg -l doesn't show any at all connected with sword. My own installation of the up-to-date sword was made using 'make install' as part of the original build. I've also used the dpkg --clear-avail and --forget-old-unavail commands to try and get rid of old history.

The version of pbuilder I have is pbuilder 0.215ubuntu7 The build is marked unstable because I have built from sword svn trunk: release will be in a few days at which point I can do a stable build.

I always have a current version of Ubuntu as well as the testing version so although I'm using 14.04, I have a dual boot 13.10 installation on a separate drive. I'm going to wipe this, and do a clean install of Saucy. Then I'll make a fresh packaging environment there to get a clean build. I will put the source there and try as before.

That's unless anyone has any further suggestions.

Regards,        Barry.


Reply to: