If it makes it to Jaunty that will be thanks to you Luka, thanks again.
--
Please sync exiv2-0.18 from Debian Experimental
https://bugs.launchpad.net/bugs/309684
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
I would like to request FFe for exiv2 0.18. This version, released in
Dec 2008, provides major improvements in the area of write support
(added support for TIFF, DNG, NEF, PEF, PNG and JP2 images) and can
properly detect Canon lens types (before only Nikon). It would be really
good to have this ver
pyexiv2 FFe submitted as bug 343549. We need to wait for motu-release
approval.
geeqie sync request (bug 341415) is also approved and is just waiting
for archive admin to do it.
--
Please sync exiv2-0.18 from Debian Experimental
https://bugs.launchpad.net/bugs/309684
You received this bug notifi
Oliver: OK, will then ensure that new 0.1.3 version is uploaded after
transition to exiv2 0.18.
it compiles fine now when I have enough space in my PPA:
https://launchpad.net/~lure/+archive/ppa
Will open FFe bug for pyexiv2 today (needs motu-release approval) and then ask
ubuntu-release team f
Luka, I don't really see the point of conditional compilation in that case.
As commented earlier, no rdepends make use of this thumbnailing code.
Moreover, pyexiv2 being a python module, no compilation process is involved for
rdepends, so as long as the API doesn't change, clients don't care about
I put together package, but for some reason it did not compile with 0.18 in PPA
- need to investigate these further:
http://launchpadlibrarian.net/22891119/buildlog_ubuntu-jaunty-amd64.pyexiv2_0.1.2-4build2~ppa~lure1_FAILEDTOBUILD.txt.gz
For transition, it would be helpful if pyexiv2 would be sti
Ups, build of 0.1.3 did not even start, as my PPA is Full. Please ignore my
first comment about build failure.
Having conditional compiling would be still great.
--
Please sync exiv2-0.18 from Debian Experimental
https://bugs.launchpad.net/bugs/309684
You received this bug notification because y
I've uploaded the tarball at https://launchpad.net/pyexiv2/0.1.x/0.1.3.
Please let me know if anything is missing.
--
Please sync exiv2-0.18 from Debian Experimental
https://bugs.launchpad.net/bugs/309684
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Olivier: great news! If you can provide the tarball, I will take care to
package/test it and try to get FeatureFreeze exception for it.
--
Please sync exiv2-0.18 from Debian Experimental
https://bugs.launchpad.net/bugs/309684
You received this bug notification because you are a member of Ubuntu
B
Note that I integrated one of the two patches to the package in the
branch (http://patch-
tracking.debian.net/patch/series/view/pyexiv2/0.1.2-4/02_noscript), that
should one patch less to maintain.
I had a look at the sources of the two rdepends, phatch and lazygal, and
none of them makes use of t
After giving it a quick look, I realized porting the current pyexiv2 0.1.2 to
libexiv2 0.18 was not that much work, so I got it done. The changes are small
and not really intrusive, they were affecting EXIF thumbnail related code only.
I now have a 0.1.3 branch (lp:~osomon/pyexiv2/pyexiv2-0.1.3)
** Changed in: libkexiv2 (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: pyexiv2 (Ubuntu)
Assignee: Luka Renko (lure) => (unassigned)
Status: In Progress => Incomplete
--
Please sync exiv2-0.18 from Debian Experimental
https://bugs.launchpad.net/bugs/309684
You r
I'm working on pyexiv2 0.2, compiled against libexiv2 0.18.
Unfortunately I'm not anywhere near a release and won't make it for
Jaunty. I will of course in time build packages in my PPA.
--
Please sync exiv2-0.18 from Debian Experimental
https://bugs.launchpad.net/bugs/309684
You received this bu
As suspected, pyexiv2 transition is painful: it is very tightly linked to
current version of exiv2 (0.17) and there is no newer release that would
support exiv2. There is 2.0 branch in LP, but does not look to be near release:
https://launchpad.net/pyexiv2/
Also note that it has two rdepends, t
I have finally found some time to push this a bit forward:
- new koffice2 beta (1.9.98.7-0ubuntu1) builds fine with 0.18
- requested removal of libkexiv2 from the archive - bug 341399
- requested sync/FFe for geeqie 1.0~alpha3-4 that builds with 0.18 - bug 341415
The only remaining problem (beside
Daniel: correct, and all these are included in my PPA. I have added
additional tasks for packages that need work, so if somebody would like
to help it would be appreciated.
--
Please sync exiv2-0.18 from Debian Experimental
https://bugs.launchpad.net/bugs/309684
You received this bug notification
Perhaps a more complete list of packages depending on the existing
libexiv2-4 API is (obviously including ones provided by the exiv2
package):
$ apt-cache rdepends libexiv2-4
libexiv2-4
Reverse Depends:
libexiv2-4-dbgsym
ufraw
rawstudio
qtpfsgui
python-pyexiv2
merkaartor
libkexiv2-3
** Also affects: pyexiv2 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: koffice2 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: libkexiv2 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: geeqie (Ubuntu)
Importance: Undecided
You can see the results in my PPA:
https://launchpad.net/~lure/+archive/ppa
Build fails for the following rdepends:
- gequie: uses old/private API - need to check it upstream has never version
- koffice2: minor change required due to API change - will talk with upstream
to fix for next beta
- lib
I've already built exiv2 in my PPA, although I've only built UFRaw
against it.
--
Please sync exiv2-0.18 from Debian Experimental
https://bugs.launchpad.net/bugs/309684
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
Will test build in my PPA.
** Changed in: exiv2 (Ubuntu)
Assignee: (unassigned) => Luka Renko (lure)
Status: New => In Progress
--
Please sync exiv2-0.18 from Debian Experimental
https://bugs.launchpad.net/bugs/309684
You received this bug notification because you are a member of Ubu
Who's going to take care of fixing these up? Did anybody attempt to
build them with the new exiv2?
--
Please sync exiv2-0.18 from Debian Experimental
https://bugs.launchpad.net/bugs/309684
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
aptitude search ~D~n^libexiv2-4$
report these packages :
exiv2
geeqie
gimp-ufraw
gnome-commander
gpscorrelate
gpscorrelate-gui
gwenview
hugin-tools
kphotoalbum
libexiv2-dev
libkexiv2-3
libkexiv2-6
python-pyexiv2
qtpfsgui
ufraw
--
Please sync exiv2-0.18 from Debian Experimental
https://bugs.laun
There are some changes in the API, but aren't most apps already
adjusted?
--
Please sync exiv2-0.18 from Debian Experimental
https://bugs.launchpad.net/bugs/309684
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
It seems like a bunch of applications will need to be rebuilt /
transitioned to a new API(?) Who's going to take care of that?
--
Please sync exiv2-0.18 from Debian Experimental
https://bugs.launchpad.net/bugs/309684
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Unsubscribing Ubuntu Universe Sponsors and subscribing Ubuntu Main
Sponsors since exiv2 is in main.
** Changed in: exiv2 (Ubuntu)
Importance: Undecided => Wishlist
--
Please sync exiv2-0.18 from Debian Experimental
https://bugs.launchpad.net/bugs/309684
You received this bug notification beca
Is there any chance of getting exiv2-0.18 into Jaunty, since the merge
window will be closing soon?
--
Please sync exiv2-0.18 from Debian Experimental
https://bugs.launchpad.net/bugs/309684
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
27 matches
Mail list logo
