On Tue, Mar 29, 2011 at 7:27 PM, Kurt Roeckx <span dir="ltr"><<a href="mailto:kurt@roeckx.be">kurt@roeckx.be</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">Note that in unstable you don't see the arch arch all version</div>
until the arch any version is also available. Or you would see<br>
the old arch all version until the new arch any version is<br>
available.<br></blockquote><div><br></div><div>That's great! My thanks to whomever had the foresight to prevent this temporary dependency breakage for all->any dependencies. I guess this would otherwise have annoyed unstable users for packages that had yet to be built for their architecture..?</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
This means that the version from unstable should always be<br>
installable, unless there is some other reason it's not like<br>
a transition of some other library.<br></blockquote><div><br></div><div>Yes, the libgmp3-dev -> libgmp-dev transition already bit me this way. I assumed I was in for more of the same with the self dependency.</div><div>
<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">The problem is that the buildds currently also see the newer<br>
arch all version. But this version will go away after some<br>
time and it will only see the version from unstable.<br></blockquote><div><br></div><div>If I may ask, for what purpose do the buildds have a special list of packages above and beyond those in unstable?</div><div><br></div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">The new version of mlton-basis will only be visible to the buildds<br>
for about a day, after which they should have no problem building<br>
it.<br></blockquote><div><br></div><div>Thank god. :)</div><div><br></div></div>