lp-signing

~cjwatson/lp-signing:master

  1. Git
  2. lp:~cjwatson/lp-signing
  3. master
Last commit made on 2023-10-11
Get this branch:
git clone -b master https://git.launchpad.net/~cjwatson/lp-signing
Only Colin Watson can upload to this branch. If you are Colin Watson please log in for upload directions.

Branch merges

Branch information

Name:
master
Repository:
lp:~cjwatson/lp-signing

Recent commits

68ea4fd... by Colin Watson

charm: Update charm-wheels/ols-layers

Merged from https://code.launchpad.net/~cjwatson/lp-signing/+git/lp-signing/+merge/452570

48817c4... by Colin Watson

doc: Simplify deployment commands

Merged from https://code.launchpad.net/~cjwatson/lp-signing/+git/lp-signing/+merge/453180

31ed916... by Colin Watson

doc: Simplify deployment commands

`upgrade-staging` and `upgrade-production` are wrapper scripts in
`launchpad-bastion-ps5.internal:~stg-launchpad-signing/bin/` that do the
same thing as the previous commands listed here, but that additionally
save the output to a log file.

be81035... by Colin Watson

charm: Update charm-wheels/ols-layers

The old version of layer-basic embedded in ols-layers had some
insufficient pinning; as a result, builds have started failing recently
due to changes in some unpinned dependencies. Updating charm-wheels and
ols-layers fixes that.

3ef7703... by Colin Watson

Add readthedocs configuration

Merged from https://code.launchpad.net/~cjwatson/lp-signing/+git/lp-signing/+merge/452533

8c63ed9... by Colin Watson

Add readthedocs configuration

47ab4ab... by Colin Watson

charm: Remove the old build system

Merged from https://code.launchpad.net/~cjwatson/lp-signing/+git/lp-signing/+merge/449463

149f2e1... by Colin Watson

charm: Remove the old build system

We use `charmcraft` and Launchpad charm recipes now, so we can get rid
of lots of cruft.

d9273fa... by Colin Watson

charm: Fix final part name

Merged from https://code.launchpad.net/~cjwatson/lp-signing/+git/lp-signing/+merge/448503

43520dc... by Colin Watson

charm: Fix final part name

The example in
https://juju.is/docs/sdk/charmcraft-yaml#heading--the-reactive-plugin
calls the final (and in that case only) part "charm". I'd thought that
was just an example. However, as of
https://github.com/canonical/charmcraft/commit/35adadf42c625c5ee5ed6d611c9bdec10413ae59
in charmcraft 2.4.0, calling the final part anything else causes charms
to be misbuilt; they end up containing unmodified copies of the
top-level `actions.yaml`, `config.yaml`, and `metadata.yaml` files
rather than merging the information provided by each layer.