Please backport bluefish 2.2.6-1 (universe) from utopic

Bug #1349065 reported by Klaus Vormweg
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
trusty-backports
Undecided
Unassigned

Bug Description

Please backport bluefish 2.2.6-1 (universe) from utopic to trusty.

Reason for the backport:
========================
Bluefish 2.2.5 has a grave functionality bug in CSS syntax highlighting + a nasty crash bug. When closing the progam while the intregated file manager has the root directory as current it will crash on startup (https://bugzilla.gnome.org/show_bug.cgi?id=728677)

Testing:
========
Mark off items in the checklist [X] as you test them, but please leave the checklist so that backporters can quickly evaluate the state of testing.

You can test-build the backport in your PPA with backportpackage:
$ backportpackage -u ppa:<lp username>/<ppa name> -s utopic -d trusty bluefish

* trusty:
[X] Package builds without modification
[X] bluefish installs cleanly and runs
[X] bluefish-dbg installs cleanly and runs
[X] bluefish-plugins installs cleanly and runs
[X] bluefish-data installs cleanly and runs

Reverse dependencies:
=====================
The following reverse-dependencies need to be tested against the new version of bluefish. For reverse-build-dependencies (-Indep), please test that the package still builds against the new bluefish. For reverse-dependencies, please test that the version of the package currently in the release still works with the new bluefish installed. Reverse- Recommends, Suggests, and Enhances don't need to be tested, and are listed for completeness-sake.

bluefish
--------
* edubuntu-desktop
  [ ] trusty (Reverse-Recommends)

bluefish-dbg
------------

bluefish-plugins
----------------

bluefish-data
-------------

Revision history for this message
Felix Geyer (debfx) wrote :

Sounds like it would be much better to release the bugfixes through a SRU so everyone benefits from the fixes:
https://wiki.ubuntu.com/StableReleaseUpdates

The diff between 2.2.5 and 2.2.6 doesn't look reviewable so the relevant commits would have to be cherry-picked.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers