Bug#688981: unblock: gedit-source-code-browser-plugin/3.0.3-2
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock
Please unblock package gedit-source-code-browser-plugin
It only fixes 2 (meta-?)documentation bugs, with a minimal debdiff:
--- gedit-source-code-browser-plugin-3.0.3/debian/changelog 2012-01-05
10:37:34.000000000 +0100
+++ gedit-source-code-browser-plugin-3.0.3/debian/changelog 2012-09-26
09:37:09.000000000 +0200
@@ -1,3 +1,10 @@
+gedit-source-code-browser-plugin (3.0.3-2) unstable; urgency=low
+
+ * Add "Enhances: gedit" (Closes: #685293)
+ * Fixed typo ("wil") in long description (Closes: #688334)
+
+ -- Pietro Battiston <me@pietrobattiston.it> Wed, 26 Sep 2012 09:32:11 +0200
+
gedit-source-code-browser-plugin (3.0.3-1) unstable; urgency=low
* Initial release. (Closes: #654685)
diff -Nru gedit-source-code-browser-plugin-3.0.3/debian/control gedit-source-
code-browser-plugin-3.0.3/debian/control
--- gedit-source-code-browser-plugin-3.0.3/debian/control 2012-01-05
11:04:52.000000000 +0100
+++ gedit-source-code-browser-plugin-3.0.3/debian/control 2012-09-22
12:56:11.000000000 +0200
@@ -12,8 +12,9 @@
Architecture: all
Depends: ${shlibs:Depends}, ${misc:Depends}, ${python:Depends}, ctags, gedit
(>= 3.0)
Breaks: ${python:Breaks}
+Enhances: gedit
Description: source code class and function browser plugin for Gedit
This plugin will add a new tab to the side pane in the Gedit text editor
which
shows symbols (functions, classes, variables, etc.) for the active document.
- Clicking a symbol in the list wil jump to the line on which that symbol is
+ Clicking a symbol in the list will jump to the line on which that symbol is
defined.
unblock gedit-source-code-browser-plugin/3.0.3-2
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (650, 'testing'), (600, 'unstable'), (500, 'stable-updates'),
(500, 'stable'), (400, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores)
Reply to: