Bug#606395: [G-I][squeeze-d-i-beta2] wrong keyboard layout in console (correct in X)
Samuel Thibault sthiba...@debian.org (09/07/2012): But doesn't it work *with* speech synthesis? (since in that case the installer uses text mode from the start) It works with a netboot-gtk image built today, against wheezy's udebs, presumably thanks to console-setup's migration during the last run. I pulled all udebs from src:console-setup based on the -udeb suffix, which fooled me, and I think the missing package for yesterday's build was: -console-setup-pc-ekmap 1.78 all +console-setup-pc-ekmap 1.80 all Mraw, KiBi. signature.asc Description: Digital signature
Bug#680926: tasksel: Typo in bug number included in changelog
Package: tasksel Version: 3.11 Severity: minor In the 3.11 changelog entry, bug #68067 is marked as closed, while it actually should be #680678. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.4-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages tasksel depends on: ii apt 0.9.7.1 ii debconf [debconf-2.0] 1.5.45 ii liblocale-gettext-perl 1.05-7+b1 ii perl5.14.2-12 ii tasksel-data3.11 tasksel recommends no packages. tasksel suggests no packages. -- debconf information excluded -- 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/20120709093558.14117.5173.reportbug@katniss.segie
Re: Bug#680900: flash-kernel: support for local overrides of db settings
On Mon, Jul 09, 2012 at 01:47:18AM +0100, Ian Campbell wrote: As discussed in #667681 it would be very useful to be able to override certain per-machine settings locally. For example Boot-Device defaults to /dev/sda1 on Dreamplug but can also be sdb1 depending on local configuration. Use /dev/disk/* for such definitions. /dev/sdX is _not_ stable. Bastian -- You can't evaluate a man by logic alone. -- McCoy, I, Mudd, stardate 4513.3 -- 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/20120709113917.gc16...@wavehammer.waldi.eu.org
Processed: Re: Bug#680748: RM: loop-aes-utils -- RoQA; unsupported
Processing commands for cont...@bugs.debian.org: tags 680748 +moreinfo Bug #680748 [ftp.debian.org] RM: loop-aes-utils -- RoQA; unsupported Added tag(s) moreinfo. clone 680748 -1 Bug #680748 [ftp.debian.org] RM: loop-aes-utils -- RoQA; unsupported Bug 680748 cloned as bug 680943 reassign -1 partman-crypto-loop Bug #680943 [ftp.debian.org] RM: loop-aes-utils -- RoQA; unsupported Bug reassigned from package 'ftp.debian.org' to 'partman-crypto-loop'. Ignoring request to alter found versions of bug #680943 to the same values previously set Ignoring request to alter fixed versions of bug #680943 to the same values previously set retitle -1 Depends on obsoleted package loop-aes-utils Bug #680943 [partman-crypto-loop] RM: loop-aes-utils -- RoQA; unsupported Changed Bug title to 'Depends on obsoleted package loop-aes-utils' from 'RM: loop-aes-utils -- RoQA; unsupported' severity -1 important Bug #680943 [partman-crypto-loop] Depends on obsoleted package loop-aes-utils Severity set to 'important' from 'normal' block 680748 by -1 Bug #680748 [ftp.debian.org] RM: loop-aes-utils -- RoQA; unsupported 680748 was not blocked by any bugs. 680748 was not blocking any bugs. Added blocking bug(s) of 680748: 680943 thanks Stopping processing here. Please contact me if you need assistance. -- 680748: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680748 680943: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680943 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.134183860912677.transcr...@bugs.debian.org
Re: Bug#680900: flash-kernel: support for local overrides of db settings
On Mon, 2012-07-09 at 13:39 +0200, Bastian Blank wrote: On Mon, Jul 09, 2012 at 01:47:18AM +0100, Ian Campbell wrote: As discussed in #667681 it would be very useful to be able to override certain per-machine settings locally. For example Boot-Device defaults to /dev/sda1 on Dreamplug but can also be sdb1 depending on local configuration. Use /dev/disk/* for such definitions. /dev/sdX is _not_ stable. At least on my dreamplug the best of these would seem to be: sda1 = /dev/disk/by-path/platform-orion-ehci.0-usb-0:1.1:1.0-scsi-0:0:0:0-part1 sdb1 = /dev/disk/by-path/platform-orion-ehci.0-usb-0:1.1:1.0-scsi-0:0:0:1-part1 Ian. Bastian -- You can't evaluate a man by logic alone. -- McCoy, I, Mudd, stardate 4513.3 -- 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/1341838655.12805.3.ca...@hastur.hellion.org.uk
Bug#680952: task-finnish-desktop: Recommends mozvoikko - xul-ext-mozvoikko
Package: task-finnish-desktop Version: 3.09 Severity: normal mozvoikko is deprecated and has become a transitional package for xul-ext-mozvoikko. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (1001, 'testing'), (11, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/2 CPU cores) Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages task-finnish-desktop depends on: ii tasksel 3.09 Versions of packages task-finnish-desktop recommends: ii iceweasel-l10n-fi1:10.0.5esr-1 ii libreoffice-help-fi 1:3.5.4-5 ii libreoffice-l10n-fi 1:3.5.4-5 ii libreoffice-voikko 3.3-3 ii mozvoikko2.0.1-1 task-finnish-desktop suggests no packages. -- 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/20120709132543.17550.8362.report...@henna.lan
Bug#482092: partman-crypto: xts support
On Sat, Jun 23, 2012 at 03:11:00PM +0200, Bastian Blank wrote: We only want to support plain64 for Wheezy. There is. You need at least 256 bit (128 for encryption, 128 for XTS). I commited support for xts-plain64 to partman-crypto. It will just double the key size used for xts, so no additional checking is necessary. Maybe someone wants to check them before I'll upload it. Bastian -- Only a fool fights in a burning house. -- Kank the Klingon, Day of the Dove, stardate unknown -- 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/20120709133747.ga2...@wavehammer.waldi.eu.org
Bug#680678: marked as done (task-ssh-server: depend on 'ssh' instead of 'openssh-server')
Your message dated Mon, 9 Jul 2012 08:50:05 -0600 with message-id 20120709145005.gj29...@mykerinos.kheops.frmug.org and subject line Re: Bug#680926: tasksel: Typo in bug number included in changelog has caused the Debian Bug report #680678, regarding task-ssh-server: depend on 'ssh' instead of 'openssh-server' 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.) -- 680678: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680678 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: task-ssh-server Version: 3.09 Severity: wishlist Dear Maintainer, 'task-ssh-server' currently depends on 'openssh-server'; IMHO, it wouldn't be wrong to depend on 'ssh' instead. 'ssh' depends on 'openssh-server' and 'openssh-client' (while 'openssh-client' is a dependency of 'openssh-server', so it's pulled by 'task-ssh-server' too). -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages task-ssh-server depends on: ii openssh-server 1:6.0p1-2 ii tasksel 3.09 task-ssh-server recommends no packages. task-ssh-server suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Version: 3.11 Quoting Adrian Lang (deb...@adrianlang.de): Package: tasksel Version: 3.11 Severity: minor In the 3.11 changelog entry, bug #68067 is marked as closed, while it actually should be #680678. Thanks for your vigilance (hmmm, isn't this en_FR?)! Fixed now. signature.asc Description: Digital signature ---End Message---
Bug#680926: marked as done (tasksel: Typo in bug number included in changelog)
Your message dated Mon, 9 Jul 2012 08:50:05 -0600 with message-id 20120709145005.gj29...@mykerinos.kheops.frmug.org and subject line Re: Bug#680926: tasksel: Typo in bug number included in changelog has caused the Debian Bug report #680926, regarding tasksel: Typo in bug number included in changelog 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.) -- 680926: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680926 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: tasksel Version: 3.11 Severity: minor In the 3.11 changelog entry, bug #68067 is marked as closed, while it actually should be #680678. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.4-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages tasksel depends on: ii apt 0.9.7.1 ii debconf [debconf-2.0] 1.5.45 ii liblocale-gettext-perl 1.05-7+b1 ii perl5.14.2-12 ii tasksel-data3.11 tasksel recommends no packages. tasksel suggests no packages. -- debconf information excluded ---End Message--- ---BeginMessage--- Version: 3.11 Quoting Adrian Lang (deb...@adrianlang.de): Package: tasksel Version: 3.11 Severity: minor In the 3.11 changelog entry, bug #68067 is marked as closed, while it actually should be #680678. Thanks for your vigilance (hmmm, isn't this en_FR?)! Fixed now. signature.asc Description: Digital signature ---End Message---
Installing Debian on s390x
Hi, I'm trying to install debian on IBM z/10 mainframe. I booted the installer from the reader but get Checking the Debian archive mirror ..25%..50%..75%..100% !! ERROR: Bad archive mirror I have downloaded debian package to pc and then use ftp method to install. Can you tell me which directory is the installer looking for? Debian archive mirror directory: Prompt: '?' for help, default=/debian/debian/dists/sid/main/debian-installer/ /debian/debian/dists/sid/main/binary-s390x/ /debian/debian/dists/sid/main/binary-s390x/ Appreciate your help. Wish you a great day and a wonderful week! Warm Regards, Tom 1-781-687-8146 *** This message (including any files transmitted with it) may contain confidential and/or proprietary information, is the property of Interactive Data Corporation and/or its subsidiaries, and is directed only to the addressee(s). If you are not the designated recipient or have reason to believe you received this message in error, please delete this message from your system and notify the sender immediately. An unintended recipient's disclosure, copying, distribution, or use of this message or any attachments is prohibited and may be unlawful. ***
Bug#652946: busybox tar fails to copy filesystem.squashfs
Today I've gave another try and this is still happening with today's sid
build.
Following your hint that this is busybox related I've tried to find how
far back this issue was happening using a patched live-build to use
snapshots.debian.org. From the available daily installers this bug is
present in all installers in http://d-i.debian.org/daily-images/i386.
The only date I didn't confirm this bug was 20110509 because the
installer stopped in the keyboard step. So I can assume this bug is
present at least since 20110930.
I've tried to enable/disable config options in busybox udeb that were
enabled since 20110930 (the last build I could reproduce this).
Looking at
http://anonscm.debian.org/gitweb/?p=d-i/busybox.git;a=history;f=debian/config/pkg;hb=HEAD
I've tried to disable in busybox udeb CONFIG_MKTEMP and
CONFIG_SWITCH_ROOT, just because their names are suspicious. Didn't
work. The installer stopped in the keyboard step without any of them.
I can't check all the busybox udeb changes to trace this, it takes too
much time to do it without knowing why the changes were made.
Another factor is busybox upstream version change since squeeze. It went
from 1.17 to actual 1.20. So, this can also be an upstream problem or
something that changed upstream. I don't know busybox enough to trace
this in upstream versions in debian-installer.
But, while I was messing with busybox udeb, I've tried to enable
CONFIG_FEATURE_TAR_FROM and tried to exclude var/lock and var/run in
busybox tar (not the target's tar as in my previous patches) and all
worked ok.
In busybox:
@@ -152,7 +152,7 @@ CONFIG_GZIP_FAST=0
CONFIG_TAR=y
CONFIG_FEATURE_TAR_CREATE=y
# CONFIG_FEATURE_TAR_AUTODETECT is not set
-# CONFIG_FEATURE_TAR_FROM is not set
+CONFIG_FEATURE_TAR_FROM=y
# CONFIG_FEATURE_TAR_OLDGNU_COMPATIBILITY is not set
# CONFIG_FEATURE_TAR_OLDSUN_COMPATIBILITY is not set
CONFIG_FEATURE_TAR_GNU_EXTENSIONS=y
In live-installer:
@@ -42,9 +42,13 @@ install_live_system () {
COUNT=0
OLD_IFS=$IFS
+
+ echo 'var/lock' /tmp/excludes
+ echo 'var/run' /tmp/excludes
+
mkdir -p /target
exec 40
- tar c . | \
+ tar c . -X /tmp/excludes | \
(chdir /target tar xv) | \
(
while read line; do
@@ -60,6 +64,8 @@ install_live_system () {
exec 04
IFS=$OLD_IFS
+ rm /tmp/excludes
+
chdir /
eval ${SUPPORT}_teardown
done
It worked, without using target tar and without chroot.
busybox udeb must be changed or the tar command will fail during the
install.
--
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/20120709182827.ga23...@gmail.com
Bug#655198: live-installer does not remove live packages in the installed system
Today I've built debian sid live images with live-installer 36. It's working, thanks. This bug can be closed for wheezy, but what about squeeze? -- 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/20120709183555.gb23...@gmail.com
Bug#652946: busybox tar fails to copy filesystem.squashfs
Um. This is just insane. The bug is filed 22-Dec 2011, today is 09-Jul 2012, you have the actual cause, and it is still open, and the maintainers of suspected package (busybox) knows nothing about it... :( Okay. Rui, you found the root cause of this issue, it is there: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652946#15 The problem is that during extraction, target directory var/lock exists, and the installer tries to replace it with something else (I guess a symlink). Busybox tar does not try to remove directories in this case, to be replaced with files. So it stops there, treating it as fatal error, and does not extract remaining files, creating issues for the system running later. Whenever it is a bug in busybox tar or not is an open question. POSIX does not specify whenever it should do that or not. GNU tar tries to rmdir() the existing file if unlink()ing it returned EISDIR, and will fail only if the directory is non-empty. Ofcourse this rmdir can be added to busybox tar too, it is rather trivial. But this is not the point. The point is the presence of var/lock directory in the target system. It should not be there to start with. We're extracting a whole set of directories, and any existing directory in the target which clashes with a file in the archive we're extracting may break the extraction with any tar implementation, not just busybox one. Ie, always extract to empty target directory. Now, I've no idea how this live system works, so I can't say more. Besides, I verified - busybox tar will correctly return failure (and write accutate reason to stderr) in this case. So something else in the live installer should be broken too -- the part which loses error messages and non-zero status codes. So, to sum it all: it is a bug in the live installer, it a) calls tar incorrectly (losing exit code and stderr) and b) does not verify that the target directory is empty or at least has sane content. Thanks, /mjt -- 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/4ffb2cdc.6020...@msgid.tls.msk.ru
Processed: possible [patch] netinst for wheezy missing r8169 driver on lemote fuloong
Processing commands for cont...@bugs.debian.org: tag 655124 patch Bug #655124 [debian-installer] netinst for wheezy missing r8169 driver on lemote fuloong Added tag(s) patch. stop Stopping processing here. Please contact me if you need assistance. -- 655124: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655124 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.134186546628753.transcr...@bugs.debian.org
Bug#655124: possible [patch] netinst for wheezy missing r8169 driver on lemote fuloong
tag 655124 patch stop Hello debian-installer team, Please have a look at this possible patch that came along on the debian-mips mailinglist - Forwarded message from Arnaud Patard arnaud.pat...@rtp-net.org - Date: Mon, 09 Jul 2012 16:59:44 +0200 From: Arnaud Patard arnaud.pat...@rtp-net.org To: Michael Stevens mstev...@etla.org Cc: debian-m...@lists.debian.org Subject: Re: What is the status of Debian on Lemote Fuloong? Organization: RtpNet Message-ID: 87r4slgeu7@lebrac.rtp-net.org User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux) Michael Stevens mstev...@etla.org writes: On Mon, Jul 09, 2012 at 02:30:07PM +, Code Blue wrote: On Sun, Jul 08, 2012 at 10:55:25AM +0200, Andreas Barth wrote: * Code Blue (codeb...@inbox.lv) [120708 10:32]: Can anybody point me to a source that describes exactly how to get this running? I have no idea how to install Debian on the Fuloong since I haven't found a bootable USB installer. see http://www.debian.org/releases/stable/installmanual and http://www.debian.org/releases/stable/mipsel/index.html.en for generic information. I usually use the images from http://d-i.debian.org/daily-images/mipsel/daily/loongson-2f/netboot/ and do netboot (please be aware that you either need to go back to the menu early to set question level to low, or you end up installing testing). If you have questions on that, please don't hesitate to ask here. Thank you, this helps a lot. It boots but it can't find the kernel module for the network adapter. I am surprised because if this is for loongson there is only one choice here, and it is not on the list. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655124 I'm guessing it's this debian-installer bug I reported some time ago? if you need the r8169 during installation, I guess that a patch like in the kernel like the following one may help (not tested at all). Index: debian/installer/mipsel/modules/mipsel-loongson-2f/nic-modules === --- debian/installer/mipsel/modules/mipsel-loongson-2f/nic-modules (revision 19204) +++ debian/installer/mipsel/modules/mipsel-loongson-2f/nic-modules (working copy) @@ -1 +1,2 @@ 8139too +r8169 Regards, Arnaud -- To UNSUBSCRIBE, email to debian-mips-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87r4slgeu7@lebrac.rtp-net.org - End forwarded message - stappers@fulong:~ $ lsmod | grep ^r r8169 41527 0 rtc_cmos8329 0 stappers@fulong:~ $ uname -a Linux fulong 2.6.35-trunk-loongson-2f #1 Tue Aug 17 21:45:32 UTC 2010 mips64 GNU/Linux stappers@fulong:~ $ cat /proc/version Linux version 2.6.35-trunk-loongson-2f (Debian 2.6.35-1~experimental.2) (m...@debian.org) (gcc version 4.4.5 20100728 (prerelease) (Debian 4.4.4-8) ) #1 Tue Aug 17 21:45:32 UTC 2010 stappers@fulong:~ $ Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. -- 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/20120709202421.gg26...@gpm.stappers.nl
Re: Installing Debian on s390x
On Mon, Jul 09, 2012 at 05:21:28PM +, Paul, Thomas wrote: Hi, I'm trying to install debian on IBM z/10 mainframe. I booted the installer from the reader but get Checking the Debian archive mirror ..25%..50%..75%..100% !! ERROR: Bad archive mirror I have downloaded debian package to pc and then use ftp method to install. Can you tell me which directory is the installer looking for? Debian archive mirror directory: Prompt: '?' for help, default=/debian/debian/dists/sid/main/debian-installer/ /debian/debian/dists/sid/main/binary-s390x/ /debian/debian/dists/sid/main/binary-s390x/ /debian/ (It will append the dists/sid/ stuff by itself.) Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#680519: lxde: please depend on gdm3
Package: task-lxde-desktop Followup-For: Bug #680519 Daniel Baumann, tasksel 3.11 does not depend on gdm3 nor xdm now, thus reopening. Heh, it's a strange thing... But it's not as bad as it seems: 'task-lxde-desktop' depends on 'lxde'; 'lxde' already depends on 'gdm3' OR (virtual) 'x-display-manager'. I'm using LightDM (which provides 'x-display-manager'); now I can remove 'xdm' without removing 'task-lxde-desktop'; finally, there's no need for me to install that GDM3. -- 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/20120709220916.10092.47755.reportbug@Chamaydan
Processed: Re: Bug#680678: task-ssh-server: depend on 'ssh' instead of 'openssh-server'
Processing commands for cont...@bugs.debian.org:
reopen 680678
Bug #680678 {Done: Christian PERRIER bubu...@debian.org} [task-ssh-server]
task-ssh-server: depend on 'ssh' instead of 'openssh-server'
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 3.11.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
680678: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680678
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.13418742619490.transcr...@bugs.debian.org
Unblocks/urgents for d-i beta 1 (take 2)
Cyril Brulebois k...@debian.org (08/07/2012): I'll try and find time to review other packages too, in later takes. Here's another round. # already ACK'd in #680676: busybox/1:1.20.0-5 # l10n and misc changes: live-installer/36 # l10n mostly, a few new features: network-console/1.37 # hardening flags + linux-any-ification: pcmciautils/018-8 # apparent bug fix/workaround for gcc 4.7, not much more; tests seem ok: slang2/2.2.4-15 # no big changes for d-i, let's reduce the testing/sid diff: syslinux/2:4.05+dfsg-6 Thanks for your time. Mraw, KiBi. signature.asc Description: Digital signature
Bug#680678: task-ssh-server: depend on 'ssh' instead of 'openssh-server'
reopen 680678 thanks Hello again, the changes in 3.11 are somewhat pointless; as for now, 'task-ssh-server': - depends on: openssh-server, tasksel - recommends: openssh-client [and it's pointless, because 'openssh-server' already _depends_ (not recommends!) on it]. Instead of making such redundant depandencies, in my original bug report I've just suggested for 'task-ssh-server' to depend only on 'ssh' metapackage :)
Re: Unblocks/urgents for d-i beta 1 (take 2)
On 10.07.2012 00:15, Cyril Brulebois wrote: # already ACK'd in #680676: busybox/1:1.20.0-5 # l10n and misc changes: live-installer/36 # l10n mostly, a few new features: network-console/1.37 # hardening flags + linux-any-ification: pcmciautils/018-8 # apparent bug fix/workaround for gcc 4.7, not much more; tests seem ok: slang2/2.2.4-15 # no big changes for d-i, let's reduce the testing/sid diff: syslinux/2:4.05+dfsg-6 With the exception of slang2, these versions already had freeze exceptions and were only blocked by the udeb freeze; all unblocked, hoping that the last set of changes in slang2 don't cause any issues. Regards, Adam -- 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/5542a832dfc7d8c0c804bb9d9da9c...@mail.adsl.funky-badger.org
Bug#652946: busybox tar fails to copy filesystem.squashfs
Hi Michael,
On Mon, Jul 09, 2012 at 11:11:24PM +0400, Michael Tokarev wrote:
Um. This is just insane. The bug is filed 22-Dec 2011,
today is 09-Jul 2012, you have the actual cause, and it
is still open, and the maintainers of suspected package
(busybox) knows nothing about it... :(
I think we didn't know for sure that busybox was the to blame. Daniel
said the error is in busybox, not a busybox error.
Because this bug is hard to trace (got to build and rebuild several live
images), lack of time, etc, time passed... Anyway, as you pointed out,
it's not busybox. Thank you.
Okay.
Rui, you found the root cause of this issue, it is there:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652946#15
The problem is that during extraction, target directory
var/lock exists, and the installer tries to replace it
with something else (I guess a symlink).
Busybox tar does not try to remove directories in this
case, to be replaced with files. So it stops there,
treating it as fatal error, and does not extract remaining
files, creating issues for the system running later.
Whenever it is a bug in busybox tar or not is an open
question. POSIX does not specify whenever it should do
that or not. GNU tar tries to rmdir() the existing
file if unlink()ing it returned EISDIR, and will fail
only if the directory is non-empty. Ofcourse this rmdir
can be added to busybox tar too, it is rather trivial.
But this is not the point.
The point is the presence of var/lock directory in the
target system. It should not be there to start with.
We're extracting a whole set of directories, and any
existing directory in the target which clashes with
a file in the archive we're extracting may break the
extraction with any tar implementation, not just
busybox one. Ie, always extract to empty target
directory.
Thanks again for clearing the fog here :)
Following your pointers I've put a sleep 2000 in
live-installer.postinst just _before_ the line mkdir -p /target and
then I've open tty2 console in debian-installer to check what was in
/target (see below).
Now, I've no idea how this live system works, so I can't
say more.
Besides, I verified - busybox tar will correctly return
failure (and write accutate reason to stderr) in this
case. So something else in the live installer should be
broken too -- the part which loses error messages and
non-zero status codes.
I think the problem about redirecting the error messages is because
live-installer.postint extracts the filesystem in background with exec
4. The relevant part of postinst:
eval ${SUPPORT}_prepare
STEPS=$(eval ${SUPPORT}_count)
db_progress INFO live-installer/progress/copying
COUNT=0
OLD_IFS=$IFS
mkdir -p /target
exec 40
tar c . | \
(chdir /target tar xv) | \
(
while read line; do
COUNT=$(($COUNT + 1))
CURRENT=$(($COUNT * 100 / $STEPS))
[ x$CURRENT = x$LAST_UPDATE ] continue
LAST_UPDATE=$CURRENT
db_progress STEP 1 4
done
)
exec 04
I don't know if adding a 2 or a |tee -a would work. It's a question
of trying it. It would really help in the future.
So, to sum it all: it is a bug in the live installer,
it a) calls tar incorrectly (losing exit code and stderr)
and b) does not verify that the target directory is empty
or at least has sane content.
Thanks for this, I really thought it was something about links or
hardlinks in the squash filesystem all the time. Turns out that is
/target that is not empty when the extraction happens!
As I've said above, I've put a sleep 2000 before mkdir -p /target
and SURPRISE (for me at least): /target, which I thought should be empty
because it is apparently created after partman has formated the
partitions (so I assumed completely empty), is _not_ empty:
root@quartor:~# tar tf target.tar.gz
./
./etc/
./etc/fstab
./lost+found/
./media/
./media/cdrom0/
./media/cdrom
./var/
./var/lock/
./var/run/
I've attached the tar file with what I've found in /target/ before the
extraction began.
I presume this must be something that line eval ${SUPPORT}_prepare
does.
Thanks,
/mjt
Thank you very much!! Debian is just great :)
target.tar.gz
Description: Binary data
Debian installer build: failed or old builds
Debian installer build overview --- Failed or old builds: * FAILED BUILD: sparc Jul 10 00:08 buildd@sompek build_cdrom http://d-i.debian.org/daily-images/sparc/daily/build_cdrom.log * FAILED BUILD: sparc Jul 10 00:08 buildd@sompek build_netboot http://d-i.debian.org/daily-images/sparc/daily/build_netboot.log * FAILED BUILD: sparc Jul 10 00:08 buildd@sompek build_miniiso http://d-i.debian.org/daily-images/sparc/daily/build_miniiso.log Totals: 89 builds (3 failed, 0 old) -- 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/e1sooo7-0005ch...@ravel.debian.org
Bug#652946: busybox tar fails to copy filesystem.squashfs
I was going to prepare another patch but I hold myself this time... I've searched what was creating those directories in the /target/. Turns out to be /lib/partman/finish.d/20mount_partitions from partman-target [1]. That code isn't touched since 2007 and creates the var/run and var/lock directories in /target. I'm not sure if /var/run and /var/lock still need to be created in /target since debian policy changed for those directories. As Michael pointed out, they are links now. If the directories still need to exist for another package other than live-installer or for anything else, then we should patch live-installer to rmdir /target/var/run /target/var/lock before extracting the squashfs. If not, maybe it should be partman-target that should stop creating those directories. What do you guys think? [1] http://anonscm.debian.org/gitweb/?p=d-i/partman-target.git -- 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/20120710053857.ga30...@gmail.com
