[resolved]Patch issues from 2.12.0 to 2.12.2

Checklist
[x] I have read intro post: About the Installation Issues category
[x] I have read the tutorials, help and searched for similar issues
[x] I provide relevant information about my server (component names and versions, etc.)
[x] I provide a copy of my logs and healthcheck
[x] I describe the steps I have taken to trouble shoot the problem
[x] I describe the steps on how to reproduce the issue

1 - seems not took the patch version (config/version.php)
2 - issue with email id

=> directly from the ‘build upgrade’ :

[FAIL] This installation is not up to date. Currently using 2.12.0 and it should be v2.12.1.
[HELP] See. https://www.passbolt.com/help/tech/update

probably here since the first install (discover with the check):
[FAIL] The server key does not have a valid email id.
[HELP] Edit or generate another key with a valid email id.
=> how to do it

< [11:04:33] - root@vault:/var/www/passbolt >
=>su -s /bin/bash -c “./bin/cake passbolt healthcheck” www-data

 ____                  __          ____  
/ __ \____  _____ ____/ /_  ____  / / /_ 

/ // / __ `/ / / __ / __ / / _/
/ / // ( |
) /
/ / /
/ / / /
/
/ _
,
/
//./_//__/

Open source password manager for teams

Healthcheck shell

Environment

[PASS] PHP version 7.3.14-1~deb10u1.
[PASS] PCRE compiled with unicode support.
[PASS] The temporary directory and its content are writable.
[PASS] The public image directory and its content are writable.
[PASS] The logs directory and its content are writable.
[PASS] GD or Imagick extension is installed.
[PASS] Intl extension is installed.
[PASS] Mbstring extension is installed.

Config files

[PASS] The application config file is present
[PASS] The passbolt config file is present

Core config

[PASS] Debug mode is off.
[PASS] Cache is working.
[PASS] Unique value set for security.salt
[PASS] Full base url is set to https://vault.pra.rip
[PASS] App.fullBaseUrl validation OK.
[PASS] /healthcheck/status is reachable.

SSL Certificate

[PASS] SSL peer certificate validates
[PASS] Hostname is matching in SSL certificate.
[PASS] Not using a self-signed certificate

Database

[PASS] The application is able to connect to the database
[PASS] 23 tables found
[PASS] Some default content is present
[PASS] The database schema up to date.

GPG Configuration

[PASS] PHP GPG Module is installed and loaded.
[PASS] The environment variable GNUPGHOME is set to /home/www-data/.gnupg.
[PASS] The directory /home/www-data/.gnupg containing the keyring is writable by the webserver user.
[PASS] The server gpg key is not the default one
[PASS] The public key file is defined in config/passbolt.php and readable.
[PASS] The private key file is defined in config/passbolt.php and readable.
[PASS] The server key fingerprint matches the one defined in config/passbolt.php.
[PASS] The server public key defined in the config/passbolt.php (or environment variables) is in the keyring.
[FAIL] The server key does not have a valid email id.
[HELP] Edit or generate another key with a valid email id.
[PASS] The public key can be used to encrypt a message.
[PASS] The private key can be used to sign a message.
[PASS] The public and private keys can be used to encrypt and sign a message.
[PASS] The private key can be used to decrypt a message.
[PASS] The private key can be used to decrypt and verify a message.
[PASS] The public key can be used to verify a signature.

Application configuration

[FAIL] This installation is not up to date. Currently using 2.12.0 and it should be v2.12.1.
[HELP] See. https://www.passbolt.com/help/tech/update
[PASS] Passbolt is configured to force SSL use.
[PASS] App.fullBaseUrl is set to HTTPS.
[PASS] Selenium API endpoints are disabled.
[PASS] Search engine robots are told not to index content.
[PASS] Registration is closed, only administrators can add users.
[PASS] Serving the compiled version of the javascript app
[PASS] All email notifications will be sent.

2 error(s) found. Hang in there!

< [11:05:27] - root@vault:/var/www/passbolt >
=>git status
On branch tags/v2.12.2
nothing to commit, working tree clean
< [11:05:36] - root@vault:/var/www/passbolt >

thank you for your help

pra

Hello @pra,

Can you confirm me, you you performed a git pull origin master ?

Best regards,
Cédric

hello

yes i do :

git pull origin master
git fetch --tags
git checkout tags/v2.12.0 -b tags/v2.12.2

and run the check after

thank you for your help

pra

Looks like you have typos in your command, you checked out v2.12.0 as v2.12.2.
You can try the following: git checkout tags/v2.12.1 -b tags/v2.12.1
And delete the tags/v2.12.2 branch: git branch -D tags/v2.12.2

git checkout tags/v2.12.1 -b tags/v2.12.1
Switched to a new branch ‘tags/v2.12.1’

=>git branch -D tags/v2.12.2
Deleted branch tags/v2.12.2 (was 3eaf5fcf64).

=> i have :
[FAIL] The server key does not have a valid email id.
[HELP] Edit or generate another key with a valid email id.

i think now i need to apply :
git checkout tags/v2.12.1 -b tags/v2.12.2

thank you for your help

pra

This is the same mistake, both version need to match.

thank you remy & cedric
i don t understand why on the ‘site’ i have 2.12.1/2.12.2

and i have :
=>git status
On branch tags/v2.12.1
nothing to commit, working tree clean

=>git pull origin master
From https://github.com/passbolt/passbolt_api

  • branch master -> FETCH_HEAD
    Already up to date

and seems not uptodate => 2.12.2 is the patch 2 is in progress or i have not access ?

thank you for your help

regards
stay safe

pra

v2.12.1 / v2.12.2 are relative to the API version / Extension version.
Looks like you are now up to date.

ah ok thank you

have a good day

regards

pra