-
Notifications
You must be signed in to change notification settings - Fork 158
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fedora-coreos-base: add in toolbox #201
Conversation
IIUC toolbox does not currently handle all of our use cases but it will in the future so let's go ahead and include it so we can fix coreos/fedora-coreos-tracker#38 and work through the issues. |
Note that there is a current issue to work out but is being worked on: containers/toolbox#267 |
weird CI issue:
|
cc @cgwalters for input |
also has anyone seen these deprecation warnings:
|
Yeah, they started appearing recently. Thought we maybe just needed a libdnf bump though that's not it (opened coreos/rpm-ostree#1929 anyway). Haven't gotten around to investigating deeper yet.
Hmm, yeah we've hit that in rpm-ostree CI too. |
There's a new update fixing the `statx` failures: https://bodhi.fedoraproject.org/updates/FEDORA-2019-566ad52d5e I strongly suspect this is also the root cause behind the recent CI failures: coreos/fedora-coreos-config#201 (comment) coreos/rpm-ostree#1929 (comment) Let's just pull it in right now so we can get things unblocked.
There's a new update awaiting karma that fixes the `statx` failures: https://bodhi.fedoraproject.org/updates/FEDORA-2019-566ad52d5e I strongly suspect this is also the root cause behind the recent CI failures: coreos/fedora-coreos-config#201 (comment) coreos/rpm-ostree#1929 (comment) Let's just pull it in right now so we can get things unblocked.
There's a new update awaiting karma that fixes the `statx` failures: https://bodhi.fedoraproject.org/updates/FEDORA-2019-566ad52d5e I strongly suspect this is also the root cause behind the recent CI failures: coreos/fedora-coreos-config#201 (comment) coreos/rpm-ostree#1929 (comment) Let's just pull it in right now so we can get things unblocked.
There's a new update awaiting karma that fixes the `statx` failures: https://bodhi.fedoraproject.org/updates/FEDORA-2019-566ad52d5e I strongly suspect this is also the root cause behind the recent CI failures: coreos/fedora-coreos-config#201 (comment) coreos/rpm-ostree#1929 (comment) Let's just pull it in right now so we can get things unblocked.
There's a new update awaiting karma that fixes the `statx` failures: https://bodhi.fedoraproject.org/updates/FEDORA-2019-566ad52d5e I strongly suspect this is also the root cause behind the recent CI failures: coreos/fedora-coreos-config#201 (comment) coreos/rpm-ostree#1929 (comment) Let's just pull it in right now so we can get things unblocked.
There's a new update awaiting karma that fixes the `statx` failures: https://bodhi.fedoraproject.org/updates/FEDORA-2019-566ad52d5e I strongly suspect this is also the root cause behind the recent CI failures: coreos/fedora-coreos-config#201 (comment) coreos/rpm-ostree#1929 (comment) Let's just pull it in right now so we can get things unblocked.
Deprecation warnings addressed in rpm-software-management/libdnf#819! |
There's a new update awaiting karma that fixes the `statx` failures: https://bodhi.fedoraproject.org/updates/FEDORA-2019-566ad52d5e I strongly suspect this is also the root cause behind the recent CI failures: coreos/fedora-coreos-config#201 (comment) coreos/rpm-ostree#1929 (comment) Let's just pull it in right now so we can get things unblocked.
are we able to retrigger CI yet? anyone opposed to merging this? |
The container is still rebuilding. Do you have the final diff for this? (Or CI will give it to us once it's back up. Edit: ahh right, this needs #176) |
The final diff is:
|
This makes sense, though I'd also like to land too |
Fixes: coreos/fedora-coreos-tracker#38