Bug#851790: installation-reports: DNS not working

2017-01-18 Thread Cyril Brulebois
Cyril Brulebois (2017-01-19): > Summing up things from IRC: > - in an uptodate sid chroot (both development version and minimal one >with daily-build script): no DNS issues with the generated mini.iso >(amd64, tested within stable's kvm on amd64). My image was also >tested successfull

Bug#851790: installation-reports: DNS not working

2017-01-18 Thread Cyril Brulebois
Cyril Brulebois (2017-01-19): > You can try downgrading the kernel, but I'd usually look at glibc first > for DNS related issues. Summing up things from IRC: - in an uptodate sid chroot (both development version and minimal one with daily-build script): no DNS issues with the generated mini.i

Bug#851539: Stretch RC1 netinst installer prompts for additional CDs

2017-01-18 Thread Josh Triplett
On Wed, Jan 18, 2017 at 02:53:29PM +, Steve McIntyre wrote: > On Tue, Jan 17, 2017 at 10:24:31AM +0100, Julien Cristau wrote: > >On 01/16/2017 07:56 PM, Josh Triplett wrote: > >> > >> How does it help for the firmware-included images? > >> > >It makes it possible to use them to install from C

Bug#851790: installation-reports: DNS not working

2017-01-18 Thread Cyril Brulebois
Steve McIntyre (2017-01-18): > For the sake of completeness, I can confirm that the same problem > shows up when running on a different network too. I also see this > using the oldest amd64 daily I can grab (from 2017-01-17) which has > the 4.9 kernel too. > > I'll see if I can debug this, but I'

Bug#851790: installation-reports: DNS not working

2017-01-18 Thread Steve McIntyre
On Wed, Jan 18, 2017 at 06:43:33PM +, Wookey wrote: >Package: installation-reports >Severity: grave >Tags: d-i >Justification: renders package unusable > >Dear Maintainer, > >The current installer, with the new 4.9 kernel, is unable to resolve >domains, so is quite seriously broken. hosts, not

Bug#851790: installation-reports: DNS not working

2017-01-18 Thread Wookey
Package: installation-reports Severity: grave Tags: d-i Justification: renders package unusable Dear Maintainer, The current installer, with the new 4.9 kernel, is unable to resolve domains, so is quite seriously broken. This was noted during install on an arm64 gigabyte MP30-AR1 desktop/server,

Bug#772901: marked as done (os-prober wrong output with grep 2.21 or later)

2017-01-18 Thread Debian Bug Tracking System
Your message dated Wed, 18 Jan 2017 16:38:24 + with message-id <20170118163824.ga5...@riva.ucam.org> and subject line Re: Bug#772901: os-prober wrong output with grep 2.21 or later has caused the Debian Bug report #772901, regarding os-prober wrong output with grep 2.21 or later to be marked as

Processed: forcibly merging 648208 794849

2017-01-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 648208 794849 Bug #648208 [os-prober] os-prober: blockdev --setro affects running kvm instances Bug #788062 [os-prober] os-prober corrupts LVs/partitions while being mounted inside a VM Bug #806273 [os-prober] os-prober: remove or dis

Bug#851429: installation-reports: mounting CD fails on qemu-system-aarch64

2017-01-18 Thread Steve McIntyre
On Sun, Jan 15, 2017 at 03:05:11PM +0100, Adam Borowski wrote: >On Sun, Jan 15, 2017 at 01:12:53AM +, Steve McIntyre wrote: >> >> I think the problem is with your setup. I've just booted that exact >> netinst image happily using >> >> qemu-system-aarch64 -m 4G -cpu cortex-a57 -M virt -smp 8 -

Bug#851539: Stretch RC1 netinst installer prompts for additional CDs

2017-01-18 Thread Steve McIntyre
On Tue, Jan 17, 2017 at 10:24:31AM +0100, Julien Cristau wrote: >On 01/16/2017 07:56 PM, Josh Triplett wrote: >> >> How does it help for the firmware-included images? >> >It makes it possible to use them to install from CD rather than from the >network. Exactly. When we first came up with the i

Processed: take ownership of my cam.ac.uk-submitted bugs

2017-01-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > submitter 716975 matth...@chiark.greenend.org.uk Bug #716975 [twittering-mode] Should deal with lack-of-curl gracefully Changed Bug submitter to 'matth...@chiark.greenend.org.uk' from 'Matthew Vernon '. > submitter 740347 matth...@chiark.greenend

flash-kernel_3.75_armel.changes ACCEPTED into unstable

2017-01-18 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 18 Jan 2017 07:00:43 +0100 Source: flash-kernel Binary: flash-kernel flash-kernel-installer Architecture: source armel Version: 3.75 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team Ch

Processing of flash-kernel_3.75_armel.changes

2017-01-18 Thread Debian FTP Masters
flash-kernel_3.75_armel.changes uploaded successfully to localhost along with the files: flash-kernel_3.75.dsc flash-kernel_3.75.tar.xz flash-kernel-installer_3.75_armel.udeb flash-kernel_3.75_armel.buildinfo flash-kernel_3.75_armel.deb Greetings, Your Debian queue daemon (runni

Bug#851740: Additional infos to point 3 and maybe 2 of my report

2017-01-18 Thread bkk
Hi, if I add break=top as kernel parameter, I come instantly to the busybox prompt. If I add break=modules it takes 90 seconds. I think it has something to do with the networkdriver igb. After a break=top, I use modeprobe igb to load it. Then I use ifconfig -a to show the interfaces: eth0 eth1 an

openchrome and "Modules" section [was: Re: [Openchrome-users] How to say No!! in a polite though ridiculous way]

2017-01-18 Thread Tzafrir Cohen
On Wed, Jan 18, 2017 at 10:26:11AM +0100, Tamás Gajdos wrote: > Hi, > > I don't know if this is a packaging problem or not. But I had the same > issue with Ubuntu 17.04 around 2017.01.10. > > I solved the problem by adding some extra modules to the xorg.conf. > > Section "Module" > Load"

Bug#851740: bug report installing 9.0 RC1

2017-01-18 Thread bkk
Package: installation-reports Boot method: Installer bootet via USB Image version: http://cdimage.debian.org/cdimage/stretch_di_rc1/amd64/iso-cd/debian-stretch-DI-rc1-amd64-netinst.iso Date: 2017-01-18 09:45 Machine: SUPERMICRO X10SBA-L-O-P Processor: Intel Celeron J1900 (cpu family:6, model: 55

Bug#800367: [Openchrome-users] How to say No!! in a polite though ridiculous way

2017-01-18 Thread Tamás Gajdos
Hi, I don't know if this is a packaging problem or not. But I had the same issue with Ubuntu 17.04 around 2017.01.10. I solved the problem by adding some extra modules to the xorg.conf. Section "Module" Load"vgahw" Load"shadowfb" Load"shadow" Load"exa" Load

Re: [Openchrome-users] How to say No!! in a polite though ridiculous way

2017-01-18 Thread Tzafrir Cohen
On Sun, Jan 15, 2017 at 08:51:06PM +0100, Tzafrir Cohen wrote: > On Fri, Jan 13, 2017 at 11:47:40PM +0100, Kevin Brace wrote: > > Hi Andreas, > > > > Throw this in your xorg.conf > > > > > > Section "Module" > > Load"vgahw" > > EndSection > > _