On 05.02.2013 23:55, Don Armstrong wrote:
On Wed, 06 Feb 2013, Cyril Brulebois wrote:Daniel Baumann <daniel.baumann@progress-technologies.net> (05/02/2013):> or: > > * apply the following tested and working patch from #699742 in > debian-installer, […]Except that this “tested and working patch” doesn't fix anything. Sameissue, as seen by Michael and myself.Is it the intention of the Release Managers not to accept a newer version of syslinux into wheezy? [That is, if the CTTE were to decide to require some "fix" to d-i, we'd also have to override the RMs?]
Given that the syslinux packages in sid are a different major upstream version from those in wheezy, with a raw diffstat of 621 files changed, 36622 insertions(+), 15023 deletions(-)and that upstream version has been in unstable for a little over a week in total, I'm certainly uncomfortable that accepting the new version at this point would be in the best interest of the release. We've already said "no" to changes in other packages which were significantly smaller and didn't carry
the possibility of affecting something as key as the installer.Shipping an installer that was built with a differing version of syslinux than we eventually ship also causes me concern, since the first update to d-i in a point release will obviously be rebuilt against wheezy's syslinux. This introduces a situation that we can't reasonably test beforehand, as we could no longer be confident that the released version of the wheezy installer could be
correctly booted on all of our architectures.(tl,dr; right now, "yes, we believe the changes are too potentially disruptive".)
Regards, Adam