Let's stabilize www-client/chromium-5.0.375.55. The 5.0.375.x have been in the tree for longer than a month, and the fourth number bumps (currently at 55) are only stability fixes, thoroughly tested by Google QA and in the field. Here's the history: chromium-5.0.375.55 (25 May 2010) chromium-5.0.375.53 (22 May 2010) chromium-5.0.375.38 (11 May 2010) chromium-5.0.375.29 (04 May 2010) chromium-5.0.375.23 (28 Apr 2010) chromium-5.0.375.9 (19 Apr 2010) chromium-5.0.375.3 (14 Apr 2010) And here's the status report for open www-client/chromium bugs. In my opinion no one of them should block the stabilization: bug #300679 - only affects the live ebuild (9999) bug #318969 - ebuild applies the workaround, keeping open to get the fix upstream bug #320145 - does not affect 5.0.375.55, the affected ebuilds have workaround bug #321127 - does not affect 5.0.375.55, also GCC 4.5.0 is involved bug #321159 - does not affect 5.0.375.55 bug #322269 - affects 5.0.375.55, but is most likely an upstream issue; in my opinion, should not block the stabilization (we might have to wait a lot for the fix)
I would agree that there needs to be some stabilization on a chromium that "works" for the most part. I've currently got "6.0.408.1 (0)" installed and the bookmarks editor doesn't seem to work at all. Before that the editor would work but wouldn't order the bookmarks where you wanted them. But before that the editor behaved in a way similar to Firefox (sorry -- don't know the precise version #'s). So it looks like at least the bookmarks editor is migrating backwards in terms of features. So Gentoo should have some minimal quality control on "approved" versions since one can't seem to guarantee it from Google. [Worth noting is that for features like the bookmarks editor, mouse wheel, etc. e.g. user interface, the functionality is something that may not be easy to test using the type of tests that I believe Google would typically run.]
Looking at chromium issue #41601 it looks like the bookmarks problems may not be resolved until chromium-5.0.384.0-2.1 (comment #15). Though I'm not sure my problems relate to that problem. The behavior of the older (non-tabbed?) bookmarks manager worked relatively fine. I'm not sure what is meant by a "tabbed bookmark manager". But it is a significant enough change that we might want to standardize on an older simpler bookmark manager as well as a newer fancier tabbed bookmark manager if it can be determined which versions those are associated with. Proper bookmarks management is critical if one is upgrading from other browsers and one wants to transfer years of carefully organized bookmarks.
We're now stabilizing 5.0.375.70. It has just been promoted to the stable channel by upstream and fixes some security issues.
amd64 stable
Archtested on x86: Everything fine. Have been using this version without issues on several computers.
(In reply to comment #3) > We're now stabilizing 5.0.375.70. It has just been promoted to the stable > channel by upstream and fixes some security issues. > I've been getting these errors for some time now, find it even stranger now that it is stable. Am I missing something? ------------------------------------------------------------------------------ base/message_pump_libevent.cc:17:19: warning: event.h: No such file or directory base/message_pump_libevent.cc: In member function ‘bool base::MessagePumpLibevent::FileDescriptorWatcher::StopWatchingFileDescriptor()’: base/message_pump_libevent.cc:83: error: ‘event_del’ was not declared in this scope base/message_pump_libevent.cc:84: warning: possible problem detected in invocation of delete operator: base/message_pump_libevent.cc:78: warning: ‘e’ has incomplete type ./base/message_pump_libevent.h:13: warning: forward declaration of ‘struct event’ base/message_pump_libevent.cc:84: note: neither the destructor nor the class-specific operator delete will be called, even if they are declared when the class is defined. base/message_pump_libevent.cc: In static member function ‘static void base::MessagePumpLibevent::OnWakeup(int, short int, void*)’: base/message_pump_libevent.cc:99: error: ‘event_base_loopbreak’ was not declared in this scope base/message_pump_libevent.cc: In constructor ‘base::MessagePumpLibevent::MessagePumpLibevent()’: base/message_pump_libevent.cc:105: error: ‘event_base_new’ was not declared in this scope base/message_pump_libevent.cc: In member function ‘bool base::MessagePumpLibevent::Init()’: base/message_pump_libevent.cc:129: error: invalid use of incomplete type ‘struct event’ ./base/message_pump_libevent.h:13: error: forward declaration of ‘struct event’ base/message_pump_libevent.cc:130: error: ‘EV_READ’ was not declared in this scope base/message_pump_libevent.cc:130: error: ‘EV_PERSIST’ was not declared in this scope base/message_pump_libevent.cc:131: error: ‘event_set’ was not declared in this scope base/message_pump_libevent.cc:132: error: ‘event_base_set’ was not declared in this scope base/message_pump_libevent.cc:134: error: ‘event_add’ was not declared in this scope base/message_pump_libevent.cc: In destructor ‘virtual base::MessagePumpLibevent::~MessagePumpLibevent()’: base/message_pump_libevent.cc:142: error: ‘event_del’ was not declared in this scope base/message_pump_libevent.cc:143: warning: possible problem detected in invocation of delete operator: base/message_pump_libevent.cc:143: warning: invalid use of incomplete type ‘struct event’ ./base/message_pump_libevent.h:13: warning: forward declaration of ‘struct event’ base/message_pump_libevent.cc:143: note: neither the destructor nor the class-specific operator delete will be called, even if they are declared when the class is defined. base/message_pump_libevent.cc:148: error: ‘event_base_free’ was not declared in this scope base/message_pump_libevent.cc: In member function ‘bool base::MessagePumpLibevent::WatchFileDescriptor(int, bool, base::MessagePumpLibevent::Mode, base::MessagePumpLibevent::FileDescriptorWatcher*, base::MessagePumpLibevent::Watcher*)’: base/message_pump_libevent.cc:161: error: ‘EV_PERSIST’ was not declared in this scope base/message_pump_libevent.cc:163: error: ‘EV_READ’ was not declared in this scope base/message_pump_libevent.cc:166: error: ‘EV_WRITE’ was not declared in this scope base/message_pump_libevent.cc:172: error: invalid use of incomplete type ‘struct event’ ./base/message_pump_libevent.h:13: error: forward declaration of ‘struct event’ base/message_pump_libevent.cc:175: error: invalid use of incomplete type ‘struct event’ ./base/message_pump_libevent.h:13: error: forward declaration of ‘struct event’ base/message_pump_libevent.cc:176: error: ‘EV_READ’ was not declared in this scope base/message_pump_libevent.cc:176: error: ‘EV_WRITE’ was not declared in this scope base/message_pump_libevent.cc:182: error: ‘event_del’ was not declared in this scope base/message_pump_libevent.cc:186: error: ‘EVENT_FD’ was not declared in this scope base/message_pump_libevent.cc:193: error: ‘event_set’ was not declared in this scope base/message_pump_libevent.cc:196: error: ‘event_base_set’ was not declared in this scope base/message_pump_libevent.cc:201: error: ‘event_add’ was not declared in this scope base/message_pump_libevent.cc: In static member function ‘static void base::MessagePumpLibevent::OnLibeventNotification(int, short int, void*)’: base/message_pump_libevent.cc:215: error: ‘EV_WRITE’ was not declared in this scope base/message_pump_libevent.cc:218: error: ‘EV_READ’ was not declared in this scope base/message_pump_libevent.cc: In function ‘void base::timer_callback(int, short int, void*)’: base/message_pump_libevent.cc:226: error: ‘event_base_loopbreak’ was not declared in this scope base/message_pump_libevent.cc: In member function ‘virtual void base::MessagePumpLibevent::Run(base::MessagePump::Delegate*)’: base/message_pump_libevent.cc:236: error: invalid use of incomplete type ‘struct event’ ./base/message_pump_libevent.h:13: error: forward declaration of ‘struct event’ base/message_pump_libevent.cc:262: error: ‘EVLOOP_ONCE’ was not declared in this scope base/message_pump_libevent.cc:262: error: ‘event_base_loop’ was not declared in this scope base/message_pump_libevent.cc:269: error: ‘event_set’ was not declared in this scope base/message_pump_libevent.cc:270: error: ‘event_base_set’ was not declared in this scope base/message_pump_libevent.cc:271: error: ‘event_add’ was not declared in this scope base/message_pump_libevent.cc:272: error: ‘EVLOOP_ONCE’ was not declared in this scope base/message_pump_libevent.cc:272: error: ‘event_base_loop’ was not declared in this scope base/message_pump_libevent.cc:273: error: ‘event_del’ was not declared in this scope ./base/scoped_ptr.h: In destructor ‘scoped_ptr<C>::~scoped_ptr() [with C = event]’: base/message_pump_libevent.cc:169: instantiated from here ./base/scoped_ptr.h:71: error: invalid application of ‘sizeof’ to incomplete type ‘event’ ./base/scoped_ptr.h:72: warning: possible problem detected in invocation of delete operator: ./base/scoped_ptr.h:72: warning: invalid use of incomplete type ‘struct event’ ./base/message_pump_libevent.h:13: warning: forward declaration of ‘struct event’ ./base/scoped_ptr.h:72: note: neither the destructor nor the class-specific operator delete will be called, even if they are declared when the class is defined. make: *** [out/Release/obj.target/base/base/message_pump_libevent.o] Error 1
We're now stabilizing chromium-5.0.375.70-r1 to get the workaround for flash hangs from bug #324365. amd64, sorry I had to add you back after you stabilized 5.0.375.70. The changes are minimal, just one patch added. I'm fine with just a compile check on your side. Tiago, please do not comment here, but file a separate bug report. Unfortunately, I can't reproduce the problem.
Sorry, will start a new one. Thanks
amd64 done
(In reply to comment #9) > amd64 done > However, this revision of chromium hangs with stable adobe-flash but works with testing one Is it just me? If so,we should drop the keywords until the latest adobe-flash is stable
x86 stable and closing
I have www-client/chromium-5.0.375.70-r1 and www-plugins/adobe-flash-10.1.53.64, and flash doesn't work anymore. (In reply to comment #10) > (In reply to comment #9) > > amd64 done > > > > However, this revision of chromium hangs with stable adobe-flash but works with > testing one > > Is it just me? If so,we should drop the keywords until the latest adobe-flash > is stable >
