On Tue, Mar 30, 2010 at 03:21:30PM -0600, Nathanael Noblet wrote:
> Sure, He's asked me to handle the package for now, also, Adam Williamson no
> longer works for Mandriva and actually works for Fedora so isn't the
> packager there either.

Thanks.

Does anyone from Mandriva know who the Mandriva contact person is?
Or is there anyone who would volunteer to find out for me? :-)


> The barry package is available in all main repos that come with Fedora, I've
> just pushed this latest update into their updates-testing repo to see if it
> fixes a number of reported bugs.
> 
> Could take a look at the two bugs marked New, I haven't even looked if they
> are related to the version that has been in fedora till now, so they could
> be fixed.
> https://bugzilla.redhat.com/buglist.cgi?component=barry&product=Fedora

Is there a stable URL for downloading individual RPMs and src RPMs from the
official repositories?



> I'm not sure if you want to follow the fedora rpm spec or not, they have a
> number of guidelines that not everyone likes sometimes. The one thing I
> noticed is that your spec file installs the barrybackup icon in
> _datadir/pixmaps which from what they tell me is deprecated, you should be
> using _datadir/icons/hicolor/XxX/apps/ so the icon file you provide is 48x48
> so that replaces the XxX. Other than that they are fairly similarly laid
> out.

Currently I'm only building releases for Debian, Ubuntu, and Fedora, when
I do a release of my own.  So if there are changes to make Barry more
friendly to the latest distro, it would be good to include it.

I'm thinking of spinning the spec files off into directories by distro
and version.  The latest barry.spec file for Fedora should always have
all the latest changes.  If I can get those changes from the maintainer,
that's even better.  Because I often don't follow the latest distro
changes until after it's released, and then I have to spend a few hours
just updating things, and sometimes figuring our how to just make it work.
And I inevitably miss things, such as policy changes like you mentioned
above.

Short version: please please please send your changes upstream. :-)



> On a completely different side note, I was testing this new version and had
> it trying to sync contacts, I was using the opensync plugins for barry and
> sunbird, it fails when trying to sync contacts, I realize you don't have
> anything to do with sunbird or their opensync plugin, however since it just
> sits there you have to kill the process, at which point the blackberry can
> no longer communicate with the system, you get some usb error. breset fixes
> that, as does un-plugging and re-plugging in the device. I'm wondering if
> that isn't something that the tool/plugin could detect automatically...
> Hopefully that made sense without specific details.

Yep, it made sense.  I suppose we could reset automatically, but I don't
like that solution.  As I already mentioned to Nicolas. :-)

I'd much rather find out what Windows does to handle this situation,
and implement that.  But maybe that's asking to much, when the reset
solution is easier to implement.

In any case, the fix would need to be optional, and only kick in when
the usual 44 size exception happens.  And preferrably make this an
easy option to use, built into the library API.

If anyone has a patch like that, I'd probably accept it.  But a proper
reverse-engineering of the Windows method of recovering would be
nicer. :-)

- Chris


------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

Reply via email to