Synctex plugin was not built in raring

The plugins package(s) were built on 13 Nov 2012 & while python-dbus-dev (1.1.1-1ubuntu2) was installed for build maybe not 'good enough' or something else, as seen in build log -
"Disabled plugins: synctex (dbus-python not found)"

When doing a package build here locally with current 1.1.1-1ubuntu3 there is no issue with the plugin being built, installed & enabled. (Whether it works right not in a position to tell, that's for someone else..

Been confirmed that the plugin does work ok, source just needs a simple rebuild.

The attachment "gedit-plugins_3.6.1-0ubuntu2.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.]

Thanks, do you have an explanation of why a no change rebuild would fix it? The diff you attached is also not a "no change" one, the debian/control description changed

the issue from https://launchpadlibrarian.net/122902634/buildlog_ubuntu-raring-i386.gedit-plugins_3.6.1-0ubuntu1_BUILDING.txt.gz is "configure: WARNING: dbus-python could not be found, synctex plugin will be disabled", e.g missing build-depends, I will fix that

(the control update was a side effect of control.in->control auto refresh, not a change)

Sorry about that (the debdiff), seemed like the source just needed to be rebuilt with no changes (didn't get why the control.in > control deal happened.
As far as build deps thought that because python-dbus depends on python-dbus-dev that it was ok for the build dep to remain on python-dbus (can't install one without the other & build log did show python-dbus-dev being installed for LP build..

This bug was fixed in the package gedit-plugins - 3.6.1-0ubuntu2

---------------
gedit-plugins (3.6.1-0ubuntu2) raring; urgency=low

  * debian/control.in: build-depends on dbus-python-dev rather than
    dbus-python, since the .pc has been moved to that binary (lp: #1165742)
 -- Sebastien Bacher <email address hidden> Wed, 10 Apr 2013 16:00:35 +0200

I have gedit-plugins - 3.6.1-0ubuntu2 installed (and re-installed) but still no synctex plugin under Ubuntu 13.04.

The build logs https://launchpadlibrarian.net/136861019/buildlog_ubuntu-raring-i386.gedit-plugins_3.6.1-0ubuntu2_UPLOADING.txt.gz and https://launchpadlibrarian.net/136860798/buildlog_ubuntu-raring-amd64.gedit-plugins_3.6.1-0ubuntu2_UPLOADING.txt.gz
still show that Synctex was disabled on build :
checking whether Python support is requested... checking for DBUSPYTHON... no
configure: WARNING: dbus-python could not be found, synctex plugin will be disabled

You guys may have already done this, but I managed to do a temporary fix by downloading the quantal gedit-plugins deb and extracting synctex plugin. I copied the plugin file and the plugin folder manually:

sudo cp -r synctex.plugin synctex /usr/lib/gedit/plugins

I have attached the necessary file and folder.

There is another problem:

python-dbus-dev requires libdbus-1-dev but does NOT depend on it, or at least pkg-config thinks so, so configure thinks it's not there.

pkg-config --cflags dbus-python
# Package dbus-1 was not found...

sudo apt-get install libdbus-1-dev

pkg-config --cflags dbus-python
# -I/usr/include/......

Once I do this, the synctex plugin builds.

So, while this *should* be fixed in dbus-python, there exists the hilarious situation right now that python-dbus depends on python-dbus-dev for backward compat, so making python-dbus-dev depend on libdbus-1-dev would pull libdbus-1-dev onto every desktop, which is less than ideal.

When that backward compat dependency is removed, someone should fix python-dbus-dev's dependencies.

gedit-plugins in saucy already has the extra libdbus-1-dev build-dep, so this should be working correctly there. Thus, the only thing that could use a fix is a raring SRU of gedit-plugins, if someone feels the urge.

raring has seen the end of its life and is no longer receiving any updates. Marking the raring task for this ticket as "Won't Fix".