Nabble - Debian Boot

Bug#558448: keyboard-configuration: Does not set right alt correctly.

2009-11-28T15:50:37Z

Package: keyboard-configuration
Version: 1.49
Severity: important

Hi,

It seems that the "AltGr key replacement" currently has no
effect. I've installed keyboard-configuration a few days
ago and at that time selected "The default for the keyboard
layout", and things kept working like they were, it still
acted like a right alt key.

Now I've booted in a new kernel and it acted like a left alt key.
So I've reconfigured it to set it to "Right Alt". But that
doesn't seem to have any effect, it still acts like a left alt
key. The config file /etc/default/keyboard says:
XKBMODEL="pc102"
XKBLAYOUT="us"
XKBVARIANT=""
XKBOPTIONS="lv3:ralt_switch,terminate:ctrl_alt_bksp"

Kurt

--
To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Bug#548837: closed by Anton Zinoviev (Bug#548837: fixed in console-setup 1.47)

2009-11-28T15:43:52Z

On Sat, Nov 28, 2009 at 7:22 PM, Anton Zinoviev <anton@...> wrote:

Maybe the selected layout doesn't support these symbols? Please send the
contents of /etc/default/keyboard and /etc/default/console-setup.

I found that the problem must be coming from usplash. The console font seems to be well set during boot, but near the end of the boot process the font appears to be reset. After removing usplash this does not happen anymore and the keyboard is well configured.

In any case (with or without usplash): I noticed that at a tty's login prompt (and only there), once I type an accented character (á, é, ...), a 'ç', an 'º' or an 'ª' (among others), I can't use the backspace key anymore. Instead, three lozengues are shown for each time I press the backspace key.
If logging in fails, the backspace key will be usable on the following login retries regardless of the characters typed. After a successful login, everything seems to be working well. This is probably not related to console-setup, but in that case I really don't know to which package I should report it. Even if this is related with console-setup, it's very likely that this should be reported as a new bug (?).

(...)

This bug is already reported (#377426). It is not related to
console-setup.

Thanks for pointing that out.

Thanks and regards,
Pitxyoki

Bug#558424: marked as done (console-setup does not honor video mode set by boot loader)

2009-11-28T12:57:04Z

Your message dated Sat, 28 Nov 2009 15:45:01 -0500 (EST)
with message-id <1226904549.6209581259441101183.JavaMail.root@...>
and subject line console-setup does not honor video mode set by boot loader
has caused the Debian Bug report #558424,
regarding console-setup does not honor video mode set by boot loader
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 owner@...
immediately.)

--
558424: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558424
Debian Bug Tracking System
Contact owner@... with problems

Package: console-setup
Version: 1.49

See Debian bug report 558414 against console-tools for more information.

The init script for console-setup, /etc/init.d/console-setup, when invoked
during boot-up, does not respect the video mode selected by the boot
loader or the font selected by console-tools.

I see, said the blind man, as he fell through the open man hole.

dpkg-reconfigure console-setup

did the trick. Everything is working as expected now.

[SRM] D-I: major update of choose-mirror for stable

2009-11-28T12:56:13Z

Hi,

I've just uploaded version 2.28lenny4 of choose-mirror for stable.
The new version includes major code changes which have been backported from
the version recently uploaded to unstable.

The changes are needed because previous versions of choose-mirror do not
support oldstable or archive.d.o, especially when installing in expert
mode, because the release selection dialog that is displayed only allows
selection of stable, testing and unstable [1]; it does not allow selection
of oldstable or selection based on codename.

Another issue with previous versions of choose-mirror is that if the
desired release is not available on the selected mirror, choose-mirror
will silently select the "next best" release that is available, which can
lead to unexpected results.

The new version is a *lot* more flexible in that regard and will display
both suite and codename in the selection dialog.

The backport is fairly large as some functions needed to be rewritten.
Changes in dialogs have been avoided in the backport in order not to
invalidate existing translations; exception is the addition of one string
for the suite "oldstable".

I have excluded a few of the cleanups that were included in the new
unstable version, but not all. Reason is that I judged it safer to
minimize the diff between the Lenny and Squeeze versions than to add
(artificial) changes to the backport to reduce the size of the diff
against the current version in stable.

The changes have been tested and reviewed extensively.

Please accept the new version for the next stable point release. Added
benefit is that the mirror list is updated to the current status.

Note that an upload of debian-installer for stable will be required to get
the changes included for all installation methods!

Unless there are objections I will also backport the changes for Etch as
that version has the same issues and I think it's worth having the better
support for installs from archive.d.o after Etch is moved there.

Cheers,
FJP

[1] The patch included in the previous stable update only partially fixed
this problem and has been reverted in the new version.

signature.asc (204 bytes) Download Attachment

Processed: Re: Bug#558386: keyboard-configuration: Keyboard map not recognized (Lenovo Thinkpad T61)

2009-11-28T12:48:10Z

Processing commands for control@...:

> reassign 558386 xkb-data 1.6-1
Bug #558386 [keyboard-configuration] keyboard-configuration: Keyboard map not recognized (Lenovo Thinkpad T61)
Bug reassigned from package 'keyboard-configuration' to 'xkb-data'.
Bug No longer marked as found in versions console-setup/1.49.
Bug #558386 [xkb-data] keyboard-configuration: Keyboard map not recognized (Lenovo Thinkpad T61)
Bug Marked as found in versions xkeyboard-config/1.6-1.
> thank you
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--
To UNSUBSCRIBE, email to debian-boot-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Bug#554196: [console-setup] Generic German keyboard cannot be setup to use AltGr key

2009-11-28T12:48:08Z

On Sat, Nov 28, 2009 at 02:32:37PM +0100, RalfGesellensetter wrote:
>
> Sorry for the delay, "@" etc. works now in KDE konsole, but still not in
> GTK applications like iceweasel.
>
> Please, find cached.kmap.gz attached.

Thank you.

I need to check whether cached.kmap.gz corresponds to your
configuration. For this I need to see the contents of
/etc/default/console-setup and /etc/default/keyboard (the last file will
exist only if the version of console-setup you use is 1.48 or next).

Anton Zinoviev

--
To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Processing of choose-mirror_2.28lenny4_amd64.changes

2009-11-28T12:43:36Z

choose-mirror_2.28lenny4_amd64.changes uploaded successfully to localhost
along with the files:
choose-mirror_2.28lenny4.dsc
choose-mirror_2.28lenny4.tar.gz
choose-mirror_2.28lenny4_all.udeb
choose-mirror-bin_2.28lenny4_amd64.udeb

Greetings,

Your Debian queue daemon (running on host ries.debian.org)

--
To UNSUBSCRIBE, email to debian-boot-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Bug#558386: keyboard-configuration: Keyboard map not recognized (Lenovo Thinkpad T61)

2009-11-28T12:41:50Z

reassign 558386 xkb-data 1.6-1
thank you

On Sat, Nov 28, 2009 at 11:53:56AM -0200, Renato S. Yamane wrote:
>
> On my last "aptitude upgrade", after restart the Debian Squeeze the
> keyboard map is not recognized anymore.
>
> My keyboard is pt-br (Lenovo Thinkpad T61), with "ç", and somekeys is
> not recognized anymore, such slash ("/").

The layout you need br(thinkpad) is not described in rules/base.xml.

Please open /etc/default/keyboard in a text editor and replace

XKBVARIANT="" or XKBVARIANT="abnt2"

by

XKBVARIANT="thinkpad"

Anton Zinoviev

--
To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Processing of choose-mirror_2.28lenny4_amd64.changes

2009-11-28T12:39:59Z

choose-mirror_2.28lenny4_amd64.changes uploaded successfully to ftp-master.debian.org
along with the files:
choose-mirror_2.28lenny4.dsc
choose-mirror_2.28lenny4.tar.gz
choose-mirror_2.28lenny4_all.udeb
choose-mirror-bin_2.28lenny4_amd64.udeb

Greetings,

Your Debian queue daemon (running on host kassia.debian.org)

--
To UNSUBSCRIBE, email to debian-boot-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: [RFC] Patch to disable GTK in installer images

2009-11-28T12:15:42Z

Hello Frans,

On Sat, Nov 28, 2009 at 6:09 PM, Frans Pop <elendil@...> wrote:

> On Saturday 28 November 2009, Otavio Salvador wrote:
>> I guess I did it but would be nice to have a review on the patch
>> before commiting it. My idea is to commit it and upload installer.
>> Once installer is built in all arches revert it back to force testing
>> of GTK frontend in daily images again.
>
> I suggest not removing the targets from the MEDIUM_SUPPORTED lines, but
> commenting them out (or maybe even better: duplicate the existing lines,
> comment one out and modify the other).
> In general I would not remove anything, but comment out lines instead (with
> an added comment why).

I removed then since it will be a patch added for a very small perid
of time and then a revert will be done. In fact I'll keep it reverted
here to push after we believe installer for A1 is done.

> I think the changes for xen are all wrong. In all cases you still need to
> define a TYPE, and for cdrom-xen.cfg you also still need EXTRATARGETS.
>
> You look to have completely missed the changes needed for
> i386/cdrom-xen.cfg and i386/netboot-xen.cfg.

Those was the ones I had doubt about. Thanks by clarify them. Will
look at it and send a new version.

> Did you actually try an all_build and check the results for i386 and amd64?
> Somehow I doubt it.

I did for amd64.

New patch later today or tomorrow.

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

--
To UNSUBSCRIBE, email to debian-boot-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: [RFC] Patch to disable GTK in installer images

2009-11-28T12:09:36Z

On Saturday 28 November 2009, Otavio Salvador wrote:
> I guess I did it but would be nice to have a review on the patch
> before commiting it. My idea is to commit it and upload installer.
> Once installer is built in all arches revert it back to force testing
> of GTK frontend in daily images again.

I suggest not removing the targets from the MEDIUM_SUPPORTED lines, but
commenting them out (or maybe even better: duplicate the existing lines,
comment one out and modify the other).
In general I would not remove anything, but comment out lines instead (with
an added comment why).

I think the changes for xen are all wrong. In all cases you still need to
define a TYPE, and for cdrom-xen.cfg you also still need EXTRATARGETS.

You look to have completely missed the changes needed for
i386/cdrom-xen.cfg and i386/netboot-xen.cfg.

Did you actually try an all_build and check the results for i386 and amd64?
Somehow I doubt it.

Cheers,
FJP

--
To UNSUBSCRIBE, email to debian-boot-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Bug#558424: console-setup does not honor video mode set by boot loader

2009-11-28T11:57:25Z

On Sat, Nov 28, 2009 at 02:25:34PM -0500, Stephen Powell wrote:
>
> See Debian bug report 558414 against console-tools for more information.
>
> The init script for console-setup, /etc/init.d/console-setup, when invoked
> during boot-up, does not respect the video mode selected by the boot
> loader

Did you configure console-setup to use a 8-pixel font?

> or the font selected by console-tools.

It doesn't have to. Console-setup is the program that configures the
console font and the console keyboard layout. Console-tools is
obsoleted and bugs of this package are rarely fixed. If you want only
one package to configure the font then install kbd instead of
console-tools.

Anton Zinoviev

--
To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Processed: Re: Bug#539108: bdf2psf does not handle empty bitmaps

2009-11-28T11:57:06Z

Processing commands for control@...:

> tags 539108 -moreinfo +confirmed
Bug #539108 [bdf2psf] bdf2psf does not handle empty bitmaps
Removed tag(s) moreinfo.
Bug #539108 [bdf2psf] bdf2psf does not handle empty bitmaps
Added tag(s) confirmed.
> thank you
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--
To UNSUBSCRIBE, email to debian-boot-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Bug#539108: bdf2psf does not handle empty bitmaps

2009-11-28T11:52:27Z

tags 539108 -moreinfo +confirmed
thank you

Thank you for your detailed report. I was able to reproduce the bug. I
don't know why during my previous test bdf2psf worked, maybe I had some
experimental development version installed.

On Sat, Nov 28, 2009 at 09:46:37PM +1100, Timothy Allen wrote:
>
> As a (presumably unrelated) aside, while I investigated the above I was
> trying to keep track of which versions of bdf2psf produced which PSF
> files, and discovered to my dismay that every run of bdf2psf produces
> different output, even using the same version with the same input files
> on the same machine.

This is normal because bdf2psf fills the unused positions in the font
with random noise (this is better than to keep these positions empty
because it helps to detect some bugs).

Anton Zinoviev

--
To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Bug#558424: console-setup does not honor video mode set by boot loader

2009-11-28T11:25:34Z

Package: console-setup
Version: 1.49

See Debian bug report 558414 against console-tools for more information.

The init script for console-setup, /etc/init.d/console-setup, when invoked
during boot-up, does not respect the video mode selected by the boot
loader or the font selected by console-tools.

--
To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Bug#548837: closed by Anton Zinoviev (Bug#548837: fixed in console-setup 1.47)

2009-11-28T11:22:56Z

On Sat, Nov 28, 2009 at 04:44:35PM +0000, Luís Picciochi Oliveira wrote:
>
> After doing "dpkg-reconfigure console-setup" and just going forward with the
> options (not changing anything), the keyboard is well recognized. However,
> after rebooting some characters are again not recognized (such as 'ç', º or
> ª).

Maybe the selected layout doesn't support these symbols? Please send the
contents of /etc/default/keyboard and /etc/default/console-setup.

> Also, under the ttys and X, the euro (€) and dollar ($) signs that are
> present above the arrow keys are still not recognized and still produce the
> same effect on /var/log/Xorg.0.log that I reported earlier.

This bug is already reported (#377426). It is not related to
console-setup. In /usr/share/hotkey-setup/acer-aspire-1600.hk you will
find the following commented lines:

#setkeycodes e033 $KEY_EURO # '€' hard to do out-of-the-box
#setkeycodes e034 $KEY_DOLLAR # '$' hard to do out-of-the-box

Anton Zinoviev

--
To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[RFC] Patch to disable GTK in installer images

2009-11-28T11:15:35Z

Hello,

To avoid delaying the installer release we intend to disable the GTK
frontend for this Alpha1 release. So far, I started to work on the
patch for it.

We need to disable it at:

- amd64
- i386
- powerpc

I guess I did it but would be nice to have a review on the patch
before commiting it. My idea is to commit it and upload installer.
Once installer is built in all arches revert it back to force testing
of GTK frontend in daily images again.

Comments?

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

[0001-Disable-GTK-based-images-due-557387.-This-ought-to-b.patch]

From 0001b43a2dd30d59c645aeaa00c561d720122510 Mon Sep 17 00:00:00 2001 From: Otavio Salvador <otavio@...> Date: Wed, 25 Nov 2009 17:23:25 -0200 Subject: [PATCH] Disable GTK+ based images due #557387. This ought to be reverted once GTK+ DFB backend is fixed. --- installer/build/config/amd64.cfg | 2 +- installer/build/config/amd64/cdrom-xen.cfg | 6 +----- installer/build/config/amd64/cdrom.cfg | 2 +- installer/build/config/amd64/hd-media.cfg | 7 +------ installer/build/config/amd64/netboot-xen.cfg | 8 +++----- installer/build/config/i386.cfg | 2 +- installer/build/config/powerpc/powerpc.cfg | 2 +- installer/build/config/powerpc/powerpc64.cfg | 2 +- installer/debian/changelog | 4 ++++ 9 files changed, 14 insertions(+), 21 deletions(-) diff --git a/installer/build/config/amd64.cfg b/installer/build/config/amd64.cfg index da8f361..22e6baa 100644 --- a/installer/build/config/amd64.cfg +++ b/installer/build/config/amd64.cfg @@ -1,4 +1,4 @@ -MEDIUM_SUPPORTED = cdrom cdrom-xen netboot netboot-gtk netboot-xen hd-media +MEDIUM_SUPPORTED = cdrom cdrom-xen netboot netboot-xen hd-media MEDIUM_SUPPORTED_EXTRA = monolithic # The version of the kernel to use. diff --git a/installer/build/config/amd64/cdrom-xen.cfg b/installer/build/config/amd64/cdrom-xen.cfg index 97b4c32..dd87293 100644 --- a/installer/build/config/amd64/cdrom-xen.cfg +++ b/installer/build/config/amd64/cdrom-xen.cfg @@ -1,5 +1,3 @@ -TYPE=cdrom/gtk - EXTRANAME=cdrom/xen/ MANIFEST-KERNEL = "kernel image for installing under Xen" @@ -8,6 +6,4 @@ MANIFEST-XENCFG = "example Xen configuration" TARGET = $(KERNEL) $(INITRD) xen_config SYMLINK_KERNEL = ../vmlinuz -SYMLINK_INITRD = ../gtk/initrd.gz - -EXTRATARGETS = build_cdrom_gtk +SYMLINK_INITRD = ../initrd.gz diff --git a/installer/build/config/amd64/cdrom.cfg b/installer/build/config/amd64/cdrom.cfg index 5678ba5..99026cd 100644 --- a/installer/build/config/amd64/cdrom.cfg +++ b/installer/build/config/amd64/cdrom.cfg @@ -1,5 +1,5 @@ # el-torito is too large at the moment, so is disabled. -FLAVOUR_SUPPORTED = isolinux gtk #el-torito +FLAVOUR_SUPPORTED = isolinux #gtk #el-torito MEDIA_TYPE = CD-ROM diff --git a/installer/build/config/amd64/hd-media.cfg b/installer/build/config/amd64/hd-media.cfg index f145d2d..982286c 100644 --- a/installer/build/config/amd64/hd-media.cfg +++ b/installer/build/config/amd64/hd-media.cfg @@ -1,4 +1,4 @@ -FLAVOUR_SUPPORTED = "" gtk +FLAVOUR_SUPPORTED = "" # Not really a floppy, this is a 239 mb image, large enough to put a # netinst iso in, and small enough to fit on a mid-range memory stick, @@ -11,11 +11,6 @@ MEDIA_TYPE = bootable drive GZIPPED = .gz EXTRANAME = hd-media/ -# Add the gtk images on to the bootable image. -EXTRATARGETS = build_hd-media_gtk -INITRD_GTK = dest/hd-media/gtk/initrd.gz -TARGET = $(KERNEL) $(INITRD) $(BOOT) - MANIFEST-BOOT = "256 mb image (compressed) for USB memory stick" MANIFEST-INITRD = "for use on USB memory sticks" MANIFEST-KERNEL = "for use on USB memory sticks" diff --git a/installer/build/config/amd64/netboot-xen.cfg b/installer/build/config/amd64/netboot-xen.cfg index 075af41..cc8c28e 100644 --- a/installer/build/config/amd64/netboot-xen.cfg +++ b/installer/build/config/amd64/netboot-xen.cfg @@ -1,5 +1,3 @@ -TYPE=netboot/gtk - EXTRANAME=netboot/xen/ MANIFEST-KERNEL = "kernel image for installing under Xen" @@ -7,7 +5,7 @@ MANIFEST-INITRD = "initrd for installing under Xen" MANIFEST-XENCFG = "example Xen configuration" TARGET = $(KERNEL) $(INITRD) xen_config -SYMLINK_KERNEL = ../gtk/debian-installer/amd64/linux -SYMLINK_INITRD = ../gtk/debian-installer/amd64/initrd.gz +SYMLINK_KERNEL = ../debian-installer/amd64/linux +SYMLINK_INITRD = ../debian-installer/amd64/initrd.gz -EXTRATARGETS = build_netboot-gtk +EXTRATARGETS = build_netboot diff --git a/installer/build/config/i386.cfg b/installer/build/config/i386.cfg index 686ef0b..76fc0ea 100644 --- a/installer/build/config/i386.cfg +++ b/installer/build/config/i386.cfg @@ -1,4 +1,4 @@ -MEDIUM_SUPPORTED = cdrom cdrom-xen netboot netboot-gtk netboot-xen hd-media #floppy +MEDIUM_SUPPORTED = cdrom cdrom-xen netboot netboot-xen hd-media #floppy MEDIUM_SUPPORTED_EXTRA = monolithic # The version of the kernel to use. diff --git a/installer/build/config/powerpc/powerpc.cfg b/installer/build/config/powerpc/powerpc.cfg index 31d24c2..9f93120 100644 --- a/installer/build/config/powerpc/powerpc.cfg +++ b/installer/build/config/powerpc/powerpc.cfg @@ -1,4 +1,4 @@ -MEDIUM_SUPPORTED = cdrom netboot netboot-gtk hd-media # floppy +MEDIUM_SUPPORTED = cdrom netboot hd-media # floppy MEDIUM_SUPPORTED_EXTRA = monolithic # The version of the kernel to use. diff --git a/installer/build/config/powerpc/powerpc64.cfg b/installer/build/config/powerpc/powerpc64.cfg index a9d398b..b2e9f16 100644 --- a/installer/build/config/powerpc/powerpc64.cfg +++ b/installer/build/config/powerpc/powerpc64.cfg @@ -1,4 +1,4 @@ -MEDIUM_SUPPORTED = cdrom netboot netboot-gtk +MEDIUM_SUPPORTED = cdrom netboot MEDIUM_SUPPORTED_EXTRA = monolithic # The version of the kernel to use. diff --git a/installer/debian/changelog b/installer/debian/changelog index 6f03823..21deb9c 100644 --- a/installer/debian/changelog +++ b/installer/debian/changelog @@ -152,6 +152,10 @@ debian-installer (2009xxxx) UNRELEASED; urgency=low [ Joey Hess ] * Remove upx from build-deps, has not been used for over a year. + [ Otavio Salvador ] + * Disable GTK+ based images due #557387. This ought to be reverted + once GTK+ DFB backend is fixed. + -- Frans Pop <fjp@...> Sun, 08 Nov 2009 04:17:16 +0100 debian-installer (20090123) unstable; urgency=low -- 1.6.5.2.155.gbb47

Processed: reassign 548589 to libgtk-directfb-2.0-0, reassign 551072 to libgtk-directfb-2.0-0 ...

2009-11-28T09:03:10Z

Processing commands for control@...:

> reassign 548589 libgtk-directfb-2.0-0
Bug #548589 [installation-reports] installation-reports: [G-I] graphical ui does not start
Bug reassigned from package 'installation-reports' to 'libgtk-directfb-2.0-0'.
> reassign 551072 libgtk-directfb-2.0-0
Bug #551072 [debian-installer] Graphical install fails
Bug reassigned from package 'debian-installer' to 'libgtk-directfb-2.0-0'.
> forcemerge 548589 551072 557387
Bug#548589: installation-reports: [G-I] graphical ui does not start
Bug#551072: Graphical install fails
Bug#557387: debian-installer: graphical installer doesn't start
Forcibly Merged 548589 551072 557387.

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--
To UNSUBSCRIBE, email to debian-boot-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Processed: tagging 480899

2009-11-28T08:48:12Z

Processing commands for control@...:

> tags 480899 + sid squeeze
Bug #480899 {Done: Colin Watson <cjwatson@...>} [cdebconf] incomplete split prevents installation of cdebconf-gtk
Added tag(s) squeeze and sid.
>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--
To UNSUBSCRIBE, email to debian-boot-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Bug#548837: closed by Anton Zinoviev (Bug#548837: fixed in console-setup 1.47)

2009-11-28T08:44:35Z

On Mon, Nov 16, 2009 at 9:42 PM, Debian Bug Tracking System <owner@...> wrote:

(...)

---------- Forwarded message ----------
From: Anton Zinoviev <zinoviev@...>
To: 548837-close@...
Date: Mon, 16 Nov 2009 21:40:10 +0000
Subject: Bug#548837: fixed in console-setup 1.47
Source: console-setup
Source-Version: 1.47

We believe that the bug you reported is fixed in the latest version of
console-setup, which is due to be installed in the Debian FTP archive:

This is not fixed as of console-setup 1.49.

After doing "dpkg-reconfigure console-setup" and just going forward with the options (not changing anything), the keyboard is well recognized. However, after rebooting some characters are again not recognized (such as 'ç', º or ª).

Also, under the ttys and X, the euro (€) and dollar ($) signs that are present above the arrow keys are still not recognized and still produce the same effect on /var/log/Xorg.0.log that I reported earlier.

Regards,
Pitxyoki

Bug#558386: keyboard-configuration: Keyboard map not recognized (Lenovo Thinkpad T61)

2009-11-28T05:53:56Z

Package: keyboard-configuration
Version: 1.49
Severity: normal

On my last "aptitude upgrade", after restart the Debian Squeeze the keyboard map is not recognized anymore.
My keyboard is pt-br (Lenovo Thinkpad T61), with "ç", and somekeys is not recognized anymore, such slash ("/").

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

Kernel: Linux 2.6.31.5 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages keyboard-configuration depends on:
ii debconf [debconf-2.0] 1.5.28 Debian configuration management sy

keyboard-configuration recommends no packages.

keyboard-configuration suggests no packages.

-- debconf information:
keyboard-configuration/layout:
keyboard-configuration/variant: Brazil
debian-installer/console-setup-udeb/title:
keyboard-configuration/unsupported_options: true
keyboard-configuration/ctrl_alt_bksp: false
keyboard-configuration/variantcode:
keyboard-configuration/other:
keyboard-configuration/optionscode:
keyboard-configuration/modelcode: abnt2
keyboard-configuration/unsupported_config_options: true
keyboard-configuration/unsupported_config_layout: true
keyboard-configuration/toggle: No toggling
keyboard-configuration/compose: No compose key
keyboard-configuration/switch: No temporary switch
keyboard-configuration/altgr: The default for the keyboard layout
keyboard-configuration/unsupported_layout: true
keyboard-configuration/model: IBM ThinkPad R60/T60/R61/T61
keyboard-configuration/layoutcode: br

--
To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Bug#554196: [console-setup] Generic German keyboard cannot be setup to use AltGr key

2009-11-28T05:32:37Z

Am Mittwoch, 11. November 2009 schrieb Anton Zinoviev:

> Please send the contents of your files /etc/default/console-setup and
> /etc/console-setup/cached.kmap.gz and the output of the command
> 'locale'.
>

Sorry for the delay, "@" etc. works now in KDE konsole, but still not in
GTK applications like iceweasel.

Please, find cached.kmap.gz attached.

$locale returns:

LANG=de_DE.UTF-8
LANGUAGE=
LC_CTYPE="de_DE.UTF-8"
LC_NUMERIC="de_DE.UTF-8"
LC_TIME="de_DE.UTF-8"
LC_COLLATE="de_DE.UTF-8"
LC_MONETARY="de_DE.UTF-8"
LC_MESSAGES="de_DE.UTF-8"
LC_PAPER="de_DE.UTF-8"
LC_NAME="de_DE.UTF-8"
LC_ADDRESS="de_DE.UTF-8"
LC_TELEPHONE="de_DE.UTF-8"
LC_MEASUREMENT="de_DE.UTF-8"
LC_IDENTIFICATION="de_DE.UTF-8"
LC_ALL=

cached.kmap.gz (5K) Download Attachment

Bug#539108: bdf2psf does not handle empty bitmaps

2009-11-28T02:46:37Z

Apologies for the questions in my previous mail, I wasn't thinking
properly.

In the interests of Science, I tried the same experiment on another
computer I have, running Ubuntu 9.10. For some reason, the only
version of bdf2psf in the Ubuntu archives is "1.34ubuntu4", which is
older than the original Debian version I tested with - and yet, the
Ubuntu version works fine: it produces PSF files with empty U+0020
glyphs. I checked the Ubuntu patches linked from
http://packages.qa.debian.org/c/console-setup.html, and it seems Ubuntu
doesn't have any special patches applied to bdf2psf.

I also note that since I filed this bug, Testing has received an
updated version of bdf2psf, version 1.49. Sadly, this behaves exactly
the same as the the version I filed this bug with, 1.44.

I tried copying the 1.34 version to my Debian machine and running it
there, and it still produced a properly working PSF file. So, some
change between 1.34 and 1.44 seems to have broken handling of
degenerate glyphs.

Although I don't know Perl, I spotted a likely-looking change in the
difference between those two versions, and when I apply the attached
patch to a copy of bdf2psf from 1.49, the patched version works
properly.

As a (presumably unrelated) aside, while I investigated the above I was
trying to keep track of which versions of bdf2psf produced which PSF
files, and discovered to my dismay that every run of bdf2psf produces
different output, even using the same version with the same input files
on the same machine. Diffing the binary files, it seems that the
segment from 0x0A05 to 0x0D04 (inclusive) changes all the time - I'm
not sure what's stored there, but it's obviously quite volatile. I
can't see any provision in the PSF file format for a 'creation' time
stamp, so I doubt it's that, and since bdf2psf isn't written in C, it's
unlikely to be un-initialised memory.

--- /usr/bin/bdf2psf 2009-11-20 23:56:56.000000000 +1100 +++ bdf2psf-debian 2009-11-28 21:39:39.000000000 +1100 @@ -376,25 +376,23 @@ next; } if (/^ENDCHAR/) { - if ($rows > 0) { - $rows == $height - ($beforebox + $afterbox) / matrix_row_size () - or die ("$0: $bdf: invalid number of rows $rows " - ."at line $current_line\n"); - if ($u == -123456) { - die ("$0: $bdf: missing ENCODING before ENDCHAR " - ."at line $current_line\n"); + $rows == $height - ($beforebox + $afterbox) / matrix_row_size () + or die ("$0: $bdf: invalid number of rows $rows " + ."at line $current_line\n"); + if ($u == -123456) { + die ("$0: $bdf: missing ENCODING before ENDCHAR " + ."at line $current_line\n"); + } + if (! defined $gliphs{$u}) { + if ($beforebox < 0) { + @gliph_bytes = @gliph_bytes[-$beforebox..$#gliph_bytes]; } - if (! defined $gliphs{$u}) { - if ($beforebox < 0) { - @gliph_bytes = @gliph_bytes[-$beforebox..$#gliph_bytes]; - } - if ($afterbox < 0) { - @gliph_bytes = @gliph_bytes[0 .. $#gliph_bytes+$afterbox]; - } - $gliphs{$u} = [ (0) x $beforebox, - @gliph_bytes, - (0) x $afterbox]; + if ($afterbox < 0) { + @gliph_bytes = @gliph_bytes[0 .. $#gliph_bytes+$afterbox]; } + $gliphs{$u} = [ (0) x $beforebox, + @gliph_bytes, + (0) x $afterbox]; } } if (/^ENDFONT$/) {

Bug#539108: bdf2psf does not handle empty bitmaps

2009-11-28T00:40:24Z

On Wed, Nov 18, 2009 at 08:46:37PM +0200, Anton Zinoviev wrote:

> On Sat, Nov 14, 2009 at 10:56:34PM +1100, Tim Allen wrote:
> > On Wed, Nov 11, 2009 at 06:40:19PM +0200, Anton Zinoviev wrote:
> > > I am unable to reproduce this - the space symbol in the psf font
> > > I obtain is correct. Can you attach your vera-mono-12.bdf and
> > > vera-mono-12.psf?
> >
> > Please find both attached.
>
> Unfortunately again I am unable to reproduce this. I used the very same
> command you put in your bug report and the result is a font with proper
> space character:
>
> bdf2psf vera-mono-12.bdf /usr/share/bdf2psf/standard.equivalents /usr/share/bdf2psf/required.set+/usr/share/bdf2psf/useful.set 256 vera-mono-12my.psf
>
> It is true that I am using a newer version of bdf2psf but I think there
> were no changes in the bdf2psf script since version 1.44 you reported.
> Are you using the same command in order to convert the font?

When I generated the vera-mono-12.psf that I attached,
I copied-and-pasted the command directly from this bug report.

When you use that command to generate a .psf from the .bdf attached to
the bug, does your generated .psf match the .psf attached to the bug?

When you load the font, are you using the default VGA text console, or
a frame-buffer console?

--
To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Bug#557296: debootstrap: Use dpkg-deb instead of ar when available

2009-11-27T12:41:59Z

Hi!

On Sun, 2009-11-22 at 19:53:29 -0200, Otavio Salvador wrote:
> debootstrap don't _need_ to support all features of all valid .debs
> but the features accepted in base packages. This doesn't mean we
> shouldn't add features when possible but it is not a requirement for
> debootstrap POV.

One of my initial arguments was that debootstrap can be easily used
with stuff other than Debian, were those policies/restrictions might
not apply.

> On Sun, Nov 22, 2009 at 4:51 AM, Guillem Jover <guillem@...> wrote:
> > Right. Additionally an option could be added to explicitly choose the
> > extractor, to ease testing.
>
> This indeed is a possible solution to be easier to test it. As Frans
> pointed out d-i is one "tester" of "basic *nix tools backend" already.

I went ahead and implemented it as a separate patch, take it if you
want, or leave it out if you wish.

> > The extractor choosed could be output to avoid that kind of situation.
> > I can amend the patch adding that if desired.
>
> Ok, you convinced me. Could you amend the patch and send it for review?

I'm attaching the three patches, the first one has not changed, but
adding it for convenience.

thanks,
guillem

>From 0f78dd071235cbcbc9d2d27a74a76c673e06b4a8 Mon Sep 17 00:00:00 2001 From: Guillem Jover <guillem@...> Date: Fri, 20 Nov 2009 19:51:44 +0100 Subject: [PATCH 1/3] Refactor deb extractors into two new functions --- functions | 43 ++++++++++++++++++++++++++------------ scripts/debian/potato | 6 +---- scripts/debian/sarge | 6 +---- scripts/debian/sarge.buildd | 6 +---- scripts/debian/sarge.fakechroot | 6 +---- scripts/debian/sid | 6 +---- scripts/debian/woody | 6 +---- scripts/debian/woody.buildd | 6 +---- scripts/ubuntu/breezy | 6 +---- scripts/ubuntu/dapper | 6 +---- scripts/ubuntu/edgy | 6 +---- scripts/ubuntu/feisty | 6 +---- scripts/ubuntu/gutsy | 6 +---- scripts/ubuntu/hoary | 6 +---- scripts/ubuntu/hoary.buildd | 6 +---- scripts/ubuntu/warty | 6 +---- scripts/ubuntu/warty.buildd | 6 +---- 17 files changed, 45 insertions(+), 94 deletions(-) diff --git a/functions b/functions index e832d70..66021e8 100644 --- a/functions +++ b/functions @@ -717,27 +717,42 @@ get_debs () { ################################################################ extraction +extract_deb_field () { + local pkg="$1" + local field="$2" + + ar -p "$pkg" control.tar.gz | zcat | + tar -O -xf - control ./control 2>/dev/null | + grep -i "^$field:" | sed -e 's/[^:]*: *//' | head -n 1 +} + +extract_deb_data () { + local pkg="$1" + local tarball=$(ar -t "$pkg" | grep "^data.tar.[bgx]z") + + case "$tarball" in + data.tar.gz) cat_cmd=zcat ;; + data.tar.bz2) cat_cmd=bzcat ;; + data.tar.xz) cat_cmd=xzcat ;; + *) error 1 UNKNOWNDATACOMP "Unknown compression type for %s in %s" "$tarball" "$pkg" ;; + esac + + if type $cat_cmd >/dev/null 2>&1; then + ar -p "$pkg" data.tar.gz | $cat_cmd | tar -xf - + else + error 1 UNPACKCMDUNVL "The $cat_cmd is not available on the system" + fi +} + extract () { ( cd "$TARGET" - local p=0 tarball cat_cmd + local p=0 cat_cmd for pkg in $(debfor "$@"); do p="$(($p + 1))" progress "$p" "$#" EXTRACTPKGS "Extracting packages" packagename="$(echo "$pkg" | sed 's,^.*/,,;s,_.*$,,')" info EXTRACTING "Extracting %s..." "$packagename" - tarball=$(ar -t "./$pkg" | grep "^data.tar.[bgx]z") - case "$tarball" in - data.tar.gz) cat_cmd=zcat ;; - data.tar.bz2) cat_cmd=bzcat ;; - data.tar.xz) cat_cmd=xzcat ;; - *) error 1 UNKNOWNDATACOMP "Unknown compression type for %s in %s" "$tarball" "$pkg" ;; - esac - - if type $cat_cmd >/dev/null 2>&1; then - ar -p "./$pkg" data.tar.gz | $cat_cmd | tar -xf - - else - error 1 UNPACKCMDUNVL "The $cat_cmd is not available on the system" - fi + extract_deb_data "./$pkg" done ); } diff --git a/scripts/debian/potato b/scripts/debian/potato index 3204c7d..304cbe0 100644 --- a/scripts/debian/potato +++ b/scripts/debian/potato @@ -43,11 +43,7 @@ first_stage_install () { x_feign_install () { local pkg=$1 local deb="$(debfor $pkg)" - local ver="$( - ar -p "$TARGET/$deb" control.tar.gz | zcat | - tar -O -xf - control ./control 2>/dev/null | - grep -i ^Version: | sed -e 's/[^:]*: *//' | head -n 1 - )" + local ver="$(extract_deb_field "$TARGET/$deb" Version)" mkdir -p "$TARGET/var/lib/dpkg/info" diff --git a/scripts/debian/sarge b/scripts/debian/sarge index e49a490..252e180 100644 --- a/scripts/debian/sarge +++ b/scripts/debian/sarge @@ -111,11 +111,7 @@ first_stage_install () { x_feign_install () { local pkg="$1" local deb="$(debfor $pkg)" - local ver="$( - ar -p "$TARGET/$deb" control.tar.gz | zcat | - tar -O -xf - control ./control 2>/dev/null | - grep -i ^Version: | sed -e 's/[^:]*: *//' | head -n 1 - )" + local ver="$(extract_deb_field "$TARGET/$deb" Version)" mkdir -p "$TARGET/var/lib/dpkg/info" diff --git a/scripts/debian/sarge.buildd b/scripts/debian/sarge.buildd index 0b9ad9a..249a035 100644 --- a/scripts/debian/sarge.buildd +++ b/scripts/debian/sarge.buildd @@ -72,11 +72,7 @@ first_stage_install () { x_feign_install () { local pkg="$1" local deb="$(debfor $pkg)" - local ver="$( - ar -p "$TARGET/$deb" control.tar.gz | zcat | - tar -O -xf - control ./control 2>/dev/null | - grep -i ^Version: | sed -e 's/[^:]*: *//' | head -n 1 - )" + local ver="$(extract_deb_field "$TARGET/$deb" Version)" mkdir -p "$TARGET/var/lib/dpkg/info" diff --git a/scripts/debian/sarge.fakechroot b/scripts/debian/sarge.fakechroot index 36234fa..2fe4a38 100644 --- a/scripts/debian/sarge.fakechroot +++ b/scripts/debian/sarge.fakechroot @@ -77,11 +77,7 @@ first_stage_install () { x_feign_install () { local pkg="$1" local deb="$(debfor $pkg)" - local ver="$( - ar -p "$TARGET/$deb" control.tar.gz | zcat | - tar -O -xf - control ./control 2>/dev/null | - grep -i ^Version: | sed -e 's/[^:]*: *//' | head -n 1 - )" + local ver="$(extract_deb_field "$TARGET/$deb" Version)" mkdir -p "$TARGET/var/lib/dpkg/info" diff --git a/scripts/debian/sid b/scripts/debian/sid index 59e70fd..50a9f50 100644 --- a/scripts/debian/sid +++ b/scripts/debian/sid @@ -59,11 +59,7 @@ first_stage_install () { x_feign_install () { local pkg="$1" local deb="$(debfor $pkg)" - local ver="$( - ar -p "$TARGET/$deb" control.tar.gz | zcat | - tar -O -xf - control ./control 2>/dev/null | - grep -i ^Version: | sed -e 's/[^:]*: *//' | head -n 1 - )" + local ver="$(extract_deb_field "$TARGET/$deb" Version)" mkdir -p "$TARGET/var/lib/dpkg/info" diff --git a/scripts/debian/woody b/scripts/debian/woody index 66a1261..d174be8 100644 --- a/scripts/debian/woody +++ b/scripts/debian/woody @@ -97,11 +97,7 @@ first_stage_install () { x_feign_install () { local pkg="$1" local deb="$(debfor $pkg)" - local ver="$( - ar -p "$TARGET/$deb" control.tar.gz | zcat | - tar -O -xf - control ./control 2>/dev/null | - grep -i ^Version: | sed -e 's/[^:]*: *//' | head -n 1 - )" + local ver="$(extract_deb_field "$TARGET/$deb" Version)" mkdir -p "$TARGET/var/lib/dpkg/info" diff --git a/scripts/debian/woody.buildd b/scripts/debian/woody.buildd index 8485135..06cb8e3 100644 --- a/scripts/debian/woody.buildd +++ b/scripts/debian/woody.buildd @@ -72,11 +72,7 @@ first_stage_install () { x_feign_install () { local pkg="$1" local deb="$(debfor $pkg)" - local ver="$( - ar -p "$TARGET/$deb" control.tar.gz | zcat | - tar -O -xf - control ./control 2>/dev/null | - grep -i ^Version: | sed -e 's/[^:]*: *//' | head -n 1 - )" + local ver="$(extract_deb_field "$TARGET/$deb" Version)" mkdir -p "$TARGET/var/lib/dpkg/info" diff --git a/scripts/ubuntu/breezy b/scripts/ubuntu/breezy index f445598..2646ca2 100644 --- a/scripts/ubuntu/breezy +++ b/scripts/ubuntu/breezy @@ -49,11 +49,7 @@ first_stage_install () { x_feign_install () { local pkg="$1" local deb="$(debfor $pkg)" - local ver="$( - ar -p "$TARGET/$deb" control.tar.gz | zcat | - tar -O -xf - control ./control 2>/dev/null | - grep -i ^Version: | sed -e 's/[^:]*: *//' | head -n 1 - )" + local ver="$(extract_deb_field "$TARGET/$deb" Version)" mkdir -p "$TARGET/var/lib/dpkg/info" diff --git a/scripts/ubuntu/dapper b/scripts/ubuntu/dapper index 7f88d55..e57680a 100644 --- a/scripts/ubuntu/dapper +++ b/scripts/ubuntu/dapper @@ -56,11 +56,7 @@ first_stage_install () { x_feign_install () { local pkg="$1" local deb="$(debfor $pkg)" - local ver="$( - ar -p "$TARGET/$deb" control.tar.gz | zcat | - tar -O -xf - control ./control 2>/dev/null | - grep -i ^Version: | sed -e 's/[^:]*: *//' | head -n 1 - )" + local ver="$(extract_deb_field "$TARGET/$deb" Version)" mkdir -p "$TARGET/var/lib/dpkg/info" diff --git a/scripts/ubuntu/edgy b/scripts/ubuntu/edgy index 0dbc5dc..483e992 100644 --- a/scripts/ubuntu/edgy +++ b/scripts/ubuntu/edgy @@ -66,11 +66,7 @@ first_stage_install () { x_feign_install () { local pkg="$1" local deb="$(debfor $pkg)" - local ver="$( - ar -p "$TARGET/$deb" control.tar.gz | zcat | - tar -O -xf - control ./control 2>/dev/null | - grep -i ^Version: | sed -e 's/[^:]*: *//' | head -n 1 - )" + local ver="$(extract_deb_field "$TARGET/$deb" Version)" mkdir -p "$TARGET/var/lib/dpkg/info" diff --git a/scripts/ubuntu/feisty b/scripts/ubuntu/feisty index 4036828..0b98170 100644 --- a/scripts/ubuntu/feisty +++ b/scripts/ubuntu/feisty @@ -66,11 +66,7 @@ first_stage_install () { x_feign_install () { local pkg="$1" local deb="$(debfor $pkg)" - local ver="$( - ar -p "$TARGET/$deb" control.tar.gz | zcat | - tar -O -xf - control ./control 2>/dev/null | - grep -i ^Version: | sed -e 's/[^:]*: *//' | head -n 1 - )" + local ver="$(extract_deb_field "$TARGET/$deb" Version)" mkdir -p "$TARGET/var/lib/dpkg/info" diff --git a/scripts/ubuntu/gutsy b/scripts/ubuntu/gutsy index 37d4b53..ba2a3f8 100644 --- a/scripts/ubuntu/gutsy +++ b/scripts/ubuntu/gutsy @@ -66,11 +66,7 @@ first_stage_install () { x_feign_install () { local pkg="$1" local deb="$(debfor $pkg)" - local ver="$( - ar -p "$TARGET/$deb" control.tar.gz | zcat | - tar -O -xf - control ./control 2>/dev/null | - grep -i ^Version: | sed -e 's/[^:]*: *//' | head -n 1 - )" + local ver="$(extract_deb_field "$TARGET/$deb" Version)" mkdir -p "$TARGET/var/lib/dpkg/info" diff --git a/scripts/ubuntu/hoary b/scripts/ubuntu/hoary index 7944999..e5fe9fc 100644 --- a/scripts/ubuntu/hoary +++ b/scripts/ubuntu/hoary @@ -70,11 +70,7 @@ first_stage_install () { x_feign_install () { local pkg="$1" local deb="$(debfor $pkg)" - local ver="$( - ar -p "$TARGET/$deb" control.tar.gz | zcat | - tar -O -xf - control ./control 2>/dev/null | - grep -i ^Version: | sed -e 's/[^:]*: *//' | head -n 1 - )" + local ver="$(extract_deb_field "$TARGET/$deb" Version)" mkdir -p "$TARGET/var/lib/dpkg/info" diff --git a/scripts/ubuntu/hoary.buildd b/scripts/ubuntu/hoary.buildd index 2596086..afb0904 100644 --- a/scripts/ubuntu/hoary.buildd +++ b/scripts/ubuntu/hoary.buildd @@ -66,11 +66,7 @@ first_stage_install () { x_feign_install () { local pkg="$1" local deb="$(debfor $pkg)" - local ver="$( - ar -p "$TARGET/$deb" control.tar.gz | zcat | - tar -O -xf - control ./control 2>/dev/null | - grep -i ^Version: | sed -e 's/[^:]*: *//' | head -n 1 - )" + local ver="$(extract_deb_field "$TARGET/$deb" Version)" mkdir -p "$TARGET/var/lib/dpkg/info" diff --git a/scripts/ubuntu/warty b/scripts/ubuntu/warty index 0e16a62..e21a6d8 100644 --- a/scripts/ubuntu/warty +++ b/scripts/ubuntu/warty @@ -58,11 +58,7 @@ first_stage_install () { x_feign_install () { local pkg="$1" local deb="$(debfor $pkg)" - local ver="$( - ar -p "$TARGET/$deb" control.tar.gz | zcat | - tar -O -xf - control ./control 2>/dev/null | - grep -i ^Version: | sed -e 's/[^:]*: *//' | head -n 1 - )" + local ver="$(extract_deb_field "$TARGET/$deb" Version)" mkdir -p "$TARGET/var/lib/dpkg/info" diff --git a/scripts/ubuntu/warty.buildd b/scripts/ubuntu/warty.buildd index b980e45..165377e 100644 --- a/scripts/ubuntu/warty.buildd +++ b/scripts/ubuntu/warty.buildd @@ -66,11 +66,7 @@ first_stage_install () { x_feign_install () { local pkg="$1" local deb="$(debfor $pkg)" - local ver="$( - ar -p "$TARGET/$deb" control.tar.gz | zcat | - tar -O -xf - control ./control 2>/dev/null | - grep -i ^Version: | sed -e 's/[^:]*: *//' | head -n 1 - )" + local ver="$(extract_deb_field "$TARGET/$deb" Version)" mkdir -p "$TARGET/var/lib/dpkg/info" -- 1.6.5.3

>From 863fb59476947ef125b24ad89afc040301938b96 Mon Sep 17 00:00:00 2001 From: Guillem Jover <guillem@...> Date: Fri, 20 Nov 2009 21:25:32 +0100 Subject: [PATCH 2/3] Use dpkg-deb if available instead of ar --- debian/control | 2 +- debootstrap | 2 ++ functions | 41 +++++++++++++++++++++++++++++++++++++++-- 3 files changed, 42 insertions(+), 3 deletions(-) diff --git a/debian/control b/debian/control index 577b759..01e7d2d 100644 --- a/debian/control +++ b/debian/control @@ -9,7 +9,7 @@ Vcs-Svn: svn://svn.debian.org/d-i/trunk/packages/debootstrap Package: debootstrap Architecture: all -Depends: wget, binutils +Depends: wget Recommends: gnupg Description: Bootstrap a basic Debian system debootstrap is used to create a Debian base system from scratch, diff --git a/debootstrap b/debootstrap index ac821b8..54ae85d 100755 --- a/debootstrap +++ b/debootstrap @@ -517,6 +517,8 @@ if am_doing_phase maketarball; then fi if am_doing_phase first_stage; then + choose_extractor + # first stage sets up the chroot -- no calls should be made to # "chroot $TARGET" here; but they should be possible by the time it's # finished diff --git a/functions b/functions index 66021e8..e2a9f73 100644 --- a/functions +++ b/functions @@ -717,7 +717,22 @@ get_debs () { ################################################################ extraction -extract_deb_field () { +# Native dpkg-deb based extractors +extract_dpkg_deb_field () { + local pkg="$1" + local field="$2" + + dpkg-deb -f "$pkg" "$field" +} + +extract_dpkg_deb_data () { + local pkg="$1" + + dpkg-deb --fsys-tarfile "$pkg" | tar -xf - +} + +# Raw .deb extractors +extract_ar_deb_field () { local pkg="$1" local field="$2" @@ -726,7 +741,7 @@ extract_deb_field () { grep -i "^$field:" | sed -e 's/[^:]*: *//' | head -n 1 } -extract_deb_data () { +extract_ar_deb_data () { local pkg="$1" local tarball=$(ar -t "$pkg" | grep "^data.tar.[bgx]z") @@ -744,6 +759,28 @@ extract_deb_data () { fi } +choose_extractor () { + local extractor + + if type dpkg-deb >/dev/null 2>&1; then + extractor="dpkg-deb" + else + extractor="ar" + fi + + info CHOSENEXTRACTOR "Chosen extractor for .deb packages: %s" "$extractor" + case "$extractor" in + dpkg-deb) + extract_deb_field () { extract_dpkg_deb_field "$@"; } + extract_deb_data () { extract_dpkg_deb_data "$@"; } + ;; + ar) + extract_deb_field () { extract_ar_deb_field "$@"; } + extract_deb_data () { extract_ar_deb_data "$@"; } + ;; + esac +} + extract () { ( cd "$TARGET" local p=0 cat_cmd -- 1.6.5.3

>From 6eca98330e91eda672c5fa89610a423deda64798 Mon Sep 17 00:00:00 2001 From: Guillem Jover <guillem@...> Date: Fri, 27 Nov 2009 19:00:39 +0100 Subject: [PATCH 3/3] Add an --extractor option to override the automatic extractor selection --- debootstrap | 20 ++++++++++++++++++++ functions | 18 +++++++++++++++++- 2 files changed, 37 insertions(+), 1 deletions(-) diff --git a/debootstrap b/debootstrap index 54ae85d..171a5ef 100755 --- a/debootstrap +++ b/debootstrap @@ -90,6 +90,8 @@ usage() Run second stage in a subdirectory instead of root (can be used to create a foreign chroot) (requires --second-stage) + --extractor=TYPE override automatic .deb extractor selection + (supported: $EXTRACTORS_SUPPORTED) --boot-floppies used for internal purposes by boot-floppies --debian-installer used for internal purposes by debian-installer EOF @@ -201,6 +203,24 @@ if [ $# != 0 ] ; then error 1 NEEDARG "option requires an argument %s" "$1" fi ;; + --extractor|--extractor=?*) + if [ "$1" = "--extractor" -a -n "$2" ] ; then + EXTRACTOR_OVERRIDE="$2" + shift 2 + elif [ "$1" != "${1#--extractor=}" ]; then + EXTRACTOR_OVERRIDE="${1#--extractor=}" + shift + else + error 1 NEEDARG "option requires an argument %s" "$1" + fi + if valid_extractor "$EXTRACTOR_OVERRIDE"; then + if ! type "$EXTRACTOR_OVERRIDE" >/dev/null 2>&1; then + error 1 MISSINGEXTRACTOR "The selected extractor cannot be found: %s" "$EXTRACTOR_OVERRIDE" + fi + else + error 1 BADEXTRACTOR "%s: unknown extractor" "$EXTRACTOR_OVERRIDE" + fi + ;; --unpack-tarball|--unpack-tarball=?*) if [ "$1" = "--unpack-tarball" -a -n "$2" ] ; then UNPACK_TARBALL="$2" diff --git a/functions b/functions index e2a9f73..33b5a46 100644 --- a/functions +++ b/functions @@ -717,6 +717,8 @@ get_debs () { ################################################################ extraction +EXTRACTORS_SUPPORTED="dpkg-deb ar" + # Native dpkg-deb based extractors extract_dpkg_deb_field () { local pkg="$1" @@ -759,10 +761,24 @@ extract_ar_deb_data () { fi } +valid_extractor () { + local extractor="$1" + + for E in $EXTRACTORS_SUPPORTED; do + if [ "$extractor" = "$E" ]; then + return 0 + fi + done + + return 1 +} + choose_extractor () { local extractor - if type dpkg-deb >/dev/null 2>&1; then + if [ -n "$EXTRACTOR_OVERRIDE" ]; then + extractor="$EXTRACTOR_OVERRIDE" + elif type dpkg-deb >/dev/null 2>&1; then extractor="dpkg-deb" else extractor="ar" -- 1.6.5.3

Processed: Re: Bug#558229: Policy violation §12.3: postinst requires files in /usr/share/doc.

2009-11-27T10:48:09Z

Processing commands for control@...:

> severity 558229 serious
Bug #558229 [console-setup] Policy violation Â§12.3: postinst requires files in /usr/share/doc.
Severity set to 'serious' from 'normal'

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--
To UNSUBSCRIBE, email to debian-boot-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Processed: Re: Updating Tasksel translation - howto?

2009-11-27T10:48:07Z

Processing commands for control@...:

> tags 540822 pending
Bug #540822 [tasksel] tasksel: [INTL:sk] Slovak translation
Added tag(s) pending.
> tags 545312 pending
Bug #545312 [tasksel] tasksel: [INTL:ru] Russian program translation update
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--
To UNSUBSCRIBE, email to debian-boot-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Bug#558229: Policy violation §12.3: postinst requires files in /usr/share/doc.

2009-11-27T09:08:44Z

severity 558229 serious
thanks

Quoting Trent W. Buck (trentbuck@...):

> Package: console-setup
> Version: 1.49
> Severity: normal
>
> When installing the emdebian "gripped" version of 1.49:
>
> > Setting up console-setup (1.49em1) ...
> > cat: /usr/share/doc/console-setup/examples/console-setup: No such file or directory
>
> Relying on the existence of files in /usr/share/doc being installed
> appears to be a policy violation:

You seem to be right. In such case, this bug should be RC.

The file in /usr/share/doc is apparently meant to be a kind of
template.

Either it should be installed in something like
/usr/share/console-setup or the postinst script should handle the
absence of the file in a clean way:

- test if the file is here
- if it isn't, use a small config file created on the file by "cat <<EOF"

signature.asc (205 bytes) Download Attachment

base-installer 1.103 MIGRATED to testing

2009-11-27T08:39:19Z

FYI: The status of the base-installer source package
in Debian's testing distribution has changed.

Previous version: 1.102
Current version: 1.103

--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See http://release.debian.org/testing-watch/ for more information.

--
To UNSUBSCRIBE, email to debian-boot-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Bug#509799: Patch

2009-11-27T05:49:47Z

* Gaudenz Steinlin <gaudenz@...> [2009-11-26 18:56]:
> Why not just ask the user if d-i should mark the partition as bootable?
> I'm not sure if this is easily implementable, but if it is, I think this
> would be user friendlier than the proposed solution.
>
> E.g something along the lines of: Your boot partition is not marked as
> bootable. Should it be marked as bootable?

I don't really know why this is not being done. I just implemented it
the way other such prompts are done in d-i. Maybe someone who knows
more about partman can comment on Gaudenz's question.

--
Martin Michlmayr
http://www.cyrius.com/

--
To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: Suggestion: Change the link names on http://www.debian.org/releases/stable/debian-installer/

2009-11-27T03:02:35Z

Hi!

* Gerfried Fuchs <rhonda@...> [091127 11:43]:
> One suggestion that is pretty easy to implement and also should be
> helpful straight ahead: Why not make amd64 and i386 appear in *bold*
> letters?

Would it be to much to ask to replace the single "amd64" with "amd64 /
Intel EM64-T" (or however it's called) on the webpages? That might
reduce the "your ia64 image doesn't boot on my intel box" complaints.

Best Regards,
Alexander

signature.asc (204 bytes) Download Attachment

Re: Suggestion: Change the link names on http://www.debian.org/releases/stable/debian-installer/

2009-11-27T02:43:27Z

* Frans Pop <elendil@...> [2009-11-27 00:27:07 CET]:
> On Thursday 26 November 2009, Matthew Wilcox wrote:
> > Why should users have to learn what Debian's internal name for their
> > architecture is?
>
> Because that is what they see/need when they look at the sources.list or
> package names?

I have no powerpc in my sources.list, and package names don't carry
powerpc for me neither.

On the other hand, enabling users to learn isn't a bad thing in itself.
If it is additional, we shouldn't depend too much on educating our users
- offering it is enough.

One suggestion that is pretty easy to implement and also should be
helpful straight ahead: Why not make amd64 and i386 appear in *bold*
letters? That way they stand out and people are more likely to
recoginize and choose them. Ordering and discussions on renaming one way
or another might confuse, having it clearly standing out is a concept
that everyone should easy be able to understand.

You can afterwards continue to discuss wether allcaps or lowercase or
the arch part from the package filename is the best option. ;)

So long! :)
Rhonda

--
To UNSUBSCRIBE, email to debian-boot-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Bug#558229: Policy violation §12.3: postinst requires files in /usr/share/doc.

2009-11-27T00:21:39Z

Package: console-setup
Version: 1.49
Severity: normal

When installing the emdebian "gripped" version of 1.49:

> Setting up console-setup (1.49em1) ...
> cat: /usr/share/doc/console-setup/examples/console-setup: No such file or directory

Relying on the existence of files in /usr/share/doc being installed
appears to be a policy violation:

> 12.3. Additional documentation
> ------------------------------
>
> [...] Packages must not require the existence of any files in
> `/usr/share/doc/' in order to function [1]. Any files that are
> referenced by programs but are also useful as stand alone
> documentation should be installed under `/usr/share/<package>/' with
> symbolic links from `/usr/share/doc/<package>'. [...]
>
> [1] The system administrator should be able to delete files in
> `/usr/share/doc/' without causing any programs to break.

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

Kernel: Linux 2.6.30-2-686 (SMP w/1 CPU core)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages console-setup depends on:
ii console-terminus 4.30-2em1 Fixed-width fonts for fast reading
ii debconf [debconf-2.0] 1.5.28em1 Debian configuration management sy
ii keyboard-configuration 1.49 system-wide keyboard preferences
ii xkb-data 1.6-1em1 X Keyboard Extension (XKB) configu

Versions of packages console-setup recommends:
ii kbd 1.15-4 Linux console font and keytable ut

Versions of packages console-setup suggests:
ii locales 2.10.1-7em1 GNU C Library: National Language (
ii lsb-base 4.0-0ubuntu3 Linux Standard Base 4.0 init scrip

-- debconf information:
* console-setup/variant: USA
console-setup/codeset47: . Combined - Latin; Slavic Cyrillic; Greek
console-setup/unsupported_options: true
console-setup/fontsize-text: 12x6
* console-setup/compose: No compose key
debian-installer/console-setup-udeb/title:
console-setup/other:
console-setup/ctrl_alt_bksp: false
console-setup/modelcode: pc105
console-setup/switch: No temporary switch
console-setup/unsupported_config_layout: true
console-setup/use_system_font:
console-setup/fontsize: 12x6
console-setup/unsupported_layout: true
* console-setup/charmap: UTF-8
console-setup/layoutcode: us
console-setup/fontface47: Terminus
console-setup/fontsize-text47: 12x6
console-setup/optionscode: ctrl:nocaps
debian-installer/console-setup/title:
* console-setup/unsupported_config_options: true
console-setup/charmap47: UTF-8
* console-setup/layout: USA
console-setup/variantcode:
console-setup/codesetcode: Uni2
* console-setup/dont_ask_layout:
* console-setup/altgr: The default for the keyboard layout
* console-setup/ttys: /dev/tty[1-6]
* console-setup/model: Generic 105-key (Intl) PC
* console-setup/fontsize-fb: 12x6
console-setup/fontsize-fb47: 12x6
* console-setup/codeset: . Combined - Latin; Slavic Cyrillic; Greek
console-setup/toggle: No toggling
* console-setup/fontface: Terminus

--
To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: Suggestion: Change the link names on http://www.debian.org/releases/stable/debian-installer/

2009-11-26T15:27:07Z

On Thursday 26 November 2009, Matthew Wilcox wrote:

> On Thu, Nov 26, 2009 at 11:17:07PM +0100, Frans Pop wrote:
> > Do you really think that having "AMD64", "Intel x86" and "Intel IA-64"
> > instead of amd64, i386, ia64 will make people magically choose AMD64
> > if they're looking for 64-bit Intel support?
>
> I hadn't realised that Simon had made this change. That was the whole
> _point_. Put the popular architectures first, and call them something
> meaningful, ie:
>
> [x86 32-bit] [x86 64-bit] [PowerPC]

Changing things this way still does not make it fit in the current layout
of the page and will still reduce readability (IMO).

Also, making this change *only* for the image links is IMO not a good idea
because it just introduces yet another identification for architectures.
We already use too many different names and descriptions in different
places.

> Why should users have to learn what Debian's internal name for their
> architecture is?

Because that is what they see/need when they look at the sources.list or
package names?

> I have no objection to changing the layout.

I would prefer a full redesign over just changing the layout. The current
pages are problematic exactly because they try to fit everything on a
single page and thus allow little room for explanation.
But OTOH that's also their great strength for users who *do* know what they
want, so solving the issue by linking to separate page(s) that add a good
explanation of what's what is still an option too.

An alternative could be to have a single page per release per architecture.
Such pages would allow for much more information about the architecture
(including links to related architectures) and more information about the
different images.

--
To UNSUBSCRIBE, email to debian-boot-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: Suggestion: Change the link names on http://www.debian.org/releases/stable/debian-installer/

2009-11-26T14:48:47Z

On Thu, Nov 26, 2009 at 11:17:07PM +0100, Frans Pop wrote:
> Do you really think that having "AMD64", "Intel x86" and "Intel IA-64"
> instead of amd64, i386, ia64 will make people magically choose AMD64 if
> they're looking for 64-bit Intel support?

I hadn't realised that Simon had made this change. That was the whole
_point_. Put the popular architectures first, and call them something
meaningful, ie:

[x86 32-bit] [x86 64-bit] [PowerPC]

The exact names are debatable of course, but expecting people to deduce
that 'amd64' is the right link to click on for their shiny new Intel
Xeon system clearly isn't working.

> The current pages would IMO be more improved by adding a clear link to a
> *separate* page with info on "how to choose the correct architecture",
> which contains a clear description of what each architecture is.

I'm not sure that's a great idea either. Why should users have
to learn what Debian's internal name for their architecture is?

> If you want to really improve the links to images, which you're very
> welcome to do, then please do it by *redesigning* the pages with the links
> instead of forcing changes into an existing layout where the changes do
> more harm than that they improve things.

I have no objection to changing the layout. I want to make this page
more new-user friendly (since it's rather key to getting new users into
Debian).

--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."

--
To UNSUBSCRIBE, email to debian-boot-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...