Uploaded 0.2.0-1ubuntu1 to edgy
** Changed in: f-spot (Ubuntu)
Status: Confirmed = Fix Released
--
New version of f-spot
https://launchpad.net/bugs/58183
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Sweet. Thanks Andrew.
--
New version of f-spot
https://launchpad.net/bugs/58183
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Sebastian -- maybe then there should be some better way of communicating
with users regarding new versions? Maybe some sort of launchpad feature
to address it?
Often times with lesser-known packages if users keep silent Ubuntu will
start shipping with really stale packages.
--
New version of
I supposed the inherent question associated with this bug is, will the
new f-spot make it into edgy? Since we're well past upstream version
freeze deadlines, we would assume the answer to be, no.
What can we do to make it possible to include?
--
New version of f-spot
By the way, I applied the f-spot_0.1.11-3ubuntu4.diff.gz file to the
pristine f-spot 0.2.0 source tree. It didn't apply completely cleanly,
but after updating (only) the debian/changelog file, I was able to
successfully build f-spot_0.2.0-0ubuntu1_i386.deb. It installs and runs
OK, but the Print
Thanks for your interest, but there is no need to create extra bug load
by opening new bugs as soon as a new version is available
** Changed in: f-spot (Ubuntu)
Importance: Untriaged = Wishlist
Status: Unconfirmed = Confirmed
--
New version of f-spot
https://launchpad.net/bugs/58183
