Re: transition: proposal libpt2.6.5->libpt2.6.6 & libopal3.6.6->libopal3.6.7

2010-05-29 Thread Mark Purcell
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 up

Re: transition: proposal libpt2.6.5->libpt2.6.6 & libopal3.6.6->libopal3.6.7

2010-05-29 Thread Eugen Dedu
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 failure

Re: Eucalyptus Cloud infrastructure and kernels/initrds

2010-05-29 Thread Andreas Barth
* 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 jo

Re: Eucalyptus Cloud infrastructure and kernels/initrds

2010-05-29 Thread Steffen Möller
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 thread on that more public list. > > Even after reading this

Re: Eucalyptus Cloud infrastructure and kernels/initrds

2010-05-29 Thread Stefano Zacchiroli
On Sat, May 29, 2010 at 11:41:09AM +0200, Lucas Nussbaum wrote: > We don't provide official tarballs with the result of debootstrap. Well, we don't because deboostrap output is not the main media to use Debian for our users, I guess. EMIs/AMIs are such a media for users of some "cloud" infrastruct

Re: Bug#582774: seed FTBFS on ia64

2010-05-29 Thread Josselin Mouette
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. > > https://buildd.debian.org/fetch.cgi?pkg=seed&arch=ia64&ver

Re: transition: proposal libpt2.6.5->libpt2.6.6 & libopal3.6.6->libopal3.6.7

2010-05-29 Thread Adam D. Barratt
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 co

Re: Eucalyptus Cloud infrastructure and kernels/initrds

2010-05-29 Thread Stefano Zacchiroli
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 k

Re: Eucalyptus Cloud infrastructure and kernels/initrds

2010-05-29 Thread Steffen Möller
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 th

Re: Eucalyptus Cloud infrastructure and kernels/initrds

2010-05-29 Thread Bastian Blank
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.

Re: Eucalyptus Cloud infrastructure and kernels/initrds

2010-05-29 Thread Andreas Barth
* 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 wi

Re: Eucalyptus Cloud infrastructure and kernels/initrds

2010-05-29 Thread Lucas Nussbaum
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 wo

Re: Eucalyptus Cloud infrastructure and kernels/initrds

2010-05-29 Thread Stefano Zacchiroli
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 pkg-eucaly

Re: Eucalyptus Cloud infrastructure and kernels/initrds

2010-05-29 Thread Lucas Nussbaum
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 t

Re: Eucalyptus Cloud infrastructure and kernels/initrds

2010-05-29 Thread Stefano Zacchiroli
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