On Thu, Dec 01, 2016 at 10:43:18AM +0100, Thomas Goirand wrote:
>On 11/30/2016 08:35 PM, Sam Hartman wrote:
>> Do the openstack images use debootstrap as a package resolver?
>
>Yes.
>
>> If so, yeah, that broke for most nontrivial installations in stretch.
>
>After some tests, it is
On 12/01/2016 04:20 PM, Steve McIntyre wrote:
> I'd suggest maybe trying doing a stretch debootstrap locally using the
> same set of packages as the build script first, and see what's
> *Actually* breaking...
That's what I did, and that's how I found out that libpam-systemd was
the root cause of
On Thu, Dec 01, 2016 at 04:59:55PM +0100, Thomas Goirand wrote:
>On 12/01/2016 04:20 PM, Steve McIntyre wrote:
>> I'd suggest maybe trying doing a stretch debootstrap locally using the
>> same set of packages as the build script first, and see what's
>> *Actually* breaking...
>
>That's what I did,
On 2016-12-01 17:37:47 +0100 (+0100), Bastian Blank wrote:
[...]
> If we use two-stage sync only within one regions, different regions may
> finish updating at different times. The exact difference depends on the
> network speed, but I assume the would be at most 15 minutes apart.
>
> With
Hi Zach
On Mon, Nov 28, 2016 at 01:04:13PM -0800, Zach Marano wrote:
> The only question I have is if the regions are synced on different
> schedules will VM's in different regions get different repo data-
> irregardless of failover issues. In other words, will a user who has a VM
> in
On Fri, Nov 11, 2016 at 10:13:03PM +0100, Geert Stappers wrote:
> On Fri, Nov 11, 2016 at 02:09:39PM +, Lars Wirzenius wrote:
> >
> > * The YAML might look somethin like this:
> >
> > - step: create_partition
> > size: rest
> > partition_type: ext4
> >