On 05.02.2013 23:55, Don Armstrong wrote:
On Wed, 06 Feb 2013, Cyril Brulebois wrote:
Daniel Baumann daniel.baum...@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
On Tue, Feb 05, 2013 at 01:48:22PM +0100, Julien Cristau wrote:
The submitters sincerely hope that all parties can work together for a
speedy resolution to this problem, avoiding further delay to this
release.
As a possibly useful data point for procedural reasons: I've verified on
IRC with
On 5 February 2013 22:48, Julien Cristau jcris...@debian.org wrote:
Package: tech-ctte
- the debian-installer source package, which builds the installer images
for debian's releases, build-depends on syslinux
- the release freeze for wheezy started in June 2012, and is now in its
final
On 06.02.2013 14:17, Anthony Towns wrote:
On 5 February 2013 22:48, Julien Cristau jcris...@debian.org wrote:
Package: tech-ctte
- the debian-installer source package, which builds the installer
images
for debian's releases, build-depends on syslinux
- the release freeze for wheezy
On 02/06/2013 12:55 AM, Don Armstrong wrote:
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?]
jftr, i never did nor intended to ask for having
On Tue, 05 Feb 2013, Julien Cristau wrote:
- the latest of these uploads breaks the installer, making it
impossible to build and upload the planned wheezy release
candidate, since build-dependencies are fetched from unstable
- when asked to revert this change, the syslinux maintainer
On 06.02.2013 17:48, Michael Biebl wrote:
Hi,
On 06.02.2013 16:36, Daniel Baumann wrote:
On 02/05/2013 09:33 PM, Michael Biebl wrote:
I tried this patch against cc123e0 from debian-installer git.
Unfortunately the problem is still the same.
indeed; only the first part of the patch was
On Wed, 06 Feb 2013, Russ Allbery wrote:
Don Armstrong d...@debian.org writes:
Assuming that the patch for #699742[0] fixes this issue with DI RC
releases being installed, is there still an outstanding issue for the
CTTE?
Earlier in this thread, there had been a couple of reports that
Russ Allbery r...@debian.org writes:
In practice, at least for the last couple of release cycles, we freeze
unstable for non-leaf packages during the release freeze because otherwise
it's too difficult with our current infrastructure to finish the
release.
I personally consider this a
Bdale Garbee bd...@gag.com writes:
I personally consider this a regrettable situation, and hope that for
jessie and beyond we can work out how to do this better. It is
unacceptable to me to freeze anything in sid for more than a week or
two at a time. Holding d-i's build dependencies static
On 06.02.2013 23:22, Don Armstrong wrote:
On Wed, 06 Feb 2013, Russ Allbery wrote:
Don Armstrong d...@debian.org writes:
Assuming that the patch for #699742[0] fixes this issue with DI RC
releases being installed, is there still an outstanding issue for the
CTTE?
Earlier in this thread,
Bdale Garbee bd...@gag.com (06/02/2013):
I personally consider this a regrettable situation, and hope that for
jessie and beyond we can work out how to do this better. It is
unacceptable to me to freeze anything in sid for more than a week or
two at a time. Holding d-i's build dependencies
Cyril Brulebois k...@debian.org writes:
Bdale Garbee bd...@gag.com (06/02/2013):
I personally consider this a regrettable situation, and hope that for
jessie and beyond we can work out how to do this better. It is
unacceptable to me to freeze anything in sid for more than a week or
two at a
On 02/06/2013 11:48 PM, Michael Biebl wrote:
Unfortunately the second patch doesn't work either. See [1].
that is incorrect; the patch works, it's just the old vbox version in
current debian testing/sid which has a bug (try the image on real
hardware or any other virtualization and it
On 07.02.2013 07:30, Daniel Baumann wrote:
On 02/06/2013 11:48 PM, Michael Biebl wrote:
Unfortunately the second patch doesn't work either. See [1].
that is incorrect; the patch works, it's just the old vbox version in
current debian testing/sid which has a bug (try the image on real
On 02/07/2013 07:35 AM, Michael Tokarev wrote:
This makes me wonder what other components are also buggy somehow and
needs to be updated?
first, this is a specific bug in vbox that was fixed some time ago but
didn't make it into debian yet (because it lags a significant amount of
upstream
On 07.02.2013 07:58, Daniel Baumann wrote:
On 02/07/2013 07:45 AM, Michael Biebl wrote:
Well, VBOX is pretty popular, so shipping an installer which doesn't
work for such an environment is certainly a no-go.
again, the syslinux in sid would not be in wheezy. making it a
*temporary* problem
On 02/07/2013 07:55 AM, Michael Biebl wrote:
I think it is obvious by now that reverting to syslinux 4 from wheezy is
the only sensible way forward at this point in the release.
'obvious'?
it requires two straight forward things, that, again, as said, are
required to be applied for jessie
sorry, forgot to put in the links to the patches..
On 02/07/2013 08:06 AM, Daniel Baumann wrote:
* patch applied against debian-installer to include the additionally
required .c32 modules when using vesamenu.c32
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699742#30
* patch
On 07.02.2013 08:06, Daniel Baumann wrote:
On 02/07/2013 07:55 AM, Michael Biebl wrote:
I think it is obvious by now that reverting to syslinux 4 from wheezy is
the only sensible way forward at this point in the release.
'obvious'?
Imho, yes. But then, it's not up to me to decide.
*
On 02/07/2013 08:12 AM, Michael Biebl wrote:
This list is getting longer with each email. Seeing that syslinux 5 has
been in sid for less then 10 days, I'm worried what other issues might
show up.
apart from the two obvious things (debian-installer and debian-cd) that
do need to be updated to
21 matches
Mail list logo
