Hi all,<div> related to this bug, it was solved a long long time ago (around 2012~rc3) but nobody closed it. I did it yesterday, after the removal. I plan to upload a new keystone package this week, so let's hope no other issues come around.</div>
<div><br></div><div> And about the team, I agree with you Loic. Openstack is too big and fast moving that keeping things working all the time is almost impossible unless you are working 100% on it, besides, Debian has a problem with timing (I remember having this conversation with Loic some time ago, so just copy/paste it with some more up-to-date data)</div>
<div><br></div><div>"T<span style>he major problem of Debian and OpenStack, is Debian itself. </span><span style>In a so fast moving project like OpenStack, having an </span><span style>"EveryThing-Ready-and-</span><span style>Included" release every two years is not viable </span><span style>for this scenario. In the case of OpenStack, Squeeze is too old to </span><span style>handle it the way it is right now (Too many things not directly </span><span style>related with OpenStack, like qemu-xen, python-modules, etc., should </span><span style>be backported to make it functional, and with just volunteer </span><span style>packagers, make it a not so viable option). In the other hand, the </span><span style>next release, is planned to 1Q 2013 (</span><span style>Wheezy being frozen in later June</span><span style>), so </span><span style>Essex release will be outdated and Folsom we be the stable release by </span><span style>then, and with G release knocking on the door (Essex is supposed to be a LTS release, supported by Canonical/Ubuntu until around April 2017so is not that bad). </span><span style>Solutions? Forget about Squeeze</span><span style>, focus in Wheezy + Essex as </span><span style>an official release , and Folsom (or G release) as a back-ported option. The other </span><span style>option (not viable in a short term), is change the way Debian makes it </span><span style>releases, and try to have something more "componentized" (like Progeny </span><span style>tried to do some years ago) or "rolling-releases", so trending-topic these days. Neither GNOME, OpenStack, LibreOffice, </span><span style>linux-kernel (just to name some) has a similar release cycle or core </span><span style>necessities to run in a system, so why try to release, prepare, </span><span style>stabilized everything at the same time no matter what's the status </span><span style>the upstream project is? (Just int he case of OpenStack, and supposing </span><span style>everything thing is going according the schedule, with a 6 month </span><span style>release cycle vs. 2 years in Debian + frozen period, when Wheezy is </span><span style>released, we are going to release an outdated version -essex (but LTS thanks to Canonical)- when </span><span style>Folsom is 4 months old! and the new release coming in less than two months!) I agree this needs a lot of more development, </span><span style>but i think it's something that Debian should have to think about." </span></div>
<div><span style><br></span></div><div><font color="#222222" face="arial, sans-serif">Re-reading it, the situation is not that bad actually. We were lucky enough that the new Ubuntu LTS was released, and we can use the excuse of Essex being supported until 2017. But the key point is the same: "Debian is huge and slow, while OpenStack (and so many other projects) are really fast-moving"</font></div>
<div><div><br></div><div>Ghe Rivero</div><div><br><div class="gmail_quote">On Tue, May 29, 2012 at 8:14 AM, Loic Dachary <span dir="ltr"><<a href="mailto:loic@enovance.com" target="_blank">loic@enovance.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Hi,<br>
<br>
This (removal of keystone from testing) is a definitive sign that
our team is understaffed :-) At the moment Ghe Rivero and Mehdi
Abaakouk are active. Unless I'm mistaken, noone else has currently
time to work on the OpenStack package issues. To address this
problem I propose that my company hires a Debian GNU/Linux packager
to resolve this crisis. Please let me know if you have a better
idea.<br>
<br>
Cheers<div><div class="h5"><br>
<br>
-------- Original Message --------
<table border="0" cellpadding="0" cellspacing="0">
<tbody>
<tr>
<th align="RIGHT" nowrap valign="BASELINE">Subject: </th>
<td>[Openstack-devel] keystone REMOVED from testing</td>
</tr>
<tr>
<th align="RIGHT" nowrap valign="BASELINE">Date: </th>
<td>Mon, 28 May 2012 16:39:14 +0000</td>
</tr>
<tr>
<th align="RIGHT" nowrap valign="BASELINE">From: </th>
<td>Debian testing watch <a href="mailto:noreply@release.debian.org" target="_blank"><noreply@release.debian.org></a></td>
</tr>
<tr>
<th align="RIGHT" nowrap valign="BASELINE">To: </th>
<td><a href="mailto:keystone@packages.debian.org" target="_blank">keystone@packages.debian.org</a></td>
</tr>
</tbody>
</table>
<br>
<br>
<pre>FYI: The status of the keystone source package
in Debian's testing distribution has changed.
Previous version: 2012.1-2
Current version: (not in testing)
Hint: <a href="http://release.debian.org/britney/hints/nthykier" target="_blank"><http://release.debian.org/britney/hints/nthykier></a>
#20120528
#20120528
The script that generates this mail tries to extract removal
reasons from comments in the britney hint files. Those comments
were not originally meant to be machine readable, so if the
reason for removing your package seems to be nonsense, it is
probably the reporting script that got confused. Please check the
actual hints file before you complain about meaningless removals.
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See <a href="http://release.debian.org/testing-watch/" target="_blank">http://release.debian.org/testing-watch/</a> for more information.
_______________________________________________
Openstack-devel mailing list
<a href="mailto:Openstack-devel@lists.alioth.debian.org" target="_blank">Openstack-devel@lists.alioth.debian.org</a>
<a href="http://lists.alioth.debian.org/mailman/listinfo/openstack-devel" target="_blank">http://lists.alioth.debian.org/mailman/listinfo/openstack-devel</a>
</pre>
</div></div></div>
<br>_______________________________________________<br>
Openstack-devel mailing list<br>
<a href="mailto:Openstack-devel@lists.alioth.debian.org">Openstack-devel@lists.alioth.debian.org</a><br>
<a href="http://lists.alioth.debian.org/mailman/listinfo/openstack-devel" target="_blank">http://lists.alioth.debian.org/mailman/listinfo/openstack-devel</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Pinky: "Gee, Brain, what do you want to do tonight?"<br>The Brain: "The same thing we do every night, Pinky—try to take over the world!"<br>
<br> .''`. Pienso, Luego Incordio <br>: :' : <br>`. `' <br> `- <a href="http://www.debian.org" target="_blank">www.debian.org</a> <a href="http://www.openstack.com" target="_blank">www.openstack.com</a><br>
<br>GPG Key: 26F020F7<br>GPG fingerprint: 4986 39DA D152 050B 4699 9A71 66DB 5A36 26F0 20F7<br>
</div></div>