Bug#681227: Can anyone reproduce #681227: installation-reports: grub-install tries to install to a nonsense string?!

2013-01-11 Thread Christian PERRIER
Quoting Steven Chamberlain (ste...@pyro.eu.org): > Patch for this actually just a diff limited to ./grub-installer from: > > $ git revert a070f516 99389d59 926cee22 Agreed from my side. I guess we now just need Cyril's ACK to apply in git and probably buildunless something else is needed in

Bug#697890: marked as done (installation-reports: iwconfig not in /sbin)

2013-01-11 Thread Debian Bug Tracking System
Your message dated Sat, 12 Jan 2013 08:10:41 +0100 with message-id <20130112071041.gl5...@mykerinos.kheops.frmug.org> and subject line Re: Bug#697890: installation-reports: iwconfig not in /sbin has caused the Debian Bug report #697890, regarding installation-reports: iwconfig not in /sbin to be ma

Bug#697953: marked as done (installation report (successful))

2013-01-11 Thread Debian Bug Tracking System
Your message dated Sat, 12 Jan 2013 08:12:06 +0100 with message-id <20130112071206.gm5...@mykerinos.kheops.frmug.org> and subject line Re: Bug#697953: installation report (successful) has caused the Debian Bug report #697953, regarding installation report (successful) to be marked as done. This me

Debian installer build: failed or old builds

2013-01-11 Thread Daily build aggregator
Debian installer build overview --- Failed or old builds: * OLD BUILD:mipsel Jan 10 00:10 buildd@rem build_cobalt_netboot-2.6_serial http://d-i.debian.org/daily-images/mipsel/daily/build_cobalt_netboot-2.6_serial.log * OLD BUILD:mipsel Jan 10

Re: Bug#697890: installation-reports: iwconfig not in /sbin

2013-01-11 Thread Brian Potkin
On Fri 11 Jan 2013 at 15:36:27 +0100, jswmb01x wrote: > Then I started the xfce "network manager" (parameters -> network > connections), filled in required information and wanted to check the > status with iwconfig. > > Could only find this : > > root? > root? find / -xdev -iname *iwconfig* > /

Bug#697890: installation-reports: iwconfig not in /sbin

2013-01-11 Thread Ben Hutchings
On Fri, 2013-01-11 at 15:36 +0100, jswmb01x wrote: > Yes, indeed ! > > It's about wheezy-xfce (testing - build cd binay-1 20121217-05:10). > > During installation I got a ~"missing rt28xx" message and was asked to > provide a "floppy" with the firmware. Answered "no" and proceeded with > insta

Bug#697953: installation report (successful)

2013-01-11 Thread harven
Package: installation-reports Boot method: cdrom Image version: http://cdimage.debian.org/cdimage/wheezy_di_beta4/amd64/iso-cd/debian-wheezy-DI-b4-amd64-netinst.iso Date: december, the 28th, 2012 Machine: DELL Latitude E6400 Processor: Intel(R) Core(TM)2 Duo CPU P8600@ Memory: Partitions: roo

Bug#697890: installation-reports: iwconfig not in /sbin

2013-01-11 Thread jswmb01x
Yes, indeed ! It's about wheezy-xfce (testing - build cd binay-1 20121217-05:10). During installation I got a ~"missing rt28xx" message and was asked to provide a "floppy" with the firmware. Answered "no" and proceeded with installation. As such the installation is OK, but it looks there are m

Processed: Re: Bug#681227: Can anyone reproduce #681227: installation-reports: grub-install tries to install to a nonsense string?!

2013-01-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 681227 + patch Bug #681227 [grub-installer] does not validate free-form input Added tag(s) patch. > block 651720 by 681227 Bug #651720 {Done: Wouter Verhelst } [src:grub-installer] new ZFS install on / fails if /boot isn't ZFS 651720 was not

Re: Bug#681227: Can anyone reproduce #681227: installation-reports: grub-install tries to install to a nonsense string?!

2013-01-11 Thread Steven Chamberlain
tags 681227 + patch block 651720 by 681227 # kFreeBSD bugfix couldn't enter wheezy yet due to regressions thanks Hi, On 07/01/13 19:56, Wouter Verhelst wrote: >> What to do with the workaround added by Wouter in grub-installer/1.84? > > The workaround tried to eliminate the possibility of invali

Re: finish-install: save entropy for target system

2013-01-11 Thread Christian PERRIER
Quoting Colin Watson (cjwat...@debian.org): > I think we should include this change in wheezy. +1...unless Cyril really wants us to be feature-frozen during the RC stage, which would be understandable. signature.asc Description: Digital signature

finish-install: save entropy for target system

2013-01-11 Thread Colin Watson
I've just committed this change to finish-install.git, inspired by comments in https://factorable.net/weakkeys12.extended.pdf. (At least for systems using sysvinit, this is the only change that I can readily see needs to be made to Debian based on that paper.) I can't immediately point to a vulne

Re: Last 2 commits in cdrom-checker

2013-01-11 Thread Christian PERRIER
Quoting Colin Watson (cjwat...@debian.org): > > I suspect e8ae8876bcea30cc45bcba25ed1e9ea2a317aff0 to be safe and a > > good idea.I have however no idea for > > 1ec13c5a378076c10988237972d4df0f1eefafd3, given my own C-fu..:-) > > It made the jenkins build stable and was non-intrusive enough t

Bug#688336: os-prober 1.56 and btrfs

2013-01-11 Thread Gene Czarcinski
This was found on Fedora 18. Both os-prober and linux-boot-prober do not support root, boot, or root+boot on a btrfs subvolume. The attached patch corrects that. It supplies information such that grub2, with an additional small patch, will not handle btrfs in 30_os-prober. I have attached

Processed: Re: Bug#697868: debian-cd: cd 1 should install a network configuration tool

2013-01-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 697868 tasksel Bug #697868 [debian-cd] debian-cd: cd 1 should install a network configuration tool Bug reassigned from package 'debian-cd' to 'tasksel'. No longer marked as found in versions debian-cd/3.1.10. Ignoring request to alter fi

Bug#697915: Problem with LVM when installing latest Debian Wheezy

2013-01-11 Thread Benoît Tonnerre
Package: installation-reports Boot method: Cd "debian-wheezy-DI-b4-amd64-netinst.iso". Image version: http://cdimage.debian.org/cdimage/wheezy_di_beta4/amd64/iso-cd/debian-wheezy-DI-b4-amd64-netinst.iso Date: Friday 11 January 2013. Machine: Tested on VirtualBox and a Dell Optiplex 960 and a Del

Processed: Commited to svn

2013-01-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 681994 + pending Bug #681994 [discover] discover-config --list doesn't work Added tag(s) pending. > tags 533688 + pending Bug #533688 [discover] (discover_2.1.2-3/avr32): FTBFS: Outdated config.{sub,guess} Added tag(s) pending. > thanks Stop

discover-data_2.2013.01.11_i386.changes ACCEPTED into unstable

2013-01-11 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 11 Jan 2013 11:16:53 +0100 Source: discover-data Binary: discover-data Architecture: source all Version: 2.2013.01.11 Distribution: unstable Urgency: low Maintainer: Debian Install System Team Changed-By: Petter Rei

Processing of discover-data_2.2013.01.11_i386.changes

2013-01-11 Thread Debian FTP Masters
discover-data_2.2013.01.11_i386.changes uploaded successfully to localhost along with the files: discover-data_2.2013.01.11.dsc discover-data_2.2013.01.11.tar.gz discover-data_2.2013.01.11_all.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUB

Bug#697839: marked as done (discover-data: usb 04b4:fd1[0123] is package sispmctl)

2013-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2013 10:32:34 + with message-id and subject line Bug#697839: fixed in discover-data 2.2013.01.11 has caused the Debian Bug report #697839, regarding discover-data: usb 04b4:fd1[0123] is package sispmctl to be marked as done. This means that you claim that the pr

Re: Adding preseeding and firmware to wheezy iso netinst

2013-01-11 Thread Mathieu Parent
hi, I'm still lacking a bit behind. My image now boots as CD-ROM Legacy and CR-ROM EFI but not as USB EFI (which works with vanillia netinst b4). Here is my xorriso: xorriso -as mkisofs -r -J -joliet-long -l -cache-inodes \ -isohybrid-mbr /usr/lib/syslinux/isohdpfx.bin -partition_offset 16 \

Re: Last 2 commits in cdrom-checker

2013-01-11 Thread Colin Watson
On Fri, Jan 11, 2013 at 07:12:49AM +0100, Christian PERRIER wrote: > Do you target wheezy for the last 2 commits your made in cdrom > -checker? There's no pressing urgency to have them in wheezy, but they're also entirely harmless and can ride along with translation updates or whatever without cau

Bug#697839: discover-data: usb 04b4:fd1[0123] is package sispmctl

2013-01-11 Thread Petter Reinholdtsen
[Helmut Grohne] > Package: discover-data > Version: 2.2013.01.09 > Severity: wishlist > > Petter Reinholdtsen called for updates to discover-data on planet.d.o. > So I can provide some IDs as well. Great. :) > The sispmctl package is used to switch a power socket. The current > version of the pa

Bug#697905: persistent naming in crypttab

2013-01-11 Thread Ropesh Thouna
Please unsubscribe.. Thank you. On Fri, Jan 11, 2013 at 2:49 PM, Trek wrote: > Package: partman-crypto > Version: 56 > > Hi, > > I think that using udev persistent device naming in /etc/crypttab > would be useful to prevent some dangerous situation, like the > following one. > > I have a 3 disk

Re: Last 2 commits in cdrom-checker

2013-01-11 Thread Samuel Thibault
Christian PERRIER, le Fri 11 Jan 2013 07:12:49 +0100, a écrit : > Hi Colin, > > Do you target wheezy for the last 2 commits your made in cdrom > -checker? > > I suspect e8ae8876bcea30cc45bcba25ed1e9ea2a317aff0 to be safe and a > good idea.I have however no idea for > 1ec13c5a378076c1098823797

Bug#697905: persistent naming in crypttab

2013-01-11 Thread Trek
Package: partman-crypto Version: 56 Hi, I think that using udev persistent device naming in /etc/crypttab would be useful to prevent some dangerous situation, like the following one. I have a 3 disks setup with the first two in raid mode and the third as archive. The swap partitions are encrypte

Last 2 commits in cdrom-checker

2013-01-11 Thread Christian PERRIER
Hi Colin, Do you target wheezy for the last 2 commits your made in cdrom -checker? I suspect e8ae8876bcea30cc45bcba25ed1e9ea2a317aff0 to be safe and a good idea.I have however no idea for 1ec13c5a378076c10988237972d4df0f1eefafd3, given my own C-fu..:-) commit 1ec13c5a378076c10988237972d4df0