Thanks Marty! I'm pushing to stable.

Ok, we've hit a week in testing and have had three people successfully test. Probably as good as we're going to get - pushing to stable.

Thanks @deknuydt and @dwd!

I got some additional positive feedback via email from Andrej Filipčič (but he wasn't able to add karma).

Since we've hit 7 days and at least three people have tested it successfully, I'm going to push to stable.

Thanks @dwd!

Karma threshold hit! I'll be queueing for stable momentarily.

Thanks @scrosby, @lincolnb, and @dwd.

Oh - given that this is a security update, I'm pushing directly to "stable" (so it should hit in the next daily update) instead of "batched" (which would cause this to wait until next Tuesday.

Given we have +3 in karma -- and FESCo's approval to move forward -- I will be pushing this forward.

Thanks to @dwd, @jthiltges, and @lincolnb for testing! If you can, we still need more karma here:

• EPEL6: FEDORA-EPEL-2018-029b32bcf4
• FC27: FEDORA-2018-02051f8300
• FC28: FEDORA-2018-da87b1e643

I did simple tests on a fresh FC27 VM (as described here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-da87b1e643). Everything looks good.

Tested the "build" (http://singularity.lbl.gov/docs-build-container; from buildfile and from a docker container) and the "exec" / "shell" workflows on a fresh F28 virtual machine.

Note that kernel-modules RPM is required in order for Squashfs-based images to function, but kernel-modules wasn't in this particular VM image. This can probably be a tweak in a future build.

Ran a few test workflows involving "singularity shell" and "singularity exec" and directory images. Runtime functions well.

May I inquire about the status here? I notice that we've hit the karma threshold, but auto-push is disabled for this release. Any guidance on when a push to stable is planned?

Many thanks!

@nucleo - are you just testing the client, or server side also? Since the debug log is only from the client, I assume the former?

Server side worked out for me for the patch.

What's the plan for pushing this to release?

DMC-737 prevents CMS from proceeding with the switch from lcg-utils to gfal2.