Comment 3 for bug 379907

Please un-subscribe main-sponsors. I thought this only needed a rebuild, but that's not the case.

The Nautilus package actually explicitly breaks nautilus-gksu (<< 2.0.2-2+b1)

From nautilus debian/control:

Package: libnautilus-extension1
Architecture: any
Section: libs
Depends: ${misc:Depends},
         ${shlibs:Depends}
Conflicts: libnautilus2-2
Breaks: nautilus (<< 2.22),
        gnome-mount (<< 0.8),
        nautilus-cd-burner (<< 2.22),
        file-roller (<< 2.24),
        python-nautilus (<< 0.5),
        nautilus-sendto (<< 0.14.0-2),
        nautilus-open-terminal (<< 0.9),
        nautilus-image-converter (<< 0.3),
        nautilus-filename-repairer (<< 0.0.5-2),
        eiciel (<< 0.9.6.1-3),
        diff-ext (<= 0.2.3-3),
        nautilus-gksu (<< 2.0.2-2+b1),
        nautilus-actions (<< 1.4.1-1+b1),
        nautilus-share (<< 0.7.2-4+b1),
        seahorse-plugins (<< 2.24.1-3+b1)

We seem to have picked this up from Debian in the last merge:

nautilus (2.26.2-1) unstable; urgency=low

  * Break eiciel, diff-ext, nautilus-gksu, nautilus-actions,
    nautilus-share and seahorse-plugins until versions rebuilt with the
    new extension path.

I think this was probably done inadvertently. Apparently 2.0.2-2ubuntu2 < 2.0.2-2+b1

Opening a Nautilus task.