Closing, Edgy is fixed. It's not the type of bug we fix in stable
releases, but if that's strongly desired, 'Backport fix to releases' is
the way to indicate this (creating a dapper task).
** Changed in: libgphoto2 (Ubuntu)
Status: Fix Committed => Fix Released
--
Kodak CX7525 support is
Fix has been committed in upstream and likely to be in edgy 2.2.1
package
** Changed in: libgphoto2 (Ubuntu)
Status: Needs Info => Fix Committed
--
Kodak CX7525 support is broken
https://launchpad.net/bugs/39409
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubun
2.2.1 has been released for quite some time soon. So this bug is fixed
in Edgy since Edgy has this feature.
I don't know how this would fit to dapper-updates. Maybe dapper-
backport.
--
Kodak CX7525 support is broken
https://launchpad.net/bugs/39409
--
ubuntu-bugs mailing list
ubuntu-bugs@list
Yes, it happens with an up-to-date dapper.
Source: libgphoto2
Version: 2.1.6-5.2ubuntu8
The bug is fixed in the libgphoto2 development branch since months.
--
Kodak CX7525 support is broken
https://launchpad.net/bugs/39409
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists
does that problem still occur? If yes, which version of libgphoto2?
** Changed in: libgphoto2 (Ubuntu)
Assignee: (unassigned) => Hubert Figuiere
Status: Unconfirmed => Needs Info
--
Kodak CX7525 support is broken
https://launchpad.net/bugs/39409
--
ubuntu-bugs mailing list
ubuntu-b
