Which issue ?
Thanks!
This is exactly what happened 
I donât how I could miss it⊠I have to reinstall everything now 
Thanks a lot 
The one described earlier in this thread.
My problem is now identified. It was my mistake, installing the 32bit version on my RPI4 
I did the same, I didnât know they were a 64bits version⊠
Wait for the news !
1 Like
2 Likes
English
Since 2016 and my first âand still runningâ Lime1, I thought it was a 64bit cpu.
Looking through the Yunohost Helpers, the running instance architecture is obtained withâŠ
dpkg --print-architecture
armhf
And compared in the installation and upgrade code of Nextcloud_ynhâŠ
And the message Sorry, Nextcloud has deprecated 32-bit support tilted me.
I did not believed it first, may be a joke or a bug or something, but sadly not.
It is said on the Debian website about armhf that itâs a 32bit architecture.
I donât know where I got this belief that it was 64bit and it bothers me to realize this after six years of using and recommending lime1 and lime2.
Next time, instead of using lscpu or uname -a or uname -m or even dpkg --print-architecture, Iâll also do a file /usr/bin/file who saysâŠ
file /usr/bin/file
/usr/bin/file: ELF 32-bit LSB shared object, ARM, EABI5 version âŠ
On a 64-bit system it saysâŠ
file /usr/bin/file
/usr/bin/file: ELF 64-bit LSB pie executable, x86-64, version âŠ
I feel sad.
Français
Depuis ma premiĂšre Lime1 de 2016 et qui fonctionne encore aujourdâhui, jâai toujours cru que le CPU Ă©tait un 64bit.
Câest au travers des Helpers de Yunohost que lâarchitecture est rĂ©cupĂ©rĂ©eâŠ
Pour ĂȘtre comparĂ©e dans le code lâinstallation ou de mise Ă jour de NextcloudâŠ
Et que le message Sorry, Nextcloud has deprecated 32-bit support mâa fait flipper.
Jây ai pas cru⊠je me suis dit que câĂ©tait une erreur ou une mauvaise blague, mais malheureusementâŠ
dpkg --print-architecture
armhf
Et sur le site de Debian câest dit que câest du 32bit.
Je ne sais pas dâoĂč je tiens cette croyance que câĂ©tait du 64bit et ça me fait bien chier dâen prendre conscience aprĂšs six ans dâutilisation et de recommandation dâutilisation des lime1 et lime2.
Ă partir de maintenant, en plus de lscpu ou uname -a ou uname -m ou mĂȘme dpkg --print-architecture, je vais aussi faire file /usr/bin/file qui ditâŠ
file /usr/bin/file
/usr/bin/file: ELF 32-bit LSB shared object, ARM, EABI5 version âŠ
Sur un systĂšme 64-bit ça ditâŠ
file /usr/bin/file
/usr/bin/file: ELF 64-bit LSB pie executable, x86-64, version âŠ
Je me sens triste.
A good news !!
We have to wait a moment 
Yep, good news for the planet 
Agree !
Hello,
Where are we on the 32 support?
Do we know if the 32 support will arrive soon ?
For the moment the 24 version is still blocked at my place.
Have you tried to install testing?
1 Like
32 bit support is still there.
However, there were a bug in early Nextcloud 25.x versions with 32 bits and quotas.
Nextcloud 25.0.3 should have fixed it. For now it is in testing for Yunohost (you can try it if you want), and it should be soon (depends on testing !) released as a normal version.
This is what we can read on github
**[Gredin67](https://github.com/Gredin67)** [Jan 24, 2023](https://github.com/YunoHost-Apps/nextcloud_ynh/pull/532#discussion_r1085000463) âą
My suggestion: "Nextcloud will deprecate 32-bit support within the next years. You should start thinking about upgrading to a 64-bit architecture.
Does anyone know when(/which version) it will become mandatory to switch from 32bit arch to 64bit ?
We donât.
It was supposed to be 25.
Now it seems to be at least 26.
There is a debate in Nextcloud community about maintaining it longer.
The future will tell us
1 Like
The funny thing is, we need user to test before merging⊠and nobody is willing to test and prefer waiting for the released version⊠I bet you can expect the master branch to come with bugs 
Hello,
I didnât understand that a user was needed to test this version. Either it was said above or it wasnât made clear.
Iâm willing to test, but I donât feel very comfortable with the system and Iâm a bit afraid of ending up with an unusable Nextcloud in production, when my family needs it daily. I donât have a test machine.
I do understand the human need to help with development, testing etc. I already participate in the QA of Mageia Linux, where I have a test machine reserved for that and where I also feel more autonomous to help me out. I donât do this on my production machine.
Now if the community is ready to give me support Iâm willing to test this version. But Iâll have to go step by step with me, starting with how to get through the testing branch to download the desired version.
We need more contributors yes, but itâs understandable people are not willing to beta test something on a production server
I tested the upgrade in 3 servers, the Continuous Integration test is happy, and itâs not a massive change, for my part I think it is not a big risk to merge as it is
If someone is willing to test this testing branch version, you will have to do it like this:
- connect to the command line interface (via SSH) to your Yunohost server
- Then use this command :
sudo yunohost app upgrade nextcloud -u https://github.com/YunoHost-Apps/nextcloud_ynh/tree/testing(note that if you have multiple Nextcloud installed, you might change the app name accordingly) - then check if Nextcloud is running correctly
A backup (of the core, not the files) of Nextcloud will be created before the upgrade, but it is always good to have a general backup somewhere
We mainly need 32bits testers here, to check if the quota bug is solved.
That said, I wonât push you to beta test this, even if the risk is small (in the worst case, you could revert to the previous backup, and in case of the Quota bug, patch it manually), if you donât feel confortable with it, donât do it, thatâs fine
Hello @Lapineige,
Iâll try it. But let me a moment to have enought time at home without children to make this test.
Iâll be back to comment on the experience.
We merged it, so itâs now a normal upgrade