Re: Bitpim on Debian Etch/stable, also Motorola e815

"A. F. Cano" <[email protected]> writes:

> Thank you! Got it and installed it with no problem (dpkg -i).

Great; you're welcome.

> However, it has the same problem as the native Etch version:

I'm sorry to hear that. :-/

> There were no complaints about the library, unless the error is caused
> by the etch version of the library.

It shouldn't be, but you can verify that by rebuilding it yourself:
additionally fetch

http://people.debian.org/~ucko/bitpim_1.0.5.dfsg.1.orig.tar.gz
http://people.debian.org/~ucko/bitpim_1.0.5.dfsg.1-1~bpo40%2b1.diff.gz
http://people.debian.org/~ucko/bitpim_1.0.5.dfsg.1-1~bpo40%2b1.dsc

and run the following commands:

    dpkg-source -x bitpim_1.0.5.dfsg.1-1~bpo40*1.dsc
    cd bitpim-1.0.5.dfsg.1
    debuild -B -us -uc

> In the changes file for the latest test version
> (bitpim_1.0.6.20080304_i386.deb) there was a note about
> something relating to certain motorola phones being fixed, so
> maybe that's it, but then someone claims that version 1.0.1 (IIRC)
> worked with this phone in Windows...

>From what I gather, BitPim is chronically prone to timeout issues on
Motorola phones, with fixes not always being as broadly applicable as
hoped. :-/  (I haven't encountered them firsthand as I've been using
an LG phone all along; I don't specifically endorse either brand,
though.)

> If you can make an etch backport of the test version, I'll be glad
> to test that.  Or you can tell me how to build a package from the
> svn tree.  I've downloaded it, but as I posted previously, I can't
> make a deb package of any release or the trunk.  I'm obviously new
> at packaging, but I can't understand why a file from the tree is making
> the procedure fail.  Any other suggestion as to how to either fix or
> work around this problem will be welcome.

As you have noticed, the files in packaging/debian are intended for
use only via buildrelease/makedist.py, which undertakes a fair bit of
preliminary work, including some amount of preprocessing.  However,
upstream's source tree and build procedure isn't suitable for etch or
even unstable anyway on account of various considerations.

Instead, I'd advise applying the patch used to build the backport I
posted (which still applies to the trunk AFAICT) and proceeding from
there:

    cd bitpim-trunk # or whatever you call your checkout
    zcat .../bitpim_1.0.5.dfsg.1-1~bpo40*1.diff.gz | patch -p1
    dch -v 1.0.6~pre-0
    debuild -us -uc

HTH; HAND.

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
Finger [email protected] (NOT a valid e-mail address) for more info.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/