FFe: Please sync with upstream version of Midori to the latest version, the current version is very unstable alpha

[Ed Hewitt]

Binary package hint: midori

The version of Midori that ships with jaunty is 0.1.2. While far more stable that 0.0.18, it is still an alpha quality release. 0.1.4 incorporates many fixes, and appears to be regression free in comparison to 0.1.2.

Debian unstable currently uses 0.1.4. Apart from the benefits of being in sync with debian, the upstream developer looks at bugs on the latest stable release before he looks at older releases which have possibly fixed bugs.

If you want to test the latest version of midori and webkit add the WebKit Team and Midori PPAs

------ Original Description -----
Binary package hint: midori

The version of Midori which comes with Xubuntu 8.10 is 0.0.18. It is a very unstable release. The browser will crash all the time. When you are loading webpages, closes or opening tabs. It will just crash unexpectedly.

Please upgrade the package to the latest version, 0.1.4

[Charlie Kravetz (cjkgeek)]

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here.

I would ask if you have tried Jaunty? It does have midori 0.1.1

Thanks for taking the time to make Ubuntu better!

[Ed Hewitt (edhewitt-deactivatedaccount)]

I am testing Jaunty, but have not tested midori in it.

Is there a backport of midori for 8.10. I would test that.

[Sindhudweep Sarkar (sindhudweep-sarkar)]

0.1.3 needs packaging for jaunty.

[Sindhudweep Sarkar (sindhudweep-sarkar)]

0.1.4

[Alessandro Scarozza (xan.scale)]

midori 0.1.4 will came in jaunty or we need to wait 9.10?

[Martin Pitt (pitti)]

I subscribed motu-release. Please include or provide a link to an upstream changelog. Does this provide any new features, or just bug fixes? In the former case, motu-release needs to acknowledge a FF exceptionl.

[Iulian Udrea (iulian)]

Please see https://wiki.ubuntu.com/FreezeExceptionProcess and include the required information.

I'm changing the status of this bug back to NEW as we use CONFIRMED when the exception is granted.

Just to let you guys know that the Feature Freeze is in effect. You will need an exception for this if the new upstream release provides new features as Martin said in the above comment, otherwise you don't need an exception. A Developer will still need to acknowledge this.

[Luca Falavigna (dktrkranz)]

Also, it could be interesting to see if outstanding bug reports are fixed with new release.

[Savvas Radevic (medigeek)]

Hi, I thought of providing some more info for this bug report:

v0.1.5:
 + Add a Colorful Tabs extension
 + Support downloading with WebKitGTK+ 1.1.3
 + Load and save settings of extensions
 + Drop internal source view
 + Require WebKitGTK+ 1.1.1, Glib 2.16 and libsoup 2.25.2

v0.1.4:
 + Automatic inline find can be disabled
 + Implement an Encoding menu
 + Add Open all in Tabs for bookmarks and history
 + Bookmarks can be moved to other folders
 + Fix blank page 'loading' and HTTP authentication
 + Display history dates in the local format
 + Allow editing of completion items

v0.1.3:
 + Sidepanel can be aligned on the right
 + Bookmarks can be organized in folders
 + Support find as you type
 + Support international domain names
 + Tweak location completion
 + Provide default search engines
 + Integrate with Maemo if available
 + Implement Mouse Gestures extension
 + Implement a Plugins panel
 + Editing the toolbar via a context menu
 + Introduce Zoom Text and Images preference

Comparing to the package midori 1.4-2 (Debian experimental), it requires the update of some other packages, libwebkit-dev (>= 1.1):

Build-Depends:
 debhelper (>= 7.2),
 quilt,
 libgtk2.0-dev (>= 2.10),
 libglib2.0-dev,
 libwebkit-dev (>= 1.1),
 libxml2-dev (>= 2.6),
# For waf:
 python,
# Optional dependencies:
 intltool,
 libidn11-dev,
 librsvg2-bin,
 libsqlite3-dev,
 libunique-dev (>= 1.0.6),
 python-docutils,
 libsoup2.4-dev (>= 2.25.2),
# Disabled optional dependencies:
Build-Conflicts:
 gtk-doc-tools,
 libgtksourceview2.0-dev (>= 2.0),
 libhildon-1-dev

[Savvas Radevic (medigeek)]

I guess the only (important?) bug fix in these versions is this one:
" + Fix blank page 'loading' and HTTP authentication"

The rest of them seem improvements, featureful, yet I don't know if the ubuntu admins/packagers would allow this. :)

[Nathan Handler (nhandler)]

Has any testing been done with this new version of midori? Also, would any of the other bugs filed against midori on Launchpad be fixed with this new upstream release? Also, just to verify, you are requesting that we update to the latest upstream version, not the version currently in Debian, correct? If so, could you please explain why we would want to do this, especially this late in the cycle?

[Sindhudweep Sarkar (sindhudweep-sarkar)]

Some testing has been done using the packages in this ppa: https://edge.launchpad.net/~webkit-team/+archive/ppa.

WRT to the issues about the lateness in the cycle, most of the changes in Midori are new features, which in theory can't regress. Upgrading webkit this late in the cycle might be more of a concern. At this point a backport for Midori might be the best option.

[Sindhudweep Sarkar (sindhudweep-sarkar)]

My mistake, the owner of the ppa split out midori into it's own ppa, which depends on the webkit ppa.

https://edge.launchpad.net/~midori/+archive/ppa

[Scott Kitterman (kitterman)]

It's rather too late for this now. In any case a sync would have been inappropriate due to the existing Ubuntu changes. This should be merged (subject of a separate bug) for Karmic.