On Thu, Aug 14, 2008 at 10:46:03AM -0700, Adam Williamson wrote:
> Hi, all. I haven't subscribed to the list before, but followed the
> archives.
Welcome to Barry! I'm always happy when potential and existing official
distro mainainers join the list, so we can keep communication open.
> I notice in a recent post - subject "Call for testing: binary
> packages" - Chris advertised OpenSUSE Build Service-based packages for
> Barry for "Mandriva 2008" (I don't know if this was in fact 2008
> Spring).
I'm not entirely sure, as it was installed on their systems by their
build service maintenance folks, but during the build for 2008, it
installs a package called:
mandriva-release-Free-2008.0-5mdv2008.0
Perhaps that tells you the exact release?
> It's worth noting that there's not much need to use these :). Barry is
> officially packaged for Mandriva (by me) and the packages are regularly
> updated in both the development distribution and in the /backports
> repository for stable releases. The packages are tested to work, and
> there are metapackages for convenience in installation and
> synchronizing: the procedure for synchronizing a Blackberry on 2008
> Spring is written up at
> http://wiki.mandriva.com/en/2008.1_Synchronization#Blackberry_devices_using_a_USB_cable
> .
That is great news, thanks!
I'm also happy to see work is going into making the GUI syncing easier
as well. This has been a tough point so far.
> Just wanted to make sure anyone using Mandriva is aware of the official
> packages.
As I'm mainly a Debian user, I was not aware, so thank you for the update.
> There's also a patch in our package. It predates my involvement with the
> package, but it is named 'barry-compile.patch', implying it fixes a
> compilation issue. It changes three ints to longs , so I suspect it's an
> x86-64 related issue. I'm attaching this in case it would make sense to
> adopt it upstream. Thanks!
And now that I have an official maintainer's ear (gleeful rubbing of hands) :-)
I can point you in the direction of the real reason for this bug. See
the section "The Case of the Broken Libtar" in Barry's documentation:
http://www.netdirect.ca/software/packages/barry/dependencies.php
In short, libtar contains some example code that, when compiled in 64bit
mode, has errors. Instead of fixing the example code, a patch was introduced
to the open/close/read/write libtar calls (which closely match the C
standard's version of them) to change the int to a long. This breaks
compatibility with C that the 32bit version of libtar had.
I believe the correct fix is to change the libtar patch, and then Barry
will not need to be patched at all.
This post describes it in detail:
http://sourceforge.net/mailarchive/message.php?msg_id=20070803200729.GA7068%40foursquare.net
Thanks again for joining the list!
- Chris
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel
