lp:~ubuntu-cdimage/ubuntu-cdimage/focal

Created by Iain Lane and last modified
Get this branch:
bzr branch lp:~ubuntu-cdimage/ubuntu-cdimage/focal
Members of Ubuntu CD Image Team can upload to this branch. Log in for directions.

Branch merges

Related bugs

Related blueprints

Branch information

Owner:
Ubuntu CD Image Team
Project:
Ubuntu CD Images
Status:
Merged

Recent revisions

1879. By Iain Lane

sign: Drop privkeydir in _signing_command(), it's unused there

1878. By Iain Lane

tree: Switch to using mktorrent rather than btmakemetafile (bittornado)

bittornado is removed from the archive as of eoan.

1877. By Iain Lane

launchpad: Handle launchpadlib ≤ 1.10.13

This didn't have the fallback= kwarg to create a CredentialStore. We need this
on 1.10.13 and newer to continue working under sudo, but older versions didn't
have that problem, so we can omit including it completely.

1876. By Iain Lane

test_checksums: Fix pep8 E501 line too long

1875. By Iain Lane

sign: Work with gpg2

gpg2 doesn't use secring.gpg. On first launch it will import the keys from a
pre-existing secring.gpg to a new directory called private-keys-v1.d. This
doesn't respect the --secret-keyring parameter, though. But gpg (both xenial's
and focal's) have a `--homedir` option which allows you to override the
location for all files. This one does work. Switch to it, and remove the direct
setting of the various keyring paths.

1874. By Iain Lane

launchpad: Create a KeyringCredentialStore to continue working under sudo

After LP: #1862948 (focal or later), Launchpadlib always uses a memory-backed
(i.e. non-persistent) keyring backend when run under sudo. This defeats most
uses of cdimage on our shared host.

The way to fix this is to explicitly create a credential store, and then
launchpadlib will use this backend rather than selecting a memory one.

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
Stacked on:
lp:ubuntu-cdimage
This branch contains Public information 
Everyone can see this information.