Hi. We have nextcloud-client 3.6.1 so far for MGA8 The latest release is 3.6.4: https://github.com/nextcloud/desktop/releases/tag/v3.6.4 which is quick fix of a mistake done while releasing 3.6.3: https://github.com/nextcloud/desktop/releases/tag/v3.6.3 3.6.4 is the recommended client with Nextcloud 25 and Hub3. 3.6.2 has corrected many bugs as well: https://github.com/nextcloud/desktop/releases/tag/v3.6.2 HOWEVER: -no bugs have been reported by Mageia users -there is no security fix with these releases -the 3.6 branch is still supported SO, my understanding is the package should go to Backport and not Core/updates. BUT, so far, all nextcloud-client updates have been pushed to Core/updates and not Backport. What should I do here, going forward? Cauldron is already up-to-date.
Hi Christian > 3.6.4 is the recommended client with Nextcloud 25 and Hub3. Good reason to update; NC25 is already at point release 25.0.2, and so is what I would want to run if I run NC myself. For NC25, client 3.6.4 is needed for proper file locking in local file edit (which I guess some users want), I read at https://nextcloud.com/blog/maintenance-releases-25-0-2-24-0-8-and-23-0-12-are-out/ > -no bugs have been reported by Mageia users There are however some OS agnostic bugs such as potential data loss if I understand #5225, and some lesser irritating bugs. > -the 3.6 branch is still supported There is not yet even a pre-release of 3.7 what I could find, so lets steam on with 3.6.x > SO, my understanding is the package should go to Backport and not > Core/updates. Why? I see no big change. And a couple bugfixes are significant, such as renaming of deep hierarchy. I suggest to go for 3.6.4, to updates testing.
CC: (none) => friAssignee: bugsquad => chb0
We can't rely solely on the major number. bugfix only updates are allowed even if they add new features, as long as they don't remove features or change configuration requirements for existing features. Basically the question to ask is "If the existing version is working for users, will installing the update stop it from working without manual changes?". If no manual changes required, then updates testing, if changes required, then backports testing. There are exceptions allowed such as maintaining compatibility with servers on other systems that are judged on a case by case evaluation based on the impact on existing users. When in doubt, ask. :-)
CC: (none) => davidwhodgins
Just now I got a message our cloud operator updated our server to 25.0.2, so we like many other users need this client 3.6.4 ;)
Hi. I’ll push it this evening then. I opened up the discussion because the last fail2ban update was as David said, « the update will keep working without user manual change » despite the major version change; the unfortunate thing was a bug in the new release. But it was said it should have been pushed in backport.
Ready for QA
Assignee: chb0 => qa-bugs
ADVISORY NOTICE PROPOSAL ======================== Updated nextcloud-client is the recommended client with Nextcloud 25 and Hub3 Description Update to version 3.6.4 fixes many bugs and is the recommended client with Nextcloud 25 and Hub3. Together with 3.6.2 and 3.6.3, the following improvements are introduced: desktop#5254 [stable-3.6] do not create GUI from a random thread and show error on real error desktop#5171 [stable-3.6] Fix typo of connector desktop#5186 [stable-3.6] fix renaming of folders with a deep hierarchy inside them desktop#5213 [stable-3.6] Make user status selector modal, show user header desktop#5225 [stable-3.6] Prevent bad encrypting of folder if E2EE has not been correctly set up desktop#5237 [stable-3.6] Feature/edit file locally restart sync desktop#5239 Add forcefoldersync method to folder manager desktop#5240 [stable-3.6] Make use of plain text-enforcing qml labels desktop#5246 [stable-3.6] Lock file when editing locally desktop#5249 [stable-3.6] Format some QLabels as plain text [stable-3.6] Fix call notification dialog buttons by @backportbot-nextcloud in #5075 [stable-3.6] emit missing signal to update folder sync status icon by @backportbot-nextcloud in #5090 [stable-3.6] Fix macOS autoupdater settings by @backportbot-nextcloud in #5103 [stable-3.6] Validate and sanitise edit locally token and relpath before sending to server by @backportbot-nextcloud in #5106 [stable-3.6] Fix compatibility with newer python3-nautilus by @backportbot-nextcloud in #5112 [stable-3.6] Refactor FolderMan's "Edit Locally" capabilities as separate class by @backportbot-nextcloud in #5111 [stable-3.6] use new public API to open an edit locally URL by @backportbot-nextcloud in #5117 [stable-3.6] Use separate variable for cfg file name in CMAKE. by @backportbot-nextcloud in #5140 Fix stable-3.6 compile on macOS by @claucambra in #5154 Fix bad backport of CustomButton changes in Stable-3.6 by @claucambra in #5155 Backport/5067/stable 3.6 by @allexzander in #5153 Backport/5092/stable 3.6 by @allexzander in #5156 [stable-3.6] properly escape a path when creating a test file during tests by @backportbot-nextcloud in #5158 References https://bugs.mageia.org/show_bug.cgi?id=31258 https://github.com/nextcloud/desktop/releases/tag/v3.6.4 https://github.com/nextcloud/desktop/releases/tag/v3.6.3 https://github.com/nextcloud/desktop/releases/tag/v3.6.2 SRPMS 8/core nextcloud-client-3.6.4-1.mga8.src.rpm PROVIDED PACKAGES: lib64nextcloudsync0-3.6.4-1.mga8 lib64ocsync0-3.6.4-1.mga8 nextcloud-client-3.6.4-1.mga8 Optional depending on Desktop Environment: nextcloud-client-caja-3.6.4-1.mga8 nextcloud-client-dolphin-3.6.4-1.mga8 nextcloud-client-nautilus-3.6.4-1.mga8 nextcloud-client-nemo-3.6.4-1.mga8 PACKAGES FOR QA TESTING ======================= x86_64: lib64nextcloudsync0-3.6.4-1.mga8.x86_64.rpm lib64ocsync0-3.6.4-1.mga8.x86_64.rpm nextcloud-client-3.6.4-1.mga8.x86_64.rpm nextcloud-client-caja-3.6.4-1.mga8.x86_64.rpm nextcloud-client-dolphin-3.6.4-1.mga8.x86_64.rpm nextcloud-client-nautilus-3.6.4-1.mga8.x86_64.rpm nextcloud-client-nemo-3.6.4-1.mga8.x86_64.rpm i586: lib64nextcloudsync0-3.6.4-1.mga8.i586.rpm lib64ocsync0-3.6.4-1.mga8.i586.rpm nextcloud-client-3.6.4-1.mga8.i586.rpm nextcloud-client-caja-3.6.4-1.mga8.i586.rpm nextcloud-client-dolphin-3.6.4-1.mga8.i586.rpm nextcloud-client-nautilus-3.6.4-1.mga8.i586.rpm nextcloud-client-nemo-3.6.4-1.mga8.i586.rpm
Marketing words... I think we should avoid mentioning "Hub" in advisory and other places too... Or in the advisory proposal change "Nextcloud 25 and Hub3" to "Nextcloud 25 aka Hub3" https://writingexplained.org/aka-or-aka Hub 1 = Nextcloud 22, with certain apps and configuration Hub 2 = Nextcloud 23 or 24, - " - Hub 3 = Nextcloud 25 and maybe further, who knows? + - " - Even upstream need to clarify this double naming for almost (not exaclty, (config, apps)) the same thing: "Nextcloud Hub 3 (25.0.1)" https://nextcloud.com/blog/maintenance-releases-25-0-1-24-0-7-and-23-0-11-are-out/ --- That said, installed and running, report later.
CC: (none) => brtians1
MGA8-64, Xfce, Asus Laptop AMD A6-9225 RADEON R4 RTL8723BE Bluetooth The following 3 packages are going to be installed: - lib64nextcloudsync0-3.6.4-1.mga8.x86_64 - lib64ocsync0-3.6.4-1.mga8.x86_64 - nextcloud-client-3.6.4-1.mga8.x86_64 375KB of additional disk space will be used. this is an upgrade -- rebooted - showing Version 3.6.4 (Mageia) in client settings - synching works
I have not checked the client log since many versions... Should have. (To get log, see https://docs.nextcloud.com/desktop/latest/advancedusage.html) Below is probably bad looking by design, i post it to have it here. It warns for every folder/subfolder that it cannot find a .sync-exclude.lst. Example: 2022-12-13 20:12:10:981 [ warning default /home/iurt/rpmbuild/BUILD/desktop-3.6.4/src/csync/csync_exclude.cpp:438 ]: System exclude list file could not be read: "/home/morgan/Synkning/Bygget/Budget/.sync-exclude.lst" I never made one. Why do it expect them to be there, it is an option to have them. Many hundreds of folders... I guess it is supposed to be informational but then why use the word "warning"? The default one is in $HOME/.config/Nextcloud/sync-exclude.lst, which it do find and use: 2022-12-13 20:11:34:024 [ info nextcloud.sync.configfile /home/iurt/rpmbuild/BUILD/desktop-3.6.4/src/libsync/configfile.cpp:1088 ]: Adding user defined ignore list to csync: "/home/morgan/.config/Nextcloud/sync-exclude.lst"
MGA8 LXQt VM Updated with QA repo ans RPms lib64nextcloudsync0 3.6.4 1.mga8 x86_64 lib64ocsync0 3.6.4 1.mga8 x86_64 nextcloud-client 3.6.4 1.mga8 x86_64 No issues after installation put and delete some files OK Messages returned at update: ldconfig: Fichier /lib64/libMagickCore-7.Q16HDRI.so.10.0.0 est vide, n'a pas été vérifié. ldconfig: Fichier /lib64/libvlccore.so.9 est vide, n'a pas été vérifié. ldconfig: Fichier /lib64/libvlc.so.5 est vide, n'a pas été vérifié. ldconfig: Fichier /lib64/libMagickWand-7.Q16HDRI.so.10 est vide, n'a pas été vérifié. ldconfig: Fichier /lib64/libvlc.so.5.6.1 est vide, n'a pas été vérifié. ldconfig: Fichier /lib64/libMagickCore-7.Q16HDRI.so.10 est vide, n'a pas été vérifié. ldconfig: Fichier /lib64/libvlccore.so.9.0.1 est vide, n'a pas été vérifié. ldconfig: Fichier /lib64/libMagickWand-7.Q16HDRI.so.10.0.0 est vide, n'a pas été vérifié. ldconfig: Fichier /lib64/libMagickCore-7.Q16HDRI.so.10.0.0 est vide, n'a pas été vérifié. ldconfig: Fichier /lib64/libvlccore.so.9 est vide, n'a pas été vérifié. ldconfig: Fichier /lib64/libvlc.so.5 est vide, n'a pas été vérifié. ldconfig: Fichier /lib64/libMagickWand-7.Q16HDRI.so.10 est vide, n'a pas été vérifié. ldconfig: Fichier /lib64/libvlc.so.5.6.1 est vide, n'a pas été vérifié. ldconfig: Fichier /lib64/libMagickCore-7.Q16HDRI.so.10 est vide, n'a pas été vérifié. ldconfig: Fichier /lib64/libvlccore.so.9.0.1 est vide, n'a pas été vérifié. ldconfig: Fichier /lib64/libMagickWand-7.Q16HDRI.so.10.0.0 est vide, n'a pas été vérifié. Tested with Nextcloud version 24.07 HubII
CC: (none) => guillaume.royer
$ uname -a Linux localhost.localdomain 5.15.82-desktop-1.mga8 #1 SMP Thu Dec 8 22:01:59 UTC 2022 i686 i686 i386 GNU/Linux new build MGA8-32, Mate The following 6 packages are going to be installed: - libcaja-gir2.0-1.24.1-1.1.mga8.i586 - libnextcloudsync0-3.6.4-1.mga8.i586 - libocsync0-3.6.4-1.mga8.i586 - nextcloud-client-3.6.4-1.mga8.i586 - nextcloud-client-caja-3.6.4-1.mga8.i586 - python3-caja-1.24.0-2.mga8.i586 14MB of additional disk space will be used. -- rebooted - Nextcloud syncing properly - caja reflecting status of nextcloud updates properly.
Whiteboard: (none) => MGA8-64-OK MGA8-32-OK
Validating. Advisory in comment 6, with additional suggestions in comment 7.
Keywords: (none) => validated_updateCC: (none) => andrewsfarm, sysadmin-bugs
Working well here in production. Server 25.0.2 Dolphin plugin reflect state, and can create share link, set password etc.
Keywords: (none) => advisory
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2022-0160.html
Resolution: (none) => FIXEDStatus: NEW => RESOLVED
Also tested OK now: the new function to edit documents locally in LibreOffice. Prerequisite: Install the Nextcloud app "Edit files with LibreOffice" (I am using a hosted Nextcloud 25.0.2) Then in the web browser log in to your Nextcloud, right click on a OpenDocument file and select "Edit with LibreOffice" :)