After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 583464 - 2.11.0 blockers
2.11.0 blockers
Product: gthumb
Classification: Other
Component: general
Other Linux
: Normal normal
: ---
Assigned To: Paolo Bacchilega
Paolo Bacchilega
Depends on: 448585 456703 501512 519433 525482 529076 560352 560743 572424 575017 579827 583466 583796 583833 583889 583891 584695 584918 584923 585185 585206 585237 585849 585958 586327 586858 586975 587795
Reported: 2009-05-21 15:43 UTC by Michael Chudobiak
Modified: 2009-08-03 23:02 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Michael Chudobiak 2009-05-21 15:43:11 UTC
This shows the 2.11.0 blockers, as far as I am concerned. Paolo may have other issues in mind, too.

- Mike
Comment 2 Michael Chudobiak 2009-05-26 12:03:16 UTC
None of those are really blockers, that absolutely must be fixed before 2.11.x.

It would be very nice to fix them, of course, but we shouldn't hold up a release for them.

- Mike
Comment 3 Paolo Benvenuto 2009-05-26 14:17:35 UTC
I think could be fixed before 2.11.x

It lets the user quite confused and could provoke errors, because every application mantains selection after a rename.
Comment 4 Matthias Hawran 2009-05-27 07:42:11 UTC
As I understand you personally don't see any showstoopers, right ?
And Paolo neither so far ?
So nothing is stopping the 2.11.x release ?

Comment 5 Michael Chudobiak 2009-05-27 09:34:21 UTC

No, sadly that's not correct. The blockers are listed below, in the "depends on" field. You can also click on the "dependency tree":

I've been working on the gio/gfile migration, personally. That is nearing completion.

Also, Paolo Bacchilega (not to be confused with donpaolo) had some plans for 2.11.x (like plug-ins), but I don't know if they will block or not.

- Mike

Comment 6 Matthias Hawran 2009-05-27 09:41:14 UTC
Ok thanks, I didn't look carefully

I'll try to contribute in any of them if I can.

Comment 7 Paolo Benvenuto 2009-05-27 21:38:21 UTC
I wanto to install gthumb from trunk in ubuntu.

I'm trying with the following instruction Mike gave me:

git clone git://
cd gthumb
./ --prefix=/usr CFLAGS="-ggdb"
sudo make install

I already "sudo apt-get build-dep gthumb", but at the end of autoget I get:

checking for GTHUMB... configure: error: Package requirements (	glib-2.0 >= 2.6.0				gthread-2.0						gmodule-2.0						gtk+-2.0 >= 2.14.0				libgnome-2.0 >= 2.6.0			libgnomeui-2.0 >= 2.6.0			libgnomecanvas-2.0 >= 2.6.0		libbonobo-2.0 >= 2.6.0			libbonoboui-2.0 >= 2.6.0			bonobo-activation-2.0 >= 2.6.0		gio-2.0 >= 2.16.1				gnome-vfs-2.0 >= 2.6.0			gnome-vfs-module-2.0					exiv2 >= 0.18				libxml-2.0 >= 2.4.0				libglade-2.0 >= 2.4.0) were not met:

No package 'exiv2' found

I have exiv2 installed, and "sudo apt-get build-dep exiv2" too.

What do I lack in order to compile gthumb?
Comment 8 Marc Pavot 2009-05-27 21:41:04 UTC

You should probably install libexiv2-dev

Comment 9 Paolo Benvenuto 2009-05-27 21:55:28 UTC
ok, now all is ok, thank you!
Comment 10 Paolo Benvenuto 2009-05-27 22:00:21 UTC
I completed the installation, but I see that it replaced my current ubuntu gthumb install.

How do I install it in such a way that I can run both jaunty and trunk gthumb?
Comment 11 Matthias Hawran 2009-05-28 09:26:05 UTC
change the prefix at autogen step, e.g.:
./ --prefix=/opt
Comment 12 Matthias Hawran 2009-05-28 09:48:29 UTC

Little remark: are you going to add every new bug you report to this blocker list?
I don't think they all qualify as blockers, we should keep the real blockers.

Maybe propose the bugs to be added for review before adding them "blindly".
(Or I missed a parallel discussion... is the ML already setup and I missed it?)

My 2 cents.

Comment 13 Paolo Benvenuto 2009-05-28 09:51:03 UTC
No, I'm not adding every new bug I submit. I think I'm evaluating the real blockers. However, if it's better I can simply suggest to add it them as blockers.
Comment 14 Marc Pavot 2009-05-28 10:03:31 UTC
It may be nice to keep this bug to track real blockers and to open a new one to list "nice to have" bugs/features for 2.11 release.

Comment 15 Michael Chudobiak 2009-05-28 11:47:45 UTC
Just to be clear, blockers should only be:

1. Bugs that represent major architectural changes (gio migration, comment / tag / metadata integration)

2. Things that are completely, embarrassingly broken (slideshow fading, tiff saving)

3. Issues that have been raised many times in bugzilla (selection weirdness after directory change)

4. Removing deprecated code.

Don't worry, Paolo! Your bug reports are much appreciated and they do get read! They just aren't blockers.

We need to keep the blocker list short and focused, so that we have some hope of making a 2.11.0 release.

This is my attempt at "good management" :-)

Perhaps when the mailing list is up we could have a "bug of the week" to fix the long list of issues that Paolo is so good at identifying.

- Mike
Comment 16 Paolo Benvenuto 2009-05-28 13:55:10 UTC
ok, let me avoid mark bugs as blockers.

But explain me this: what is 2.11.0 intended to be?
- a working-although-carrying-significative-bugs release
- a pre-release for testing purpose in order to prepare to 2.12 release
- a developers-only release
- ...

Perhaps I lacked some explication when 2.11 was planned.
Comment 17 Paolo Benvenuto 2009-05-28 13:56:15 UTC
ok, let me avoid marking bugs as blockers.

But explain me this: what is 2.11.0 intended to be?
- a working-although-carrying-significative-bugs release
- a pre-release for testing purpose in order to prepare to 2.12 release
- a developers-only release
- ...

Perhaps I lacked some explication when 2.11 was planned.
Comment 18 Paolo Benvenuto 2009-05-28 13:57:08 UTC
(excuse my double comment...)
Comment 19 Matthias Hawran 2009-05-28 14:05:59 UTC
Perhaps I lacked some explication when 2.11 was planned.

That's the key point: there's no such info (or at least it's not public).
It's in Paolo B. and/or Mike's head ;-)

Mike we need the ML fast ! ;-)
Comment 20 Michael Chudobiak 2009-05-28 14:46:11 UTC
I have requested the mailing list, but the gnome sysadmin team is usually slow.

Generally, the even series (2.10.x) have been stable branches where only bug fixes are allowed, and new features are not allowed.

Odd series (2.11.x) have been unstable, and new features are allowed.

All releases should be working, usable, and crash-free. All releases have minor bugs.

That's my view, anyway.

- Mike

Comment 21 Michael Chudobiak 2009-05-28 14:58:10 UTC
It would be helpful if someone could look at bug 583891 - rotation progress bar is broken.

- Mike
Comment 22 Michael Chudobiak 2009-06-03 13:15:01 UTC
*** Bug 584695 has been marked as a duplicate of this bug. ***
Comment 23 Michael Chudobiak 2009-08-03 23:02:43 UTC
Paolo has rebased the gthumb code in the new "ext" branch. 2.11.x will come from this new branch. The current master branch is dead, so I'm closing this tracker bug; it is no longer relevant. See the mailing list for details.

- Mike