Launchpad itself

Merge detection can be very slow for repositories with deep history,
because as currently defined it has to walk through the whole ancestry
of a given target commit looking for "mainline" (first parent only)
commits that introduce a merge of any of the given source commits. In
particular, this often times out for Linux kernel repositories.

However, we can do much better. Merge proposals are normally only
created in Launchpad once the target branch has been scanned, and we can
reasonably assume that when a merge proposal is created it won't yet
have been merged. This means that Launchpad can tell turnip's
`detect-merges` API to stop walking through history whenever it
encounters the commit that it had previously scanned on the target
branch, and then we only have to look through the changes introduced by
a push rather than the entire history of the branch. This should be
much less likely to time out.

LP: #1955040

4b7a45b... by Colin Watson on 2023-08-18

Refactor queries in PublishingSet.getBuildsForSourceIds

`PublishingSet.getBuildsForSourceIds` made one database query to work
out the set of build IDs (in an inefficient way that pulled a lot more
data back into Python than needed), and then a second query to get the
full result set to return. Refactor this to do all the work in a single
query.

The approach I've taken here also moves the `BinaryPackageBuild` parts
of the query into a left join, which should soon make it easier to
extend this method to support CI builds as well.

408d2ce... by Colin Watson on 2023-08-17

charm: Set up Apache relation for ftpmaster-publisher

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

Launchpad itself

~ines-almeida/launchpad:specify-yaml-exception-in-charms

Branch merges

Related source package recipes

Related snap packages

Related charm recipes

Branch information

Recent commits