Review from Microsoft Store

2023-03-06 Thread Matthias Seidel
Hi all,

I now have users on the Microsoft Store complaining about "locked" files
after updating to AOO 4.1.14:

Update Broken
The fact that the update doesn't run through the Microsoft Store is a
big red flag for me. It would simplify things if software initially
installed through Microsoft Store updated properly through that channel.
The bigger problem is after installing the update, all my files are
locked. I can't open any of them. All I get is a warning about the files
being password protected when I did no such thing. If I can't access my
files, what's the point. I might as well throw away money on monthly
extortion to access my work via Microsoft Office.

Any idea?

The "problem" with the Store itself is known, but not under our control.

Regards,
   Matthias


smime.p7s
Description: S/MIME Cryptographic Signature


Re: Review from Microsoft Store

2023-03-06 Thread Matthias Seidel
Am 06.03.23 um 17:14 schrieb Matthias Seidel:
>
> Hi all,
>
> I now have users on the Microsoft Store complaining about "locked"
> files after updating to AOO 4.1.14:
>
> Update Broken
> The fact that the update doesn't run through the Microsoft Store is a
> big red flag for me. It would simplify things if software initially
> installed through Microsoft Store updated properly through that
> channel. The bigger problem is after installing the update, all my
> files are locked. I can't open any of them. All I get is a warning
> about the files being password protected when I did no such thing. If
> I can't access my files, what's the point. I might as well throw away
> money on monthly extortion to access my work via Microsoft Office.
>
> Any idea?

The user complains about not being able to install the update, then he
complains that his files are now "locked" or "password protected" now.

So how did he install the update after all?

I asked him to write details to this list...

>
> The "problem" with the Store itself is known, but not under our control.

The "solution" is to deinstall AOO before installing 4.1.14.

Microsoft still has to deliver a better way to install updates through
the Store.

Regards,

   Matthias

>
> Regards,
>    Matthias


smime.p7s
Description: S/MIME Cryptographic Signature


Re: Buildbot problems

2023-03-06 Thread Damjan Jovanovic
Unfortunately that's not our only problem.

Even before the MozillaBuild update, every "build --all" got "cancelled"
after about 37 minutes. For example see
https://ci2.apache.org/#/builders/67/builds/628

Regards
Damjan

On Sun, Mar 5, 2023 at 10:16 PM Matthias Seidel 
wrote:

> Hi Damjan,
>
> Thank you for all the work on the buildbots!
>
> Looking at the Windows bot now:
>
> checking whether to build LDAP configuration backend... checking whether to 
> build the internal NSS module... yes
> configure: error: Mozilla build tooling incomplete!
>
> It seems like MozillaBuild was updated to 4.x, which we do not support yet.
>
> Regards,
>
>Matthias
>
> Am 02.03.23 um 05:46 schrieb Damjan Jovanovic:
>
> On Sun, Jan 22, 2023 at 1:33 PM Matthias Seidel  
> 
> wrote:
>
>
> Now regarding Awk, instead of doing:
> rm /bin/awk
> mv /bin/gawk.exe /bin/awk.exe
> can't we prepend PATH with a directory containing an "awk" script that
>
> just
>
> calls gawk.exe?
>
> It would be great if there is a better way to do it. I just followed our
> Windows building guide all these years.
>
> But this is beyond my capabilities and one of the reasons why I cannot
> maintain our buildbots anymore.
>
>
> This approach did eventually work. I eventually succeeded in creating an
> "awk" script that calls "gawk" and setting PATH to its directory within
> Cygwin, and ./configure now gets further.
>
> Now the next problem is that Cygwin doesn't have gcc and g++ 
> (https://ci2.apache.org/#/builders/67/builds/516/steps/9/logs/stdio):
>
> which: no gcc in
>
>
> (/cygdrive/e/buildbot/openoffice-win10/utils:/usr/local/bin:/usr/bin:/cygdrive/e/Python39/Scripts:/cygdrive/e/Python39:/cygdrive/c/ProgramData/Oracle/Java/javapath:/cygdrive/c/Windows/system32:/cygdrive/c/Windows:/cygdrive/c/Windows/System32/Wbem:/cygdrive/c/Windows/System32/WindowsPowerShell/v1.0:/cygdrive/c/Windows/System32/OpenSSH:/cygdrive/c/Program
>
> Files/Puppet Labs/Puppet/bin:/cygdrive/c/Program Files
> (x86)/Subversion/bin:/cygdrive/c/Program
> Files/Git/cmd:/cygdrive/e/buildbot/tools/Windows Kits/10/Windows
> Performance
> Toolkit:/cygdrive/c/Users/buildbot/AppData/Local/Microsoft/WindowsApps)
> configure: error: cygwin gcc and g++ are needed, please install them.
>
> How can we install them?
>
> That's an Infra job. ;-)
>
>
>
> Weeks ago, on the openoffice-win10 buildbot, many Cygwin dependencies
> somehow got deleted, and days of battling Buildbot and working with Infra
> on https://issues.apache.org/jira/browse/INFRA-24114 were needed to install
> them again.
>
> The git crlf problem on Cygwin was another major issue that needed fixing.
>
> Awk was another, my idea for an "awk" script that calls gawk didn't work, I
> ended up copying /usr/bin/gawk.exe to awk.exe in a directory that is then
> prepended to the PATH environment variable passed to "configure" and
> "build", which worked in my own build and should work on the buildbot too.
> Since this copies gawk on every build, this approach won't be broken by
> future Cygwin upgrades like our previous renaming of gawk to awk by Infra
> was.
>
> I also changed haltOnFailure to False for the "build" step, so that the
> logs are uploaded even when the build fails, like the Linux buildbots do.
> Haven't checked whether that works yet.
>
> It eventually got through configure and started building, but every time
> that happened, the build was cancelled somehow.
>
> Then Java 8 changed somehow (upgrade or whatever), and Java detection
> broke. That has taken several more weeks to fix, and a command I was trying
> to run to log Java's files wasn't working due to a missing bracket which I
> eventually found and fixed.
>
> A further Java problem is that oowintool fails to detect Java, as it's
> looking for the 32 bit Java registry key, while we only have a 64 bit Java
> installed. I had to dig through the buildbot script's history to find a
> working 32 bit Java directory to specify (which oowintool can't detect
> because it's just unzipped, not installed and added to the registry).
>
> With those endless problems fixed, the build is now progressing 
> nicely:https://ci2.apache.org/#/builders/67/builds/625
>
>
> Regards,
>
>Matthias
>
>
>
> Regards
> Damjan
>
>
>


Probleme nach 4.1.14 Update

2023-03-06 Thread christian200...@aol.com.INVALID
Benutze nun seit Jahren täglich ohne Probleme Windows 10 mit Apache Openoffice, 
immer mit den selben Einstellungen. Das System ist zeitnah immer aktuell und 
auf mich als Administrator mit allen Rechten eingerichtet. Seit dem Update auf 
4.1.14 lassen sich die Dateien nur Schreibgeschützt oder als Arbeitskopie 
öffnen. Mit der 4.1.13 auf einem anderem Rechner war es noch normal zu öffnen, 
nach dem Update auf 4.1.14 dann nicht mehr.
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org