On Thu, Aug 25, 2016 at 12:30 AM, Frederic Bonnard
wrote:
>> Could you take a try the D-I for stretch alpha-7, which don't start
>> screen by default?
>> It's located under:
>> http://cdimage.debian.org/cdimage/stretch_di_alpha7/
>
> Already tried and the issue doesn't appear on this one.
> FTR,
> Could you take a try the D-I for stretch alpha-7, which don't start
> screen by default?
> It's located under:
> http://cdimage.debian.org/cdimage/stretch_di_alpha7/
Already tried and the issue doesn't appear on this one.
FTR, here are the tests ran on the isos on ppc64el :
http://ftp.unicamp.b
On Wed, Aug 24, 2016 at 10:56 PM, Frederic Bonnard
wrote:
> Hi Roger/all,
> I see that on some daily isos
> ( http://cdimage.debian.org/mirror/cdimage/daily-builds/daily/current/)
> screen seems to be activated by default. I'd like to know if there is a way
> to disable it as this was discussed.
Hi Roger/all,
I see that on some daily isos
( http://cdimage.debian.org/mirror/cdimage/daily-builds/daily/current/)
screen seems to be activated by default. I'd like to know if there is a way
to disable it as this was discussed.
This question is related to :
http://bugs.debian.org/cgi-bin/bugrep
On Aug 15, 2016, at 3:03 AM, Philip Hands wrote:
> Rick Thomas writes:
>
>> On Aug 14, 2016, at 7:37 PM, Cyril Brulebois wrote:
>>
>>> Also, I'm not sure whether we have any input methods which might be
>>> confused by ^A being “eaten” by screen. Does anyone know?
>>
>> Yes… That’s a proble
Hi Ben,
and thanks for your input.
Ben Hutchings (2016-08-15):
> I think that all builds of the installer should provide the same
> functionality so far as possible
ACK, looks good to me.
> and that the options to switch to a
> shell and to view the log are im
On Mon, 2016-08-15 at 04:37 +0200, Cyril Brulebois wrote:
> Hi Roger,
>
> > Roger Shimizu (2016-08-08):
> >
> > Dear KiBi,
> >
> > Sorry for not being able to reply earlier.
> > You feedback keeps me thinking a fix.
> >
> > > > On Tue, Jul 5, 2016 at 7:35 AM, Cyril Brulebois wrote:
> > >
> >
Hi,
Cyril Brulebois wrote:
> > During RFC stage of adding screen-udeb, firstly I though it's not
> > necessary for normal PC, which is not exact the same with "everyone"
> > you mentioned but should be close to, however a few feedbacks
> > convinced me that normal PC still need screen-udeb [0][1][
Rick Thomas writes:
> On Aug 14, 2016, at 7:37 PM, Cyril Brulebois wrote:
>
>> Also, I'm not sure whether we have any input methods which might be
>> confused by ^A being “eaten” by screen. Does anyone know?
>
> Yes… That’s a problem if you’re used to using “screen” as a terminal
> emulator to a
On Aug 14, 2016, at 7:37 PM, Cyril Brulebois wrote:
> Also, I'm not sure whether we have any input methods which might be
> confused by ^A being “eaten” by screen. Does anyone know?
Yes… That’s a problem if you’re used to using “screen” as a terminal emulator
to access the serial port on the t
Hi Roger,
Roger Shimizu (2016-08-08):
> Dear KiBi,
>
> Sorry for not being able to reply earlier.
> You feedback keeps me thinking a fix.
>
> On Tue, Jul 5, 2016 at 7:35 AM, Cyril Brulebois wrote:
> >
> > I still disagree with the UI changes it imposes on everyone, for the
> > reasons I've alr
On Aug 7, 2016, at 11:08 AM, Roger Shimizu wrote:
>
> I think the solution below is a middle ground, which I guess it can be
> accepted by everyone.
> - Keep screen-udeb in "common" for everyone, but don't start it
> automatically on i386/amd64.
> - Create a new "MEDIUM_SUPPORTED" or new folder
Dear KiBi,
Sorry for not being able to reply earlier.
You feedback keeps me thinking a fix.
On Tue, Jul 5, 2016 at 7:35 AM, Cyril Brulebois wrote:
>
> I still disagree with the UI changes it imposes on everyone, for the
> reasons I've already given.
During RFC stage of adding screen-udeb, first
Hi Roger,
Roger Shimizu (2016-07-05):
> On Mon, Jul 4, 2016 at 4:48 AM, Cyril Brulebois wrote:
> > So I've just checked: what started as "screen support would be nice
> > to have in some particular situation, on an opt-in basis" became
> > "let's use screen unconditionally", adding an extra line
Dear KiBi,
Thanks for your feedback!
On Mon, Jul 4, 2016 at 4:48 AM, Cyril Brulebois wrote:
> Cyril Brulebois (2016-07-04):
>> Cyril Brulebois (2016-07-04):
>> > Roger Shimizu (2016-07-04):
>> > > For the change I mentioned yesterday, I already tested on:
>> > > - armel/kirkwood
>> > > - am
Cyril Brulebois writes:
...
> Even if the release announce is not ready yet, the image build has
> finished and testing shows no major regressions, so we're going to
> publish this set of images as Stretch Alpha 7. I've lifted the udeb
> freeze some time ago; and you can feel free to push changes
Cyril Brulebois (2016-07-04):
> Cyril Brulebois (2016-07-04):
> > Roger Shimizu (2016-07-04):
> > > For the change I mentioned yesterday, I already tested on:
> > > - armel/kirkwood
> > > - amd64
> > > and they're working as expected.
> > >
> > > So I just pushed the commit to add screen supp
Cyril Brulebois (2016-07-04):
> Roger Shimizu (2016-07-04):
> > For the change I mentioned yesterday, I already tested on:
> > - armel/kirkwood
> > - amd64
> > and they're working as expected.
> >
> > So I just pushed the commit to add screen support.
> >
> > I hope all ARCHs still (daily) bu
Roger Shimizu (2016-07-04):
> For the change I mentioned yesterday, I already tested on:
> - armel/kirkwood
> - amd64
> and they're working as expected.
>
> So I just pushed the commit to add screen support.
>
> I hope all ARCHs still (daily) build fine when I get up tomorrow morning.
> If not
Dear KiBi,
Thanks for your reply!
On Mon, Jul 4, 2016 at 12:05 AM, Cyril Brulebois wrote:
> Hi,
>
> Roger Shimizu (2016-07-03):
>> On Sun, Jul 3, 2016 at 12:44 AM, Cyril Brulebois wrote:
>> > Please don't. We want to avoid pushing changes which aren't relevant to
>> > the release being prepare
Hi,
Roger Shimizu (2016-07-03):
> On Sun, Jul 3, 2016 at 12:44 AM, Cyril Brulebois wrote:
> > Please don't. We want to avoid pushing changes which aren't relevant to
> > the release being prepared, in case we need to do some fixup before
> > uploading and building again.
>
> It's lucky that I d
On Sun, Jul 3, 2016 at 12:44 AM, Cyril Brulebois wrote:
> Roger Shimizu (2016-07-03):
>> I saw it's already reached archive, so I thought it's done.
>> OK. Understand.
>
> That's one part. Then images are built on pettersson, tested, and
> eventually signed and published. We're not there yet.
>
>
Roger Shimizu (2016-07-03):
> I saw it's already reached archive, so I thought it's done.
> OK. Understand.
That's one part. Then images are built on pettersson, tested, and
eventually signed and published. We're not there yet.
> I just prepared the commit to support screen:
> -
> https://anons
Dear KiBi,
Thanks for your prompting reply!
On Sun, Jul 3, 2016 at 6:12 AM, Cyril Brulebois wrote:
> Hi Roger,
>
> Roger Shimizu (2016-07-03):
>> On Sat, Jun 25, 2016 at 7:22 AM, Cyril Brulebois wrote:
>> > Having checked with -release already, I'm freezing udebs right away.
>>
>> I think the
Hi Roger,
Roger Shimizu (2016-07-03):
> On Sat, Jun 25, 2016 at 7:22 AM, Cyril Brulebois wrote:
> > Having checked with -release already, I'm freezing udebs right away.
>
> I think the monthly release is done, so could you un-freeze the udebs?
> I see ncurses is still pending to testing [0]:
>
Dear KiBi,
On Sat, Jun 25, 2016 at 7:22 AM, Cyril Brulebois wrote:
> Having checked with -release already, I'm freezing udebs right away.
I think the monthly release is done, so could you un-freeze the udebs?
I see ncurses is still pending to testing [0]:
- 11 days old (needed 10 days)
- Not tou
Hi,
Nicholas D Steeves (2016-06-28):
> Could someone please tell me what the deadline is for adding expanded
> partman-btrfs functionality? My proposal is in a thread on
> debian-boot@lists.debian.org, subject: "Re: btrfs subvolume naming
> scheme". A résumé of the read is: add the volume-manag
Karsten Merker (2016-06-29):
> I have in the meantime run further tests with u-boot
> 2016.03+dfsg1-6 (including going through a full installation
> process with a locally-built d-i) on an Olimex A20-Lime1 and on
> an Olimex A20-SOM-EVB - none of them shows any freezes,
> so I think we are clear t
On 24 June 2016 at 18:22, Cyril Brulebois wrote:
> Hi,
>
> I've just checked with Ben, it seems we could be getting a 4.6 kernel
> suitable for testing (no regressions reported from previous version +
> mips* FTBFS fix) shortly. We could think about urgenting it into testing
> and releasing a new
Karsten Merker (2016-06-28):
> On Tue, Jun 28, 2016 at 09:49:02AM +0200, Vagrant Cascadian wrote:
> > On 2016-06-27, Cyril Brulebois wrote:
> > > Vagrant Cascadian (2016-06-27):
> > >> On 2016-06-27, Cyril Brulebois wrote:
> > >> > for some reasons I failed at double checking when u-boot is used
On 2016-06-27, Cyril Brulebois wrote:
> [ Unknown signature status ]
> Vagrant Cascadian (2016-06-27):
>> On 2016-06-27, Cyril Brulebois wrote:
>> > for some reasons I failed at double checking when u-boot is used; it's
>> > needed at build time for debian-installer, so we'd need the u-boot fix
>
Vagrant Cascadian (2016-06-27):
> On 2016-06-27, Cyril Brulebois wrote:
> > for some reasons I failed at double checking when u-boot is used; it's
> > needed at build time for debian-installer, so we'd need the u-boot fix
> > before uploading src:debian-installer.
> >
> > Do you have any time fram
On 2016-06-27, Cyril Brulebois wrote:
> Cyril Brulebois (2016-06-27):
>> FWIW I'm going to upload debian-installer very shortly; it'd be nice if
>> u-boot could be uploaded while src:debian-installer is getting built,
>> urgented, and dak copy-installer'd into testing; so that it has a chance
>> t
Hi again,
Cyril Brulebois (2016-06-27):
> FWIW I'm going to upload debian-installer very shortly; it'd be nice if
> u-boot could be uploaded while src:debian-installer is getting built,
> urgented, and dak copy-installer'd into testing; so that it has a chance
> to reach testing before we start b
Hi Vagrant, Karsten,
Cyril Brulebois (2016-06-25):
> Vagrant Cascadian (2016-06-25):
> > On 2016-06-25, Cyril Brulebois wrote:
> > > Karsten Merker (2016-06-25):
> > >> on armhf we currently face some u-boot-related problems. U-Boot
> > >> 2016.03 (in unstable and testing) causes kernel hangs
Vagrant Cascadian (2016-06-25):
> On 2016-06-25, Cyril Brulebois wrote:
> > Karsten Merker (2016-06-25):
> >> on armhf we currently face some u-boot-related problems. U-Boot
> >> 2016.03 (in unstable and testing) causes kernel hangs under certain
> >> conditions on a number of sunxi platforms.
On 2016-06-25, Cyril Brulebois wrote:
> Karsten Merker (2016-06-25):
>> on armhf we currently face some u-boot-related problems. U-Boot
>> 2016.03 (in unstable and testing) causes kernel hangs under certain
>> conditions on a number of sunxi platforms. These issues are fixed in
>> u-boot v2016.0
(Trimming cc a bit.)
Karsten Merker (2016-06-25):
> on armhf we currently face some u-boot-related problems. U-Boot
> 2016.03 (in unstable and testing) causes kernel hangs under certain
> conditions on a number of sunxi platforms. These issues are fixed in
> u-boot v2016.05 (latest official rele
Hi,
I've just checked with Ben, it seems we could be getting a 4.6 kernel
suitable for testing (no regressions reported from previous version +
mips* FTBFS fix) shortly. We could think about urgenting it into testing
and releasing a new d-i early in the week, which seems OK on the -cd
side too.
G
39 matches
Mail list logo
