Nextcloud 34 for Trixie? #67

Closed
opened 2026-06-15 18:13:23 +02:00 by daniel · 4 comments

Nextcloud 34 looks officially supported on Debian 12 and 13:
https://docs.nextcloud.com/server/latest/admin_manual/installation/system_requirements.html

Nextcloud 34 looks officially supported on Debian 12 and 13: https://docs.nextcloud.com/server/latest/admin_manual/installation/system_requirements.html
Owner

I set new upstream Nextcloud 34.0.1 fir Trixie

I set new upstream Nextcloud 34.0.1 fir Trixie
Author

I set new upstream Nextcloud 34.0.1 fir Trixie

This broke my setup: v34 got installed via apt upgrade, but the update script does not support skipping major versions.

I fixed it as follows:

  • Manually create a v33 package.
  • Force install using dpkg -i. This upgraded com v32 to v33.
  • Open Nextcloud admin settings. Check for pending occ migration calls which have not been called automatically, e.g. for mime types. Run them manually as required.
  • Upgrade from v33 to v34 using apt upgrade.
  • Again, check for pending occ migration calls.
> I set new upstream Nextcloud 34.0.1 fir Trixie This broke my setup: v34 got installed via `apt upgrade`, but the update script does not support skipping major versions. I fixed it as follows: * Manually create a v33 package. * Force install using `dpkg -i`. This upgraded com v32 to v33. * Open Nextcloud admin settings. Check for pending occ migration calls which have not been called automatically, e.g. for mime types. Run them manually as required. * Upgrade from v33 to v34 using `apt upgrade`. * Again, check for pending occ migration calls.
Author

Other than that, thank you for maintaining Nextcloud deb packages!!

Other than that, thank you for maintaining Nextcloud deb packages!!

Hy!
Same here... I had a snapshot beforhand, so I was able to move back, copy over and do the upgrade to v33, then install v34 from your package... It would be nice to handle this, since everyone will have the same DB problem, and v34 upgrade already change stuff inside the db, so v33 cannot be applied. (at least, i not started figuring out which has to be undone inside the SQL)

Hy! Same here... I had a snapshot beforhand, so I was able to move back, copy over and do the upgrade to v33, then install v34 from your package... It would be nice to handle this, since everyone will have the same DB problem, and v34 upgrade already change stuff inside the db, so v33 cannot be applied. (at least, i not started figuring out which has to be undone inside the SQL)
Sign in to join this conversation.
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: ijurisic/nextcloud-deb#67