grub-installer_1.124_i386.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 21 Jun 2015 14:09:40 +0200 Source: grub-installer Binary: grub-installer Architecture: source i386 Version: 1.124 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team Changed-By: Christian

Processing of grub-installer_1.124_i386.changes

grub-installer_1.124_i386.changes uploaded successfully to localhost along with the files: grub-installer_1.124.dsc grub-installer_1.124.tar.xz grub-installer_1.124_i386.udeb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debia

Processing of grub-installer_1.124_i386.changes

grub-installer_1.124_i386.changes uploaded successfully to ftp-master.debian.org along with the files: grub-installer_1.124.dsc grub-installer_1.124.tar.xz grub-installer_1.124_i386.udeb Greetings, Your Debian queue daemon (running on host coccia.debian.org) -- To UNSUBSCRIBE, em

Processing of console-setup_1.129_i386.changes

console-setup-pc-ekbd_1.129_all.udeb doesn't exist console-setup-pc-ekmap_1.129_all.udeb doesn't exist console-setup-sun4-ekmap_1.129_all.udeb doesn't exist console-setup-sun5-ekmap_1.129_all.udeb doesn't exist console-setup-udeb_1.129_all.udeb doesn't exist console-setup_1.129_all.deb doesn't exis

Re: U-Boot, d-i and selecting the console device

On Sun, Jun 21, 2015 at 05:52:20PM +0200, Karsten Merker wrote: > Hello everybody, Hi, > AFAICS there is no way to determine the "active" console in > u-boot and set either the u-boot console variable or the > stdout-path property accordingly. Even if there was such a > mechanism, the question

Processed: hw-detect: install open-vm-tools in d-i

Processing control commands: > retitle 782287 hw-detect: install open-vm-tools in d-i Bug #782287 [hw-detect] hw-detect: install open-vm-tools in d-i Ignoring request to change the title of bug#782287 to the same title -- 782287: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782287 Debian Bug

Processed: hw-detect: install open-vm-tools in d-i

Processing control commands: > retitle 782287 hw-detect: install open-vm-tools in d-i Bug #782287 [hw-detect] (no subject) Set Bug title to 'hw-detect: install open-vm-tools in d-i'. -- 782287: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782287 Debian Bug Tracking System Contact ow...@bugs.

Bug#782287: hw-detect: install open-vm-tools in d-i

Control: retitle 782287 hw-detect: install open-vm-tools in d-i hi, with my open-vm-tools maintainer head on, I can NOT recommend to add a hard dependency on the open-vm-tools package to the installer - although I'd be very happy to have this functionality in d-i as having a running vmtoolsd is

Re: U-Boot, d-i and selecting the console device

Hi, Karsten Merker (2015-06-21): > On Sun, Jun 21, 2015 at 09:17:12AM -0700, Vagrant Cascadian wrote: > > > On 2015-06-21, Karsten Merker wrote: > > > If we don't pass a console variable to the kernel, d-i starts > > > on the console device defined by the platform's stdout-path > > > property, i

Bug#789475: udhcpc: valid rfc1123 hostname recognized as "bad"

On Sun, 21 Jun 2015, Geert Stappers wrote: > Control: tag -1 moreinfo > On Sun, Jun 21, 2015 at 02:14:17PM +0200, Bodo Eggert wrote: > > The valid hostname "52-54-0-12-34-56" is recognized as bad > > while it should be valid according to rfc1123 (Section 2.1). > > What programma and/or device did

Re: U-Boot, d-i and selecting the console device

On 2015-06-21, Karsten Merker wrote: > If we don't pass a console variable to the kernel, d-i starts > on the console device defined by the platform's stdout-path > property, i.e. usually on a serial console - again bad luck > for people having only a framebuffer console. > > If we set the console

Bug#789499: busybox: FTBFS with clang instead of gcc

Source: busybox Version: 1.22.0 Severity: minor Dear Maintainer, Hello, Using the rebuild infrastructure, your package fails to build with clang instead of gcc. The error message is like this: >>debianutils/lib.a(mktemp.o): In function `mktemp_main': >>/home/builder/workspace/busybox/busybox-1

Processed: Re: Bug#789475: udhcpc: valid rfc1123 hostname recognized as "bad"

Processing control commands: > tag -1 moreinfo Bug #789475 [busybox] udhcpc: valid rfc1123 hostname recognized as "bad" Ignoring request to alter tags of bug #789475 to the same tags previously set -- 789475: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789475 Debian Bug Tracking System Cont

Processed: Re: Bug#789475: udhcpc: valid rfc1123 hostname recognized as "bad"

Processing control commands: > tag -1 moreinfo Bug #789475 [busybox] udhcpc: valid rfc1123 hostname recognized as "bad" Added tag(s) moreinfo. -- 789475: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789475 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSC

Bug#789475: udhcpc: valid rfc1123 hostname recognized as "bad"

Control: tag -1 moreinfo On Sun, Jun 21, 2015 at 02:14:17PM +0200, Bodo Eggert wrote: > > The valid hostname "52-54-0-12-34-56" is recognized as bad > while it should be valid according to rfc1123 (Section 2.1). What programma and/or device did recognize "52-54-0-12-34-56" as bad? How was the e

Bug#789475: udhcpc: valid rfc1123 hostname recognized as "bad"

Package: busybox Version: 1:1.22.0-9+deb8u1 Severity: normal Tags: d-i Dear Maintainer, The valid hostname "52-54-0-12-34-56" is recognized as bad while it should be valid according to rfc1123 (Section 2.1). - Capture of the DHCP reply: be1.lrz.bootps > 192.168.7.107.bootpc: BOOTP/DHCP,

unsubscibe