Hi Andi, any chance for a quick fix there? Thanks a lot, Thorsten Stephan Bergmann wrote:
Quoting <https://bugs.freedesktop.org/show_bug.cgi?id=65795#c7> on "Syntax error in Extension Manager when trying to update": "The reason [for the syntax error] is that <http://updateexte.libreoffice.org/ExtensionUpdateService/check.Update> references a completely empty file. That URL is the value of the ExtensionUpdateURL property in the version ini file. It is used by getDefaultUpdateInfos (desktop/source/deployment/misc/dp_update.cxx) to try and obtain 'backup' update information from one central place for all those extensions that fail to provide their own update information. The current <http://updateexte.libreoffice.org/ExtensionUpdateService/check.Update> URL is used since <http://cgit.freedesktop.org/libreoffice/core/commit/?id=52456c0acaaebe1c85d07c90a94a82c9efa4850f> 'Switch all urls from TDF to LibreOffice.' The prior, OOo-specific URL <http://updateexte.services.openoffice.org/ExtensionUpdateService/check.Update> still delivers a file starting with<?xml version="1.0" encoding="utf-8"?> <feed xmlns="http://www.w3.org/2005/Atom"; xml:lang="en-US"> <title>Extension Update Feed</title> <link rel="alternate" type="text/html" href="http://extensions.openoffice.org"/> <updated>2013-03-18T12:03:22+00:00</updated>"I have no idea who is responsible for the empty file at <http://updateexte.libreoffice.org/ExtensionUpdateService/check.Update>. "I see three options to fix this: "1 Fix the file at <http://updateexte.libreoffice.org/ExtensionUpdateService/check.Update> to conform to the expected syntax (even if it would not contain any true payload yet, but could do so in the future). That would fix this issue even for already released versions of LO. "2 Give the ExtensionUpdateURL property in the version ini file an empty value. That would not fix this issue for already released versions of LO, and for future versions of LO would disable the (currently unused) feature of providing such central 'backup' extension update information (until we change the value back in a later release). "3 Remove the (currently unused) feature of providing such central 'backup' extension update information completely from the code. That would not fix this issue for already released versions of LO. "I favour option 1 and will see to get hold of somebody to fix the file at <http://updateexte.libreoffice.org/ExtensionUpdateService/check.Update>." So, who can fix that file (or propose a better fix)? Stephan _______________________________________________
-- Thorsten
Attachment:
signature.asc
Description: Digital signature