Your message dated Tue, 06 Oct 2015 01:50:02 +0200
with message-id <56130caa.9080...@debian.org>
and subject line Re: amd64: netboot 2015-04-22, 2015-06-04, 2015-08-13 fail,
wheezy succeeds
has caused the Debian Bug report #797095,
regarding amd64: netboot 2015-04-22, 2015-06-04, 2015-08-13 fail,
Hi,
Cyril Brulebois wrote:
> Depending on particular changes I'd like to check (e.g. grub-installer),
> I indeed end up building an image with debian-cd.
I think this is what I must do. It just feels a bit excessive for
recreational testing, or even within a Jenkins job.
Jenkins also tests PXE
Hi,
Steven Chamberlain (2015-10-05):
> Does anyone test d-i for stable-proposed-updates? If so, how?
> It seems rather difficult currently.
Around p-u time, when d-i's been built (uploaded or binNMUd) against p-u.
> You could build the d-i jessie branch from Git, or get release-candidate
> sta
Hi!
Does anyone test d-i for stable-proposed-updates? If so, how?
It seems rather difficult currently.
You could build the d-i jessie branch from Git, or get release-candidate
stable-p-u images from
http://ftp.debian.org/debian/dists/jessie-proposed-updates/main/installer-amd64/current/images/
Steven Chamberlain wrote:
> Next, it would be nice to test that the base system in stable-p-u is
> still installable. d-i's debootstrap can't seem to do this as it
> doesn't recognise "-proposed-updates" suites, so would need a patch to
> add those. I tried that but ran into some other issue next
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 04 Oct 2015 13:56:34 +0100
Source: flash-kernel
Binary: flash-kernel flash-kernel-installer
Architecture: armel source
Version: 3.46~bpo8+1
Distribution: jessie-backports
Urgency: medium
Maintainer: Debian Install
6 matches
Mail list logo
