Re: Upstream branch naming changes breaking source mirrors

Mark Hatle

On 7/7/20 9:16 AM, Richard Purdie wrote:
On Tue, 2020-07-07 at 08:58 -0500, Joshua Watt wrote:

On 7/7/20 6:42 AM, Richard Purdie wrote:
A number of upstream git repos we build from are transitioning
branches to "main" branches. They're doing this and removing the

The scale of the problem this causes us is only just becoming
iso-codes did this, I tested a patch to update master-next.
was fine until I did this as DL_DIR has "master" in it.

After I tested the change in master-next, the new main branch was
to DL_DIR and the old master branch was removed. This broke master
which now no longer had the correct source in the mirror or from
upstream. It will have also broken dunfell and perhaps a number of
other releases. Those do have sources from the release period we
use but they're not configured to fall back to them at present
probably should be?).
I'm a little confused; is the old SHA1 not an ancestor of the new
branch head? I would have expected the required SHA1 to be in DL_DIR
just the same as if the master branch head had moved?
The fetcher is strict about which branch the SHA1 is on. There were
good reasons we started enforcing that, I have to admit I don't
remember the reasons offhand. Its that which is tripping things up
One of the reasons we were enforcing this, there were people doing package
updates calling a package one version and pulling the source from a completely
different branch.

It was making it difficult to properly name the version, look for CVEs, etc.

Is this caused because the SRC_URI specifies a branch and the fetched
only downloads that specific branch from upstream? If a branch is
specified, should that be encoded in the DL archive somehow?
We only have one archive per repository, not per branch.
That has hurt in the past for the opposite reason. (Binutils) someone creates
branch ABC. Then they remove branch ABC, and create a new branch ABC/XYZ.

If you don't prune ABC, then you can't create the directory ABC to have XYZ in
it. (So you can't win in this case, you HAVE to prune or your HAVE to ignore
the new branch.)

(This likely won't be an issue for master/main -- but it's something to be aware




Join { to automatically receive all group messages.