ijurisic/nextcloud-deb
ijurisic/nextcloud-deb
1
2
Fork 5
Code Issues 1 Pull Requests Packages Projects Releases 23 Wiki Activity

Unable to upgrade Nextcloud when going from Buster to Bookworm #25

New Issue
Closed
opened 2024-05-10 01:38:48 +02:00 by adamhax0rbana · 3 comments
adamhax0rbana commented 2024-05-10 01:38:48 +02:00
Contributor
Copy Link

Problem

When I upgraded from Bullseye to Bookworm today, it broke Nextcloud because Nextcloud can not handle multiple major version changes at once. In the jurisic.org apt repo, the latest on Bullseye is v25, the oldest (and only) version on bookworm is 29.

Suggested fix

Use the -m flag when running dpkg-scanpackages on the apt repo. This will allow multiple versions to be served up and thus users who are upgrading from Bullseye to Bookworm can explicitly request Nextcloud v26, then 27 and so on until they get fully updated.

This also assumes that the intermediate .deb packages are still on the apt server. I was unable to confirm this on account of directory indexes being disabled.

GitLab has this exact same problem of not being able to skip major versions during an upgrade and their answer is to allow users to use apt to explicitly select the version they want to install.

Workaround

People can build and host their own apt repos with these intermediate versions of the Nextcloud package.

Here is a tested (on a fresh Debian 12 system) way to build nextcloud v26 using this repo:

sudo apt-get install build-essential fakeroot devscripts apache2-dev
git clone https://git.jurisic.org/ijurisic/nextcloud-deb.git
cd nextcloud-deb
git checkout bookworm
sed -i 's/29//g' debian/watch
uscan --verbose --download-version 26.0.13
cd ../nextcloud-server-26.0.13/
dch -n
dpkg-buildpackage -rfakeroot -us -uc
cd ..
ls -lh nextcloud-server_26.0.13-1.1_all.deb

This same process (starting from the uscan command) can be used to build versions 27, 28, and any other versions for that matter.

An alternative approach would be to check out specific releases from this repo and build those. This limits the versions which are available (e.g. there are no releases in this repo for versions 26.0.5 - 26.0.13), but it's possible to build enough major releases to get up to date. You can either browse though the releases to find old version numbers or browse the tags.

Here are the commands I used to take this approach:

sudo apt-get install build-essential fakeroot devscripts apache2-dev
git clone https://git.jurisic.org/ijurisic/nextcloud-deb.git
cd nextcloud-deb
git checkout bookworm.v26.0.4
uscan --verbose --download-current-version
cd ../nextcloud-server-26.0.4
dch -n
dpkg-buildpackage -rfakeroot -us -uc
cd ..
ls -lh nextcloud-server_26.0.4-1.1_all.deb

Again, these commands were tested on a fresh Debian 12 system. Continuing to show the full upgrade path...

# ... continued from the set of commands directly above
cd nextcloud-deb
git checkout bookworm.v27.1.6
uscan --verbose --download-current-version
cd ../nextcloud-server-27.1.6
dch -n
dpkg-buildpackage -rfakeroot -us -uc
cd ..
ls -lh nextcloud-server_27.1.6-1.1_all.deb

cd nextcloud-deb
git checkout bookworm.v28.0.3
uscan --verbose --download-current-version
cd ../nextcloud-server-28.0.3
dch -n
dpkg-buildpackage -rfakeroot -us -uc
cd ..
ls -lh nextcloud-server_28.0.3-1.1_all.deb

cd nextcloud-deb
git checkout bookworm.v29.0.0-1
uscan --verbose --download-current-version
cd ../nextcloud-server-29.0.0
dch -n
dpkg-buildpackage -rfakeroot -us -uc
cd ..
ls -lh nextcloud-server_29.0.0-1.1_all.deb

If anyone is in this exact same situation, feeling lazy, and wants to trust another apt repo, you can use my repo, which now has the versions above. Keep jurisic's apt repo too, as I'm just hosting these so I can upgrade my own server, and I don't plan on keeping Nextcloud updated in my repo.

curl -o /usr/share/keyrings/hax0rbana.gpg https://repo.hax0rbana.org/debs/KEY.gpg
echo 'deb [signed-by=/usr/share/keyrings/hax0rbana.gpg] https://repo.hax0rbana.org/debian bookworm main' > /etc/apt/sources.list.d/hax0rbana.list
apt update
apt list -a nextcloud-server
apt install nextcloud-server=26.0.4-1.1

Logs

Below are the logs when running apt upgrade on a Debian 12 system (freshly upgraded from Debian 11).

Setting up nextcloud-server (29.0.0-1~deb12) ...
Conf nextcloud already enabled
Nextcloud or one of the apps require upgrade - only a limited number of commands are available
You may use your browser or the occ upgrade command to do the upgrade
Nextcloud or one of the apps require upgrade - only a limited number of commands are available
You may use your browser or the occ upgrade command to do the upgrade
Nextcloud or one of the apps require upgrade - only a limited number of commands are available
You may use your browser or the occ upgrade command to do the upgrade
Setting log level to debug
Exception: Updates between multiple major versions and downgrades are unsupported.
Update failed
Maintenance mode is kept active
Resetting log level
dpkg: error processing package nextcloud-server (--configure):
 installed nextcloud-server package post-installation script subprocess returned error exit status 5
Errors were encountered while processing:
 nextcloud-server
# Problem When I upgraded from Bullseye to Bookworm today, it broke Nextcloud because Nextcloud can not handle multiple major version changes at once. In the [jurisic.org apt repo](https://apt.jurisic.org/debian/), the latest on Bullseye is v25, the oldest (and only) version on bookworm is 29. # Suggested fix Use the `-m` flag when running `dpkg-scanpackages` on the apt repo. This will allow multiple versions to be served up and thus users who are upgrading from Bullseye to Bookworm can explicitly request Nextcloud v26, then 27 and so on until they get fully updated. This also assumes that the intermediate .deb packages are still on the apt server. I was unable to confirm this on account of directory indexes being disabled. GitLab has this exact same problem of not being able to skip major versions during an upgrade and their answer is to allow users to use apt to explicitly select the version they want to install. # Workaround People can build and host their own apt repos with these intermediate versions of the Nextcloud package. Here is a tested (on a fresh Debian 12 system) way to build nextcloud v26 using this repo: ``` sudo apt-get install build-essential fakeroot devscripts apache2-dev git clone https://git.jurisic.org/ijurisic/nextcloud-deb.git cd nextcloud-deb git checkout bookworm sed -i 's/29//g' debian/watch uscan --verbose --download-version 26.0.13 cd ../nextcloud-server-26.0.13/ dch -n dpkg-buildpackage -rfakeroot -us -uc cd .. ls -lh nextcloud-server_26.0.13-1.1_all.deb ``` This same process (starting from the `uscan` command) can be used to build versions 27, 28, and any other versions for that matter. An alternative approach would be to check out specific releases from this repo and build those. This limits the versions which are available (e.g. there are no releases in this repo for versions 26.0.5 - 26.0.13), but it's possible to build enough major releases to get up to date. You can either browse though the [releases](https://git.jurisic.org/ijurisic/nextcloud-deb/releases) to find old version numbers or browse the [tags](https://git.jurisic.org/ijurisic/nextcloud-deb/tags). Here are the commands I used to take this approach: ``` sudo apt-get install build-essential fakeroot devscripts apache2-dev git clone https://git.jurisic.org/ijurisic/nextcloud-deb.git cd nextcloud-deb git checkout bookworm.v26.0.4 uscan --verbose --download-current-version cd ../nextcloud-server-26.0.4 dch -n dpkg-buildpackage -rfakeroot -us -uc cd .. ls -lh nextcloud-server_26.0.4-1.1_all.deb ``` Again, these commands were tested on a fresh Debian 12 system. Continuing to show the full upgrade path... ``` # ... continued from the set of commands directly above cd nextcloud-deb git checkout bookworm.v27.1.6 uscan --verbose --download-current-version cd ../nextcloud-server-27.1.6 dch -n dpkg-buildpackage -rfakeroot -us -uc cd .. ls -lh nextcloud-server_27.1.6-1.1_all.deb cd nextcloud-deb git checkout bookworm.v28.0.3 uscan --verbose --download-current-version cd ../nextcloud-server-28.0.3 dch -n dpkg-buildpackage -rfakeroot -us -uc cd .. ls -lh nextcloud-server_28.0.3-1.1_all.deb cd nextcloud-deb git checkout bookworm.v29.0.0-1 uscan --verbose --download-current-version cd ../nextcloud-server-29.0.0 dch -n dpkg-buildpackage -rfakeroot -us -uc cd .. ls -lh nextcloud-server_29.0.0-1.1_all.deb ``` If anyone is in this exact same situation, feeling lazy, and wants to trust another apt repo, you can use my repo, which now has the versions above. Keep jurisic's apt repo too, as I'm just hosting these so I can upgrade my own server, and I don't plan on keeping Nextcloud updated in my repo. ``` curl -o /usr/share/keyrings/hax0rbana.gpg https://repo.hax0rbana.org/debs/KEY.gpg echo 'deb [signed-by=/usr/share/keyrings/hax0rbana.gpg] https://repo.hax0rbana.org/debian bookworm main' > /etc/apt/sources.list.d/hax0rbana.list apt update apt list -a nextcloud-server apt install nextcloud-server=26.0.4-1.1 ``` # Logs Below are the logs when running `apt upgrade` on a Debian 12 system (freshly upgraded from Debian 11). ``` Setting up nextcloud-server (29.0.0-1~deb12) ... Conf nextcloud already enabled Nextcloud or one of the apps require upgrade - only a limited number of commands are available You may use your browser or the occ upgrade command to do the upgrade Nextcloud or one of the apps require upgrade - only a limited number of commands are available You may use your browser or the occ upgrade command to do the upgrade Nextcloud or one of the apps require upgrade - only a limited number of commands are available You may use your browser or the occ upgrade command to do the upgrade Setting log level to debug Exception: Updates between multiple major versions and downgrades are unsupported. Update failed Maintenance mode is kept active Resetting log level dpkg: error processing package nextcloud-server (--configure): installed nextcloud-server package post-installation script subprocess returned error exit status 5 Errors were encountered while processing: nextcloud-server ```
ijurisic commented 2024-05-10 07:27:42 +02:00
Owner
Copy Link

Latest version for Buster is v23.x not v25.x, in that case upgrade proces need start from v24,v25,v26,v27,v28,v29.

Latest version for Buster is v23.x not v25.x, in that case upgrade proces need start from v24,v25,v26,v27,v28,v29.
adamhax0rbana commented 2024-05-10 08:01:26 +02:00
Author
Contributor
Copy Link

🤦‍♂️ I kept writing Buster when I meant Bullseye. Too many consecutive codenames that start with the letter "B"! Edited my initial post to correct that error.

🤦‍♂️ I kept writing Buster when I meant Bullseye. Too many consecutive codenames that start with the letter "B"! Edited my initial post to correct that error.
ijurisic commented 2024-05-13 08:28:34 +02:00
Owner
Copy Link

I'n case to upgrade from Bullseye (nextcloud-server-25.0.13-1~deb11) to Bookworm need to rebuild packages with order v26.0.x,v27.0.x,v27.1.x,v28.0.x and v29.0.x or can use rebuilded packages from my repository:

Example:

  1. Disable my repository (if using), upgrade Debian from Bullseye to Bookworm.

  2. Expect You have NC 25.0.13 installed , now need to upgrade step by step:

wget https://apt.jurisic.org/debian/pool/main/n/nextcloud-server/nextcloud-server_26.0.4-1deb12_all.deb
dpkg -i nextcloud-server_26.0.4-1deb12_all.deb

wget https://apt.jurisic.org/debian/pool/main/n/nextcloud-server/nextcloud-server_27.0.2-1deb12_all.deb
dpkg -i nextcloud-server_27.0.2-1deb12_all.deb

wget https://apt.jurisic.org/debian/pool/main/n/nextcloud-server/nextcloud-server_27.1.6-1deb12_all.deb
dpkg -i nextcloud-server_27.1.6-1deb12_all.deb

wget https://apt.jurisic.org/debian/pool/main/n/nextcloud-server/nextcloud-server_28.0.2-1deb12_all.deb
dpkg -i nextcloud-server_28.0.2-1deb12_all.deb

wget https://apt.jurisic.org/debian/pool/main/n/nextcloud-server/nextcloud-server_29.0.0-1deb12_all.deb
dpkg -i nextcloud-server_29.0.0-1deb12_all.deb

I'n case to upgrade from Bullseye [(nextcloud-server-25.0.13-1~deb11)](https://apt.jurisic.org/debian/pool/main/n/nextcloud-server/nextcloud-server_25.0.13-1~deb11_all.deb) to Bookworm need to rebuild packages with order v26.0.x,v27.0.x,v27.1.x,v28.0.x and v29.0.x or can use rebuilded packages from my repository: Example: 1. Disable my repository (if using), upgrade Debian from Bullseye to Bookworm. 2. Expect You have NC 25.0.13 installed , now need to upgrade step by step: wget https://apt.jurisic.org/debian/pool/main/n/nextcloud-server/nextcloud-server_26.0.4-1~deb12_all.deb dpkg -i nextcloud-server_26.0.4-1~deb12_all.deb wget https://apt.jurisic.org/debian/pool/main/n/nextcloud-server/nextcloud-server_27.0.2-1~deb12_all.deb dpkg -i nextcloud-server_27.0.2-1~deb12_all.deb wget https://apt.jurisic.org/debian/pool/main/n/nextcloud-server/nextcloud-server_27.1.6-1~deb12_all.deb dpkg -i nextcloud-server_27.1.6-1~deb12_all.deb wget https://apt.jurisic.org/debian/pool/main/n/nextcloud-server/nextcloud-server_28.0.2-1~deb12_all.deb dpkg -i nextcloud-server_28.0.2-1~deb12_all.deb wget https://apt.jurisic.org/debian/pool/main/n/nextcloud-server/nextcloud-server_29.0.0-1~deb12_all.deb dpkg -i nextcloud-server_29.0.0-1~deb12_all.deb
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something is not working
duplicate
This issue or pull request already exists
enhancement
New feature
help wanted
Need some help
invalid
Something is wrong
question
More information is needed
wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
ijurisic
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: ijurisic/nextcloud-deb#25
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?