Ilya Maximets <[email protected]> writes: > On 2/1/21 3:08 PM, Aaron Conole wrote: >> Ilya Maximets <[email protected]> writes: >> >>> Some repositories that are enabled in GHA are not stable and lead >>> to 'apt update' failures: >>> >>> E: The repository >>> 'https://apt.postgresql.org/pub/repos/apt bionic-pgdg Release' >>> no longer has a Release file. >>> >>> This causes the job failure. >>> In most cases we don't really need any packages from these failed >>> repositories, so we could try to continue the job. >>> >>> Proviously this kind of failures happened on older branches with >>> ubuntu 16.04 base image, so we have this workaround already there. >>> Now it started to fail on bionic images, so fixing there too. >>> >>> Fixes: 02f76fb42ae9 ("github: Fix Ubuntu package installation.") >>> Signed-off-by: Ilya Maximets <[email protected]> >>> --- >> >> Acked-by: Aaron Conole <[email protected]> >> >> Incidentally, I was sure there was a way to ignore this condition (with >> something like -m instead), but that started me down a rabbit hole and I >> wasn't able to find the option anywhere. >> > > apt-get has '-m' a.k.a. '--ignore-missing', but I'm not sure if it will > affect this cese since it's for packages and not for broken repositories.
That only affects packages, not the repositories. I did try it on a local machine. > apt doesn't have this flag documented anywhere. apt(8) documentation even says to use 'apt-get' et. al. in scripts (which this is), but ubuntu specifically says not to do so. It's a bit confusing, TBH. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
