On Thu, Jul 29, 2010 at 10:52:35AM -0400, Martin Owens wrote:
> Hey Chris,
>
> See the attached patch for the debian/control file.
>
> It adds a version limit on each part to relate to the others.
Thanks Martin! Applied.
> Interestingly libbarry0 wasn't a dep for the opensync plugin, I wonder
Hey Chris,
See the attached patch for the debian/control file.
It adds a version limit on each part to relate to the others.
Interestingly libbarry0 wasn't a dep for the opensync plugin, I wonder
if that was an oversight.
Martin
On Sun, 2010-07-25 at 07:53 -0400, Chris Frey wrote:
> I know.
Thank you, gentlemen! I can only assume that there was a previous
attempt at making Barry work on this machine, leaving the 0.15 version
of barry-utils behind, which then didn't get upgraded when I did the
"apt-get install libbarry*" because of the version dependency issue that
Chris mentioned
On Sun, Jul 25, 2010 at 1:53 PM, Chris Frey wrote:
> On Sun, Jul 25, 2010 at 11:49:35AM +0200, Jose Carlos Garcia Sogo wrote:
[...]
>
> I know. But nearly all Barry releases so far have changed the API in
> some small way; so the package should be, perhaps, libbarry16 by now.
> If you wish to pac
On Sun, Jul 25, 2010 at 11:49:35AM +0200, Jose Carlos Garcia Sogo wrote:
> On Sun, Jul 25, 2010 at 11:38 AM, Chris Frey wrote:
> > On Sun, Jul 25, 2010 at 11:11:55AM +0200, Jose Carlos Garcia Sogo wrote:
> >> If there is an API change, first the soname of the library should be
> >> bumped (that's
On Sun, Jul 25, 2010 at 11:38 AM, Chris Frey wrote:
> On Sun, Jul 25, 2010 at 11:11:55AM +0200, Jose Carlos Garcia Sogo wrote:
>> If there is an API change, first the soname of the library should be
>> bumped (that's upstream labor) so the package should move from
>> libbarry0 to libbarry1.
>
> Ye
On Sun, Jul 25, 2010 at 11:11:55AM +0200, Jose Carlos Garcia Sogo wrote:
> If there is an API change, first the soname of the library should be
> bumped (that's upstream labor) so the package should move from
> libbarry0 to libbarry1.
Yes, this is the way it will be done once we release a version
On Sun, Jul 25, 2010 at 11:03 AM, Martin Owens wrote:
> My PPA looks fine, shouldn't it have pulled in all the latest parts from
> my ppa and clobered the old ones.
>
> hmmm, if there is a missing piece in the way we're doing the ppa
> release, let me know.
If there is an API change, first the so
My PPA looks fine, shouldn't it have pulled in all the latest parts from
my ppa and clobered the old ones.
hmmm, if there is a missing piece in the way we're doing the ppa
release, let me know.
On Sun, 2010-07-25 at 04:47 -0400, Chris Frey wrote:
> Try to keep the versions the same, otherwise you
Le samedi 24 juillet 2010 à 23:43 -0400, Charles McCabe a écrit :
> This seems like an issue for this list. Just installed barry from the Martin
> Owens builds and btool crash with the output below:
>
>[...]
>
> The installed packages are:
>
> ii barry-util 0.15-1ubun
On Sat, Jul 24, 2010 at 11:43:30PM -0400, Charles McCabe wrote:
> The installed packages are:
>
> ii barry-util 0.15-1ubuntu2
>Command line utilities for working with the
> ii libbarry00.16-2010071553-0git
This seems like an issue for this list. Just installed barry from the Martin
Owens builds and btool crash with the output below:
=
btool: Symbol `_ZN5Barry11ContactLdif8FieldMapE' has different size in shared
object
12 matches
Mail list logo
