+1
Maybe this would be something for long-term?
But what about getting a Developer ID from Apple to get rid of the
gatekeeper-messages?
A lot of traffic on the user-mailinglist is from people who think they
can not install AOO on MacOS because of that...
https://support.apple.com/en-us/HT202491
Hi,
I’m afraid we need a lot of changes to the software to comply with the
sandboxing policy of the Appstore, see
With about three hours to go on the vote, I've prepared a spreadsheet
based on the [VOTE] thread.
The current situation is 10 votes, one [0], nine [+1]. Of the +1 votes,
five are binding. The comments indicate a range of different approaches
to testing, which is good.
Please check the
Le 08/10/2016 à 12:34, Peter Kovacs a écrit :
You seem to like the way ODFormat is defined.
To be precise, I like the the intent of ODF. Several parties decided to work
together so that a fully documented file format could be used with advanced
application features (I mean that could store
+1
I have installed binary 4.1.3-rc1 de Version on OSX El Capitan.
Check the general functionality on the writer module. And checked issue
12662 base not open tables and queries in Mac OSX.
I have opened a empty document in all other modules.
Jose R R schrieb am Sa., 8.
On Wed, Oct 5, 2016 at 2:07 PM, Patricia Shanahan wrote:
> The Apache OpenOffice 4.1.3 source and binaries,
> https://dist.apache.org/repos/dist/dev/openoffice/4.1.3-rc1/, contain
> several bug fixes. See the draft release notes at
>
Patricia Shanahan wrote:
Please test again. I have tried to fix both MIT and the KEYS file.
Thanks, it works now after importing the new KEYS file:
$ gpg --verify apache-openoffice-4.1.3-r1761381-src.tar.gz.asc
apache-openoffice-4.1.3-r1761381-src.tar.gz
gpg: Signature made Sat Oct 1
Patricia Shanahan wrote:
I had to make a change in the key preferences to meet the release
signing requirements. I uploaded to a couple of servers, including MIT,
and waited a few days.
I can find mine here (note: you have to add "0x" for the search to succeed):
I had to make a change in the key preferences to meet the release
signing requirements. I uploaded to a couple of servers, including MIT,
and waited a few days.
I didn't think we were supposed to update KEYS directly?
On 10/8/2016 6:08 AM, Andrea Pescetti wrote:
This is not a blocker for the
This is not a blocker for the release (and moreover signature files are
explicitly allowed to be updated during the release vote if needed), but
I couldn't verify signatures in a straightforward way for source packages.
One of the signatures is mine; no problem with that, and that itself is
On 05/10/2016 Patricia Shanahan wrote:
Please vote on releasing it as 4.1.3 by replying to this thread
[ ] +1 Approve, with description of any testing you have done
[ ] 0 Abstain
[ ] -1 Disapprove, with explanation.
+1 (Binding)
Source: verified hashes and (my own) signature, README, LICENSE,
On 04.10.2016 22:04, Hagar Delest wrote:
Le 04/10/2016 à 06:50, Peter Kovacs a écrit :
ODF has a better trancperency then OOXML. But beeing open we need to
embrace and value both formats.
My fear is: if AOO exports in OOXML (as LibO does), what will happen
to ODF?
You seem to like the
12 matches
Mail list logo