[Swan-dev] 474b105c2c KVM_PACKAGE_UPGRADE Re: [Swan-commit]

[Andrew Cagney]

On Tue, 6 Aug 2019 at 15:25, Paul Wouters <paul at nohats.ca> wrote:

> On Tue, 6 Aug 2019, Antony Antony wrote:
>
> > My guess is that 474b105c2c is trying to pin some packages such as kernel
> > or/and strongswan.
> > If that is the case I would prefer /etc/dnf/dnf.conf way of excluding
> than
> > $(KVM_PACKAGE_UPGRADE) alone, otherwise  dnf update and daily install
> would
> > conflict.
>
> We should not pin strongswan or the kernel? Now that we are on "bleeding
> edge", I think we can take the bleeding when it happens.
>
>
Having just tried to go through old releases and reproduce test results,
I'm forced to conclude that agreeing to unpinning strongswan and the kernel
was a stupid foolish mistake.

For instance, I can't even reproduce f28's results (yet alone anything
earlier).  This is because a kernel that didn't even exist at the time f28
was released gets installed on the test VMs.  Instead, for the test VMs we
need to ensure that what we tested the release against an always (within a
few limitations) be reproduced.

Andrew
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.libreswan.org/pipermail/swan-dev/attachments/20190806/81aec1ab/attachment-0001.html>