~lgp171188/lpci:fix-snapcraft-build-error-snapcraft-8.x

Last commit made on 2024-02-14
Get this branch:
git clone -b fix-snapcraft-build-error-snapcraft-8.x https://git.launchpad.net/~lgp171188/lpci
Only Guruprasad can upload to this branch. If you are Guruprasad please log in for upload directions.

Branch merges

Branch information

Name:
fix-snapcraft-build-error-snapcraft-8.x
Repository:
lp:~lgp171188/lpci

Recent commits

51b2a69... by Guruprasad

Fix the build error with snapcraft 8.x

snapcraft 8.x is built on core22 while 7.x was built on core20, which is
the same base used by lpci. Due to this change and possible bug in the
lpci snapcraft.yaml causing the build process to depend on the version
of python used by snapcraft, there was a conflict in the available vs expected
versions of pip. This is now fixed by moving the lpci's python site
customization script to run at the end of the build process so that it
only comes into effect in the actual snap instead of affecting the build
environment too.

LP: #2053109

Succeeded
[SUCCEEDED] test:0 (build)
[SUCCEEDED] build:0 (build)
12 of 2 results
1cb6372... by Jürgen Gmach

Prepare release version 0.2.5

e251376... by Corey Bryant

Add timeout constants for curl and snap install

0162c4f... by Corey Bryant

Add support for 23.10 (mantic) and drop 22.10 (kinetic)

This requires an update to depend on craft-providers>=1.19.0.
requirements.txt is regeneraged as a result.

The environment and hostname usage in LPCIBuilddBaseConfiguration is
updated based on craft-providers refactoring of base handling code.

Unit tests are updated with timeout argument that was added in
craft-providers refactoring of base handling code.

Also fix mypy complaint:
'error: Unused "type: ignore" comment [unused-ignore]'

6854681... by Colin Watson

Release version 0.2.4

1dd9ae1... by Colin Watson

Release the latest build of each architecture

`lpci release` incorrectly released the latest build regardless of
architecture; this approach was OK when builds were typically only
dispatched for a single architecture, but now that we need to handle
releasing for (e.g.) both amd64 and arm64, it doesn't work so well.
Release the latest build for each architecture for which builds exist
instead, and add a new `--architecture` option for the case where people
want to override this behaviour and only release the latest build for a
single architecture.

0bea94e... by Jürgen Gmach

Clarify environment variable handling

- document precedence of environment variable handling
- refactor environment variable handling

636c48a... by Ines Almeida

Update documentation about parallel job execution

0b29d3d... by Jürgen Gmach

Set minimum version for PyYAML

... in order to avoid build issues, see
https://github.com/yaml/pyyaml/issues/601.

cbeddad... by Guruprasad

Prepare release 0.2.3

Succeeded
[SUCCEEDED] test:0 (build)
[SUCCEEDED] build:0 (build)
12 of 2 results