[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
[atomic-devel] Requesting freeze exception for atomic in F26 to drop rpm-build deps
- From: Jonathan Lebon <jlebon redhat com>
- To: atomic-devel <atomic-devel projectatomic io>, Fedora Cloud SIG <cloud lists fedoraproject org>
- Subject: [atomic-devel] Requesting freeze exception for atomic in F26 to drop rpm-build deps
- Date: Tue, 30 May 2017 10:58:18 -0400 (EDT)
Hi,
If I understand correctly, in its current state, F26 AH will
be shipping with the atomic package which added the
rpm-build deps. The update that removes it again is blocked
in testing:
https://bodhi.fedoraproject.org/updates/FEDORA-2017-ac1919a04b
Double-checking the current state:
$ ostree remote add fedora-26 --no-gpg-verify https://kojipkgs.fedoraproject.org/atomic/26/
$ ostree pull fedora-26 --subpath=/usr/share/rpm --depth=0 fedora/26/x86_64/atomic-host
$ ostree checkout -U --subpath=/usr/share/rpm fedora-26:fedora/26/x86_64/atomic-host tmp/rpmdb-26
$ rpm -qa --dbpath $PWD/tmp/rpmdb-26 | grep -E '(rpm-build|gdb)'
gdb-headless-7.12.50.20170226-4.fc26.x86_64
rpm-build-libs-4.13.0.1-4.fc26.x86_64
rpm-build-4.13.0.1-4.fc26.x86_64
gdbm-1.13-1.fc26.x86_64
If this is what the F26 AH deliverables will be based on,
then would it be possible to justify a freeze exception out
of this? It's a pretty big wart on a new AH release, esp.
since the motto is that we're a streamlined OS, though it's
obviously not a critical release blocker.
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]