Re: d-i upload for 8.11 (was: Re: Scheduling final Jessie point release, 8.11)

2018-06-21 Thread Cyril Brulebois
Hi,

Cyril Brulebois  (2018-06-19):
> I might try and give amd64/i386 netinst a shot, just to be sure.

Of course we won't have netinst until the point release has happened;
and I guess I didn't really mean netboot either since we're currently
lacking udebs for the new ABI (only in o-p-u for now), so I could only
test the installer boots fine, and that speech synthesis also starts
properly.

Very low on free time, so I'm really unsure I'll be able to play the
“hack the archive” game where I pretend to have merged oldstable and
o-p-u into something d-i can process; sorry…


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature


Re: d-i upload for 8.11 (was: Re: Scheduling final Jessie point release, 8.11)

2018-06-19 Thread Cyril Brulebois
Hi,

Adam D. Barratt  (2018-06-18):
> Yes, d-i and dini are the last things I'm expecting for the point
> release; everything else has been in place for at least a couple of
> dinstalls already.
> 
> If the d-i upload could happen before the end of tomorrow, that should
> still give us plenty of time to get dini organised afterwards.

Built locally, and debdiff'd against version currently in jessie.
Everything looks good to me, so just uploaded.

FWIW, changes include mostly (1) Built-Using getting some versions
bumped, and (2) filenames where the kernel ABI is embedded, in
addition to the usual Installed-Size and Version updates.

(1)
 - gdk-pixbuf (= [-2.31.1-2+deb8u6),-] {+2.31.1-2+deb8u7),+}
 - gnupg (= [-1.4.18-7+deb8u4),-] {+1.4.18-7+deb8u5),+}
 - libxcursor (= [-1:1.1.14-1),-] {+1:1.1.14-1+deb8u1),+}
 - linux (= [-3.16.51-2),-] {+3.16.56-1+deb8u1),+}
 - openssl (= [-1.0.1t-1+deb8u7),-] {+1.0.1t-1+deb8u8)

(2)
- -rw-r--r--  root/root   
/usr/lib/debian-installer/images/8/armel/versatile/vmlinuz-3.16.0-4-versatile
+ -rw-r--r--  root/root   
/usr/lib/debian-installer/images/8/armel/versatile/vmlinuz-3.16.0-6-versatile

- -rw-r--r--  root/root   
/usr/lib/debian-installer/images/8/mips/malta/vmlinux-3.16.0-4-4kc-malta
- -rw-r--r--  root/root   
/usr/lib/debian-installer/images/8/mips/octeon/vmlinux-3.16.0-4-octeon
- -rw-r--r--  root/root   
/usr/lib/debian-installer/images/8/mips/sb1-bcm91250a/vmlinux-3.16.0-4-sb1-bcm91250a
+ -rw-r--r--  root/root   
/usr/lib/debian-installer/images/8/mips/malta/vmlinux-3.16.0-6-4kc-malta
+ -rw-r--r--  root/root   
/usr/lib/debian-installer/images/8/mips/octeon/vmlinux-3.16.0-6-octeon
+ -rw-r--r--  root/root   
/usr/lib/debian-installer/images/8/mips/sb1-bcm91250a/vmlinux-3.16.0-6-sb1-bcm91250a

- -rw-r--r--  root/root   
/usr/lib/debian-installer/images/8/mipsel/loongson-2e/vmlinux-3.16.0-4-loongson-2e
- -rw-r--r--  root/root   
/usr/lib/debian-installer/images/8/mipsel/loongson-2f/vmlinux-3.16.0-4-loongson-2f
- -rw-r--r--  root/root   
/usr/lib/debian-installer/images/8/mipsel/loongson-3/vmlinux-3.16.0-4-loongson-3
- -rw-r--r--  root/root   
/usr/lib/debian-installer/images/8/mipsel/malta/vmlinux-3.16.0-4-4kc-malta
- -rw-r--r--  root/root   
/usr/lib/debian-installer/images/8/mipsel/sb1-bcm91250a/vmlinux-3.16.0-4-sb1-bcm91250a
+ -rw-r--r--  root/root   
/usr/lib/debian-installer/images/8/mipsel/loongson-2e/vmlinux-3.16.0-6-loongson-2e
+ -rw-r--r--  root/root   
/usr/lib/debian-installer/images/8/mipsel/loongson-2f/vmlinux-3.16.0-6-loongson-2f
+ -rw-r--r--  root/root   
/usr/lib/debian-installer/images/8/mipsel/loongson-3/vmlinux-3.16.0-6-loongson-3
+ -rw-r--r--  root/root   
/usr/lib/debian-installer/images/8/mipsel/malta/vmlinux-3.16.0-6-4kc-malta
+ -rw-r--r--  root/root   
/usr/lib/debian-installer/images/8/mipsel/sb1-bcm91250a/vmlinux-3.16.0-6-sb1-bcm91250a

Please let me know if you need further actions from my side.

For the sake of completeness/transparency, I didn't do any runtime tests
with that version yet, because of final D-I Buster Alpha 3 preparations.
I might try and give amd64/i386 netinst a shot, just to be sure.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature


Re: d-i upload for 8.11 (was: Re: Scheduling final Jessie point release, 8.11)

2018-06-18 Thread Cyril Brulebois
Adam D. Barratt  (2018-06-18):
> Yes, d-i and dini are the last things I'm expecting for the point
> release; everything else has been in place for at least a couple of
> dinstalls already.

Great.

> If the d-i upload could happen before the end of tomorrow, that should
> still give us plenty of time to get dini organised afterwards.

Almost dput debian-installer_20150422+deb8u5_source.changes but
remembered jessie needs binaries along. Will upload once I've made sure
I have a fresh jessie build schroot around.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature


Re: d-i upload for 8.11 (was: Re: Scheduling final Jessie point release, 8.11)

2018-06-18 Thread Adam D. Barratt
Hi,

On Mon, 2018-06-18 at 20:02 +0200, Cyril Brulebois wrote:
> Adam D. Barratt  (2018-06-18):
> > One thing I'd overlooked when scheduling binNMUs for d-i in
> > preparation for the point release is that there's been a kernel ABI
> > change (actually, two) in opu since the previous point release, so
> > we
> > will need a source d-i upload after all.
> > 
> > KiBi: Is that an easy change? Is it one that you have time to deal
> > with currently?
> 
> It should be/seems to be. I've just pushed the required change to git
> after a quick netboot build with (o)pu enabled; currently performing
> a full build on amd64 just to be sure.

Great.

> What would be an appropriate timetable from your point of view for
> the relevant upload? Relatedly: are all changes expected for this
> final point release in place already?

Yes, d-i and dini are the last things I'm expecting for the point
release; everything else has been in place for at least a couple of
dinstalls already.

If the d-i upload could happen before the end of tomorrow, that should
still give us plenty of time to get dini organised afterwards.

Cheers,

Adam



Re: d-i upload for 8.11 (was: Re: Scheduling final Jessie point release, 8.11)

2018-06-18 Thread Cyril Brulebois
Hi,

Adam D. Barratt  (2018-06-18):
> One thing I'd overlooked when scheduling binNMUs for d-i in
> preparation for the point release is that there's been a kernel ABI
> change (actually, two) in opu since the previous point release, so we
> will need a source d-i upload after all.
> 
> KiBi: Is that an easy change? Is it one that you have time to deal
> with currently?

It should be/seems to be. I've just pushed the required change to git
after a quick netboot build with (o)pu enabled; currently performing a
full build on amd64 just to be sure.

What would be an appropriate timetable from your point of view for the
relevant upload? Relatedly: are all changes expected for this final
point release in place already?


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature


d-i upload for 8.11 (was: Re: Scheduling final Jessie point release, 8.11)

2018-06-18 Thread Adam D. Barratt
[recipient list dropped to KiBi, -boot and -release]

On Tue, 2018-05-15 at 22:56 +0200, Cyril Brulebois wrote:
Anything June/July-ish should be good for me.
> 
> 
> debian-boot@, if there's anything needing a fix in jessie, please
> follow up to the list and myself.

One thing I'd overlooked when scheduling binNMUs for d-i in preparation
for the point release is that there's been a kernel ABI change
(actually, two) in opu since the previous point release, so we will
need a source d-i upload after all.

KiBi: Is that an easy change? Is it one that you have time to deal with
currently?

Cheers,

Adam



Re: Scheduling final Jessie point release, 8.11

2018-06-03 Thread Jonathan Wiltshire
On Mon, May 14, 2018 at 06:26:08PM +0100, Jonathan Wiltshire wrote:
>  - 23rd Jun
>  - (30th Jun I already know is impossible, for the sake of completeness)
>  - 7th July

Let's go for 23rd June. I'll send the premliminaries shortly.

Thanks,

-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51



Re: Scheduling final Jessie point release, 8.11

2018-05-20 Thread Joerg Jaspert
On 15037 March 1977, Jonathan Wiltshire wrote:

>  - 23rd Jun

Ok.

>  - 7th July

No.

-- 
bye, Joerg



Re: Scheduling final Jessie point release, 8.11

2018-05-18 Thread Laura Arjona Reina
Hello

El 14/05/18 a las 19:26, Jonathan Wiltshire escribió:
> Hi,
> 
> According to my records main security support for Jessie can end any time
> after 17th June. 
> 
> So to the security team: do you have a date in mind?
> 
> I also presume that LTS will take over the existing security suites as
> before. [1] lists the current delta between security and o-p-u-new which
> would ideally be as short as possible before the EOL date.
> 
> For everyone else, assuming it'll be soon after that date please
> indicate your availability from:
> 
>  - 23rd Jun
Publicity available

>  - (30th Jun I already know is impossible, for the sake of completeness)
Publicity we can't

>  - 7th July
> 
Publicity available.

> or adjacent Sundays.
> 
Sundays we are available, with some difficulty if we decide 1 July, but do-able.

Thanks
-- 
Laura Arjona Reina
https://wiki.debian.org/LauraArjona



Re: Scheduling final Jessie point release, 8.11

2018-05-15 Thread Cyril Brulebois
Hi,

Jonathan Wiltshire  (2018-05-14):
> According to my records main security support for Jessie can end any
> time after 17th June. 
> 
> So to the security team: do you have a date in mind?
> 
> I also presume that LTS will take over the existing security suites as
> before. [1] lists the current delta between security and o-p-u-new
> which would ideally be as short as possible before the EOL date.
> 
> For everyone else, assuming it'll be soon after that date please
> indicate your availability from:
> 
>  - 23rd Jun
>  - (30th Jun I already know is impossible, for the sake of completeness)
>  - 7th July

Anything June/July-ish should be good for me.


debian-boot@, if there's anything needing a fix in jessie, please follow
up to the list and myself.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature


Re: Scheduling final Jessie point release, 8.11

2018-05-14 Thread Steve McIntyre
On Mon, May 14, 2018 at 06:26:08PM +0100, Jonathan Wiltshire wrote:
>Hi,
>
>According to my records main security support for Jessie can end any time
>after 17th June. 
>
>So to the security team: do you have a date in mind?
>
>I also presume that LTS will take over the existing security suites as
>before. [1] lists the current delta between security and o-p-u-new which
>would ideally be as short as possible before the EOL date.
>
>For everyone else, assuming it'll be soon after that date please
>indicate your availability from:
>
> - 23rd Jun

Looks possible.

> - (30th Jun I already know is impossible, for the sake of completeness)

ACK :-)

> - 7th July

Looks possible.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"I can't ever sleep on planes ... call it irrational if you like, but I'm
 afraid I'll miss my stop" -- Vivek Das Mohapatra



Re: Scheduling final Jessie point release, 8.11

2018-05-14 Thread Moritz Mühlenhoff
On Mon, May 14, 2018 at 06:26:08PM +0100, Jonathan Wiltshire wrote:
> Hi,
> 
> According to my records main security support for Jessie can end any time
> after 17th June. 
> 
> So to the security team: do you have a date in mind?

The 17th :-)

Cheers,
Moritz