Hi,
I talked with kwizart this weekend , he wants bootstrap buildroot for
ppc64/ppc64le support [1], at same time do the mass rebuild of F26 ,
before branch F26, until them our rawhide buildroot "switched to use
development/26 over rawhide (f27)"
Also we may slip one week : "sergiomb, I'm about to enable the mass
rebuilt this week, but I will give a training, so I might not have much
time to handle this, maybe it's better to way one more week"
So, F26 proper is branched and we may use RPMFusion rawhide with it.
VirtualBox 5.1.16 was release some minutes ago and might have support
to kernel 4.11-rcx .
I wounder if mock rpmfusion F26 works in mirrors or we have to enable
rpmfusion rawhide mirrrors ...
Anyway I could update my vm to F26 with :
dnf update "dnf*" --refresh
dnf config-manager --set-disable rpmfusion-free rpmfusion-free-updates rpmfusion-nonfree
rpmfusion-nonfree-updates
dnf config-manager --set-enable rpmfusion-free-rawhide rpmfusion-nonfree-rawhide
dnf repolist
dnf system-upgrade download --releasever=26 --nogpg --allowerasing
vi /etc/dnf/dnf.conf and add keepcache=1 (to avoid download all packages again)
dnf remove foo2hiperc sox-plugins-freeworld
dnf system-upgrade download --releasever=26 --nogpg --allowerasing
dnf system-upgrade reboot
[1]
"enabling ppc64/ppc64le would probably means there is a need to head
some "ordored" rebuild (rebuild the packages that only have BR from
fedora and not from RPM Fusion), then the others"
On Qua, 2017-03-08 at 12:18 -0700, Orion Poplawski wrote:
In a fit of madness, I bumped the rpmfusion-free-release to 27
before
realizing that we hadn't branched yet. And I can't untag the build:
$ koji-rpmfusion untag-build f26-free rpmfusion-free-release-27-0.1
ActionNotAllowed: policy violation (tag)
Can some admin do this ASAP?
So very sorry, I'm incredibly ashamed..
--
Sérgio M. B.