Josselin Mouette [EMAIL PROTECTED] writes:
epiphany-browser (2.22.3-5) unstable; urgency=low
unblock epiphany-browser/2.22.3-6
gdm (2.20.7-4) unstable; urgency=low
gnome-session (2.22.3-2) unstable; urgency=low
libgnomeprint (2.18.5-1) unstable; urgency=low
libgnomeprintui (2.18.3-1)
Package: busybox
Version: 1:1.10.2-2
Severity: wishlist
User: [EMAIL PROTECTED]
Usertags: package-dependencies
Hello,
this bug originates on on the smartphones-standards mailing list [1] and
I expect this should be the case for all embedded device where every
single kB matters.
Basically, while
Package: installation-reports
Version: 2.38
Severity: normal
Boot method: network
Image version: http://people.debian.org/~joeyh/d-i/images/current/
Date: 20081031
Machine: Xen Paravirtual machine on a lenny Dom0
Partitions:
Device Boot Start End Blocks Id System
/dev
On Fri, 2008-10-31 at 12:58 +0100, Guido Guenther wrote:
Package: installation-reports
Version: 2.38
Severity: normal
Boot method: network
Image version: http://people.debian.org/~joeyh/d-i/images/current/
Date: 20081031
Machine: Xen Paravirtual machine on a lenny Dom0
Partitions
On Fri, 2008-10-31 at 12:56 +, Ian Campbell wrote:
The installtion itself worked great but d-i failed to install an
appropriate kernel for Xen Paravirt so the system failed to boot.
To fix this up I mounted the partition in the dom0 and installed the
correct kernel. d-i installed
Hi Ian,
On Fri, Oct 31, 2008 at 01:26:08PM +, Ian Campbell wrote:
[..snip..]
d-i should have installed the 686-bigmem image when running under Xen
due to the use of the 686-bigmem kernel for the Xen variant of the
installer. I'll investigate why this didn't happen.
It seems to be
On Fri, 2008-10-31 at 16:31 +0100, Guido Günther wrote:
Hi Ian,
On Fri, Oct 31, 2008 at 01:26:08PM +, Ian Campbell wrote:
[..snip..]
d-i should have installed the 686-bigmem image when running under Xen
due to the use of the 686-bigmem kernel for the Xen variant of the
installer.
On Fri, Oct 31, 2008 at 12:56:48PM +, Ian Campbell wrote:
On Fri, 2008-10-31 at 12:58 +0100, Guido Guenther wrote:
Package: installation-reports
Version: 2.38
Severity: normal
Boot method: network
Image version: http://people.debian.org/~joeyh/d-i/images/current/
Date: 20081031
On Fri, 2008-10-31 at 15:38 +, Ian Campbell wrote:
So to me it seems the workaround can be removed:
* removed for VIA Ester altogeher
* removed vor VIA Nehemiah once we ship 2.6.27
Do you happen to know the Family/Model for the Nehemiah?
Your cpuinfo shows that Esther is Family
://people.debian.org/~joeyh/d-i/images/current/
Date: 20081031
Machine: Xen Paravirtual machine on a lenny Dom0
Partitions:
Device Boot Start End Blocks Id System
/dev/xvda1 * 1 242 1943833+ 83 Linux
/dev/xvda2 243
On Fri, Oct 31, 2008 at 03:38:30PM +, Ian Campbell wrote:
On Fri, 2008-10-31 at 16:31 +0100, Guido Günther wrote:
Hi Ian,
On Fri, Oct 31, 2008 at 01:26:08PM +, Ian Campbell wrote:
[..snip..]
d-i should have installed the 686-bigmem image when running under Xen
due to the
Hi,
As I looked more in detail, debian-installer works fine (does not over
write unrelated data) and usable if MBR is used as BIOS emultion mode
boot loader. (I.e., installed to /dev/sda (hd0)
So problem is when installing to /dev/sda3 or in other word to (hd0,3).
Since this causes data loss,
On Fri, Oct 31, 2008 at 03:46:22PM +, Ian Campbell wrote:
diff --git a/packages/base-installer/kernel/i386.sh
b/packages/base-installer/kernel/i386.sh
index cba6d9b..e8929ea 100644
--- a/packages/base-installer/kernel/i386.sh
+++ b/packages/base-installer/kernel/i386.sh
@@ -36,10 +36,17
On Fri, Oct 31, 2008 at 04:31:00PM +0100, Guido Günther wrote:
So to me it seems the workaround can be removed:
* removed for VIA Ester altogeher
* removed vor VIA Nehemiah once we ship 2.6.27
Please read #464962 first.
Bastian
--
Women professionals do tend to over-compensate.
On Fri, 2008-10-31 at 17:11 +0100, Guido Günther wrote:
Yes, this looks just right!
This is functionally identical but is more self-documenting...
diff --git a/packages/base-installer/debian/changelog
b/packages/base-installer/debian/changelog
index 59404b5..5fd1b4c 100644
---
On Fri, Oct 31, 2008 at 03:52:43PM +, Ian Campbell wrote:
[..snip..]
d-i should have installed the 686-bigmem image when running under Xen
due to the use of the 686-bigmem kernel for the Xen variant of the
installer. I'll investigate why this didn't happen.
Could you please
On Fri, 2008-10-31 at 17:22 +0100, Bastian Blank wrote:
On Fri, Oct 31, 2008 at 04:31:00PM +0100, Guido Günther wrote:
So to me it seems the workaround can be removed:
* removed for VIA Ester altogeher
* removed vor VIA Nehemiah once we ship 2.6.27
Please read #464962 first.
OK, so I
Package: console-setup
Version: 1.25
Severity: normal
Tags: patch
Hi
line 3109:
if (chr($uni) =~ /\p{IsAlpha}/) {
cause a warning:
Use of uninitialized value $uni in pattern match (m//) at /usr/bin/ckbcomp
line 3109.
This is visible on boot on minimal system which don't have
1) I have succeeded with network boot / network install with etch-r3. I have
patched the
netboot initrd with ide modules stolen from debian-40r3-i386-DVD-1.iso. Not
nice but it works.
2) Trying with recent debian version still fails.
Kernel and initrd is from
On Fri, Oct 31, 2008 at 05:08:48PM +0100, Loïc Minier wrote:
Package: console-setup
Version: 1.25
Severity: normal
Tags: patch
perl -e 'use warnings all; chr(hex(323)) =~ /\p{IsAlpha}/'
Use of uninitialized value $x in scalar assignment at
/usr/share/perl/5.10/utf8_heavy.pl line 242.
ALLIED GLOBAL NURSING AND MEDICAL SCHOOL
PT. German Centre Indonesia German Centre,
Suite 4220 Jl.
Good day,
Kindly confirm if there is availability in your language school. We are 4 in
our group coming for a vacation and would wish to be enrolled in your
languageschool. We are medical
21 matches
Mail list logo
