base-installer_1.162_i386.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 19 Feb 2016 07:01:14 +0100 Source: base-installer Binary: base-installer bootstrap-base Architecture: source all i386 Version: 1.162 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team

Processing of base-installer_1.162_i386.changes

base-installer_1.162_i386.changes uploaded successfully to localhost along with the files: base-installer_1.162.dsc base-installer_1.162.tar.xz base-installer_1.162_all.udeb bootstrap-base_1.162_i386.udeb Greetings, Your Debian queue daemon (running on host franck.debian.org)

Processing of base-installer_1.162_i386.changes

base-installer_1.162_i386.changes uploaded successfully to ftp-master.debian.org along with the files: base-installer_1.162.dsc base-installer_1.162.tar.xz base-installer_1.162_all.udeb bootstrap-base_1.162_i386.udeb Greetings, Your Debian queue daemon (running on host

Processed: unblock 814341 with 806926, unblock 806926 with 814341

Processing commands for cont...@bugs.debian.org: > unblock 814341 with 806926 Bug #814341 [mtd-utils] let flashcp fail on nand and document it's only suitable for nor 814341 was blocked by: 806926 814341 was blocking: 806926 Removed blocking bug(s) of 814341: 806926 > unblock 806926 with 814341

Bug#806926: Bug#766400: installation-reports: [armhf] Netgear ReadyNAS104 report

* Uwe Kleine-König [2016-02-18 20:47]: > Do we need "Bootloader-Sets-Incorrect-Root: yes"? I modified the u-boot > env to pass the right root= and rootflags= parameter. Right, that's requrired, too. > Gijs uses > > U-Boot-Initrd-Address: 0x0 > > on a rn102,

Bug#704162: Wrong sum for GTK installer initrd.gz inside netboot.tar.gz

* Cyril Brulebois [2014-03-03 01:40]: > > There must be a small packaging bug somewhere… > > The timestamp issue was indeed a nice clue. gzip has -n to avoid storing > such information, improving build reproducibility: > I shall note pigz needs has -n and -T: ... > Tagging with

Bug#806926: Bug#766400: installation-reports: [armhf] Netgear ReadyNAS104 report

Hi Martin, On 02/18/2016 08:36 PM, Martin Michlmayr wrote: > Uwe, does that look ok? Yes, the rn104 entry is what I'm using, I'm just missing the Kernel-Flavors line, which looks ok, too. Do we need "Bootloader-Sets-Incorrect-Root: yes"? I modified the u-boot env to pass the right root= and

Bug#806926: Bug#766400: installation-reports: [armhf] Netgear ReadyNAS104 report

Uwe, does that look ok? diff --git a/README b/README index 1774af6..d354c87 100644 --- a/README +++ b/README @@ -46,6 +46,8 @@ The following systems are supported: - Marvell OpenRD-Client - Marvell OpenRD-Ultimate - Neo FreeRunner (GTA02) + - NETGEAR ReadyNAS 102 + - NETGEAR ReadyNAS 104

Bug#760993: console-setup: CHARMAP no longer set properly

On Thu, Feb 18, 2016 at 06:16:26PM +0200, Anton Zinoviev wrote: > On Tue, Sep 09, 2014 at 08:18:01PM +0200, Kurt Roeckx wrote: > > Package: console-setup > > Version: 1.111 > > Severity: important > > > > In /etc/default/console-setup I have: > > CHARMAP="ISO-8859-1" > > > > However, my console

Bug#673644: Message at end of successful install talks about floppies (should be updated)

On Sun, Mar 02, 2014 at 04:26:29PM +0100, Christian PERRIER wrote: >Quoting Cyril Brulebois (k...@debian.org): > >> debian-cd@/Steve, any opinion on this? I don't think we're going to drop >> support for CD, DVD, or USB flash disk any time soon. Not spending our >> time trying to make stuff fit on

Bug#707844: marked as done (di-utils: No error message in case of wrong architecture)

Your message dated Thu, 18 Feb 2016 09:32:22 -0800 with message-id <20160218173222.ga23...@jirafa.cyrius.com> and subject line Re: Bug#707844: di-utils: No error message in case of wrong architecture has caused the Debian Bug report #707844, regarding di-utils: No error message in case of wrong

Bug#760993: console-setup: CHARMAP no longer set properly

On Tue, Sep 09, 2014 at 08:18:01PM +0200, Kurt Roeckx wrote: > Package: console-setup > Version: 1.111 > Severity: important > > In /etc/default/console-setup I have: > CHARMAP="ISO-8859-1" > > However, my console acts like it's in UTF-8 mode. > > If I restart the console-setup service it does

Re: d-i daily 2/18 is missing for armel only

I cannot find today(2/18)'s armel d-i daily image [0], while other >> arch is correctly downloadable [1][2]. >> If there's build error, there should be build log to check, but >> unfortunately there's no 2/18's folder. So I'm asking what happened. > > Looking at /home

Re: d-i daily 2/18 is missing for armel only

On Thu, Feb 18, 2016 at 6:44 PM, Roger Shimizu wrote: > Dear D-I Maintainer, > > I cannot find today(2/18)'s armel d-i daily image [0], while other > arch is correctly downloadable [1][2]. > If there's build error, there should be build log to check, but > unfortunately

Re: Bug report - ext4: Unknown symbol __getblk_gfp (err 0)

On Thu, 2016-02-18 at 13:18 +0100, Miroslav Svoboda wrote: > [...] > Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01) x86_64 GNU/Linux > > [...] > Any idea what is the problem? Your local vmlinux and initrd binaries are out of sync with the kernel modules in the mirror network, due

Re: Bug report - ext4: Unknown symbol __getblk_gfp (err 0)

On Thu, 2016-02-18 at 13:18 +0100, Miroslav Svoboda wrote: > Dear Debian team,  > > I have problem with debian Jessie PXE installation with preseed. I'm > trying to install Debian Jessie on amd64 server. The installation goes > fine until partitionning and fails right after when trying to mount

Bug report - ext4: Unknown symbol __getblk_gfp (err 0)

Dear Debian team, I have problem with debian Jessie PXE installation with preseed. I'm trying to install Debian Jessie on amd64 server. The installation goes fine until partitionning and fails right after when trying to mount the newly created partitions with ext4 filesystem. Dmesg give us an

Re: d-i daily 2/18 is missing for armel only

der. So I'm asking what happened. Looking at /home/d-i/di/logs/di-autobuild_daily-armel-20160218- on abel (the porterbox currently used for armel d-i daily builds), it seems due to a transient network error at the beginning of the build, hich triggered an early abort (and no logs are uploaded in

Bug#707844: di-utils: No error message in case of wrong architecture

> Can someone confirm? I just tried. It now gives a good error message. -- Salvo Tomaselli "Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione ed intelletto intendesse che noi ne facessimo a meno." -- Galileo Galilei

d-i daily 2/18 is missing for armel only

Dear D-I Maintainer, I cannot find today(2/18)'s armel d-i daily image [0], while other arch is correctly downloadable [1][2]. If there's build error, there should be build log to check, but unfortunately there's no 2/18's folder. So I'm asking what happened. [0]