Re: Bug#906016: transition: gjs built with mozjs60

2019-03-04 Thread Cyril Brulebois
in the subject returned this small list of bug reports: #575682, #296930, #608407, #694771, #851790, #859889, #923524 (which you know about…). Anyway, just to confirm: if one hacks an archive to get gnome-core out of the amd64's Packages file, tasksel (run from a chroot rather than from d-i, c

Re: Bug#906016: transition: gjs built with mozjs60

2019-02-08 Thread Cyril Brulebois
default desktop: https://salsa.debian.org/installer-team/tasksel/blob/master/default_desktop I'm not sure how to hide a particular entry on a particular arch; I'm not a tasksel expert and won't be one in the next 5 minutes. But it seems to me the immediate concern was abou

Re: Bug#858943: unblock: systemd/232-22

2017-04-09 Thread Cyril Brulebois
Philipp Kern (2017-04-09): > On 04/01/2017 01:45 AM, Cyril Brulebois wrote: > > Adding debian-s390@lists.debian.org to the loop to make sure they're > > aware of this. Can't really judge whether this could be annoying in d-i, > > it seems to me that's just fixi

Re: Bug#858943: unblock: systemd/232-22

2017-03-31 Thread Cyril Brulebois
Hi, Michael Biebl (2017-03-28): > since 232-19, a couple of fixes accumulated which we'd like to see enter > testing/stretch > > As this potentially affects the installer, I've CC debian-boot aka KiBi. > > A complete debdiff is attached. > > The changelog + annotations follows. Sorry if it's a

Fwd: Re: Bug#571136: please remove useless devices from devices.tar.gz

2016-01-09 Thread Cyril Brulebois
Hi ports people, I'm not exactly sure what happened with debian-ports@ (I think there were some planned changes but I don't remember the outcome), so I'm explicitly sending this to bsd/hurd lists since I suspect the linux ports are less likely to be affected by this. We have a bug report with a p

Re: Bug#808041: s390-zfcp: Install Debian on FC-attached SCSI devices on s390

2015-12-15 Thread Cyril Brulebois
Hi! Hendrik Brueckner (2015-12-15): > Package: d-i.debian.org > Severity: normal > Tags: d-i > > Dear Debian Installer Team and Maintainers, > > I would like to contribute a new package for the Debian Installer > to configure FCP devices and install Debian on SCSI devices which > are available

Re: Bits from the Release Team (Jessie freeze info)

2013-10-26 Thread Cyril Brulebois
Johannes Schauer (2013-10-26): > (I was not able to find the debian-ports list on lists.debian.org (so I > subscribed via email) did I just miss it?) Dead list: http://lists.debian.org/debian-ports/ AFAICT it's now an alias for all debian-$port lists. Mraw, KiBi. signature.asc Description: Di

Preparation for d-i beta 1

2012-06-24 Thread Cyril Brulebois
Hi folks, as you may know, nobody else stepped up, so I'm volunteering again to try and get a new debian-installer release out, codenamed « beta 1 ». I have looked at the packages mentioned on the udeb testing summary page[1] and I have “urgented” many of them, so that they reach testing sooner t

Re: Bug#673590: libxml-libxml-perl: FTBFS on s390x: Failed 1/51 test programs. 0/2419 subtests failed.

2012-05-20 Thread Cyril Brulebois
Hi Niko, and thanks for the quick follow-up. Niko Tyni (20/05/2012): > See the attached patch, which just makes 'len' an int and removes the > problematic pointer cast. I wonder if the STRLEN cast on becomes an > issue, though. Is it possible that an int doesn't fit into a size_t > variable some

Bug#673590: libxml-libxml-perl: FTBFS on s390x: Failed 1/51 test programs. 0/2419 subtests failed.

2012-05-19 Thread Cyril Brulebois
Source: libxml-libxml-perl Version: 1.98+dfsg-1 Severity: important Hi, your package FTBFS on s390x, in the test suite: | Test Summary Report | --- | t/12html.t(Wstat: 256 Tests: 41 Failed: 0) | Non-zero exit status: 1 | Parse errors: Bad plan. You pla

Graphical installer for s390(x)?!

2012-05-19 Thread Cyril Brulebois
Hello, (what a catchy subject!) looking at uninstallable packages, diffing s390 and s390x, this one popped up: xserver-xorg-input-evdev-udeb because it's missing that one: xserver-xorg-core-udeb Basically, the former is arch: any, while the latter has an explicit arch list. ISTR graphics +