Hi, > How are exporters supposed to be registered ? Can we manually request a > re-registration > of that exporter, possibly with verbose traces ?
Only what unopkg sync does... (which is what the trigger does) afaik. > broken, and a bold warning should be displayed from preinst, should that > be the case. Had that once when we called unopkg add and that would fail when OOo was there. Since then it's gone, and no, I don't want this mess back. > Looking at the various installed filters .xcu files, it looks like this > one is the only one > using <<oor:op="fuse">>, other (writer2latex, pdfimport) rather use > <<oor:op="replace">>. Good catch. > mv /usr/lib/libreoffice/share/extensions/wiki-publisher / > /var/lib/dpkg/info/libreoffice-common.postinst triggered > /usr/lib/libreoffice/share/extensions > mv /wiki-publisher/ /usr/lib/libreoffice/share/extensions/ > $EDITOR /usr/lib/libreoffice/share/extensions/wiki-publisher/Filter.xcu > /var/lib/dpkg/info/libreoffice-common.postinst triggered > /usr/lib/libreoffice/share/extensions > > ... and guess what ? it just worked :) Whee. > Now the export filter is selectable in the export dialog, and "send to" > finds it as well... > > So one question remains, what was this "fuse" supposed to do ? Honestly, I need to google that up myself... Regards, Rene -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
