Hi,
Raphaël Hertzog (06/12/2012):
> I have a derivative distribution which has its own codename. […]
Thanks for the patch, but it looks to me like (1) that's just too late
for wheezy, (2) it doesn't affect it directly. That shouldn't even be
a blocker anyway since you're rolling up your derivati
On Mon, Dec 17, 2012 at 02:45:41AM +, Ben Hutchings wrote:
> On Mon, 2012-12-17 at 00:11 +, Colin Watson wrote:
> [...]
> > Rather than the Sisyphean task of giving all the appropriate utilities
> > machine-parseable progress interface, I instead suggest that we study
> > the current progre
Hi,
Raphael Hertzog (06/12/2012):
> I agree. Here's the corresponding patch. It would be nice if someone
> could commit it so that it gets included in the next d-i release.
>
> It's needed to have a proper live image for wheezy.
thanks everyone involved, but rc1 doesn't look like an appropriate
On Sun, Dec 16, 2012 at 10:22:49PM -0500, Phillip Susi wrote:
> Not too long ago I was looking at patching gparted to support this and
> while it did not seem difficult to process the output of the e2fsprogs
> utilities for the progress information, I was wondering why the
> various fs utilities do
If mklibs is called with both --root and --sysroot specified, and
for a library found in rpath, mklibs searches this library in
// which is an invalid path. Since
already points to an absolute directory on host, we should not
add prefix to it. Here is a mklibs patch for this issue.
Lei
* Fix
I just had the same problem installing wheezy beta4 to and SD card in an
ASUS EeeBox B202 with a "Realtek Semiconductor Corp. USB 2.0 multicard
reader"
I eventually worked around it by downloading the wheezy
linux-image-3.2.0-4-486 package to another machine, extracting it and
running:
> nc
Package: debian-installer
Version: 20121114
Severity: wishlist
Since apt_0.8.16~exp3 one can disable secure apt for specific
repositories instead of having to use --allow-unauthenticated and
disable verification for all repositories. Such entries look like
deb [trusted=yes] file:///some/where
Processing commands for cont...@bugs.debian.org:
> #debian-installer (20121115) UNRELEASED; urgency=low
> #
> # * When building with localudebs, only disable secure apt checking for that
> #repository, while keeping it working for network repositories,
> #by using [trusted=yes] in sources
Package: debian-installer
Severity: normal
Tags: d-i
This is using one of today's i386 netinst ISOs from sid_d-i at
cdimage.debian.org/, but the beta-4 image behaves in the same way.
I remastered the image to have
debian-installer/keymap=es
and
keymap=es
on the kernel command line. (O
We tested with the new weekly build[1] of 17 Dec 2012 - this failed in the
same way.
Neale.
[1]
http://cdimage.debian.org/cdimage/weekly-builds/i386/iso-cd/debian-testing-i386-xfce-CD-1.iso
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trou
Package: installation-reports
Severity: serious
Image version: beta4 netinst CD amd64
System type: Toshiba Satellite P305-S8825
Installer is fine
During Debian's first and subsequent boot, the console becomes corrupted
The X display is just blank too
Access to the box is possible using ssh
A
Your message dated Tue, 18 Dec 2012 11:43:48 +0400
with message-id <50d01eb4.8030...@msgid.tls.msk.ru>
and subject line Bug#599200: base-installer: Install amd64 kernel on i686 kvm
guest - and fail to boot
has caused the Debian Bug report #599200,
regarding base-installer: Install amd64 kernel on
On 2012-12-13T01:42:13+, Steve McIntyre wrote:
> >Booting into rescue mode and running modprobe efivars ; efibootmgr
> >--verbose gives this output:
> >
> >BootCurrent: 0003
> >Timeout: 1 seconds
> >BootOrder: ,0003,0001,0002
> >Boot* debian Vendor(99e275e7-75a0-4b37-a2e6-c5385e6c0
13 matches
Mail list logo
