On Mon, Nov 10, 2014 at 12:46:05AM -0600, Dennis Gilmore wrote:
On Sat, 08 Nov 2014 13:16:19 -0500
Colin Walters walt...@verbum.org wrote:
On Fri, Nov 7, 2014, at 08:03 AM, Dennis Gilmore wrote:
On Sun, 02 Nov 2014 16:33:57 -0500
Colin Walters walt...@verbum.org wrote:
Currently,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, 08 Nov 2014 13:16:19 -0500
Colin Walters walt...@verbum.org wrote:
On Fri, Nov 7, 2014, at 08:03 AM, Dennis Gilmore wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 02 Nov 2014 16:33:57 -0500
Colin Walters
On Fri, Nov 7, 2014, at 08:03 AM, Dennis Gilmore wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 02 Nov 2014 16:33:57 -0500
Colin Walters walt...@verbum.org wrote:
Currently, the Atomic cloud image still tries to contact the compose
server internal mirror for updates.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 7 Nov 2014 08:58:29 -0500
Matthew Miller mat...@fedoraproject.org wrote:
On Fri, Nov 07, 2014 at 07:03:28AM -0600, Dennis Gilmore wrote:
Do we know what the final mirrorlist URL will be? Where are we on
getting content sync'd out?
On Mon, Nov 3, 2014, at 11:24 AM, Luke Macken wrote:
I'm not sure exactly where the final bits will live, or what the URL
will be, but the fedmsg-atomic-composer is up and running on the
composer.stg box and successfully spitting out rawhide f21 trees.
Nice. Maybe we can deprecate
On Tue, Nov 04, 2014 at 10:28:02AM -0500, Colin Walters wrote:
Assuming that this is correct, what needs to change? Is this a
kickstart line? We should make the appropriate change _today_.
That's not a globally replicated location, it means we're not taking
advantage of mirrorlists.
On Tue, Nov 04, 2014 at 10:34:30AM -0500, Colin Walters wrote:
Pushing this out to a production releng box will be simple once we
determine where the trees will live on /pub.
Who owns that decision/how do we move forward?
Ticket at https://fedorahosted.org/rel-eng/ — I think the existing alt
On Sun, Nov 02, 2014 at 04:33:57PM -0500, Colin Walters wrote:
Currently, the Atomic cloud image still tries to contact the compose server
internal mirror for updates.
Do we know what the final mirrorlist URL will be? Where are we on getting
content sync'd out?
I'm not sure exactly
On Mon, Nov 03, 2014 at 11:24:18AM -0500, Luke Macken wrote:
I'm not sure exactly where the final bits will live, or what the URL
will be, but the fedmsg-atomic-composer is up and running on the
composer.stg box and successfully spitting out rawhide f21 trees.
Pushing this out to a production
Currently, the Atomic cloud image still tries to contact the compose server
internal mirror for updates.
Do we know what the final mirrorlist URL will be? Where are we on getting
content sync'd out?
___
cloud mailing list
10 matches
Mail list logo
