Comments

49 Comments

Works fine for me.

Works fine for me.

@ozeszty Thanks. It looks similar to: https://bugzilla.redhat.com/show_bug.cgi?id=1762705

I believe this is some weirdness of copy-jdk-configs and how java.security files get transplanted from one NVRA to the next. Did you observe any ill effect because of this?

Looks OK.

The vendor version is wrong, though. It still has JDK 12'th version (March 2019) and should be September 2019: https://src.fedoraproject.org/rpms/java-latest-openjdk/pull-request/5

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: 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: 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 :(