Bug#749991: A tiresome subject for YEARS.

2019-02-25 Thread Adrian Almenar

This also happens with daily and weekly testing images:

At least, tried with netinst from here:

https://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/

And daily from here:

https://cdimage.debian.org/cdimage/daily-builds/daily/current/amd64/


PXE installation is also broken with the same issue as reported by Jan.


On Mon, 11 Feb 2019 15:50:25 +0100 Jan Huijsmans  wrote:

> On Mon, 11 Feb 2019 15:21:12 +0100
> Jan Huijsmans  wrote:
>
> > Sorry for the spam, PEBKAC, wront netboot.tar.gz. (wget renamed as the
> > old one from just after 4.19.0-2 kernel update was still there)
> >
> > Linking kernel + netboot update would be great though, or is there a
> > standard delay of a day or 2?
>
> I shouldn't do this mailing thing when I'm tired... :(
>
> PEBKAC on the PEBKAC report, issue still exists, the netboot.tar.gz
> just downloaded for amd64 (timestamp on server ftp.nl.debian.org
> 19-01-2019 18:03) contains kernel 4.19.0-1-amd64 (4.19.12 (2018-12-22))
> but the repo has 4.19.0-2-amd64 (4.19.16-1 (2019-01-17)). When I look
> at the date of the netboot.tar.gz upload, it should be able to have the
> new kernel, but it hasn't.
>
> The file I use is downloaded from:
> 
http://ftp.nl.debian.org/debian/dists/buster/main/installer-amd64/current/images/netboot/

>
> The source (I guess) is at:
> 
http://ftp.debian.org/debian/dists/buster/main/installer-amd64/current/images/netboot/

>
> and has timestamp 2019-01-18 20:43.
>
> ---
>
> Jan Huijsmans huysm...@koffie.nu
>
> ... cannot activate /dev/brain, no response from main coffee server
>
>
>
>



Bug#749991: A tiresome subject for YEARS.

2019-02-11 Thread Jan Huijsmans
On Mon, 11 Feb 2019 15:21:12 +0100
Jan Huijsmans  wrote:

> Sorry for the spam, PEBKAC, wront netboot.tar.gz. (wget renamed as the
> old one from just after 4.19.0-2 kernel update was still there)
> 
> Linking kernel + netboot update would be great though, or is there a
> standard delay of a day or 2?

I shouldn't do this mailing thing when I'm tired... :(

PEBKAC on the PEBKAC report, issue still exists, the netboot.tar.gz
just downloaded for amd64 (timestamp on server ftp.nl.debian.org
19-01-2019 18:03) contains kernel 4.19.0-1-amd64 (4.19.12 (2018-12-22))
but the repo has 4.19.0-2-amd64 (4.19.16-1 (2019-01-17)). When I look
at the date of the netboot.tar.gz upload, it should be able to have the
new kernel, but it hasn't.

The file I use is downloaded from:
http://ftp.nl.debian.org/debian/dists/buster/main/installer-amd64/current/images/netboot/

The source (I guess) is at:
http://ftp.debian.org/debian/dists/buster/main/installer-amd64/current/images/netboot/

and has timestamp 2019-01-18 20:43.

---

Jan Huijsmans  huysm...@koffie.nu

... cannot activate /dev/brain, no response from main coffee server



Bug#749991: A tiresome subject for YEARS.

2019-02-11 Thread Jan Huijsmans
On Mon, 11 Feb 2019 15:17:04 +0100
Jan Huijsmans  wrote:

> On Thu, 25 Oct 2018 15:09:31 +0200 Oliver Riesener
>  wrote:
> > On 10/25/18 11:06 AM, Oliver Riesener wrote:
> > > On 10/25/18 1:45 AM, Ben Hutchings wrote:
> > >> On Wed, 2018-10-24 at 18:44 +0200, John Paul Adrian Glaubitz
> > >> wrote:
> > >>> On 10/24/18 6:42 PM, Oliver Riesener wrote:
> >  No unetbootin, it’s the stock  stretch netboot   installation.
> >  initrd kernel from actual
> >  Debian9.5/…./amd64/netboot/netboot.tar.gz didn’t find kernel
> >  modules anymore. The old one before too. It’s a point release
> >  problem. Older versions of modules (.udeb ?) seems
> >  to be from debian repo.
> > >>> Are you sure you used a matching kernel image and initrd? Both
> > >>> have to match
> > >>> their version otherwise it won't work.
> > >> But when you use netboot the udebs in the archive *also* have to
> > >> match. And they don't after a point release.
> > >>
> > >> Ben.
> > > Yes, that's the point. Packages are updated, today it runs perfect
> > > again.
> > Oh, i am sorry, i got the issue yesterday with jessie 8.0 point
> > release, becource
> > my (old) bootp entry points to 8.0/pxelinux.0.
> > 
> > Upgraded to jessie/current/netboot image, works also fine.
> 
> The problem exists again with the buster netboot.tar.gz from the
> server (just downloaded). The available netboot.tar.gz still contains
> the 4.19.0-1 kernel, while the 4.19.0-2 is the only one available in
> the repo.
> 
> Would it be possible to update the netboot.tar.gz for the arch the
> moment the updated kernel is being added in the repo. (or leave the
> old kernel with modules in the repo until the netboot.tar.gz is
> updated)
> 
> I expect the generation of the tars is automated, so it would be nice
> if the kernel and tar update can be linked.

Sorry for the spam, PEBKAC, wront netboot.tar.gz. (wget renamed as the
old one from just after 4.19.0-2 kernel update was still there)

Linking kernel + netboot update would be great though, or is there a
standard delay of a day or 2?

---

Jan Huijsmans  huysm...@koffie.nu

... cannot activate /dev/brain, no response from main coffee server



Bug#749991: A tiresome subject for YEARS.

2019-02-11 Thread Jan Huijsmans
On Thu, 25 Oct 2018 15:09:31 +0200 Oliver Riesener
 wrote:
> On 10/25/18 11:06 AM, Oliver Riesener wrote:
> > On 10/25/18 1:45 AM, Ben Hutchings wrote:
> >> On Wed, 2018-10-24 at 18:44 +0200, John Paul Adrian Glaubitz wrote:
> >>> On 10/24/18 6:42 PM, Oliver Riesener wrote:
>  No unetbootin, it’s the stock  stretch netboot   installation.
>  initrd kernel from actual
>  Debian9.5/…./amd64/netboot/netboot.tar.gz didn’t find kernel
>  modules anymore. The old one before too. It’s a point release
>  problem. Older versions of modules (.udeb ?) seems
>  to be from debian repo.
> >>> Are you sure you used a matching kernel image and initrd? Both
> >>> have to match
> >>> their version otherwise it won't work.
> >> But when you use netboot the udebs in the archive *also* have to
> >> match. And they don't after a point release.
> >>
> >> Ben.
> > Yes, that's the point. Packages are updated, today it runs perfect
> > again.
> Oh, i am sorry, i got the issue yesterday with jessie 8.0 point
> release, becource
> my (old) bootp entry points to 8.0/pxelinux.0.
> 
> Upgraded to jessie/current/netboot image, works also fine.

The problem exists again with the buster netboot.tar.gz from the server
(just downloaded). The available netboot.tar.gz still contains the
4.19.0-1 kernel, while the 4.19.0-2 is the only one available in the
repo.

Would it be possible to update the netboot.tar.gz for the arch the
moment the updated kernel is being added in the repo. (or leave the old
kernel with modules in the repo until the netboot.tar.gz is updated)

I expect the generation of the tars is automated, so it would be nice
if the kernel and tar update can be linked.

---

Jan Huijsmans  huysm...@koffie.nu

... cannot activate /dev/brain, no response from main coffee server



Bug#749991: A tiresome subject for YEARS.

2018-10-25 Thread Oliver Riesener



On 10/25/18 11:06 AM, Oliver Riesener wrote:


On 10/25/18 1:45 AM, Ben Hutchings wrote:

On Wed, 2018-10-24 at 18:44 +0200, John Paul Adrian Glaubitz wrote:

On 10/24/18 6:42 PM, Oliver Riesener wrote:

No unetbootin, it’s the stock  stretch netboot   installation.
initrd kernel from actual Debian9.5/…./amd64/netboot/netboot.tar.gz
didn’t find kernel modules anymore. The old one before too.
It’s a point release problem. Older versions of modules (.udeb ?) 
seems

to be from debian repo.
Are you sure you used a matching kernel image and initrd? Both have 
to match

their version otherwise it won't work.

But when you use netboot the udebs in the archive *also* have to match.
And they don't after a point release.

Ben.

Yes, that's the point. Packages are updated, today it runs perfect again.


Oh, i am sorry, i got the issue yesterday with jessie 8.0 point release, 
becource

my (old) bootp entry points to 8.0/pxelinux.0.

Upgraded to jessie/current/netboot image, works also fine.

Oliver

I'm creating debian-installer images myself on a regular basis and 
from my
current knowledge and testing, it's very unlikely that there is a 
bug in

the kernel and initrd matching.




Bug#749991: A tiresome subject for YEARS.

2018-10-25 Thread Oliver Riesener



On 10/25/18 1:45 AM, Ben Hutchings wrote:

On Wed, 2018-10-24 at 18:44 +0200, John Paul Adrian Glaubitz wrote:

On 10/24/18 6:42 PM, Oliver Riesener wrote:

No unetbootin, it’s the stock  stretch netboot   installation.
initrd kernel from actual Debian9.5/…./amd64/netboot/netboot.tar.gz
didn’t find kernel modules anymore. The old one before too.
It’s a point release problem. Older versions of modules (.udeb ?) seems
to be from debian repo.

Are you sure you used a matching kernel image and initrd? Both have to match
their version otherwise it won't work.

But when you use netboot the udebs in the archive *also* have to match.
And they don't after a point release.

Ben.

Yes, that's the point. Packages are updated, today it runs perfect again.

I'm creating debian-installer images myself on a regular basis and from my
current knowledge and testing, it's very unlikely that there is a bug in
the kernel and initrd matching.




Bug#749991: A tiresome subject for YEARS.

2018-10-24 Thread Ben Hutchings
On Wed, 2018-10-24 at 18:44 +0200, John Paul Adrian Glaubitz wrote:
> On 10/24/18 6:42 PM, Oliver Riesener wrote:
> > No unetbootin, it’s the stock  stretch netboot   installation.
> > initrd kernel from actual Debian9.5/…./amd64/netboot/netboot.tar.gz
> > didn’t find kernel modules anymore. The old one before too. 
> > It’s a point release problem. Older versions of modules (.udeb ?) seems
> > to be from debian repo. 
> Are you sure you used a matching kernel image and initrd? Both have to match
> their version otherwise it won't work.

But when you use netboot the udebs in the archive *also* have to match.
And they don't after a point release.

Ben.

> I'm creating debian-installer images myself on a regular basis and from my
> current knowledge and testing, it's very unlikely that there is a bug in
> the kernel and initrd matching.

-- 
Ben Hutchings
The obvious mathematical breakthrough [to break modern encryption]
would be development of an easy way to factor large prime numbers.
   - Bill Gates




signature.asc
Description: This is a digitally signed message part


Bug#749991: A tiresome subject for YEARS.

2018-10-24 Thread John Paul Adrian Glaubitz
On 10/24/18 6:42 PM, Oliver Riesener wrote:
> No unetbootin, it’s the stock  stretch netboot   installation.
> initrd kernel from actual Debian9.5/…./amd64/netboot/netboot.tar.gz
> didn’t find kernel modules anymore. The old one before too. 
> It’s a point release problem. Older versions of modules (.udeb ?) seems
> to be from debian repo. 
Are you sure you used a matching kernel image and initrd? Both have to match
their version otherwise it won't work.

I'm creating debian-installer images myself on a regular basis and from my
current knowledge and testing, it's very unlikely that there is a bug in
the kernel and initrd matching.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913



Bug#749991: A tiresome subject for YEARS.

2018-10-24 Thread Oliver Riesener
No unetbootin, it’s the stock  stretch netboot   installation.
initrd kernel from actual Debian9.5/…./amd64/netboot/netboot.tar.gz
didn’t find kernel modules anymore. The old one before too. 
It’s a point release problem. Older versions of modules (.udeb ?) seems
to be from debian repo. 


> Am 24.10.2018 um 17:26 schrieb John Paul Adrian Glaubitz 
> :
> 
> On 10/24/18 5:15 PM, Oliver Riesener wrote:
>> Debian Stretch 9.5 (stable) kernel 3.16.0-4
>> * no packages matching kernel failed.
> 
> This error usually comes up with installation media created using
> unetbootin. Have you, by any chance, used unetbootin to create your
> installation medium?
> 
> Adrian
> 
> -- 
> .''`.  John Paul Adrian Glaubitz
> : :' :  Debian Developer - glaub...@debian.org
> `. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
>  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
> 



Bug#749991: A tiresome subject for YEARS.

2018-10-24 Thread John Paul Adrian Glaubitz
On 10/24/18 5:15 PM, Oliver Riesener wrote:
> Debian Stretch 9.5 (stable) kernel 3.16.0-4
> * no packages matching kernel failed.

This error usually comes up with installation media created using
unetbootin. Have you, by any chance, used unetbootin to create your
installation medium?

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913



Bug#749991: A tiresome subject for YEARS.

2018-10-24 Thread Oliver Riesener

A tiresome subject for YEARS.

It has happened again today.


Debian Stretch 9.5 (stable) kernel 3.16.0-4
* no packages matching kernel failed.