Comments

65 Comments
karma

Same issue here on an non-up-to-date F29 with respect to libseccomp:

podman: symbol lookup error: podman: undefined symbol: seccomp_api_get

Also, with systemd.unified_cgroup_hierarchy=1 this fails rather spectacularly:

$ sudo podman run -ti --memory 1g --cpuset-cpus 0,1 fedora:30 /bin/bash
Error: time="2019-07-04T21:01:58+02:00" level=warning msg="signal: killed"
time="2019-07-04T21:01:58+02:00" level=error msg="container_linux.go:346: starting container process caused \"process_linux.go:297: applying cgroup configuration for process caused \\\"mountpoint for devices not found\\\"\"\n"
container_linux.go:346: starting container process caused "process_linux.go:297: applying cgroup configuration for process caused \"mountpoint for devices not found\""
: OCI runtime error

This shouldn't get pushed as it would install JDK 12 on systems with epel-7 repo enabled and using "yum install java-openjdk". Should install java-1.8.0-openjdk.

Seems to work fine for me, modulo the wayland + black charts issue. Works fine under X.

Works fine for me.

Thanks for the update!

The update details above don't make much sense. Was the intention to update java-11-openjdk?

@ueno What's the policy of getting this pushed to stable? It's blocking one of our java-1.8.0-openjdk updates: https://bodhi.fedoraproject.org/updates/FEDORA-2018-e3483fc1b6

@ueno What's the policy of getting this pushed to stable? It's blocking one of our java-1.8.0-openjdk updates: https://bodhi.fedoraproject.org/updates/FEDORA-2018-d90ffdf984

Thanks for the feedback. I'll push this to stable as soon as the NSS update reaches stable.

I'll push this to stable as soon as the NSS update reached stable.

Sure, done. Though, the dependent update reached the stable threshold. It should reach stable soon.

Kevin, thanks for the reminder. I've disabled auto-push.

Hmm, this unpush causes the byteman build to fail: See #1579749 :(

karma

Is there still something blocking this update? It prevents vim-enhanced from installing which is in stable already: Last metadata expiration check: 0:50:24 ago on Wed 09 May 2018 09:14:16 AM CEST. Dependencies resolved.

Problem 1: cannot install the best update candidate for package vim-enhanced-2:8.0.1704-1.fc28.x86_64 - nothing provides perl(:MODULE_COMPAT_5.26.2) needed by vim-enhanced-2:8.0.1788-1.fc28.x86_64 Problem 2: problem with installed package vim-enhanced-2:8.0.1704-1.fc28.x86_64 - package vim-enhanced-2:8.0.1704-1.fc28.x86_64 requires vim-common = 2:8.0.1704-1.fc28, but none of the providers can be installed - cannot install both vim-common-2:8.0.1788-1.fc28.x86_64 and vim-common-2:8.0.1704-1.fc28.x86_64 - cannot install both vim-common-2:8.0.1704-1.fc28.x86_64 and vim-common-2:8.0.1788-1.fc28.x86_64 - cannot install the best update candidate for package vim-common-2:8.0.1704-1.fc28.x86_64 - nothing provides perl(:MODULE_COMPAT_5.26.2) needed by vim-enhanced-2:8.0.1788-1.fc28.x86_64 =================================================================================================================================================================================================================== Package Arch Version Repository Size =================================================================================================================================================================================================================== Skipping packages with conflicts: (add '--best --allowerasing' to command line to force their upgrade): vim-common x86_64 2:8.0.1788-1.fc28 updates 6.4 M Skipping packages with broken dependencies: vim-enhanced x86_64 2:8.0.1788-1.fc28 updates 1.3 M

Works fine for me.

Works for me.

Looks good to me. Eclipse works and other basic smoke tests passed.