[fedora-atomic] PR #27 `post: Work around LVM archival conflicting with ostree`

walters commented on the pull-request: `post: Work around LVM archival conflicting with ostree` that you are following: `` It's still valid. I may get back to it. `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/27

Ownership of the Cloud Base Image

After some discussions with mattdm and sgallagh about the cloud base image and the server WG we have decided for now to leave the cloud base image out of the server WG. Obviously it doesn't make sense to have it stay as owned by the Atomic WG so here is what I would like to propose: - Have the

Re: next steps for migrating Cloud Base image to Fedora Server?

On 02/08/2017 04:35 PM, Adam Williamson wrote: > On Tue, 2016-12-06 at 16:38 -0500, Matthew Miller wrote: >> I think we had general agreement around what we want to do here: >> have the Cloud Base Image become instead Fedora Server, but shipped >> as a cloud image and made available in cloud

Re: owncloud container in fedora container registry

On 8 February 2017 at 22:16, Josh Berkus wrote: > On 02/08/2017 02:12 PM, Adam Williamson wrote: >> >> This seems entirely likely, but it seems very unlikely that anyone >> upstream (at either OC or NC) gives a damn about making it work on PHP >> 5.4. >> > > Mind you, this

[atomic-wg] Issue #213 `Move atpmic_scan_openscap container image from Fedora-Dockerfiles GitHub into DistGit`

The status of the issue: `Move atpmic_scan_openscap container image from Fedora-Dockerfiles GitHub into DistGit` of project: `atomic-wg` has been updated to: Closed as Duplicate by maxamillion. https://pagure.io/atomic-wg/issue/213 ___ cloud mailing

[atomic-wg] Issue #223 `Move container-best-practices container image from Fedora-Dockerfiles GitHub into DistGit`

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/container-best-practices `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/223

[atomic-wg] Issue #222 `Move systemd-apache httpd container image from Fedora-Dockerfiles GitHub into DistGit`

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/systemd/apache `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/222

[atomic-wg] Issue #220 `Move earthquake container image from Fedora-Dockerfiles GitHub into DistGit`

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/earthquake `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/220

[atomic-wg] Issue #219 `Move registry container image from Fedora-Dockerfiles GitHub into DistGit`

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/registry `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/219

[atomic-wg] Issue #218 `Move postgresql container image from Fedora-Dockerfiles GitHub into DistGit`

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/postgresql `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/218

[atomic-wg] Issue #215 `Move redis httpd container image from Fedora-Dockerfiles GitHub into DistGit`

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/redis `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/215

[atomic-wg] Issue #213 `Move atpmic_scan_openscap container image from Fedora-Dockerfiles GitHub into DistGit`

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/atomic_scan_openscap `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/213

[atomic-wg] Issue #214 `Move tools container image from Fedora-Dockerfiles GitHub into DistGit`

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/tools `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/214

[atomic-wg] Issue #212 `Move qpid container image from Fedora-Dockerfiles GitHub into DistGit`

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/qpid `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/212

[atomic-wg] Issue #211 `Move rabbitmq container image from Fedora-Dockerfiles GitHub into DistGit`

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/rabbitmq `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/211

[atomic-wg] Issue #210 `Move systemd-systemd container image from Fedora-Dockerfiles GitHub into DistGit`

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/systemd/systemd `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/210

[atomic-wg] Issue #208 `Move mariadb container image from Fedora-Dockerfiles GitHub into DistGit`

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/mariadb `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/208

[atomic-wg] Issue #207 `Move couchdb container image from Fedora-Dockerfiles GitHub into DistGit`

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/couchdb `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/207

[atomic-wg] Issue #206 `Move nginx container image from Fedora-Dockerfiles GitHub into DistGit`

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/nginx `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/206

[atomic-wg] Issue #205 `Move memcached container image from Fedora-Dockerfiles GitHub into DistGit `

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/memcached `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/205

[atomic-wg] Issue #204 `Move ssh container image from Fedora-Dockerfiles GitHub into DistGit `

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/ssh `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/204

Re: owncloud container in fedora container registry

On 02/08/2017 02:12 PM, Adam Williamson wrote: > On Wed, 2017-02-08 at 14:10 -0800, Josh Berkus wrote: >> Really, our best hope is that NextCloud cleans up the Owncloud >> architecture to make it supportable. > > This seems entirely likely, but it seems very unlikely that anyone > upstream (at

Re: owncloud container in fedora container registry

On Wed, 2017-02-08 at 14:10 -0800, Josh Berkus wrote: > Really, our best hope is that NextCloud cleans up the Owncloud > architecture to make it supportable. This seems entirely likely, but it seems very unlikely that anyone upstream (at either OC or NC) gives a damn about making it work on PHP

Re: owncloud container in fedora container registry

On 02/08/2017 02:04 PM, Mats Wichmann wrote: > On 02/08/2017 10:12 AM, James Hogarth wrote: >> On 8 Feb 2017 16:10, "Dusty Mabe" wrote: >> >> >> >> On 02/08/2017 05:42 AM, James Hogarth wrote: >>> Hi guys, >>> >>> I just submitted a container review request for owncloud. >>>

Re: Fedora Rawhide-20170208.n.0 compose check report

On Wed, Feb 08, 2017 at 01:09:33PM -0800, Adam Williamson wrote: > On Wed, 2017-02-08 at 20:34 +, Fedora compose checker wrote: > > Missing expected images: > > Cloud_base qcow2 x86_64 > > This seems to be running into some kind of size issue: >

[fedora-atomic] PR #27 `post: Work around LVM archival conflicting with ostree`

ausil commented on the pull-request: `post: Work around LVM archival conflicting with ostree` that you are following: `` is this needed still? it has conflicts currently `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/27

Re: owncloud container in fedora container registry

On 02/08/2017 10:12 AM, James Hogarth wrote: > On 8 Feb 2017 16:10, "Dusty Mabe" wrote: > > > > On 02/08/2017 05:42 AM, James Hogarth wrote: >> Hi guys, >> >> I just submitted a container review request for owncloud. >> >>

[atomic-wg] Issue #203 `Move apache httpd container image from Fedora-Dockerfiles GitHub into DistGit`

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/apache `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/203

Re: next steps for migrating Cloud Base image to Fedora Server?

On Tue, 2016-12-06 at 16:38 -0500, Matthew Miller wrote: > I think we had general agreement around what we want to do here: > have the Cloud Base Image become instead Fedora Server, but shipped > as a cloud image and made available in cloud providers. What are the > next steps to actually get

Re: 2017-02-08 Atomic WG Meeting Minutes

On 8 February 2017 at 18:07, Trishna Guha wrote: > Full Log: > https://meetbot.fedoraproject.org/fedora-meeting-1/2017-02-08/fedora_atomic_wg.2017-02-08-17.00.log.html > Summary: >

Re: Fedora Rawhide-20170208.n.0 compose check report

show_bug.cgi?id=1420508 I believe there may be some other packages needing a rebuild too, will investigate and file those. > Cloud_base raw-xz x86_64 Same as the other cloud_base. > Xfce raw-xz armhfp Seems to be some kind of compose mishap: https://kojipkgs.fedoraproject.org/compose/rawh

2017-02-08 Atomic WG Meeting Minutes

Full Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2017-02-08/fedora_atomic_wg.2017-02-08-17.00.log.html Summary: https://meetbot-raw.fedoraproject.org/fedora-meeting-1/2017-02-08/fedora_atomic_wg.2017-02-08-17.00.txt === #fedora-meeting-1:

[atomic-wg] Issue #200 `Planning for interim container releases: To rebuild or not rebuild?`

kushal added a new comment to an issue you are following: `` > > We should do what's needed to ensure that our images pick up the most recent > rpms -- when you say rebuild all content, do you mean rebuild the rpms > themselves, or rebuild all the images? > > Sorry for lack of clarification,

[atomic-wg] Issue #202 `Syncing released Fedora container images to Docker Hub`

kushal added a new comment to an issue you are following: `` +1 to stay with the current namespace. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/202 ___ cloud mailing list --

[atomic-wg] Issue #202 `Syncing released Fedora container images to Docker Hub`

dustymabe added a new comment to an issue you are following: `` +1 for current name space `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/202 ___ cloud mailing list -- cloud@lists.fedoraproject.org To

Re: owncloud container in fedora container registry

On 8 Feb 2017 16:10, "Dusty Mabe" wrote: On 02/08/2017 05:42 AM, James Hogarth wrote: > Hi guys, > > I just submitted a container review request for owncloud. > > https://bugzilla.redhat.com/show_bug.cgi?id=1420275 > > Since PHP is stuck at 5.4 in EL7 this is my first step

[atomic-wg] Issue #198 `move ostree ref to be "container-host"`

walters added a new comment to an issue you are following: `` The design I had for ostree refspecs is that they go from "general -> specific". Hence it'd look like this: ``` fedora/25/x86_64/atomic-host fedora/25/x86_64/workstation ``` The rationale for the `standard` thing was that in

Re: owncloud container in fedora container registry

On 02/08/2017 05:42 AM, James Hogarth wrote: > Hi guys, > > I just submitted a container review request for owncloud. > > https://bugzilla.redhat.com/show_bug.cgi?id=1420275 > > Since PHP is stuck at 5.4 in EL7 this is my first step of still being > able to provide owncloud to EL7 users when

owncloud container in fedora container registry

Hi guys, I just submitted a container review request for owncloud. https://bugzilla.redhat.com/show_bug.cgi?id=1420275 Since PHP is stuck at 5.4 in EL7 this is my first step of still being able to provide owncloud to EL7 users when owncloud 10 releases and bumps the minimal version to 5.6 This

[atomic-wg] Issue #189 `Remove-Kube: document new Kubernetes install process`

trishnag added a new comment to an issue you are following: `` We currently have DOC in here http://fedoracloud.readthedocs.io. It makes sense to have all documentation in one place. Here is the git repo: https://github.com/fedora-cloud/fedoracloud `` To reply, visit the link below or just

[atomic-wg] Issue #202 `Syncing released Fedora container images to Docker Hub`

trishnag added a new comment to an issue you are following: `` +1 on sticking with the current namespace. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/202 ___ cloud mailing list --