FWIW, I've been using <a href="https://launchpad.net/%7Enova-core/+archive/release">ppa:nova-core/release</a> and it's worked pretty well with instructions for a <a href="http://docs.openstack.org/openstack-compute/admin/content/ch03s02.html#d5e194">Manual Install of Nova on Ubuntu</a> (just substitute ppa:nova-core/release for <code class="code"></code>ppa:nova-core/trunk in the instructions).<br>
<br>The link to the release PPA (<a href="https://launchpad.net/nova-core/+archive/stable">https://launchpad.net/nova-core/+archive/stable</a>) from the archived email that Ahmed mentions is broken. Perhaps it's been superseded by <a href="https://launchpad.net/%7Enova-core/+archive/release">https://launchpad.net/~nova-core/+archive/release</a>?<br>
<br>As for the stability of ppa:nova-core/release, I too think it shouldn't change unless there is a post release exception. For instance, in Bexar, there was the <a href="https://bugs.launchpad.net/nova/+bug/714678">Missing items in Bexar release tarball</a> bug. Because this was a bug that directly impacted the release I would expect that the result of this bug fix would be new a new nova package on ppa:nova-core/release.<br>
<br>Can anyone confirm that the fix for the <a href="https://bugs.launchpad.net/nova/+bug/714678">Missing items in Bexar release tarball</a> bug will cause a new nova package on ppa:nova-core/release?<br><br>Everett<br><br>
On Thu, Feb 10, 2011 at 11:34 AM, Wayne Walls <span dir="ltr"><<a href="mailto:wayne@openstack.org">wayne@openstack.org</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Just to clear up some issues I've ran into as well...I'm using a<br>
deployment script for my internal testing, which leverages<br>
'ppa:nova-core/trunk' so I can access the latest nova-* packages. I know<br>
at one time there was 'ppa:nova-core/ppa', and this was considered the<br>
'stable' area for nova-* packages. This PPA is no longer is use, but<br>
there is a 'ppa:nova-core/release'. If I'm out doing a demo somewhere, I<br>
should use this PPA? Is this being kept up-to-date? Unfortunately<br>
relying on trunk for packages has landed me in some situations where<br>
things just don't work :( I'm not against pulling stable source, but I<br>
like my three minute script to do all the work for me :D<br>
<font color="#888888"><br>
Wayne<br>
</font><div><div></div><div class="h5"><br>
On 2/10/11 12:19 PM, "Jay Pipes" <<a href="mailto:jaypipes@gmail.com">jaypipes@gmail.com</a>> wrote:<br>
<br>
>I think this may have to do with confusion over what the release<br>
>series on Launchpad are...<br>
><br>
>The Bexar series is frozen at this point, and does not get any<br>
>non-critical bug fixes or feature patches that have been going into<br>
>the Cactus (trunk) series, unless a post-bexar-release exception is<br>
>made (none have been yet, AFAIK).<br>
><br>
>So, if you pull lp:glance/bexar, you won't see ANY of the commits that<br>
>have been going into trunk since the 3rd of February.<br>
><br>
>lp:glance == the latest trunk series (Cactus right now) and contains<br>
>all fixes, features and patches that have been merged since after<br>
>Bexar was released.<br>
><br>
>I think it's just the case that you have been using lp:glance thinking<br>
>it is the stable release series. It isn't. lp:glance/bexar is.<br>
><br>
>Cheers!<br>
>jay<br>
><br>
>On Thu, Feb 10, 2011 at 12:26 PM, Jason Cannavale <<a href="mailto:jason@cannavale.com">jason@cannavale.com</a>><br>
>wrote:<br>
>> All,<br>
>><br>
>> I'm not sure if this has been discussed before at any length, but I<br>
>>would<br>
>> like to discuss if it makes sense to have source code in the stable<br>
>>trunk<br>
>> and installable packages built and provided from the rapidly changing<br>
>> development trunk.<br>
>><br>
>> For some background we've been working through some proof of concept<br>
>> deployments. Because the packages are coming from the development trunk<br>
>>we<br>
>> have been bitten repeatedly by having packages updated following code<br>
>>merges<br>
>> throughout the day. This has resulted in services such as networking no<br>
>> longer functioning. It seems to me, at least, that it would make sense<br>
>>to<br>
>> have a set of known working packages, packaged at each release point,<br>
>>in the<br>
>> stable trunk and having the source to build from in the development<br>
>>trunk.<br>
>><br>
>> Thoughts?<br>
>><br>
>> Jason<br>
>><br>
>> _______________________________________________<br>
>> Mailing list: <a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/~openstack</a><br>
>> Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
>> Unsubscribe : <a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/~openstack</a><br>
>> More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
>><br>
>><br>
><br>
>_______________________________________________<br>
>Mailing list: <a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/~openstack</a><br>
>Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
>Unsubscribe : <a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/~openstack</a><br>
>More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
<br>
<br>
<br>
_______________________________________________<br>
Mailing list: <a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/~openstack</a><br>
Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/~openstack</a><br>
More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
</div></div></blockquote></div><br>