Summary: | media-gfx/gthumb-3.6.0 version bump | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sergey Torokhov <torokhov-s-a> |
Component: | Current packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | poncho |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Sergey Torokhov
2017-09-14 07:57:52 UTC
*** This bug has been marked as a duplicate of bug 626490 *** (In reply to Gilles Dartiguelongue from comment #1) > > *** This bug has been marked as a duplicate of bug 626490 *** The bug that is about gthumb 3.5.2 but not about 3.5.1 as describe in https://bugs.gentoo.org/show_bug.cgi?id=626490 As mentioned there by Mart Raudsepp: > I guess we could consider a p.masked 3.5.x, but it'd be nice to at least have a newer > and hopefully more polished 3.5.2 from upstream if not yet ready for 3.6 > Upstream says: > The 3.6.0 version is planned in late September or October, > there will be some 3.5.x releases before that. I don't see any serious commits (there are only translation upgrades) in upstream (https://git.gnome.org/browse/gthumb/log/, https://github.com/GNOME/gthumb/commits/master) since gthumb 3.5.2 was released. So I don't expect 3.6.x release in near future. So what about gthumb 3.5.2 version bump? Could you reconsider decision and reopen bug? Upstream replied me: "Probably next Monday I'll do another release, still not sure if another 3.5.x or the final 3.6.0 version." Lets wait for that and see then (In reply to Mart Raudsepp from comment #3) > Upstream replied me: > "Probably next Monday I'll do another release, still not sure if another > 3.5.x or the final 3.6.0 version." > > Lets wait for that and see then gthumb 3.6.0 was released on 20 Nov 2017: https://mail.gnome.org/archives/gnome-announce-list/2017-November/msg00009.html I don't understand gthumb version numeration. Does this relase is "stable" (non-development) release? Could it be added to portage tree? Yes, it should be added. Looks like I stopped monitoring for the release to finally happened just before it happened, and then forgot about it. It follows gnome versioning, so odd minor version number (second number) means development, and even minor version number means stable. Do you meet any difficulty or is just time running short? It's at 3.6.1 now - a great release, seamless video on wayland in main window - just renaming gthumb-3.4.5.ebuild to gthumb-3.6.1.ebuild worked here! The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a1c81928f4e4f4f0cba97d94505688b3fcceb43a commit a1c81928f4e4f4f0cba97d94505688b3fcceb43a Author: Mart Raudsepp <leio@gentoo.org> AuthorDate: 2018-07-14 23:49:17 +0000 Commit: Mart Raudsepp <leio@gentoo.org> CommitDate: 2018-07-14 23:50:12 +0000 media-gfx/gthumb: bump to 3.6.1 * dcraw direct usage is gone, now doing this via libraw dcraw API; thus dcraw dep removed * new colord optional support, some of which depends on lcms option; so implicitly enable lcms even without USE=lcms in case of USE=colord, because colord will pull in lcms2 anyways Closes: https://bugs.gentoo.org/630956 Package-Manager: Portage-2.3.40, Repoman-2.3.9 media-gfx/gthumb/Manifest | 1 + media-gfx/gthumb/gthumb-3.6.1.ebuild | 94 ++++++++++++++++++++++++++++++++++++ media-gfx/gthumb/metadata.xml | 1 + 3 files changed, 96 insertions(+) |