severity 638682 important
thanks
Hi,
at some point in the future we want to change to only use the new
InRelease file. Which debootstrap currently does not support.
This is not RC, so i set it to important only, but if we can have
debootstrap additionally deal with InRelease short after wheezy,
Processing commands for cont...@bugs.debian.org:
severity 638682 important
Bug #638682 [debootstrap] [debootstrap] debootstrap does not support InRelease
file
Severity set to 'important' from 'normal'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
638682:
On Sunday 20 May 2012 04:31:19 Holger Wansing wrote:
Chris: could you check if the wheezy alpha1 still panics on
your machine?
Still panics very early I'm afraid with both kernel types (standard
and FreeBSD 9). ISO was dated 12-May-2012 03:03 and named:
Package: debian-installer
Version: wheezy alpha
Severity: minor
Tags: d-i
At the end of a successful install you get the 'installation complete'
message: installation is complete, so it is time to boot into your
new system. Make sure to remove the installatio media (CD-ROM,
floppies), ...
I
Package: installation-reports
Severity: normal
Hello,
I ran a few installs using Wheezy Alpha on my machines (SunBlade 2000
and Sun T1000 server) over the last couple of days and it went mostly
smoothly, see details below.
1. Machine: SunBlade 2000
Medium: netboot
Console: serial
Processing commands for cont...@bugs.debian.org:
reassign 673644 finish-install
Bug #673644 [debian-installer] Message at end of successful install talks about
floppies (should be updated)
Bug reassigned from package 'debian-installer' to 'finish-install'.
Ignoring request to alter found
Package: installation-reports
Version: 2.46
Severity: wishlist
-- Package-specific info:
Boot method: Cd
Image version:
http://cdimage.debian.org/cdimage/wheezy_di_alpha1/amd64/iso-cd/debian-wheezy-DI-a1-amd64-CD-1.iso
Date: Date and time of the install
Machine: Lenovo Thinkpad T410
Hi,
I just try to install a system with /boot and root system in btrfs, like the
first message of this report. I use the Debian Installer 7.0 Alpha1
release and get the same error. The workaround cited works to me too.
--
Rogerio Bastos
--
To UNSUBSCRIBE, email to
Package: installation-guide
Severity: normal
X-Debbugs-Cc: 666...@bugs.debian.org
According to 4.3.1. Copying the files — the easy way:
Note that, although convenient, this method does have one major
disadvantage: the logical size of the device will be limited to 256
MB, even if the capacity
Joerg Jaspert wrote:
I understand it right that doing it this way (ie. current symlink stays
around), it won't break anything, so we can just do it for all suites?!
It appears that debmirror will be broken, if it helps. :/
I can't find anything that will break in debian-cd.
--
see shy jo
Debian installer build overview
---
Failed or old builds:
* OLD BUILD:armel May 08 08:10 buildd@ancina build_iop32x_netboot
http://d-i.debian.org/daily-images/armel/daily/build_iop32x_netboot.log
* OLD BUILD:armel May 08 08:13 buildd@ancina
11 matches
Mail list logo