Bug#484287: tasksel: avoid installing java through OpenOffice with desktop task
Frans Pop wrote: Package: tasksel Version: 2.74 Severity: wishlist As previously discussed on IRC we could save 109MB installed size and 43MB download size/CD space for the desktop task by dropping the parts of OpenOffice that depend on Java. This will result in the removal of: * packages depending on openoffice.org-java-common: - openoffice.org-base (MS Access equivalent, not a real -base package) This will also remove the "mail merge" functionality (i.e., fetching values from some data source or maybe from a spreadsheet, and printing them on envelopes in the address field and as attribution on paper sheets to be put inside these envelopes). Is this OK? If MS Office also requires installation of MS Access for mail merge, please note this in this bug report and forget my comment. -- Alexander E. Patrakov -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#484748: debian-installer: Asks for Latin <-> Russian keyboard layout switch combination twice
Package: debian-installer Severity: normal Tags: l10n To reproduce: download mini.iso (either text-mode or graphical). Start installation, select Russian as the language. At some point, you will be asked (by console-setup) which key combination to use for switching between layouts. Then you'll hit http://bugs.debian.org/473559, please work around it by switching to the second virtual console, issuing "rm /target/usr/share/locale/ru/LC_MESSAGES/*apt*", switching back, and setting debconf priority back to normal. This is not, however, the subject of this bug report. Then the installer will download and install language-specific packages, and console-cyrillic among them. This package also asks for the keyboard layout switching combination. So the end result is that two packages are setting the keyboard layout in the installed system: console-setup and (later, thus overriding the settings) console-cyrillic. It is also ugly to see essentially the same question being asked twice via debconf (first by console-setup, and then by console-cyrillic). I understand that there is a plan to remove console-cyrillic and rely solely on console-setup in the future. However, this doesn't work now: if I remove console-cyrillic in hope to rely only on console-setup, the keyboard becomes completely unusable when I press Alt+Shift in order to switch to Russian (the presence of console-cyrillic, thus, masks the bug in console-setup). Since Lenny is nearly frozen, I suggest reverting the decision to use console-setup for languages (including Russian) where its settings are overridden later. In other words, for Lenny, when Russian language is selected during installation, please install only console-cyrillic, not console-setup. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.24-1-amd64 (SMP w/2 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#484748: debian-installer: Asks for Latin <-> Russian keyboard layout switch combination twice
Christian Perrier wrote: reassign 484748 console-setup retitle 484748 Should not need console-cyrillic for proper operation thanks Well, Anton pushed for console-setup to be used for Cyrillic languages, so I guess he might have clues about this. The point seems to be that c-s does not work alone from what you claim above So, I prefer reassigning this to console-setup and get Anton's advice. After some more research, the following facts came up: 1) The "unusable keyboard" bug affects the Alt+Shift and Ctrl+Shift combinations (Alt+Shift is the default in MS Windows and thus is a popular choice) 2) After I press Alt+Shift or Ctrl+Shift (i.e., press Alt or Ctrl, press Shift, release Shift, release Alt or Ctrl), the kernel seems to think that Alt (or Ctrl) is still pressed (e.g., after pressing Alt+Shift, F2 switches to the second virtual console or, after typing "cat" and pressing Ctrl+Shift, pressing "O" produces "^O") until I switch the virtual console. 3) If I press this key combination as Shift+Alt or Shift+Ctrl (i.e., press Shift, press Alt or Ctrl, release Alt or Ctrl, release Shift), it works as it should. 4) Some presented options to switch layouts actually don't work (e.g., if I configure LShift+RShift, this combination has simply no effect). -- Alexander E. Patrakov -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Fixed apt now in testing - new installs in Russian should work again
Frans Pop wrote: > Hi, > > A fixed version of apt that should solve the problems with aptitude in > Russian (#473559) has now reached testing. IMHO, the erratum text should mention that a workaround exists: 1) install Debian as usual until you hit the error 2) switch to the second virtual console 3) run this command: rm /target/usr/share/locale/ru/LC_MESSAGES/*apt* 4) switch back 5) change the debconf priority back to high, and the installation will continue. -- Alexander E. Patrakov -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#490205: Consistency with other font packages
Maybe it is a good idea to act in accordance with the existing practice for other font packages (e.g., ttf-dejavu). Look, ttf-dejavu is not mentioned explicitly in the desktop task, but it is one of the alternative dependencies of fontconfig-config. Why not do the same with ttf-liberation? -- Alexander E. Patrakov -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#403706: Udev sometimes forgets to RUN a program when renaming network interface
To Marco d'Itri: this testcase may explain at least a fraction of Debian bug
#403706 (because in Debian ifup is run, essentially, from udev rules),
that's why the CC. Udev version is 0.100-2.3. Also reproducible with 0.103-1.
To repeat the steps below, you need a Debian Etch installation CD, and
VMware Server. QEMU may be able to reproduce this too, but it is untested.
1) Create a virtual machine with two network cards. The first of them should
look into a custom empty virtual network (e.g., /dev/vmnet2 - the intention
is to simulate a useless network card looking into nowhere). The other card
should use host-only or NAT networking (the intention is that it gets its IP
address via DHCP).
2) Install Debian Etch into this virtual machine from the CD. Select eth1 as
the primary network interface. Do not update the system, because this would
trigger the update-initramfs script and break the testcase! (the testcase
relies on the fact that udev not in initramfs has to swap the two network
interfaces at step 6)
This installation procedure creates the following files:
/etc/network/interfaces:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug eth1
iface eth1 inet dhcp
/etc/udev/rules.d/z25_persistent-net.rules:
# This file was automatically generated by the /lib/udev/write_net_rules
# program, probably run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single line.
# PCI device 0x1022:0x2000 (pcnet32)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:0c:29:d8:39:6e",
NAME="eth1"
# PCI device 0x1022:0x2000 (pcnet32)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:0c:29:d8:39:64",
NAME="eth0"
3) Create the file /etc/udev/rules.d/z49_debug.rules with the following
contents:
SUBSYSTEM=="net", ACTION=="add", RUN+="/bin/sh -c 'echo FOUND NETWORK
INTERFACE %k >/dev/console'"
4) Reboot the system, watch how it prints that it found eth1, eth0 and lo.
So far so good. Note that the renaming rules above are not really triggered,
because these two network cards are PCI cards served by the same module.
5) Now edit /etc/network/interfaces so that it mentions eth0 instead of
eth1, and edit /etc/udev/rules.d/z25_persistent-net.rules by swapping eth0
and eth1 (so that 00:0c:29:d8:39:6e becomes eth0 and 00:0c:29:d8:39:64
becomes eth1). The intention is, as you may have guessed, is to swap the
names, so that the used card becomes eth0, and the useless one is eth1. The
consequence is that the renaming rules become essential.
6) Reboot. This time it prints the message:
udevd-event[2669]: rename_netif: error changing net interface name
eth1_rename to eth0: No such device
(but "ifconfig -a" shows that the 00:0c:29:d8:39:6e card does become eth0)
Then it prints a message that it found eth1 and lo, and no message about
eth0. And of course, the network is not up, because udev forgot to run
net.agent for the new eth0. Bug!
While it took us some special preparations to trigger this bug with two
identical network cards, I guess that this will happen by itself with 50%
probability if the network cards are not identical, due to random module
loading order.
7) This time, repeat step (5), using names "used" and "unused" for the two
interfaces, reboot and watch how udev finds the "used", "unused" and "lo"
interfaces.
--
Alexander E. Patrakov
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#403706: Udev sometimes forgets to RUN a program when renaming network interface
Joey Hess wrote: Please file this as a separate bug on udev. Done, see #405775. -- Alexander E. Patrakov -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#466251: (no bug?)
Antanas Bublys wrote: Package: installation-report Base System Installation Checklist: Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] In other words, the installer says that everything is installed successfully, and thus there is no bug. Congratulations! If this is indeed a successful installation, please say so to [EMAIL PROTECTED] If something is wrong, please describe (by human-readable words) what exactly failed and send this description to [EMAIL PROTECTED] -- Alexander E. Patrakov -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
