On Mon, 11 May 2009 06:49:57 +0200
Michael Wagner wrote:
> >
> > Unfortunately, this happens (even though we try to avoid it), and
> > it's not always obvious to either the submitter or us when it
> > does. As with the actual Slackware tree, the best we can hope to
> > happen is to quickly catch
Unfortunately, this happens (even though we try to avoid it), and it's
not always obvious to either the submitter or us when it does. As with
the actual Slackware tree, the best we can hope to happen is to quickly
catch it when it does and push an update. I'll try to look at the new
gwenview as
On Sat, 09 May 2009 17:08:28 +0200
Michael Wagner wrote:
> > Updating exiv2 and libkexiv2 to the current version will break
> > gwenview. Neither will an existing binary work anymore nor will you
> > be able to compile against the updated libraries!
> >
>
> An update has already been submitted t
Le Sat, 09 May 2009 17:08:28 +0200,
Michael Wagner a écrit :
>
> > Updating exiv2 and libkexiv2 to the current version will break
> > gwenview. Neither will an existing binary work anymore nor will you
> > be able to compile against the updated libraries!
> >
> >
>
> An update has already b
Updating exiv2 and libkexiv2 to the current version will break gwenview.
Neither will an existing binary work anymore nor will you be able to compile
against the updated libraries!
An update has already been submitted to the pending queue.
Shouldn't it be necessary to mention an API/ABI/
Just a quick warning...
Updating exiv2 and libkexiv2 to the current version will break gwenview.
Neither will an existing binary work anymore nor will you be able to compile
against the updated libraries!
There's a more recent gwenview 1.4.3 which *might* work, but I haven't tried
it because t
