Launchpad itself

~petermakowski/launchpad:add-ubuntu-mono-font

  1. Git
  2. lp:~petermakowski/launchpad
  3. add-ubuntu-mono-font
Last commit made on 2023-05-25
Get this branch:
git clone -b add-ubuntu-mono-font https://git.launchpad.net/~petermakowski/launchpad
Only Peter Makowski can upload to this branch. If you are Peter Makowski please log in for upload directions.

Branch merges

Branch information

Name:
add-ubuntu-mono-font
Repository:
lp:~petermakowski/launchpad

Recent commits

9f4e1e1... by Peter Makowski <email address hidden>

add ubuntu mono font

Succeeded
[SUCCEEDED] docs:0 (build)
[SUCCEEDED] lint:0 (build)
[SUCCEEDED] mypy:0 (build)
1 → 3 of 3 results First • Previous • Next • Last
62dd843... by Colin Watson

Include download-cache/yarn/ in deployment tarballs

Merged from https://code.launchpad.net/~cjwatson/launchpad/+git/launchpad/+merge/442018

2983a20... by Colin Watson

Make apidoc generation work outside a git working tree

Merged from https://code.launchpad.net/~cjwatson/launchpad/+git/launchpad/+merge/442017

785c4ab... by Colin Watson

Include download-cache/yarn/ in deployment tarballs

This adds about 25 MiB to the size of those tarballs, but it makes it
possible for us to run `make build` in a charmed deployment, which is
needed for deploying our frontend assets using Juju.

70b5f5e... by Colin Watson

Make apidoc generation work outside a git working tree

Our machine-readable API documentation files are generated using the
time of the last commit as their file modification times, in order that
`ETag` headers are consistent. However, when building API documentation
in a charmed deployment, we don't have a git working tree. Pick up the
timestamp from `version-info.py` instead.

e94a319... by Colin Watson

Revert "Include built assets in deployment tarballs"

Merged from https://code.launchpad.net/~cjwatson/launchpad/+git/launchpad/+merge/441878

c1e30bc... by Colin Watson

Revert "Include built assets in deployment tarballs"

This reverts commits 58bc1d894a8d5f7e17b643d11d8c54185eb010f8 and
97990c559e9c4a7234c78b2aa238523c432a2abf. It turns out that it's
impossible to include assets in deployment tarballs, because API
documentation includes the API host name and so needs to be built
separately for each environment. We'll need to take a different
approach here.

efcea95... by Colin Watson

Move asset build to be local to build-tarball

Merged from https://code.launchpad.net/~cjwatson/launchpad/+git/launchpad/+merge/441863

97990c5... by Colin Watson

Move asset build to be local to build-tarball

The `build_wheels_only` target in the `Makefile` is used by both legacy
deployments (via a complex chain of systems that include a call to `make
build_wheels`) and Juju deployments (via a Jenkins job that calls `make
publish-tarball`). We need `make publish-tarball` to build assets in
order to support a future charm, but `make build_wheels` can't do so
because the legacy build machine doesn't have the right dependencies
installed - and we probably don't want to re-engineer those deployments
too heavily anyway.

Moving this to the `build-tarball` script and reverting the `Makefile`
changes lets us make things work the way they need to for Juju
deployments, while fixing legacy deployments.

6b6fcdf... by Jürgen Gmach

Do not try to delete the `by-hash` directory

Merged from https://code.launchpad.net/~jugmac00/launchpad/+git/launchpad/+merge/441821