Win10 with LIBO_UPDATER_TEST_ENABLE variable set. Version: 24.2.5.1 (X86_64) / LibreOffice Community Build ID: 2ccb78ad6bdfe3f3356a7a7f294ec388775c5816 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: default; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded
From 24.2.5.1 install would expect MAR updt to 24.2.5.2 at this point, or now even 24.2.6.1. Log full of checks and download failure "warning: error by the updaterdownload did not succeed: Likewise for a /a admin install of 24.8.0.3 on Win10, Would expect MAR updt to 24.8.1.1, but that may be too soon. =-Log snippets-= Update Check Time: 4659010 Update check: https://update-mar.libreoffice.org/update/check/1/LibreOffice 24.2.5.1/2ccb78ad6bdfe3f3356a7a7f294ec388775c5816/Windows_X86_64/LOOnlineUpdater Download: https://update-mar.libreoffice.org/update/check/1/LibreOffice 24.2.5.1/2ccb78ad6bdfe3f3356a7a7f294ec388775c5816/Windows_X86_64/LOOnlineUpdater warning: error by the updaterdownload did not succeed same warning for weeks, every launch of LO, even across manual updates as I applied via MSI (which changed the build ID logged). Likewise on an /a admin install of 24.8.0.3, each launch checks but fails. Update Check Time: 3647674 Update check: https://update-mar.libreoffice.org/update/check/1/LibreOffice/0bdf1299c94fe897b119f97f3c613e9dca6be583/Windows_X86_64/LOOnlineUpdater Download: https://update-mar.libreoffice.org/update/check/1/LibreOffice/0bdf1299c94fe897b119f97f3c613e9dca6be583/Windows_X86_64/LOOnlineUpdater warning: error by the updaterdownload did not succeed
Created attachment 196042 [details] multi-week updating.log from profile (non-priv) with failed downloads across installs updating.log attached @cloph, is there a packaging issue as per your prior note? https://bugs.documentfoundation.org/show_bug.cgi?id=68274#c83
I never got pass 24.2.4.2 but in my case, it doesn't even start the update process. It just starts Libreoffice normally like there is no new versions available...
@Stephan Bergmann Any clue on how we can fix this (if we can even do anything at all...) ??? Either with -env:LIBO_UPDATER_TEST_ENABLE (or -env:LIBO_UPDATER_ENABLE for that matter) or without it and just starting normally It just doesn't work! And this happens for several versions already... thank you!
I'm having the same problem with admin /a installed 24.2.4 on Windows 11 23H2. Just regular MAR configuration through UI (enable experimental features, turn on autoupdate), no env variable involved. -- Snippet from updating.log -- Update Check Time: 66398116 Update check: https://update-mar.libreoffice.org/update/check/1/LibreOffice/51a6219feb6075d9a4c46691dcfe0cd9c4fff3c2/Windows_X86_64/LOOnlineUpdater Download: https://update-mar.libreoffice.org/update/check/1/LibreOffice/51a6219feb6075d9a4c46691dcfe0cd9c4fff3c2/Windows_X86_64/LOOnlineUpdater warning: error by the updaterdownload did not succeed
just to be sure, if one wants to force update on 24.8 what we have to run is: soffice.exe -env:LIBO_UPDATER_ENABLE=1 no commas, no _TEST, just like it is... can anyone confirm?
(In reply to Maverick from comment #6) >... > soffice.exe -env:LIBO_UPDATER_ENABLE=1 > > > no commas, no _TEST, just like it is... > > can anyone confirm? Nope, there has been no change in source to the env varaibles LIBO_UPDATER_TEST_ENABLE LIBO_UPDATER_TEST_UPDATE LIBO_UPDATER_TEST_RUNNING Though, don't set any but the LIBO_UPDATER_TEST_ENABLE "1"--or what ever that env gets adjusted to--LO won't launch otherwise. The URL for update-mar.libreoffice.org resolves in DNS (aliased from gimli.documentfoundation.org where the SDK docs reside). The MAR updates just do not seem to be rolling/posting. @Cloph? =-PS-= QA appology--setting NEW myself as I also continue to be unable to update with MAR packaging.
Created attachment 196504 [details] update.log from LO 24.2.0.3 /a admin install and update to 24.2.4.2 but no further @cloph, are the MAR incrementals somehow misconfigured? Or even being built beyond 24.2.4.2? Attached log from a clean /a admin install on Win10 with LIBO_UPDATER_TEST_ENABLE set enabled. On first launch the install cycles through a MAR update, but stops at 24.2.4.2 Subsequent launches log the update check but show error: "warning: error by the updaterdownload did not succeed"
Just checked, and both 24.2.0.3 and 24.8.0.3 /a admin installs are receiving their full MAR update sequence to current release build. Log visible in the user profile 'updates' directory.
It's been, apparently, working in the last few days because i've got a few machines updating... however, i have a few other points: 1. i have a few other machines that got updated to 24.2.5 but that are not updating to 24.2.6 (even with the variable set/forced to)... 2. i have another one i'm using for testing this that had 24.8.0.3 and updated to 24.8.1.1 but not to 24.8.1.2 3. I was also expecting it to make the jump from 24.2 to 24.8 (since the latter is available ans is "supperior")... Will that ever happen automatically (maybe when 24.8.3 is out / after the EOL of 24.2) ??? can anyone clarify some of this points? Thanks
OK, i've found a solution to 1. by resetting LO definitions. So it might have been "something" i did or "something", somehow, got broken with usage... anyway, resetting fixed it. 2. and 3. however, remain...
LibreOffice has not updated to 24.8.2 either (even with it being out for a while now) When a new version is out doesn't the MAR files get generated automatically??? If yes, i think someone should really fixed it because it does not seem to be working
*** Bug 163940 has been marked as a duplicate of this bug. ***
Today we received another round of MAR updates (update.mar) 24.8.2.1 -> 24.8.3.1, and then -> 24.8.3.2 Recorded in the user profile. E.g. defaults on Windows to: C:\Users\<username>\AppData\Roaming\LibreOffice\4\updates\updating.log
just a question: 24.2 is now on End-Of-Life! Are we to expect it to eventually auto-update to 24.8 automatically? Or do we have to manually download and install 24.8? Can anyone, please, clarify this?
"Automatic Update" has never worked for me so far. Now I'm on version 24.8.3 and, three days after the release of version 24.8.4, I've received no updates. Traditionally, I update manually as soon as a new version is published. I don't know if an "Automatic Update" should take more than a few days. I think I'll manually update again this time, and hopefull things will work from 24.8.4 to 24.8.5.
(In reply to David García from comment #16) > "Automatic Update" has never worked for me so far. > > Now I'm on version 24.8.3 and, three days after the release of version > 24.8.4, I've received no updates. If you like to have the updates as soon as they're out (like me), then you'll have to update manually for now. My experience is that the update system does work, but someone is not creating the mar files (which i believe were suppose to be created automatically but, somehow, aren't and depend on some "manual" intervention)... these updates come late (e.g.: weeks after the release) and sometimes even come after one or two releases (resulting in LO applying multiple updates in a single day to catch up). They'll eventually fix it... i hope... The bottom line is that the system does work and you can indeed leave it be if you want and it will eventually update itself! "Eventually" is the key-word here!
(In reply to Maverick from comment #17) > (In reply to David García from comment #16) > > "Automatic Update" has never worked for me so far. > > > > Now I'm on version 24.8.3 and, three days after the release of version > > 24.8.4, I've received no updates. > > If you like to have the updates as soon as they're out (like me), then > you'll have to update manually for now. > > My experience is that the update system does work, but someone is not > creating the mar files (which i believe were suppose to be created > automatically but, somehow, aren't and depend on some "manual" > intervention)... > > these updates come late (e.g.: weeks after the release) and sometimes even > come after one or two releases (resulting in LO applying multiple updates in > a single day to catch up). > > They'll eventually fix it... i hope... > > The bottom line is that the system does work and you can indeed leave it be > if you want and it will eventually update itself! > > "Eventually" is the key-word here! Thanks for the information. I think I'll wait for 25.02 and try again to see if the feature works as expected. In the meantime, I'll just keep updating manually.
MAR incremental update packages for 24.8.4.1 (1be9007 30 Nov 2024) and then 24.8.4.2 (bb3cfa 15 Dec 2024) just rolled today 20250111 against a 24.8.3.2 (48a6bac 9 Nov 2024) install updated at the last round on a system with LIBO_UPDATER_TEST_ENABLE set true. @cloph, @sberg are the incrementals being auto built now on a schedule, and we should expect this one month delay from community patch release builds, and no early delivery of the rc1? Or are they still being rolled by hand, with rc1/rc2 done together as they come due?
there won't be updates from stable to rc1 unless you use custom staging URL, so yes, for most users they'll always get rc1 and rc2 simultaneously - delay of the current release was just due to holiday season, but usually you can expect the rollout to start the week after the announcement. There's a little infra work to be done since unfortunately the hoster did significantly cut down included traffic for cloud machines, but that should be transparent to the enduser. if you're on manually installed rc1, you can expect earlier update to rc2/final, but the timing is also not defined since adding to the mar-update mirrors is done separately after prepping the regular mirrors/the regular installsets. Esp. populating mar mirrors with in-between versions might be delayed if there's multiple branches to be done since building the full installsets takes priority over creating the diff-packages. Also cross-update of older version to newer version will only be enabled once the demand for same-codeline updates did settle down, to ensure reliable connections/fast downloads.
(In reply to Christian Lohmaier from comment #20) Yay! And see you've started to annotate MAR dates on the release plan [1] Incremental updating progressing nicely! Key takeaways for normal users: -- about 1-week following release date of each branch minor's final (rc1 + rc2 then pkg as final with MARs incremental to each) -- possibility of offering a MAR based branch major version cross-update is still maturing, but not yet Appreciate the update. =-ref-= [1] https://wiki.documentfoundation.org/ReleasePlan
(In reply to V Stuart Foote from comment #21) > -- possibility of offering a MAR based branch major version cross-update is > still maturing, but not yet i'm sorry, can you elaborate a bit more on this? You mean, e.g.: 24.2.7 > 24.8.4 ? if yes, what seems to be the obstacles?