Comment 2 for bug 859104

I originally planned to send the following email to all the projects listed at the bottom, but it turns out to be more complicated than I thought, between the larger projects that have maintainer groups, and individuals without a public email address. I am thus going to add the projects as being affected by this bug, if not you can change the status of this bug for your own program.

Subject: About your Nautilus extension being [probably] broken in Ubuntu 11.10
To: All developers of Nautilus scripts written in Python

Body:
Hi all,

I'm sending you this email since you are developing a Nautilus extension in Python that is available in Ubuntu 11.10 (list of such packages at the end of this email).
I have created such an extension myself and packaged it for Debian. It is available there in the "testing" version [0]. The extension installs correctly in Debian. However, the extension does not show up in Nautilus in Ubuntu 11.10 (beta 2 for now) (exact same version as in Debian).

These are the version of Nautilus-Python/Python-Nautilus that are packaged:
- In Debian: 0.6.1 [1]
- In Ubuntu 11.10: 1.0 [2]

Looking at the release notes, significant changes have been made in versions 0.7 and 1.0 that change the paths where the extensions are to be looked in.

I have opened 2 bug reports that are relevant to this issue [3] and [4]. I suspect the problem is related to 2 things:
- The extensions are not looked for anymore in the familiar /usr/lib/nautilus/extensions-2.0/python
- Importing the module `nautilus` is not valid anymore

I have installed various of your extensions, all of which failed to display in Nautilus. I suspect that a lot (all?) of the Nautilus extensions written in Python are currently broken in Ubuntu 11.10. Have you tested your packages in the latest Ubuntu Beta, before your regular users start opening bug reports? This is the reason for the broad list of recipients.

I have opened a bug report against Nautilus-Python [5] for us to track the extent of this issue, and hopefully find a solution for it. Please mark your project/package as affected by this bug (by using the "Also affects distribution" link) so that we can keep track of the affected packages, and share the solution to fix this. Don't forgot to add a comment to this bug when doing so.

Sorry for the "spam", let's fix this!
Cheers,
    +Emilien

[0] http://packages.qa.debian.org/n/nautilus-image-manipulator.html
[1] http://packages.qa.debian.org/n/nautilus-python.html
[2] https://launchpad.net/ubuntu/+source/nautilus-python
[3] https://bugs.launchpad.net/ubuntu/+source/nautilus-python/+bug/858925
[4] https://bugs.launchpad.net/ubuntu/+source/nautilus-image-manipulator/+bug/849361
[5] https://bugs.launchpad.net/ubuntu/+source/nautilus-python/+bug/859104

emilien@ubuntu1110b2:~$ apt-cache rdepends python-nautilus
python-nautilus
Reverse Depends:
  tortoisehg-nautilus
  sparkleshare
  rabbitvcs-nautilus
  postr
  nautilus-pastebin
  nautilus-image-manipulator
  nautilus-clamscan
  nautilus-bzr
  nautilus-arista
  kupfer
  groundcontrol
  arkose-nautilus
  libnautilus-extension1