Hi I just packaged 3.3.4 Actually, packaging wise, nothing to do after all the adjustments made to upgrade from 3.1. Nicolas, the src.rpm is available at the usual location. I just tested it on MGA8 Cinnamon, Gnome and KDE. Update went smoothly from 3.3.3. Of course, more comprehensive tests are required. I would be surprised if any issue, but it is never 100% granted. ====== ADVISORY INSIGHTS ===== = Linux bug fixes reported in the announcement: desktop#3757 https://github.com/nextcloud/desktop/pull/3757 5[stable-3.3] prevent infinte recursion when closing a websocket in case of SSL errors desktop#3791 https://github.com/nextcloud/desktop/pull/3791 3[stable-3.3] Accept nc scheme in provider page = new src.rpm: nextcloud-client-3.3.4-1.mga8.src.rpm = new rpm provided (arch dependent): lib64nextcloudsync0-3.3.4-1.mga8.x86_64.rpm nextcloud-client-dolphin-3.3.4-1.mga8.x86_64.rpm lib64ocsync0-3.3.4-1.mga8.x86_64.rpm nextcloud-client-nautilus-3.3.4-1.mga8.x86_64.rpm nextcloud-client-3.3.4-1.mga8.x86_64.rpm nextcloud-client-nemo-3.3.4-1.mga8.x86_64.rpm nextcloud-client-caja-3.3.4-1.mga8.x86_64.rpm Just let me know what else you need.
Thank you Christian. Christian is apprentice, not yet packager. Did 3.3.3 in Bug 29043. Assigning to Nicolas with hope he can again check and put packages in updates_testing, if not please reassign to all packagers ( pkg-bugs@ml.mageia.org ) Please reassign to QA once packages are in updates_testing
Assignee: bugsquad => mageiaCC: (none) => fri
Hi Nicolas told me yesterday he pushed it into Cauldron. Should anything be changed on this report?
Good you note here so people running cauldron can test if they like. Other than that, no. When 3.3.4 is in mga8 updates_testing, set Asignee to qa-bugs@ml.mageia.org
Who should push it to updates_testing? Last time, if I well remember, it was done at the same time, give or take. Wasn't it?
This is normal, often packages get pushed to cauldron first. Shipping to supported release need a bit more scrutinising. I believe Nicolas will push for mga8 when he have had more time to look.
Hi Nicolas just pushed it in update_testing. Ready for testing then :)
...so we assign it to QA team :)
Assignee: mageia => qa-bugs
It seems I am not allowed to assign to qa-bugs@ml.mageia.org Are specific rights required to do so?
Ah yes, i dont know when apprentices will get such rights, maybe ask your mentor - apologies if i jumped the gun on assignin to QA already, should be decision by packager, but sometimes forgotten - (Sometimes packages get into updates testing, together with notes is is not really ready or intended to be shipped to updates in current version, like some revision of Thunderbird a couple weeks ago) To be perfect, a note from packager that he thinks it is ready for real test or just some pre-test would be a plus.
Hi. I checked with Nicolas before posting. He was just lacking time to push it. It is ready for testing. I have also done some tests myself.
That was what i was waiting for :) Clean update to - lib64nextcloudsync0-3.3.4-1.mga8.x86_64 - lib64ocsync0-3.3.4-1.mga8.x86_64 - nextcloud-client-3.3.4-1.mga8.x86_64 - nextcloud-client-dolphin-3.3.4-1.mga8.x86_64 Logged out and into desktop. It started, resumed all activated syncing. Have no time to test more right now.
(In reply to christian barranco from comment #8) > It seems I am not allowed to assign to qa-bugs@ml.mageia.org > Are specific rights required to do so? Yes. Restrictions were added to bugzilla to cut down on the spammers ability to mess things up. Editbugs privilege on bugzilla granted. My understanding is that the editbugs privilege would be included when full packaging rights are granted too.
CC: (none) => davidwhodgins
Hi My understanding of the process is this report should be move to resolved/fixed, as it is ready for testing. If I was wrong, my apologies and let me know.
Resolution: (none) => FIXEDStatus: NEW => RESOLVED
No, it is only fixed when fully approved and moved from updates_testing to updates, which users use for updating. Currently this bug is in testing phase, indicated by it is assigned to QA. If problems, it will be reassigned to packager for a new version, then back to QA. When QA is satisfied, we will set Keyword "validated_update", and CC sysadmin-bugs@ml.mageia.org for move to updates. If advisory is required and done keyword "advisory" added. When moved to updates, bug is marked fixed. Take a peek of the handling in some other bugs :)
Resolution: FIXED => (none)Status: RESOLVED => REOPENED
More on QA processes: https://wiki.mageia.org/en/QA_Team_portal
For Cauldron, QA is not involved, and bugs -if even opened- are often marked fixed directly, neither updates not testing repo normally used. In Cauldron, updates and testing repo is only used for packages that many things rely on, like compiler, and big changes like new version of Plasma, and really must be tested.
Hi If one clicks on Assignee in the bug description area, the following will be shown under Closed Bugs: RESOLVED A resolution has been performed, and it is awaiting verification by QA. From here bugs are either reopened and given some open status, or are verified by QA and marked VERIFIED. VERIFIED QA has looked at the bug and the resolution and agrees that the appropriate resolution has been taken. This is the final status for bugs. As it is awaiting QA verification, I thought it would be its status from now on. Then, indeed, if VERIFIED is set, FIX comes automatically. It might be a bit misleading. In another hand, it is fixed and just waiting for the final verifications.
Apparently you followed that description correctly :) Interesting discrepancy between description and routine... Selecting "RESOLVED" force us to also select "FIXED" which it is not, or another state to tell we will not fix it which also is wrong... Fixed it is only when the fix is released to users. There is no status to select to describe it is in testing :( IMO that would be good to have. I.e Status "TESTING"
$ uname -a Linux localhost.localdomain 5.10.70-desktop-1.mga8 #1 SMP Thu Sep 30 10:19:49 UTC 2021 i686 i686 i386 GNU/Linux installed client without issue able to sync with local test nextcloud server - no issues. Works for me.
CC: (none) => brtians1
the 3.3.5 version is out. Can we use this bugreport to update or do we need it to be validated and then create a new bugreport ?
CC: (none) => mageia
(In reply to Nicolas Lécureuil from comment #20) > the 3.3.5 version is out. > > Can we use this bugreport to update or do we need it to be validated and > then create a new bugreport ? Just to complement, the package for 3.3.5 is ready, and I have been using it on MGA8 KDE for a few days.
Yes please, put 3.3.5 in testing :) Give this back to QA then.
Assignee: qa-bugs => mageiaSummary: nextcloud-client update to 3.3.4 (bug fixes) => nextcloud-client update to 3.3.5 (bug fixes)
Yes do add to test repo, I don't see it out there for me to test yet. Be aware, the NextCloud team releases a new version after every two week sprint .... about. We may want to do updates once every couple of months or a critical security item pops into view. Otherwise, this will eat up your time.
I agree with Brian. Adding it is wise hold off from x.x.0, and wait for .1 or .2 bugfix release. (unless .0 is fixing serious problems with a previous x.x) But now lets go for 3.3.5 as it is almost here :)
ok let's update to 3.3.5 but don't update every version in mageia stable release. I agree then ( i wasn't aware of the speed of releases :) )
Thanks, i see it in testing repo. If/when ready for QA testing, please set Assignee = qa-bugs@ml.mageia.org
it is ready :-)
Hi. Update for 3.3.5 ====== ADVISORY INSIGHTS ===== = Linux bug fixes reported in the announcement: desktop#3757 https://github.com/nextcloud/desktop/pull/3757 5[stable-3.3] prevent infinte recursion when closing a websocket in case of SSL errors desktop#3791 https://github.com/nextcloud/desktop/pull/3791 3[stable-3.3] Accept nc scheme in provider page desktop#3850 https://github.com/nextcloud/desktop/pull/3850 Fix incorrect db name for nextcloud command line client. desktop#3851 https://github.com/nextcloud/desktop/pull/3851 Don't log encryption data in release mode = new src.rpm: nextcloud-client-3.3.5-1.mga8.src.rpm = new rpm provided (arch dependent): lib64nextcloudsync0-3.3.5-1.mga8.x86_64.rpm nextcloud-client-dolphin-3.3.5-1.mga8.x86_64.rpm lib64ocsync0-3.3.5-1.mga8.x86_64.rpm nextcloud-client-nautilus-3.3.4-1.mga8.x86_64.rpm nextcloud-client-3.3.5-1.mga8.x86_64.rpm nextcloud-client-nemo-3.3.5-1.mga8.x86_64.rpm nextcloud-client-caja-3.3.5-1.mga8.x86_64.rpm
Thanks. 64 bit, Plasma, Dolphin integration: Quick test: Updated, reboot, works. Need testing: fresh install, add new server and shares, and caja, nautilus, and nemo integrations.
Thanks. MGA8-64, Xfce upgrading existing The following 5 packages are going to be installed: - glibc-2.32-20.mga8.x86_64 - glibc-devel-2.32-20.mga8.x86_64 - lib64nextcloudsync0-3.3.5-2.mga8.x86_64 - lib64ocsync0-3.3.5-2.mga8.x86_64 - nextcloud-client-3.3.5-2.mga8.x86_64 Works as designed.
MGA8-64, Gnome, nextcloud client upgrade The following 4 packages are going to be installed: - lib64nextcloudsync0-3.3.5-2.mga8.x86_64 - lib64ocsync0-3.3.5-2.mga8.x86_64 - nextcloud-client-3.3.5-2.mga8.x86_64 - nextcloud-client-nautilus-3.3.5-2.mga8.x86_64 rebooted Synching properly links work nautilus is correct reflecting nextcloud status of files. works as designed.
MG8-64, Mate, VM New Install of Nextcloud-Client The following 26 packages are going to be installed: - lib64caja-gir2.0-1.24.1-1.mga8.x86_64 - lib64cloudproviders0-0.3.1-1.mga8.x86_64 - lib64event7-2.1.12-1.mga8.x86_64 - lib64minizip1-1.2.11-9.mga8.x86_64 - lib64nextcloudsync0-3.3.5-2.mga8.x86_64 - lib64ocsync0-3.3.5-2.mga8.x86_64 - lib64qt5keychain1-0.11.1-2.mga8.x86_64 - lib64qt5pdf5-5.15.6-1.mga8.x86_64 - lib64qt5positioning5-5.15.2-1.mga8.x86_64 - lib64qt5quickcontrols2_5-5.15.2-1.mga8.x86_64 - lib64qt5quicktemplates2_5-5.15.2-1.mga8.x86_64 - lib64qt5quickwidgets5-5.15.2-1.mga8.x86_64 - lib64qt5svg5-5.15.2-1.1.mga8.x86_64 - lib64qt5webchannel5-5.15.2-1.mga8.x86_64 - lib64qt5webengine5-5.15.6-1.mga8.x86_64 - lib64qt5webenginecore5-5.15.6-1.mga8.x86_64 - lib64qt5webenginewidgets5-5.15.6-1.mga8.x86_64 - lib64qt5websockets5-5.15.2-1.mga8.x86_64 - lib64re2_9-20201101-2.mga8.x86_64 - lib64snappy1-1.1.8-2.mga8.x86_64 - nextcloud-client-3.3.5-2.mga8.x86_64 - nextcloud-client-caja-3.3.5-2.mga8.x86_64 - python3-caja-1.24.0-2.mga8.x86_64 - qtquickcontrols25-5.15.2-1.mga8.x86_64 - qtsvg5-5.15.2-1.1.mga8.x86_64 - qtwebengine5-5.15.6-1.mga8.x86_64 -- was able to connect to two separate servers and synch them both. Rebooted Caja (mate file manager) is reflecting nextcloud status.
Thanks Brian. Very good you tested all integrations, was a while ago we did that IIRC :) One 32 bit test of any kind would be nice too.
Whiteboard: (none) => MGA8-64-OK
MGA8-64, Plasma new install The following 17 packages are going to be installed: - gcr-3.38.0-1.mga8.x86_64 - gnome-keyring-3.36.0-3.mga8.x86_64 - lib64cloudproviders0-0.3.1-1.mga8.x86_64 - lib64gcr-ui3_1-3.38.0-1.mga8.x86_64 - lib64gnome-keyring-3.36.0-3.mga8.x86_64 - lib64gnome-keyring0-3.12.0-12.mga8.x86_64 - lib64handy1_0-1.0.3-1.mga8.x86_64 - lib64nextcloudsync0-3.3.5-2.mga8.x86_64 - lib64ocsync0-3.3.5-2.mga8.x86_64 - lib64qt5keychain1-0.11.1-2.mga8.x86_64 - lib64qt5websockets5-5.15.2-1.mga8.x86_64 - libgnome-keyring-i18n-3.12.0-12.mga8.noarch - libhandy-common-1.0.3-1.mga8.x86_64 - nextcloud-client-3.3.5-2.mga8.x86_64 - nextcloud-client-dolphin-3.3.5-2.mga8.x86_64 - pinentry-gnome3-1.1.1-1.mga8.x86_64 - seahorse-3.38.0.1-1.mga8.x86_64 -- rebooted - able to connect to server and sync - dolphin is reflecting nextcloud status properly good here. yes will do 1 32-bit test.
MGA8-32bit, Mate, Caja The following 25 packages are going to be installed: - libcaja-gir2.0-1.24.1-1.mga8.i586 - libcloudproviders0-0.3.1-1.mga8.i586 - libminizip1-1.2.11-9.mga8.i586 - libnextcloudsync0-3.3.5-2.mga8.i586 - libocsync0-3.3.5-2.mga8.i586 - libqt5keychain1-0.11.1-2.mga8.i586 - libqt5pdf5-5.15.6-1.mga8.i586 - libqt5positioning5-5.15.2-1.mga8.i586 - libqt5quickcontrols2_5-5.15.2-1.mga8.i586 - libqt5quicktemplates2_5-5.15.2-1.mga8.i586 - libqt5quickwidgets5-5.15.2-1.mga8.i586 - libqt5svg5-5.15.2-1.1.mga8.i586 - libqt5webchannel5-5.15.2-1.mga8.i586 - libqt5webengine5-5.15.6-1.mga8.i586 - libqt5webenginecore5-5.15.6-1.mga8.i586 - libqt5webenginewidgets5-5.15.6-1.mga8.i586 - libqt5websockets5-5.15.2-1.mga8.i586 - libre2_9-20201101-2.mga8.i586 - libsnappy1-1.1.8-2.mga8.i586 - nextcloud-client-3.3.5-2.mga8.i586 - nextcloud-client-caja-3.3.5-2.mga8.i586 - python3-caja-1.24.0-2.mga8.i586 - qtquickcontrols25-5.15.2-1.mga8.i586 - qtsvg5-5.15.2-1.1.mga8.i586 - qtwebengine5-5.15.6-1.mga8.i586 -- ipl'd connect to nextcloud host - sync'd - caja reflecting correctly works as designed
Whiteboard: MGA8-64-OK => MGA8-64-OK MGA8-32-OK
Many thanks for all testing Advisory in comment 28
CC: (none) => sysadmin-bugsKeywords: (none) => validated_update
Keywords: (none) => advisory
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2021-0198.html
Resolution: (none) => FIXEDStatus: REOPENED => RESOLVED