Probably this was based on some outdated version, since the calculation already changed on:

       nexedi/erp5@6ded2571

  The code was rework to be visible by anonymous

the vulnerability database content seems to have changed

Stop and delete b2b services

- Support Slave Instance allocated in the same tree
- allow creating allocation consistency ticket on Instance Node
- handle allocation consistency for Slave Instance without Instance Node

This is a fixup of d42de18b.

history and statistics files are sometimes corrupted because of invalid json

We do 2 things to improve this:
 1. we use json.load to read the previous file (this will detect if the file is corrupted)
 2. we use json.dump to write the entire file at once in a temporary file and then we move this file to be atomic.

Probably this will consume more resources.

See merge request nexedi/slapos.core!728

  This prevents installation update modification date due Web Page
  modification date is newer.

  This fixes the coding style tests broken by:

    slapos_web_deploy: Added missing standalone-test
    slapos_web_deploy: Add rplc_coupler deploy script

  It was create a while ago, but never pushed.

Do not acquire from Person to an Organisation, as most user do not have access to the organisation_module

- directly show the software_release and sofware_type informations
- instance title is meaningless on this view, as admin want to get an understanding of which kind of software are instanciated
- drop creation_date, image columns

See merge request nexedi/slapos.core!727

copy netrc file to software home location with the good ownership.

slapos_erp5&cloud: Reimplement (and speed up) security to use ERP5User_getUserSecurityCategoryValueList

 No need external script for this.

 This change introduces a test change on testSlapOSCloudShadow, that
 include R-COMPUTER and R-INSTANCE for shadow users.

 After check, this feature (shadow) is not used for compute node or
 software instance users, so despite it is not needed (introduced 12yr
 ago), I kept just for reference.

 If those tests eventually break or cause problem, it is safe to remove
 them later on.

  Include a custom ERP5Type_asSecurityGroupIdSet, since we need to handle
  the order of source_project + function (sort) a non-standard way.

See merge request nexedi/slapos.core!721