On Sat, May 29, 2010 at 01:13:45AM +0200, Steffen Möller wrote:
since today, we have Eucalyptus in the archive, which
is a Free clone of the Amazon Web Services for computing
and storage. Stefano wants to tag Squeeze as cloud
ready, and, frankly, for the very exact moment nobody
really knows
On 29/05/10 at 01:13 +0200, Steffen Möller wrote:
The bottleneck for the selection of Debian as a cloud
OS (at least for the AWS clouds) is the offering of
some certified kernel and root images, from which one
then jumps into the rest of Squeeze. Amazon restricts
that, with Eucalyptus there
On Sat, May 29, 2010 at 10:19:09AM +0200, Lucas Nussbaum wrote:
I think that enabling users to build their own customized images is
more in the spirit of doing things the Debian way, and also has the
advantage of not adding more work for any core debian team.
I've been told by the
On 29/05/10 at 11:20 +0200, Stefano Zacchiroli wrote:
On Sat, May 29, 2010 at 10:19:09AM +0200, Lucas Nussbaum wrote:
I think that enabling users to build their own customized images is
more in the spirit of doing things the Debian way, and also has the
advantage of not adding more work for
* Stefano Zacchiroli (z...@debian.org) [100529 09:29]:
I believe this is the most relevant part for -release. AFAIK the
pkg-eucalyptus team already has all the software to create on the fly
the needed images and kernel/initrds. The point is then which work-flow
do you want to synchronize with
On Sat, May 29, 2010 at 01:13:45AM +0200, Steffen Möller wrote:
I'll postpone an email to debian-devel for a week or
two until the workload at Eucalyptus allows upstream
to join the thread on that more public list.
Even after reading this mail I'm not sure what exactly you are trying to
do.
On 05/29/2010 11:54 AM, Andreas Barth wrote:
* Stefano Zacchiroli (z...@debian.org) [100529 09:29]:
I believe this is the most relevant part for -release. AFAIK the
pkg-eucalyptus team already has all the software to create on the fly
the needed images and kernel/initrds. The point is then
On Sat, May 29, 2010 at 01:29:13PM +0200, Steffen Möller wrote:
This Debian-like self-building is what is happening today and yes,
we can continue like that. My mail was just thought as an invitation
to think along, not as a request for anything. If the perfect answer is
VMbuilder I don't know
On Wed, May 12, 2010 12:23, Eugen Dedu wrote:
News:
- I have fixed all the appropriate upstream bugs
- I have tested the branches and they are ok from my point of vue, so
they can be packaged to a new release
- but before I am looking at the hppa failure
- as soon as I fix it, I will contact
Le dimanche 23 mai 2010 à 15:06 +0100, peter green a écrit :
Package: seed
Version: 2.30.0-1
Severity: serious
Seed fails to build on ia64. Unfortunately I don't have access to an
ia64 system so I can't debug this myself.
* Steffen Möller (steffen_moel...@gmx.de) [100529 16:52]:
On 05/29/2010 02:18 PM, Bastian Blank wrote:
On Sat, May 29, 2010 at 01:13:45AM +0200, Steffen Möller wrote:
I'll postpone an email to debian-devel for a week or
two until the workload at Eucalyptus allows upstream
to join the
On 29/05/10 14:31, Adam D. Barratt wrote:
On Wed, May 12, 2010 12:23, Eugen Dedu wrote:
News:
- I have fixed all the appropriate upstream bugs
- I have tested the branches and they are ok from my point of vue, so
they can be packaged to a new release
- but before I am looking at the hppa
On Saturday 29 May 2010 22:31:28 Adam D. Barratt wrote:
Does ekiga require any sourceful changes for the ptlib/opal transition?
If not then I'll schedule (yet) another set of binNMUs for ekiga so we can
try and get both transitions ready asap.
Yes ekiga does currently require a sourceful
13 matches
Mail list logo
