schroot.conf says squeeze is stable and lenny is oldstable (because it targets the squeeze release). stable. This does seem somewhat of a chicken-and-egg situation for any package which hardcodes examples about which distributions are currently stable.
Yes. The configuration file is merely giving examples of how one might configure schroot. The actual names in there are not important--they are only intended to be illustrative. I have generally attempted to keep these examples up-to-date. As you correctly noted, the current examples are intended for the squeeze release (and I'll update them for wheezy once squeeze is released). Regarding this bug report, I'm not clear on what, if anything, you are proposing should be changed, or if there is any any other action which you would like to be taken. I.e. I'm unsure if there's anything I can actually do to resolve it. Regards, Roger
Well, I'm sure there are other things to do right now (hence, minor, and could be downgraded to wishlist). The changes that I came up with at first thought seemed more trouble than they were worth, to me (swapping out example configs based on something that indicates the release happened)... but perhaps in time a good solution could be found.
I'm afraid I'll have to close this bug. It's not ideal, but we do out of necessity need to target the release at the next (rather than current) stable release, and this inevitably leads to the sample configurations being ahead at some points in the release cycle. There's not much we can do about this--we'll also get complaints that it's out of date if it goes into a stable release with the oldstable names. Regards, Roger
So, in the fullness of (not even all that much) time... It looks like the distro-info-data package now provides up-to-date information that could be used to generate the config file with correct release names (both before and after release). Not that it is of particular severity (hence, minor, and perhaps should be wishlist), but with the metainfo/chicken-and-egg problems solved in a distribution-wide rather than schroot-specific fashion, perhaps we could now keep this bug open? It might pique someone's interest enough to submit a good patch. :) Thanks.
I can certainly take a look when I have some spare time. However, schroot isn't Debian-specific so it's not something I'd like to have a hard dependency upon. Regards, Roger