Launchpad itself

~twom/launchpad:gdpr-overview-data

  1. Git
  2. lp:~twom/launchpad
  3. gdpr-overview-data
Last commit made on 2021-07-14
Get this branch:
git clone -b gdpr-overview-data https://git.launchpad.net/~twom/launchpad
Only Tom Wardill can upload to this branch. If you are Tom Wardill please log in for upload directions.

Branch merges

Branch information

Name:
gdpr-overview-data
Repository:
lp:~twom/launchpad

Recent commits

4c586c9... by Tom Wardill

Use inbuilt any, not a DB any

9b78e9c... by Tom Wardill

Assert against dict contents

72cf765... by Tom Wardill

Add overview data to GDPR result

1b66c07... by Colin Watson

Move markSuiteDirty to IArchiveAppend

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

ad9c75b... by Colin Watson

Move markSuiteDirty to IArchiveAppend

`markSuiteDirty` allows forcing a suite in an archive to be republished
as if by an upload without actually uploading to it. It was previously
in `IArchiveEdit`, which requires the distribution owner in the case of
primary archives and the archive owner in all other cases. This turns
out to be inconvenient in practice for Ubuntu, where the archive owner
is ~ubuntu-archive and handles day-to-day archive administration work,
and the distribution owner is ~techboard which doesn't.

There isn't an obvious perfect fit here, but `IArchiveAppend` seems a
lot closer: it requires the archive owner or somebody with upload
permission in the case of PPAs, and the archive owner in all other
cases. The only significant downside is that Launchpad administrators
won't be able to use it any more, but I think this is tolerable. If it
becomes a problem, we can probably press the `launchpad.Owner`
permission into service, since it's currently unused for archives.

LP: #1874859

87f3554... by Colin Watson

charms: Don't require charmcraft.yaml to build

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

a446744... by Tom Wardill

Upload single-arch to manifest digest, rather than final tag

lp: #1929693

Merged from https://code.launchpad.net/~twom/launchpad/+git/launchpad/+merge/405376

86d8f8a... by Tom Wardill

Test for uploading to a sha tag

f66f11d... by Tom Wardill

Upload single-arch to manifest digest, rather than final tag

da9b06f... by Colin Watson

charms: Don't require charmcraft.yaml to build

Confusingly, "charmcraft build" doesn't seem to actually require
charmcraft.yaml, and we only use it to determine the DASes to build on
and have reasonable defaults for that. Allow dispatching builds without
charmcraft.yaml, thereby allowing us to build more actually-existing
Operator Framework charms.