Uyghur translation for Debian Installer

[Gheyret Tohti]

Hi,
I visited http://d-i.debian.org/l10n-stats/translation-status.html, and find 
there is no Uyghur language. We translated Debian Installer (level1, 
level2,level3).Where to send those files?.


Gheyret Kenji
2011/02/17



  

Bug#613676: installation-reports: Keyboard does not work in Gnome/X after upgrade to squeeze

[Matyas]

On 02/16/2011 09:41 AM, Cyril Brulebois wrote:
> I'll reassign as needed once you've told us a bit more about your
> system.
> 
> KiBi.

So I suspect that this was covered under:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571636

Unfortunately, I do not know enough about hal, udev and their config and I do
not understand the solution I am supposed to implement.  (Not even that, but
I cannot deduce the steps to take towards a fix.)  Can someone give a pointer
how to proceed to fix the configuration issue?  (Like reconfigure a package
or reinstall a package, maybe?)

Here is what I tried: I commented out the lines in /etc/default/keyboard as
mentioned in that thread and rebooted, but still no joy.  (My xorg.conf was
generated by Xorg -configure.) I have the following in Xorg.0.log:

(II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(II) config/udev: Adding input device Power Button (/dev/input/event1)
(**) Power Button: Applying InputClass "evdev keyboard catchall"
(**) Power Button: always reports core events
(**) Power Button: Device: "/dev/input/event1"
(II) Power Button: Found keys
(II) Power Button: Configuring as keyboard
(II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(II) config/udev: Adding input device AT Translated Set 2 keyboard
(/dev/input/event0)
(**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
(**) AT Translated Set 2 keyboard: always reports core events
(**) AT Translated Set 2 keyboard: Device: "/dev/input/event0"
(II) AT Translated Set 2 keyboard: Found keys
(II) AT Translated Set 2 keyboard: Configuring as keyboard
(II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard"
(type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"

More info generated by the bug reporting tool:

-- Package-specific info:
/var/lib/x11/X.roster does not exist.

/var/lib/x11/X.md5sum does not exist.

X server symlink status:
lrwxrwxrwx 1 root root 13 Apr 19  2010 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 1733468 Jan 11 21:50 /usr/bin/Xorg

/var/lib/x11/xorg.conf.roster does not exist.

VGA-compatible devices on PCI bus:
00:12.0 VGA compatible controller: nVidia Corporation C68 [GeForce 7050 PV /
nForce 630a] (rev a2)

/var/lib/x11/xorg.conf.md5sum does not exist.

Xorg X server configuration file status:
-rw-r--r-- 1 root root 1972 Feb 16 20:57 /etc/X11/xorg.conf

Contents of /etc/X11/xorg.conf:
Section "ServerLayout"
Identifier "X.org Configured"
Screen  0  "Screen0" 0 0
InputDevice"Mouse0" "CorePointer"
InputDevice"Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
ModulePath   "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/X11/misc"
FontPath "/usr/share/fonts/X11/cyrillic"
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"
FontPath "/usr/share/fonts/X11/Type1"
FontPath "/usr/share/fonts/X11/100dpi"
FontPath "/usr/share/fonts/X11/75dpi"
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
FontPath "built-ins"
EndSection

Section "Module"
Load  "dri2"
Load  "extmod"
Load  "dri"
Load  "dbe"
Load  "record"
Load  "glx"
EndSection

Section "InputDevice"
Identifier  "Keyboard0"
Driver  "kbd"
EndSection

Section "InputDevice"
Identifier  "Mouse0"
Driver  "mouse"
Option  "Protocol" "auto"
Option  "Device" "/dev/input/mice"
Option  "ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
Identifier   "Monitor0"
VendorName   "Monitor Vendor"
ModelName"Monitor Model"
EndSection

Section "Device"
Identifier  "Card0"
#Driver  "nv"
Driver  "nvidia"
#   Driver  "nouveau"
VendorName  "nVidia Corporation"
BoardName   "C68 [GeForce 7050 PV / nForce 630a]"
BusID   "PCI:0:18:0"
#Option  "UseEDID" "False"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor"Monitor0"
SubSection "Display"
Viewport   0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport   0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport   0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport   0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport   0 0
Depth 16

Debian installer build: failed or old builds

[Daily build aggregator]

Debian installer build overview
---

Failed or old builds:

* OLD BUILD:hppa Jan 17 07:06 didaily@c3700 build_cdrom 
http://d-i.debian.org/daily-images/hppa/daily/build_cdrom.log

* OLD BUILD:hppa Jan 17 07:10 didaily@c3700 build_netboot 
http://d-i.debian.org/daily-images/hppa/daily/build_netboot.log

* OLD BUILD:hppa Jan 17 07:14 didaily@c3700 build_miniiso 
http://d-i.debian.org/daily-images/hppa/daily/build_miniiso.log

* OLD BUILD:kfreebsd-amd64 Feb 05 00:11 buildd@fano build_cdrom 

http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_cdrom.log

* OLD BUILD:kfreebsd-amd64 Feb 05 00:13 buildd@fano build_netboot 

http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot.log

* OLD BUILD:kfreebsd-i386 Feb 05 00:12 buildd@finzi build_cdrom 

http://d-i.debian.org/daily-images/kfreebsd-i386/daily/build_cdrom.log

* OLD BUILD:kfreebsd-i386 Feb 05 00:14 buildd@finzi build_netboot 

http://d-i.debian.org/daily-images/kfreebsd-i386/daily/build_netboot.log

* daily mipsel images build:
The build daemon responsible for these builds is currently moving to a
new hosting location. Daily builds should be available again within the
first two weeks of 2011.

* daily sparc images build:
Due to the lack of buildd suitable buildd machine there are currently no daily
builds for the SPARC architecture. These builds will be reenabled as soon as
as a suitable machine is available.

* OLD BUILD:amd64 Feb 07 22:17 debian-cd@pettersson 2squeezepowerpc 
http://cdbuilder.debian.org/cdimage-log/2squeezepowerpc

* FAILED BUILD: amd64 Feb 07 22:17 debian-cd@pettersson 2squeezepowerpc 
http://cdbuilder.debian.org/cdimage-log/2squeezepowerpc

* OLD BUILD:amd64 Feb 07 22:17 debian-cd@pettersson Csqueezepowerpc 
http://cdbuilder.debian.org/cdimage-log/Csqueezepowerpc

* FAILED BUILD: amd64 Feb 07 22:17 debian-cd@pettersson Csqueezepowerpc 
http://cdbuilder.debian.org/cdimage-log/Csqueezepowerpc

* OLD BUILD:amd64 Feb 07 22:17 debian-cd@pettersson 1squeezesparc 
http://cdbuilder.debian.org/cdimage-log/1squeezesparc

* FAILED BUILD: amd64 Feb 07 22:17 debian-cd@pettersson 1squeezesparc 
http://cdbuilder.debian.org/cdimage-log/1squeezesparc

* OLD BUILD:amd64 Feb 07 22:17 debian-cd@pettersson 2squeezesparc 
http://cdbuilder.debian.org/cdimage-log/2squeezesparc

* FAILED BUILD: amd64 Feb 07 22:17 debian-cd@pettersson 2squeezesparc 
http://cdbuilder.debian.org/cdimage-log/2squeezesparc

* OLD BUILD:amd64 Feb 07 22:17 debian-cd@pettersson 2squeezemulti-arch-1 
http://cdbuilder.debian.org/cdimage-log/2squeezemulti-arch-1

* FAILED BUILD: amd64 Feb 07 22:17 debian-cd@pettersson 
2squeezemulti-arch-1 
http://cdbuilder.debian.org/cdimage-log/2squeezemulti-arch-1

* OLD BUILD:amd64 Feb 07 22:17 debian-cd@pettersson Csqueezemulti-arch-1 
http://cdbuilder.debian.org/cdimage-log/Csqueezemulti-arch-1

* FAILED BUILD: amd64 Feb 07 22:17 debian-cd@pettersson 
Csqueezemulti-arch-1 
http://cdbuilder.debian.org/cdimage-log/Csqueezemulti-arch-1

* OLD BUILD:amd64 Feb 07 22:17 debian-cd@pettersson 1squeezekfreebsd-amd64 
http://cdbuilder.debian.org/cdimage-log/1squeezekfreebsd-amd64

* FAILED BUILD: amd64 Feb 07 22:17 debian-cd@pettersson 
1squeezekfreebsd-amd64 
http://cdbuilder.debian.org/cdimage-log/1squeezekfreebsd-amd64

* OLD BUILD:amd64 Feb 07 22:17 debian-cd@pettersson 2squeezekfreebsd-amd64 
http://cdbuilder.debian.org/cdimage-log/2squeezekfreebsd-amd64

* FAILED BUILD: amd64 Feb 07 22:17 debian-cd@pettersson 
2squeezekfreebsd-amd64 
http://cdbuilder.debian.org/cdimage-log/2squeezekfreebsd-amd64

* OLD BUILD:amd64 Feb 07 22:17 debian-cd@pettersson 1squeezekfreebsd-i386 
http://cdbuilder.debian.org/cdimage-log/1squeezekfreebsd-i386

* FAILED BUILD: amd64 Feb 07 22:17 debian-cd@pettersson 
1squeezekfreebsd-i386 
http://cdbuilder.debian.org/cdimage-log/1squeezekfreebsd-i386

* OLD BUILD:amd64 Feb 07 22:17 debian-cd@pettersson 2squeezekfreebsd-i386 
http://cdbuilder.debian.org/cdimage-log/2squeezekfreebsd-i386

* FAILED BUILD: amd64 Feb 07 22:17 debian-cd@pettersson 
2squeezekfreebsd-i386 
http://cdbuilder.debian.org/cdimage-log/2squeezekfreebsd-i386

* OLD BUILD:amd64 Feb 08 00:49 debian-cd@pettersson multi-arch 
http://cdbuilder.debian.org/cdimage-log/multi-arch

* FAILED BUILD: amd64 Feb 08 00:49 debian-cd@pettersson multi-arch 
http://cdbuilder.debian.org/cdimage-log/multi-arch


Totals: 171 builds (11 failed, 26 old)


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists

Bug#613623: network-console: Cannot start with some locales (eg. sl_SI)

[Samuel Thibault]

tags 613623 + confirmed
thanks

Matej Bažec, le Wed 16 Feb 2011 09:32:27 +0100, a écrit :
> The network-console can't be started (can't be selected from the d-i menu)
> if the language is set to slovene. I have to choose a different language 
> first.
> Maybe it affects some other locale too..

Confirmed with the i386 business card image: boot in export mode,
configure slovenian language, keyboard, cd, load the network component,
configure network, and then when back at the main menu the SSH entry is
split in two parts:

Nadaljuj namstitev oddaljeno
preko SSH

It seems like the comma in the translation poses problem by splitting
into two menu entries, neither of which are working.

€ grep -A1 'Continue installation remotely using SSH' debian/po/* | grep ,
debian/po/hr.po-msgstr "Nastavi instalaciju daljinski, rabeći SSH"
debian/po/ka.po-msgstr "გავაგრძელოთ ინსტალაცია დისტანციურად, SSH-ის გამოყენებით"
debian/po/lt.po-msgstr "Įdiegimą tęsti nutolus, naudojant SSH protokolą"
debian/po/ro.po-msgstr "Se continuă instalarea de la distanță, utilizând SSH"
debian/po/sl.po-msgstr "Nadaljuj namestitev oddaljeno, preko SSH"
debian/po/te.po-msgstr "దూరంగా  వ్యవస్థీకరణ, SSH ఉపయోగించి కొనసాగించండి"

I tried hr, it indeed has the issue too, I guess the others have it too.
I guess other packages may have the issue for some languages, too...
That needs more careful look.

Samuel



--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110217004634.go5...@const.famille.thibault.fr

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 613382 hard drive not detected on I/O Data GLAN TANK
Bug #613382 [installation-reports] (no subject)
Changed Bug title to 'hard drive not detected on I/O Data GLAN TANK' from '(no 
subject)'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
613382: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613382
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.129790098820951.transcr...@bugs.debian.org

Bug#580281: marked as done (support for PERC H200 controller)

[Debian Bug Tracking System]

Your message dated Wed, 16 Feb 2011 23:51:56 +
with message-id <201102162351.56355.el...@debianpt.org>
and subject line 
has caused the Debian Bug report #580281,
regarding support for PERC H200 controller
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
580281: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580281
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports

Boot method: < CD>
Image version: 
Date: <1st May 2010>

Machine: 
Processor: XEON 2.4G
Memory: 12G
Partitions: 

Output of lspci -knn (or lspci -nn):

Base System Installation Checklist: [E]

Initial boot:   [ok ]
Detect network card:[ok but i provided the driver from debian site]
Configure network:  [ok ]
Detect CD:  [ok ]
Load installer modules: [ ok]
Detect hard drives: [KO  no HDD detectet ]
Partition hard drives:  [ NA]
Install base system:[ NA]
Clock/timezone setup:   [ NA]
User/password setup:[ NA]
Install tasks:  [ NA]
Install boot loader:[ NA]
Overall install:[ KO]

Comments/Problems:

No HDD detected, unable to install the system.
The server is equiped with a PERC H200 RAID controler and 2 SAS 146G HDDs

Is the PERC H200 controler supported? exist a driver?

Regards

Ch. LAIOS



--- End Message ---
--- Begin Message ---
Hi,

the controller it is supported on the installer since kernel-wedge version 
2.63 with the module mpt2sas.

-- 
Melhores cumprimentos/Best regards,

Miguel Figueiredo
http://www.DebianPT.org

--- End Message ---

Bug#546033: marked as done (bug report against the installation-reports pseudo package)

[Debian Bug Tracking System]

Your message dated Wed, 16 Feb 2011 23:41:12 +
with message-id <201102162341.13030.el...@debianpt.org>
and subject line 
has caused the Debian Bug report #546033,
regarding bug report against the installation-reports pseudo package
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
546033: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=546033
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports

Boot method: < CD >
Image version: 
Date: < 2009/09/10 >

Machine: 

1st Computer


customized computer - INSTALLATION ON AN EXTERNAL DISK (sdb)
WITH MAIN DISK (sda) DISCONECTED - 

Processor: Intel core2-duo 8400 (3 GHz)
Memory: 2 Gb

Partitions: < df -Tl >

Sys. de fich. Type1K-blocs   Occupé Disponible Capacité Monté
sur
/dev/sda6 ext315488716   3618208  11083728  25% /
tmpfstmpfs 1024352 0   1024352   0% /lib/init/rw
udev tmpfs   10240   980  9260  10% /dev
tmpfstmpfs 1024352 0   1024352   0% /dev/shm
/dev/sda2 ext3   77749 20533 53202  28% /boot
/dev/sda7 ext3   103216920  25685852  72287856  27% /home
/dev/sda8  fuseblk   262148636  79371928 182776708  31% /mnt/SDA8
/dev/sdb7 ext356680060806256  52994556   2% /media/home_pass
/dev/sdb3  fuseblk51608812   3336392  48272420
7% /media/PASS-NTFS  
/dev/sdb1 ext3   69972 23205 43154  35% /media/Grub_pass
/dev/sdb6 ext3 7566400   4275228   2906820
60% /media/Debian_pass


Output of lspci -knn

00:00.0 Host bridge [0600]: Intel Corporation 82G33/G31/P35/P31 Express
DRAM Controller [8086:29c0] (rev 02)
Kernel driver in use: agpgart-intel
Kernel modules: intel-agp
00:02.0 VGA compatible controller [0300]: Intel Corporation 82G33/G31
Express Integrated Graphics Controller [8086:29c2] (rev 02)
00:02.1 Display controller [0380]: Intel Corporation 82G33/G31 Express
Integrated Graphics Controller [8086:29c3] (rev 02)
00:03.0 Communication controller [0780]: Intel Corporation
82G33/G31/P35/P31 Express MEI Controller [8086:29c4] (rev 02)
00:19.0 Ethernet controller [0200]: Intel Corporation 82566DC-2 Gigabit
Network Connection [8086:294c] (rev 02)
Kernel driver in use: e1000e
Kernel modules: e1000e
00:1a.0 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family)
USB UHCI Controller #4 [8086:2937] (rev 02)
Kernel driver in use: uhci_hcd
Kernel modules: uhci-hcd
00:1a.1 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family)
USB UHCI Controller #5 [8086:2938] (rev 02)
Kernel driver in use: uhci_hcd
Kernel modules: uhci-hcd
00:1a.2 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family)
USB UHCI Controller #6 [8086:2939] (rev 02)
Kernel driver in use: uhci_hcd
Kernel modules: uhci-hcd
00:1a.7 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family)
USB2 EHCI Controller #2 [8086:293c] (rev 02)
Kernel driver in use: ehci_hcd
Kernel modules: ehci-hcd
00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD
Audio Controller [8086:293e] (rev 02)
Kernel driver in use: HDA Intel
Kernel modules: snd-hda-intel
00:1c.0 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI
Express Port 1 [8086:2940] (rev 02)
Kernel driver in use: pcieport-driver
Kernel modules: shpchp
00:1c.1 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI
Express Port 2 [8086:2942] (rev 02)
Kernel driver in use: pcieport-driver
Kernel modules: shpchp
00:1c.2 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI
Express Port 3 [8086:2944] (rev 02)
Kernel driver in use: pcieport-driver
Kernel modules: shpchp
00:1c.3 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI
Express Port 4 [8086:2946] (rev 02)
Kernel driver in use: pcieport-driver
Kernel modules: shpchp
00:1c.4 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI
Express Port 5 [8086:2948] (rev 02)
Kernel driver in use: pcieport-driver
Kernel modules: shpchp
00:1d.0 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family)
USB UHCI Controller #1 [8086:2934] (rev 02)
Kernel driver in use: uhci_hcd
Kernel modules: uhci-hcd
00:1d.1 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family)
USB UHCI Controller #2 [8086:2935] (rev 02)
Kernel driver in use: uhci_hcd
Kernel modules: uhci-hcd
00:1d.2 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family)

Bug#544493: marked as done (Tyan S7002 fails to detect network chips??)

[Debian Bug Tracking System]

Your message dated Wed, 16 Feb 2011 23:39:10 +
with message-id <201102162339.10663.el...@debianpt.org>
and subject line 
has caused the Debian Bug report #544493,
regarding Tyan S7002 fails to detect network chips??
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
544493: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=544493
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: installation-reports

Boot method:  CD
Image version:   
http://cdimage.debian.org/debian-cd/5.0.2a/amd64/iso-cd/debian-502a-amd64-netinst.iso
Date: Aug 31 2009

Machine: Tyan S7002
Processor:
Memory:
Partitions: na

Output of lspci -knn (or lspci -nn): Copied lines by hand:
0200.0 Ethernet controller intel corporation 82574L gigabit network connection 
[8086:10D3]
0300.0 Ethernet controller intel corporation 82574L gigabit network connection 
[8086:10D3]


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [o]
Detect network card:[E]
Configure network:  [ ]
Detect CD:  [ ]
Load installer modules: [ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:

I checked and the e1000e driver exists.  Tried several things with the BIOS - updated BIOS to latest 
version (1.03) NICs are enabled. Plugging live network cable in - causes lights to light - after 
very small delay.


Google led me to this:

http://lists.debian.org/debian-kernel/2009/06/msg00305.html

Is there someplace I can get an updated driver?



Karl Schmidt  EMail k...@xtronics.com
Transtronics, Inc.  WEB http://xtronics.com
3209 West 9th Street Ph (785) 841-3089
Lawrence, KS 66049  FAX (785) 841-0434

The best way to cheer yourself up
is to try to cheer somebody else up. -- Mark twain




--- End Message ---
--- Begin Message ---
This network card it's supported in current release (Squeeze) with the module 
e1000e on kernel 2.6.32.
Hence, closing.

-- 
Melhores cumprimentos/Best regards,

Miguel Figueiredo
http://www.DebianPT.org

--- End Message ---

Bug#520506: marked as done (Bad title on "Choose a country, territory or area" screen )

[Debian Bug Tracking System]

Your message dated Wed, 16 Feb 2011 23:33:47 +
with message-id <201102162333.48208.el...@debianpt.org>
and subject line 
has caused the Debian Bug report #520506,
regarding Bad title on "Choose a country, territory or area" screen 
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
520506: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=520506
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: debian-installer
Version: lenny-5.0

After selecting lanugage, on another page there is a "Based on your language,
you are probably located in one of these countries or regions" screen.

Problem is that in the title there is still a confusing "Choose language" title.

I suggest that the title should be changed to "Choose a country" string.

I'm installing Debian Lenny 5.0 i386 netinst.iso

-- 
Best regards
Martin Sarfy


--- End Message ---
--- Begin Message ---
Hi,

with current behaviour the titles now are:

"select a language" -> "select your location"

-- 
Melhores cumprimentos/Best regards,

Miguel Figueiredo
http://www.DebianPT.org

--- End Message ---

Re: differences in busybox configurations, part1 (longish)

[Neil Williams]

On Wed, 16 Feb 2011 21:15:57 +
Otavio Salvador  wrote:

> On Wed, Feb 16, 2011 at 21:06, Neil Williams 
> wrote: ...
> > I cannot recommend any embedded system should use any version of
> > busybox built by Debian for d-i without *also* installing and using
> > coreutils, login, passwd, shadow, perl and all the rest. i.e.
> > busybox from Debian is only suitable for what Debian normally does
> > with busybox
> > - which explicitly does *not* include handling passwords, shadow or
> > otherwise.
> 
> Please take a look on this thread:
> http://lists.debian.org/debian-boot/2011/02/msg00471.html
> 
> Basically we're going to revamp busybox and busybox-static
> configuration (d-i one is not going to be changed too much) and then
> we wish to try to be more "friendly" to this kind of use-cases.

As I'm sure you're aware, busybox is not one package, it's 50 or more -
and that's just counting the common variations in source configuration,
not counting the variations of C library used.

> Doing the proposed changes I guess we fit this gab.

Only in the static model, which explains why the binary is so large.
Emdebian Crush shipped with a binary of ~700kb but that was a much
older version. Embedded users who want a static version are probably
going to want a static version linked against uClibc and with no
coreutils, login, passwd etc. installed and all symlinks enabled. I
don't see how Debian can even test such a configuration, let alone
recommend it for widespread usage.

I think the best option is for d-i to simply keep up with busybox
releases. (Current stable is 1.18.3, Debian has 1.17.1, even with
bubulle's update since Squeeze.) That is, itself, a signficant challenge
for a busy and overworked team like d-i and has proved to be an
unreachable target before - especially once a release process starts up
and the rest of d-i needs so much testing. Busybox needs to freeze
early, that's entirely understandable.

The "standard" build won't be (ever) able to install the symlinks which
actually make busybox useful for embedded devices. (It can be hard to
run something on device to create the symlinks when the device cannot
boot because the symlinks don't exist.) The only real solution would be
a fourth build with the symlinks enabled but which conflicts with dpkg,
coreutils, login, passwd and numerous other utilities. I tried to make
this fourth build available just for a single architecture via
cross-building - it is a lot of work. This doesn't even start to handle
the more common instance where the device needs a customised busybox
configuration in the first place.

It's a bigger problem than kernels because users who want busybox want
busybox because there isn't room on the system for anything else and
every 10kb less in /bin/busybox makes it worth reconfiguring and
rebuilding it.

Trying to be friendly is a good thing - adding work for the d-i team
which still means that busybox needs to be reconfigured and rebuilt for
actual embedded devices anyway isn't being friendly - either to the
rest of the d-i team or the embedded users.

> Most important: what's the usage for the static build?

Umm, exactly - not much IMHO.

In the opinion of the dpkg maintainers, around the time of the Lenny
freeze, a system which replaces coreutils, dpkg and passwd is "not
Debian any more". In the opinion of many embedded developers, a system
with a full size busybox *and* coreutils, dpkg and the rest is simply
wasting precious space.

I don't want to be overly negative over this, I'm just trying to ensure
that a commendable desire to be friendly does not actually result in
wasting time within the d-i team and then turn out to not be useful
to embedded users.

IMHO, the best thing d-i can do is to ensure that Debian stays as close
to the current busybox stable release as possible. Updating to current
upstream stable as soon as possible after the release is done and
ensuring it is again updated before the next freeze takes hold. That's
a minimum of only two updates per release cycle, but updates which go
directly to latest upstream stable. It will necessarily slip during all
release freezes but that one commitment may well be enough. Rebuilding
from a Debian source package with adjusted configuration is a lot more
friendly than using wget on busybox.net.

Keep the deb and udeb configuration exactly as d-i requires - maybe
even drop the static version if d-i doesn't use it. Just keep the
package up to date and it will make embedded use a lot simpler than
trying to mangle together some incomplete, broken configuration which
isn't directly usable.

-- 


Neil Williams
=
http://www.linux.codehelp.co.uk/



pgprrywdQGAKp.pgp
Description: PGP signature

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 525946 + pending
Bug #525946 [hw-detect] hw-detect: snd-powermac not added to /etc/modules
Bug #525902 [hw-detect] audio not working at G4
Bug #606984 [hw-detect] PowerMac G4 (Digital Audio) sound
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
525946: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=525946
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.129789414022199.transcr...@bugs.debian.org

Bug#613714: debian-installer: make debian-installer builds available through Debian infrastructure

[Otavio Salvador]

On Wed, Feb 16, 2011 at 21:54, Hector Oron  wrote:
...
> True, maybe a parallel development daily builder is useful, but the
> reason I am asking for such feature is to ease the release process and
> those builds might be useful for other projects such debian-live.
...

I believe we ought to make more regular uploads but not sure if
automated in any specific frequency will give any benefit for us. Live
and others can use dailies but fetch them from a different URL.

-- 
Otavio Salvador                             O.S. Systems
E-mail: ota...@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br



--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/AANLkTinCa8Q=htp5zujlziy0axbqywwqxwyp_k9vy...@mail.gmail.com

Re: RM auto-install ?

[Otavio Salvador]

On Wed, Feb 16, 2011 at 20:44, Joey Hess  wrote:
> The auto-install package has in its changelog
> "DEPRECATED - auto-install functionality has been integrated in preseed"
> But the udebs are still in the archive.
>
> Shall we start the removal process?

IMO yes.

-- 
Otavio Salvador                             O.S. Systems
E-mail: ota...@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/AANLkTikäjcypylbfr3uxhazgmavasvxz6zrqwxh...@mail.gmail.com

Bug#613714: debian-installer: make debian-installer builds available through Debian infrastructure

[Hector Oron]

Hello Otavio,

2011/2/16 Otavio Salvador :

> Right but in daily basis? it seems too frequent for me.

True, maybe a parallel development daily builder is useful, but the
reason I am asking for such feature is to ease the release process and
those builds might be useful for other projects such debian-live.

Cheers,
-- 
 Héctor Orón

"Our Sun unleashes tremendous flares expelling hot gas into the Solar
System, which one day will disconnect us."

-- Day DVB-T stop working nicely
Video flare: http://antwrp.gsfc.nasa.gov/apod/ap100510.html



--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/AANLkTimF_Yk-b8oSTE16--9Cf45AZ1SfmJxG2J9ct=z...@mail.gmail.com

Bug#613714: debian-installer: make debian-installer builds available through Debian infrastructure

[Otavio Salvador]

On Wed, Feb 16, 2011 at 21:30, Hector Oron  wrote:
>> You mean like fake uploads?
>
> No, I mean full debian-installer builds to happen in the buildds
> instead of cron tasks in other servers.

Right but in daily basis? it seems too frequent for me.

-- 
Otavio Salvador                             O.S. Systems
E-mail: ota...@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br



--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktin53_v3ykdi41c-ooduh0olgqjm4vsjux5ca...@mail.gmail.com

Re: differences in busybox configurations, part1 (longish)

[Otavio Salvador]

On Wed, Feb 16, 2011 at 21:06, Neil Williams  wrote:
...
> I cannot recommend any embedded system should use any version of
> busybox built by Debian for d-i without *also* installing and using
> coreutils, login, passwd, shadow, perl and all the rest. i.e. busybox
> from Debian is only suitable for what Debian normally does with busybox
> - which explicitly does *not* include handling passwords, shadow or
> otherwise.

Please take a look on this thread:
http://lists.debian.org/debian-boot/2011/02/msg00471.html

Basically we're going to revamp busybox and busybox-static
configuration (d-i one is not going to be changed too much) and then
we wish to try to be more "friendly" to this kind of use-cases.

Doing the proposed changes I guess we fit this gab.

-- 
Otavio Salvador                             O.S. Systems
E-mail: ota...@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/AANLkTimidko_9QT9qtd-ypsvjYaKV3aC2Z5n=fv2w...@mail.gmail.com

Bug#613714: debian-installer: make debian-installer builds available through Debian infrastructure

[Hector Oron]

Hello Otavio,

2011/2/16 Otavio Salvador :
> On Wed, Feb 16, 2011 at 19:52, Hector Oron  wrote:

>>  It would be useful if debian-installer images are built through Debian 
>> buildd infrastructure instead having to setup build daemons on random sites. 
>> It might be a nice goal for next release.

> You mean like fake uploads?

No, I mean full debian-installer builds to happen in the buildds
instead of cron tasks in other servers.

Cheers,
-- 
 Héctor Orón

"Our Sun unleashes tremendous flares expelling hot gas into the Solar
System, which one day will disconnect us."

-- Day DVB-T stop working nicely
Video flare: http://antwrp.gsfc.nasa.gov/apod/ap100510.html



--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktin+hbtle1vlhdj8dsww4toj1gqgecuhnvbhs...@mail.gmail.com

Re: differences in busybox configurations, part1 (longish)

[Otavio Salvador]

On Wed, Feb 16, 2011 at 20:44, Hector Oron  wrote:
...
> Crush development has been postponed until multiarch is ready but some
> of the bits for the proof of concept can be found at emdebian svn [0].
...

What should we do? Just "sync" static with deb and later work on that?
Seems like a more logical way for now at least.

-- 
Otavio Salvador                             O.S. Systems
E-mail: ota...@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/AANLkTi=ta=Fg2HOQVrPehbOUhcZSmD1afR_xx2bYRzL=@mail.gmail.com

Bug#613623: network-console: Cannot start with some locales (eg. sl_SI)

[Matej Bažec]

Thank you Christian for such a quick response.

Selecting the second one has the same effect. Even by preseeding you
would get the same result.

If this helps, you can omit the comma in the translation. In fact, it
is grammatically incorrect to put it there.

Regards.


On Wed, Feb 16, 2011 at 6:27 PM, Christian PERRIER wrote:

> reassign 613623 main-menu
> thanks
>
> Hello Matej, thanks for reporting this issue...
>
> Quoting Matej Bažec (matbaz...@gmail.com):
> > Package: network-console
> > Version: 1.27
> > Severity: normal
> > Tags: d-i l10n
> >
> >
> > The network-console can't be started (can't be selected from the d-i
> menu)
> > if the language is set to slovene. I have to choose a different language
> first.
> > Maybe it affects some other locale too..
>
>
> The bug comes from this:
>
> msgid "Continue installation remotely using SSH"
> msgstr "Nadaljuj namestitev oddaljeno, preko SSH"
>
>
> And, particularly, from the comma in the translation. This string is
> the menu entry text (debian-installer/network-console/title debconf
> template).
>
> The commas leads to the string being split in two parts:
>
> Nadaljuj namestitev oddaljeno
> preko SSH
>
>
> choosing the first makes apparently something crash and you're back to
> the main menuin English (where the menu entry is complete). I
> haven't tested what happens when choosing "preko SSH"
>
> At first glance, I suspect the problem to lie in main-menu that omits
> to escape commas before building the choices list. Hence reassigning
> and CC'ing Joey who is likely to be the right person for dealing with
> that bug.
>
> In the meantime, we can of course drop the comma in the Solevenian
> translation filebut it would be better to fix that bug, of course
>
>
>
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.10 (GNU/Linux)
>
> iQIcBAEBCAAGBQJNXAj/AAoJEIcvcCxNbiWoESUQAMPsYiZC3ur3O/pBNNYoMCzw
> fRWuRfj22Z9oYRS/ptGvImacrd/Oc5ky4QqFG/3neDVxeI8UOXWVhLqv2GFz+5dh
> 2M2vvito3su+j6H24O0EFAalEZFB+3E8uxfunhn+V3m7SjWR55JkpRosv44NkafD
> xC+olNo9fI7a1yu2WiDyqLbAWl4Kmcx92T8HwjD6FoGUhr61KBssQc1RY3rYrIvS
> bf68nTv5J83McPDE1jHDAZyDAAMvQEy368C/dUidg1UAc70eRGki2dBJdabF458l
> LaG/4Bc8xMBu8rtyq3wfGVnkE4w9qW8zj8oj2u4MlspIvrPItmP+/SQoSHvt/Sga
> aje/NpA1F0kADpSmH5f/TMBE6Fb4FHxvww5w7u7z/a6XH5kT8REk50w5JVjNn/8a
> G8+i8JlSN1W+36+nE/Z/p84bi5Pkw+vlnI25S5BtBrx9JEGfn7LXsmjrSpLUiwMC
> HpM5w1K8BBQ2jpMCgAgkj/pxtTgiBtxfLA4ad1mleazRq2WzyDyKgmeZNKpRHJEH
> IuW6EV8I5q3uMmJGEJcRFCGA3a9oXh32cgLcc/VHzQkVpjHbRPgLBOLVnR3MYncg
> HVgFkdasa0TncUVY7uoELYkP7IL07MDTdg0qHEGC3PsGv7gqf1lmtqp9KJaF3A4w
> 8YGZS50RwvUSmEVelpkA
> =Qc7I
> -END PGP SIGNATURE-
>
>

Re: differences in busybox configurations, part1 (longish)

[Neil Williams]

On Wed, 16 Feb 2011 20:55:13 +
Otavio Salvador  wrote:

> On Wed, Feb 16, 2011 at 20:44, Hector Oron 
> wrote: ...
> > Crush development has been postponed until multiarch is ready but
> > some of the bits for the proof of concept can be found at emdebian
> > svn [0].
> ...
> 
> What should we do? Just "sync" static with deb and later work on that?
> Seems like a more logical way for now at least.

Each embedded installation may benefit from a slightly tweaked busybox
from the busybox upstream default. All embedded installations of busybox
are likely to benefit from a busybox built against a configuration
completely unlike anything useful in standard Debian.

For Emdebian Crush, I stuck to a busybox config which was fairly close
to the standard default busybox configuration and nothing like the
Debian config.

I don't think there is a way of providing a single configuration of
busybox which is both ideal for d-i and friendly to embedded systems.

I cannot recommend any embedded system should use any version of
busybox built by Debian for d-i without *also* installing and using
coreutils, login, passwd, shadow, perl and all the rest. i.e. busybox
from Debian is only suitable for what Debian normally does with busybox
- which explicitly does *not* include handling passwords, shadow or
otherwise.

-- 


Neil Williams
=
http://www.linux.codehelp.co.uk/



pgpasXOgQEtp9.pgp
Description: PGP signature

Bug#613714: debian-installer: make debian-installer builds available through Debian infrastructure

[Otavio Salvador]

On Wed, Feb 16, 2011 at 19:52, Hector Oron  wrote:
...
>  It would be useful if debian-installer images are built through Debian 
> buildd infrastructure instead having to setup build daemons on random sites. 
> It might be a nice goal for next release.

You mean like fake uploads?

-- 
Otavio Salvador                             O.S. Systems
E-mail: ota...@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br



--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/AANLkTimFoZH=ir31xdbvwhmcul6mj7mzzhfwjppa5...@mail.gmail.com

RM auto-install ?

[Joey Hess]

The auto-install package has in its changelog
"DEPRECATED - auto-install functionality has been integrated in preseed"
But the udebs are still in the archive.

Shall we start the removal process?

-- 
see shy jo


signature.asc
Description: Digital signature

Re: differences in busybox configurations, part1 (longish)

[Hector Oron]

Hello Ferenc,

2011/2/15 Ferenc Wagner :
> Otavio Salvador  writes:
>
>> On Mon, Feb 14, 2011 at 22:06, Michael Tokarev  wrote:
>>
>>> FEATURE_SHADOWPASSWDS
>>> support for getspent() and friends.
>>> Current: deb n  static y  udeb n
>>> Proposed action: enable for deb
>>> Discussion: It is quite unexpected that busybox can't
>>> use shadow passwords.  On the other hand, there's just
>>> a few applets which actually deals with passwords, and
>>> most of them are disabled for deb build.
>>
>> I'd say to enable it on deb since it can be an important applet for
>> embedded people to rely on.
>
> I have the gut feeling that static busybox was mostly used for testing
> cross-built system images under Qemu user-mode emulation.  I can't serve
> with references now, but a web search would surely give you relevant
> hits.  That's why the current static config is so much different from
> the other two: all three serve rather different purposes (deb: initramfs
> and rescue, udeb: d-i, static: full system testing).  However, maybe the
> emulation use case isn't present anymore, since qemu-user gained the -L
> option...  I hope embedded people can report on the current practices.

Once upon a time there was an attempt to have a cross built Debian
derivative based around busybox instead coreutils et al, it was named
Crush and Neil Williams did an amazing work through some packages to
be able to cross build them.

Crush development has been postponed until multiarch is ready but some
of the bits for the proof of concept can be found at emdebian svn [0].

Currently I cannot tell if that is an important option or not for
cross-built systems derived from Debian.

Best regards,

[0] http://www.emdebian.org/trac/browser/current/target/busybox-crush/trunk

Best regards,
-- 
 Héctor Orón

"Our Sun unleashes tremendous flares expelling hot gas into the Solar
System, which one day will disconnect us."

-- Day DVB-T stop working nicely
Video flare: http://antwrp.gsfc.nasa.gov/apod/ap100510.html


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/AANLkTi=yrtnwa1ek4sadeaqljhxyarpdqbh5vaben...@mail.gmail.com

Processed: limit source to main-menu, tagging 613623

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #main-menu (1.35) UNRELEASED; urgency=low
> #
> #  * Support escaping of menu items containing commas. Closes: #613623
> #
> limit source main-menu
Limiting to bugs with field 'source' containing at least one of 'main-menu'
Limit currently set to 'source':'main-menu'

> tags 613623 + pending
Bug #613623 [main-menu] network-console: Cannot start with some locales (eg. 
sl_SI)
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
613623: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613623
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.129788853326706.transcr...@bugs.debian.org

Educación Virtual Diplomados online

[unicolombia]

Resolucio 4720 de Nov 10 2005 Secretaria de Educación de Bogota D.C
www.unicolombia.edu.co 




Cordial y Respetuoso Saludo,

Esta es una invitación a participar en nuestros programas Diplomados en la 
modalidad Virtual, los cuales le permiten a usted y/o sus colaboradores 
actualización profesional en área de conocimiento.

Visitenos en www.unicolombia.edu.co donde podrá ver nuestro listado completo en 
las siguientes áreas, asi: 

ÁREA CIENCIAS ECONÓMICAS Y ADMINISTRACIÓN 
ÁREA DE LA SALUD 
ÁREA CIENCIAS JURÍDICAS 
ÁREA INGENIERÍAS.

Acreditación Válida Jurídicamente en su País.




FECHA DE INICIO: Febrero 21 de 2011
FECHA LIMITE PARA MATRICULARSE:  Febrero 18 de 2011

Para ingresar como Estudiante Regular visite: 
http://procesomatricula.unicolombia.edu.co 

Medios de Pago : Tarjeta de Credito Online o Giro Internacional.


Corporacion de Educacion Virtual Unicolombia
Resolución 4720 de Nov 10 de 2005
Secretaria de Educación de Bogota D.C
www.unicolombia.edu.co 

GALARDONES  A UNICOLOMBIA :

V PREMIO IBEROAMERICANO A LA EXCELENCIA EDUCATIVA 2008.
EMPRESA DEL AÑO LATIN AMERICAN QUALITY INSTITUTE 2010
CERTIFICADO DE LA CALIDAD - LATIN AMERICAN QUALITY INSTITUTE 2010

Atentamente,

Yesica María Osorio
Departamento de Información
informac...@unicolombia.edu.co
www.unicolombia.edu.co

Sede Principal : 
Calle 94A Nº 11A - 66 Piso 1 
Bogotá Colombia
Teléfonos en Colombia: 
571 - 224 53 13
571 - 813 58 09
Teléfono en México :
55 - 84 21 49 95
Teléfono en USA :
954 - 357 39 28 
Contactenos Online:
Skype : unicolombia



Para ser retirado de nuestra lista de Boletines Unicolombia, envie correo en 
blanco con asunto Borrar a sopo...@unicolombia.edu.co 

Bug#613714: debian-installer: make debian-installer builds available through Debian infrastructure

[Hector Oron]

Package: debian-installer
Version: 20101020
Severity: wishlist

Hello,

  It would be useful if debian-installer images are built through Debian buildd 
infrastructure instead having to setup build daemons on random sites. It might 
be a nice goal for next release.

Best regards,
  -- Hector Oron

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20110216195246.11086.6648.report...@flaco.tsc-farm.upc.es

Bug#590897: (Extended) Haiku detection for os-prober

[Jeroen Oortwijn]

Package: os-prober
Version: 1.39
Severity: normal
Tags: patch

I made an extended version of the Haiku os-prober module. It will also detect
if the partition was "makebootable'd".

Do note that util-linux v1.18 or higher has to be installed for the detection
to work. As before, 'blkid' wouldn't detect BeFS partitions.

- Jeroen



-- System Information:
Debian Release: squeeze/sid
  APT prefers maverick-updates
  APT policy: (500, 'maverick-updates'), (500, 'maverick-security'), (500, 
'maverick')
Architecture: i386 (i686)

Kernel: Linux 2.6.35-25-generic (SMP w/1 CPU core)
Locale: LANG=en_IE.utf8, LC_CTYPE=en_IE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages os-prober depends on:
ii  libc6 2.12.1-0ubuntu10.2 Embedded GNU C Library: Shared lib

os-prober recommends no packages.

os-prober suggests no packages.

-- no debconf information
#!/bin/sh
# Detects Haiku on BeFS partitions.

.. /usr/share/os-prober/common.sh

partition="$1"
mpoint="$2"
type="$3"

# Weed out stuff that doesn't apply to us
case "$type" in
	befs) debug "$partition is a BeFS partition" ;;
	*) debug "$partition is not a BeFS partition: exiting"; exit 1 ;;
esac

if head -c 512 "$partition" | grep -qs "system.haiku_loader"; then
	debug "Stage 1 bootloader found"
else
	debug "Stage 1 bootloader not found: exiting"
	exit 1
fi

if system="$(item_in_dir "system" "$2")" &&
	item_in_dir -q "haiku_loader" "$mpoint/$system" &&
	item_in_dir -q "kernel_x86" "$mpoint/$system"
then
	debug "Stage 2 bootloader and kernel found"
	label="$(count_next_label Haiku)"
	result "$partition:Haiku:$label:chain"
	exit 0
else
	debug "Stage 2 bootloader and kernel not found: exiting"
	exit 1
fi

Bug#590897: (Extended) Haiku detection for os-prober

[Jeroen Oortwijn]

Package: os-prober
Version: 1.39
Severity: normal
Tags: patch

I made an extended version of the Haiku os-prober module. It will also detect
if the partition was "makebootable'd".

Do note that util-linux v1.18 or higher has to be installed for the detection
to work. As before 'blkid' wouldn't detect BeFS partitions.

- Jeroen



-- System Information:
Debian Release: squeeze/sid
  APT prefers maverick-updates
  APT policy: (500, 'maverick-updates'), (500, 'maverick-security'), (500,
'maverick')
Architecture: i386 (i686)

Kernel: Linux 2.6.35-25-generic (SMP w/1 CPU core)
Locale: LANG=en_IE.utf8, LC_CTYPE=en_IE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages os-prober depends on:
ii  libc6 2.12.1-0ubuntu10.2 Embedded GNU C Library: Shared lib

os-prober recommends no packages.

os-prober suggests no packages.
#!/bin/sh
# Detects Haiku on BeFS partitions.

. /usr/share/os-prober/common.sh

partition="$1"
mpoint="$2"
type="$3"

# Weed out stuff that doesn't apply to us
case "$type" in
	befs) debug "$partition is a BeFS partition" ;;
	*) debug "$partition is not a BeFS partition: exiting"; exit 1 ;;
esac

if head -c 512 "$partition" | grep -qs "system.haiku_loader"; then
	debug "Stage 1 bootloader found"
else
	debug "Stage 1 bootloader not found: exiting"
	exit 1
fi

if system="$(item_in_dir "system" "$2")" &&
	item_in_dir -q "haiku_loader" "$mpoint/$system" &&
	item_in_dir -q "kernel_x86" "$mpoint/$system"
then
	debug "Stage 2 bootloader and kernel found"
	label="$(count_next_label Haiku)"
	result "$partition:Haiku:$label:chain"
	exit 0
else
	debug "Stage 2 bootloader and kernel not found: exiting"
	exit 1
fi

Processed: Re: Bug#613623: network-console: Cannot start with some locales (eg. sl_SI)

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 613623 main-menu
Bug #613623 [main-menu] network-console: Cannot start with some locales (eg. 
sl_SI)
Ignoring request to reassign bug #613623 to the same package
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
613623: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613623
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.129788165926000.transcr...@bugs.debian.org

Processed: reassign 613623 to main-menu

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 613623 main-menu
Bug #613623 [network-console] network-console: Cannot start with some locales 
(eg. sl_SI)
Bug reassigned from package 'network-console' to 'main-menu'.
Bug No longer marked as found in versions network-console/1.27.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
613623: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613623
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.129788165225971.transcr...@bugs.debian.org

Bug#613623: network-console: Cannot start with some locales (eg. sl_SI)

[Christian PERRIER]

reassign 613623 main-menu
thanks

Hello Matej, thanks for reporting this issue...

Quoting Matej Bažec (matbaz...@gmail.com):
> Package: network-console
> Version: 1.27
> Severity: normal
> Tags: d-i l10n
> 
> 
> The network-console can't be started (can't be selected from the d-i menu)
> if the language is set to slovene. I have to choose a different language 
> first.
> Maybe it affects some other locale too..


The bug comes from this:

msgid "Continue installation remotely using SSH"
msgstr "Nadaljuj namestitev oddaljeno, preko SSH"


And, particularly, from the comma in the translation. This string is
the menu entry text (debian-installer/network-console/title debconf
template).

The commas leads to the string being split in two parts:

Nadaljuj namestitev oddaljeno
preko SSH


choosing the first makes apparently something crash and you're back to
the main menuin English (where the menu entry is complete). I
haven't tested what happens when choosing "preko SSH"

At first glance, I suspect the problem to lie in main-menu that omits
to escape commas before building the choices list. Hence reassigning
and CC'ing Joey who is likely to be the right person for dealing with
that bug.

In the meantime, we can of course drop the comma in the Solevenian
translation filebut it would be better to fix that bug, of course





signature.asc
Description: Digital signature

Re: busybox v. 1.18.3

[Otavio Salvador]

On Tue, Feb 15, 2011 at 21:41, Joey Hess  wrote:
> Michael Tokarev wrote:
>> this is first refresh of new upstream (1.18) branch,
>> currently at 1.18.3.
...
> Merging that with your branch allows it to build
> without needing to faff with tarballs. Would it make sense
> to include upstream source in our busybox repo now that
> it's in git? It would be more consistent with the rest of d-i,
> although bb is still the only package in d-i that has a
> separate upstream source.
...

I think it would be nice since it would allow for us to grep to code
and track upstream changes more easily.

-- 
Otavio Salvador                             O.S. Systems
E-mail: ota...@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/AANLkTi=icmxs-xh65mfb0sb4hqu6ef2el8dspwdde...@mail.gmail.com

Processed: Re: Bug#613676: installation-reports: Keyboard does not work in Gnome/X after upgrade to squeeze

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 613676 normal
Bug #613676 [installation-reports] installation-reports: Keyboard does not work 
in Gnome/X after upgrade to squeeze
Severity set to 'normal' from 'critical'

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
613676: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613676
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.12978709014877.transcr...@bugs.debian.org

Bug#613676: installation-reports: Keyboard does not work in Gnome/X after upgrade to squeeze

[Cyril Brulebois]

severity 613676 normal
thanks

Matyas A. Sustik  (16/02/2011):
> Package: installation-reports
> Severity: critical
> Justification: breaks unrelated software
> 
> 
> (First bug report; please be kind...)

(Sure.)

> After doing apt-get dist-upgrade to squeeze I lost keyboard
> functionality under X/Gnome.

Please see second part of:
  http://pkg-xorg.alioth.debian.org/howtos/report-bugs.html

> This is an upgrade, but I did not see such topic.  Please let me
> know if I need to refile and under what section.

I'll reassign as needed once you've told us a bit more about your
system.

KiBi.


signature.asc
Description: Digital signature

Bug#613676: installation-reports: Keyboard does not work in Gnome/X after upgrade to squeeze

[Matyas A. Sustik]

Package: installation-reports
Severity: critical
Justification: breaks unrelated software


(First bug report; please be kind...)
After doing apt-get dist-upgrade to squeeze I lost keyboard functionality under 
X/Gnome.

Keyboard works during boot (setup, grub menu).  If I stop gdm then keyboard 
works on text screen.

Additional info:
This is a mythtv frontend machine.  No mouse.  I use the keyboard to drive the 
mouse (when I rarely need it) using the numeric keypad.  Interestingly that 
still works!  Pressing caps lock or num lock does not register though.

I have not changed hardware setup only did the OS/system upgrade.
I am not sure what information this reportbug program collected; please let me 
know what else I should submit.

I tried to do my best with reportbug, but I am not sure that the picked 
"installation report" is the best description.  I could not pick better due to 
lack of options.  This is an upgrade, but I did not see such topic.  Please let 
me know if I need to refile and under what section.

Thanks!
-- Package-specific info:

Boot method: network
Image version: upgrade to squeeze using apt-get
Date: 

Machine: desktop, AMD CPU
Partitions: 


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [ ]
Detect network card:[ ]
Configure network:  [ ]
Detect CD:  [ ]
Load installer modules: [ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:




-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="6.0 (squeeze) - installer build 20100211"
X_INSTALLATION_MEDIUM=netboot

==
Installer hardware-summary:
==
uname -a: Linux lizard 2.6.30-2-486 #1 Sat Sep 26 00:03:46 UTC 2009 i686 
GNU/Linux
lspci -knn: 00:00.0 RAM memory [0500]: nVidia Corporation MCP67 Memory 
Controller [10de:0547] (rev a2)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82b3]
lspci -knn: 00:01.0 ISA bridge [0601]: nVidia Corporation MCP67 ISA Bridge 
[10de:0548] (rev a2)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82b3]
lspci -knn: 00:01.1 SMBus [0c05]: nVidia Corporation MCP67 SMBus [10de:0542] 
(rev a2)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82b3]
lspci -knn: 00:02.0 USB Controller [0c03]: nVidia Corporation MCP67 OHCI USB 
1.1 Controller [10de:055e] (rev a2)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82b3]
lspci -knn: Kernel driver in use: ohci_hcd
lspci -knn: 00:02.1 USB Controller [0c03]: nVidia Corporation MCP67 EHCI USB 
2.0 Controller [10de:055f] (rev a2)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82b3]
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: 00:04.0 USB Controller [0c03]: nVidia Corporation MCP67 OHCI USB 
1.1 Controller [10de:055e] (rev a2)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82b3]
lspci -knn: Kernel driver in use: ohci_hcd
lspci -knn: 00:04.1 USB Controller [0c03]: nVidia Corporation MCP67 EHCI USB 
2.0 Controller [10de:055f] (rev a2)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82b3]
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: 00:06.0 IDE interface [0101]: nVidia Corporation MCP67 IDE 
Controller [10de:0560] (rev a1)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82b3]
lspci -knn: Kernel driver in use: AMD_IDE
lspci -knn: 00:07.0 Audio device [0403]: nVidia Corporation MCP67 High 
Definition Audio [10de:055c] (rev a1)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8290]
lspci -knn: 00:08.0 PCI bridge [0604]: nVidia Corporation MCP67 PCI Bridge 
[10de:0561] (rev a2)
lspci -knn: 00:09.0 IDE interface [0101]: nVidia Corporation MCP67 AHCI 
Controller [10de:0550] (rev a2)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82b3]
lspci -knn: Kernel driver in use: ahci
lspci -knn: 00:0a.0 Ethernet controller [0200]: nVidia Corporation MCP67 
Ethernet [10de:054c] (rev a2)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82b3]
lspci -knn: Kernel driver in use: forcedeth
lspci -knn: 00:0b.0 PCI bridge [0604]: nVidia Corporation MCP67 PCI Express 
Bridge [10de:0562] (rev a2)
lspci -knn: Kernel driver in use: pcieport-driver
lspci -knn: 00:0c.0 PCI bridge [0604]: nVidia Corporation MCP67 PCI Express 
Br

Bug#604080: Xen domU fails to boot after install

[Ian Campbell]

On Wed, 2011-02-16 at 00:50 +0100, Tech Nux wrote:
> Hi,
> 
> I found an easier solution, Xen dom0 on squeeze / DomU on lenny the
> dist-upgrade and reboot failed. :

Thanks.

This is a somewhat separate (although related) problem to the original
issue with installation.

The original issue was a complete lack of grub2 support in pygrub in
Lenny.

In this case it relates to unsupported syntax in the grub1 menu.lst
configuration file. This unusual syntax arises due to the grub packages'
attempt to ensure the upgrade goes smoothly.

If your dom0 supported grub2 then I think it would prefer the grub2
grub.cfg and you wouldn't see this issue.

Your workaround is reasonable.

Can you dig out the pygrub error code (in xend.log IIRC). Although I
doubt we will ever see this syntax again in future upgrades it would be
worth ensuring that pygrub handles it gracefully.

Ian.
> 
> First mount the /boot partition of your domU to the dom0 :
>  xm block-attach 0 phy:/dev/vm/squeeze xvda w
> mount /dev/xvda1 /mnt
> 
> Then edit /mnt/grub/menu.lst, and comment thoses line :
> 
> #title  Chainload into GRUB 2
> #root   (hd0,0)
> #kernel /grub/core.img
> #
> #title
> Ä
> #root
> #
> #title  When you have verified GRUB 2 works, you can use this
> command to
> #root
> #
> #title  complete the upgrade:  upgrade-from-grub-legacy
> #root
> #
> #title
> Ä
> #root
> 
> It seems Pygrub on lenny and squeeze doesn't understant this menu, so
> comment it. Umount partition and disk :
>  xm block-detach 0 xvda

-- 
Ian Campbell

Advertising is the rattling of a stick inside a swill bucket.
-- George Orwell




--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1297848874.21980.5832.ca...@zakaz.uk.xensource.com

Bug#613623: network-console: Cannot start with some locales (eg. sl_SI)

[Matej Bažec]

Package: network-console
Version: 1.27
Severity: normal
Tags: d-i l10n


The network-console can't be started (can't be selected from the d-i menu)
if the language is set to slovene. I have to choose a different language first.
Maybe it affects some other locale too..


-- System Information:
Debian Release: 6.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20110216083227.12034.49113.report...@fpp6588.fpp.uni-lj.si