Your message dated Tue, 29 Jan 2013 13:27:34 +0100
with message-id <[email protected]>
and subject line Re: accessodf: doesn't work with LO 4.0; uses (internal) 
unpublished API
has caused the Debian Bug report #699234,
regarding accessodf: doesn't work with LO 4.0; uses (internal) unpublished API
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
699234: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699234
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: accessodf
Version: 0.1-1.3
Severity: important
Tags: upstream wheezy-ignore

Hi,

rene@SheevaPlug:~/accessodf-0.1$ grep -r com\.sun\.star\.accessibility
addon/be/docarch/accessodf/ooo/toolpanel/AccessibilityPanel.java:import 
com.sun.star.accessibility.XAccessible;

Unfortunately that was _internal_ API and now unpublished in LO 4.0, see
https://wiki.documentfoundation.org/ReleaseNotes/4.0#API_Changes in
"Unpublishing UNO APIs"

accessodf needs to be adapted. Testversions of LO 4.0 are available
at http://people.debian.org/~rene/libreoffice/4.0.0/ (needs stuff
from experimental)

[ this will become grave when LO 4.0 is going to enter unstable... ]

Regards,

Rene

--- End Message ---
--- Begin Message ---
Hi,

On Tue, Jan 29, 2013 at 12:55:33PM +0100, Rene Engelhard wrote:
> Unfortunately that was _internal_ API and now unpublished in LO 4.0, see
> https://wiki.documentfoundation.org/ReleaseNotes/4.0#API_Changes in
> "Unpublishing UNO APIs"
> 
> accessodf needs to be adapted. Testversions of LO 4.0 are available

Nevermind. Discussion on IRC says that I was wrong ;-):

12:56 <@_rene_> hrm. I just noticed a extension which uses 
                com.sun.star.accessibility.XAccessible (unpublished in LO 
                4.0)...
12:56 <@pmladek> sberg: shm_get does the release builds for MAC
12:59 <@_rene_> (http://sourceforge.net/p/accessodf/home/Home/)
13:00 <@_rene_> in Debian as packages.debian.org/accessodf...
13:00  * _rene_ filed http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699234, 
          let's see...
13:00 < loirkerbot> LibreOffice (core) [libreoffice-4-0] heinzlesspam * 
                    icon-themes/tango/ (18 files in 2 dirs): Partially Revert 
                    "New Save, Save As and Reload File icons for the Tango 
                    theme"
13:01 <@_rene_> sberg: am I right with this or am I confusing something? (the 
                extension at least registers in 3.5 and fails to do so in 4.0, 
                so..)
13:03 <@_rene_> thorsten: ^ (you committed 
http://cgit.freedesktop.org/libreoffice/core/commit/?id=70626249cd247d9acdad417b8eaf252bae22c059,
 so..)
13:03 < IZBot> core - API CHANGE a11y unpublishing and add/removeListener 
               rename.
13:03 <@_rene_> sberg, thorsten: JYFI :)
[...]
13:21 < mst__> _rene_, the only thing that actually changed in 
               css.accessibility is one listener interface; "unpublished" just 
               means that it may change in the future if a real need for change 
               arises; it's not like we've got _another_ published 
               accessibility interface somewhere that people should use...
13:21 -!- tibbylickle 
          [[email protected]] has 
          quit [Quit: Leaving.]
13:22 <@sberg> pmladek, for the truncation problem I mentioned earlier, I'm 
               working on a patch ATM
13:22 <@_rene_> mst__: so that's not the reason accessodf fails to register in 
                4.0?
13:22 -!- llunak [[email protected]] has quit [Remote 
          host closed the connection]
13:23 <@pmladek> sberg: I am going to add it to MAB. Thanks a lot for 
                 discovering it and also for working on the truncation problem
13:23 < mst__> _rene_, there may be a problem if the extension implements 
               XAccessibleEventBroadcaster but otherwise it's a different 
               problem
13:24 <@_rene_> then it probably is, a grep -r for XAccessibleEventBroadcaster 
                gives nothing, just the one match for 
                com.sun.star.accessibility.XAccessible
13:25 <@_rene_> mst__: thanks. /me will go closing the bug again

Regards,
 
Rene

--- End Message ---

Reply via email to