Please upgrade libpst from upstream at www.five-ten-sg.com/libpst

BTW: I would like input on how to proceed here.

I have packaged libpst-0.6.25 in my PPA (https://launchpad.net/~hggdh2/+archive). I would like feedback on it so that I can correct packaging errors that I am certain I did.

Please note that upstream provides the distribution tarball pre-debianised; unfortunately, this does not work, and required changes under the ./debian directory. Also, a (currently) needed upstream patch has been added.

My package provides 3 binaries: libpst and libpst-dev for the new shared library, and the current readpst.

I have opened an upgrade request on Debian, and am waiting on confirmation. I have no idea if I used the correct format for the request, though.

To review the package I just diff-ed the two debian/ directories (got the old package by running "apt-get source libpst"), and I noticed that you have added a bunch of new files. Why did you not re-use the old packaging?

Check out https://wiki.ubuntu.com/PackagingGuide/Recipes/PackageUpdate as well.

I am sorry, I think I was not clear: the current Debian libpst package is incompatible with the Evolution needs. This is why I am proposing the *other* fork: this fork has been continuously developed (as opposed to the Debian's, where, pretty much, only maintenance patches are applied.

So. If Evolution 2.26 on Jaunty is to provide the Outlook PST importer, we have to split from Debian on libpst.

Additionally, the upstream at 5-10 provides the source already "debianised", but in a rather incomplete and broken way, which required me to make some changes to the source.

I will check the link you provided as soon as I land. Thank you.

I'm not arguing about the new upstream tarball. The changes in debian/ are just huge and there seem to be added *.ex and *.EX changes all over the place.

Let me know if I looked at the wrong package or something.

No, you did not look at the wrong package. As I said, the source upstream tarball comes pre-debianised in a basic, incomplete, and wrong, way. All the sample *.ex and *.EX are added this way (as can be seen by looking at the orig.tar). I did not change these files, I tried to take them out. It really looks like upstream just ran dh_make, and then packaged the distribution tarball.

I discussed this on #ubuntu-motu, and got no definite answer on how to proceed.

I don't think it's wrong to pick the fork if that makes more sense, but I'd try to ensure that the packaging is similar to what it was before, it'll also help with getting the Debian bug fixed. :-)

Daniel, I think this time I got it right. Can you please check the package in my PPA (libpst-0.6.27-1ppa4 and friends)?

ah well. Got hit by a wrong expectation that libtool would be automatically included by CDBS (like automake and autoconf). Anyway, the correct version is 0.6.27-1ppa5 now.

Also, the diff for the package is quite small, so I guess I am on the right track.

Good work.

Here's a few changes I'd do:
 - use {shlibs:Depends} instead of explicit library dependencies, add {misc:Depends} too
 - rename libpst to libpst1
 - remove a few (with cdbs) unneccesary files
 - small fixes here and there.

Please ask Séb to give it another spin. I'm sure he'll find something else. :-)

thanks. Changes done, submitted 1ppa6; chatted with Sébastien, and he will have a go at it after I get a successful build.

the packaging looks mostly fine to me, the rules is a rather complicated and running autootols at build is not optimal but that should work, otherwise there is makefiles to clean in the debian directory

Done (but still using autotools: I wanted to be sure that anyone could get the source and build it outside of Ubuntu).

I guess, now, I should adjust the cahngelog and submit it to Revu, Correct?

libpst-0.6.27-1 has been uploaded to REVU.

debdiff for Evolution 2.26.0 to activate pst-import is attached.

This bug was fixed in the package libpst - 0.6.27-0ubuntu1

---------------
libpst (0.6.27-0ubuntu1) jaunty; urgency=low

  [ HggdH ]
  * new upstream source being used (LP: #317602) -- www.five-ten-sg.com/libpst:
    Debian's libpst version does not provide a shared library, and
    does not support newer Evolution PST files; dropping it.
  * remove upstream basic debianisation, and re-debianise using CDBS.
    upstream provides a basic, incomplete, and non-functional ./debian;
    also, add a ./debian/rules get-orig-source target in order to
    cleanup nicely.
  * debian/patches/10-current-attach.patch: patch for Evolution use,
      should be eventually dropped for a Evolution patch upstream.
  * debian/patches/05-disable-debian-gen.patch: adjust configure.in
    and Makefile.am not to generate the debian directory and files.
  * changed dependency from libgd2-noxpm to libgd2-xpm >= 2.0.36
      (current jaunty alpha 3 level).
  * add a Conflitcs for readpst < 0.6.27, to guarantee upgrade for
    those using the old libpst packages.

  [ Iain Lane ]
  * Set priority: extra and remove conflicts on same binary package
  * debian/copyright: Update and mention GPL-2+ licensed file src/lzfu.c

 -- HggdH <email address hidden> Wed, 25 Feb 2009 10:49:13 -0600

s/extra/optional/ - braino in the changelog ;)

Hi,
libpst - 0.6.27-0ubuntu1 package is not installed by default (on a fresh install) in Jaunty RC (I guess that's where the optional comes in play...). Shouldn't it be there by default to help new users migration? I haven't found Ubuntu related documentation stating one should install this package to migrate one's .pst files to Evolution.

Hi Vincent.

Yes, libpst is not installed by default on Jaunty. It ended up that Evolution did not get the PST-import plugin enabled for Jaunty: we did not have enough time to get it in; it might get in on either an update for Jaunty, or on Karmic (Jaunty+1).

Although you can manually select and install libpst, this will *not* make Evolution able to run the plugin: the plugin has to be built. But 'readpst', one of the binary packages generated by the libpst source, allows one to convert PST from the command-line. Granted, not as nice as through Evo, but at least it works right now.

Ouch, that's really bad luck, it was one of the (few) good selling
points for Gnome 2.26... I really hope it will be in an update.

Thanks for your hard work to make Ubuntu as good as it is.

Vincent

On Fri, Apr 17, 2009 at 19:11, C de-Avillez <email address hidden> wrote:
> Hi Vincent.
>
> Yes, libpst is not installed by default on Jaunty. It ended up that
> Evolution did not get the PST-import plugin enabled for Jaunty: we did
> not have enough time to get it in; it might get in on either an update
> for Jaunty, or on Karmic (Jaunty+1).
>
> Although you can manually select and install libpst, this will *not*
> make Evolution able to run the plugin: the plugin has to be built. But
> 'readpst', one of the binary packages generated by the libpst source,
> allows one to convert PST from the command-line. Granted, not as nice as
> through Evo, but at least it works right now.
>
> --
> Please upgrade libpst from upstream at www.five-ten-sg.com/libpst
> https://bugs.launchpad.net/bugs/317602
> You received this bug notification because you are a direct subscriber
> of the bug.
>