NCP auto "downgrade"?

Support intro

Sorry to hear you’re facing problems :slightly_frowning_face:

help.nextcloud.com is for home/non-enterprise users. If you’re running a business, paid support can be accessed via portal.nextcloud.com where we can ensure your business keeps running smoothly.

In order to help you as quickly as possible, before clicking Create Topic please provide as much of the below as you can. Feel free to use a pastebin service for logs, otherwise either indent short log examples with four spaces:

example

Or for longer, use three backticks above and below the code snippet:

longer
example
here

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can :heart:

NCP Version: before 1.31.1 after 1.30.1
Nextcloud version (eg, 18.0.2): 19.0.4.2
Operating system and version (eg, Ubuntu 20.04): Raspbian 5.4.72-v7l+
Apache or nginx version (eg, Apache 2.4.25): 2.4.38 (Raspbian)
PHP version (eg, 7.1): 7.3.19-1~deb10u1

The issue you are facing:

Is this the first time you’ve seen this error? (Y/N): Y

Steps to replicate it:

  1. running ncp-config / updates / nc-update results in downgrading from NCP 1.31.1 to NCP 1.30.1
  2. second run gives same result

The output of your log in:

[ nc-update ] (Thu Nov 26 16:53:34 CET 2020)
Downloading updates
Downloading updates
Performing updates
NextCloudPi updated to version v1.30.1

ncp releases
v1.31.0 is in devel to update to and test NC 20.0.2 at present moment (26-11-2020)
latest stable is v1.30.1

Yes, that’s what I can see but why was v1.31.1 installed before for many days if not weeks? To get there I just used the standard manuale nc-upgrade as today?

Any point in the log files where I can see the version info over time?

/var/log/ncp.log

[ nc-update ] (Fri Nov 20 09:42:21 CET 2020)
Downloading updates
Performing updates
NextCloudPi updated to version v1.31.0

and today

[ nc-update ] (Thu 26 Nov 16:34:20 CET 2020)
Downloading updates
Performing updates
NextCloudPi updated to version v1.30.1

??? :worried:???

So it’s not a problem for me but maybe there has been or still is a bug