On Sat, 03 Oct 2015, Mattia Rizzolo wrote:
> > What kind of mails are we referring to?
>
> We are talking about very short mails, actually one-liners like
>
> 2015-10-03 11:43 https://reproducible.debian.net/unstable/amd64/derby changed
> from FTBFS -> unreproducible
>
> (this one will be sent
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
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/
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,
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
5 matches
Mail list logo