On Thu, 2008-08-14 at 16:10 -0400, Chris Frey wrote: > 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?
Yes, that would be 2008, our second-to-last stable release, not 2008 Spring, our latest stable release. I guess the OpenSUSE build service didn't get around to handling 2008 Spring (aka 2008.1) yet. > 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. If any other distro maintainers are interested in using this stuff, you can easily find it in our kdenetwork package: http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/kdepim/current in SOURCES there is configguibarry.cpp , configguibarry.h , and kdepim-3.5.9-kitchensync-barry.patch . Together these implement GUI configuration of the Barry opensync plugin in (the KDE 3 branch of) Kitchensync (although they could be improved somewhat). You can see from SPECS/kdepim.spec how it all gets glued together. Unfortunately there'll be a massive regression coming up for us (and other distros) soon, as there is currently no KDE 4 plugin for opensync , so you can't synchronize anything with Kmail, Kontact etc in KDE 4 using opensync. Only KDE 3's kdepim and GNOME (Evolution) currently are supported by opensync. I've poked opensync about this, there may be some movement on it around September / October. > 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 Aha, I was not aware of that, and it's interesting. I will poke our libtar maintainer (assuming we have one :>) and see if maybe we should change this. Thanks. -- adamw ------------------------------------------------------------------------- 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
