I noticed this commit a few days ago, when it broke some hacks I use! That is another story.
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 pinned kernel a while ago, and decided against it. https://github.com/libreswan/libreswan/commit/5302808c6cc1b998cc825353cc70ddfdfe300411 We go back and forth on pinning kernel other packages. https://github.com/libreswan/libreswan/commit/0eaf13a7c0600d31ab464c0fc735cce074b07c47 if we want pin packages again prefered method is /etc/dnf/dnf.conf -antony On Sat, Jul 20, 2019 at 02:49:02AM +0000, Andrew Cagney wrote: > New commits: > commit 474b105c2c0acba855ed8554fd042158323db3fd > Author: Andrew Cagney <cagney at gnu.org> > Date: Fri Jul 19 14:51:49 2019 -0400 > > testing: add $(KVM_KERNEL_VERSION) and $(KVM_KERNEL_PACKAGES) > > So kernel version can be controlled a little. > (default is latest) > > Update fedora28.mk and fedora30.mk, but delete fedora29.mk. > _______________________________________________ Swan-dev mailing list [email protected] https://lists.libreswan.org/mailman/listinfo/swan-dev
