Bug#514211: Version
I just forgot to mention that I was using debian-Lenny-DI-rc2-sparc-netinst.iso -- Michal Čihař | http://cihar.com | http://blog.cihar.com signature.asc Description: PGP signature
Bug#514211: lenny not installable on sparc (Qemu)
Package: debian-installer Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi I just wanted to test something on sparc and tried to install Lenny in Qemu and it fails, it looks like silo configuration is somehow broken, but I don't know the platform at all. 4.0r6 installation starts fine, so it looks like a regression. SILO fails with: Your imagename `install' and arguments `' have either wrong syntax, or describe a label which is not present in silo.conf Attaching screenshot of qemu... - -- Michal Čihař | http://cihar.com | http://blog.cihar.com - -- System Information: Debian Release: 5.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.25.20-0.1-default (SMP w/2 CPU cores) Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkmKpeYACgkQ3DVS6DbnVgRC7ACgrLys/AcPoPn63ZrYJhTkHc4u AzIAoINMytN041XP6anVO71iqR3huqUx =XwmE -END PGP SIGNATURE- attachment: qemu-sparc.png
Bug#514212: console-setup: on UTF-8 console, caps lock is turned into a shift lock
Package: console-setup
Version: 1.29
Severity: normal
Tags: patch
Hello,
While upgrading from console-data's keymaps to console-setup, my caps
lock became a shift lock, and the caps lock led doesn't work any more.
This is due to these few lines:
# A hack to work around a bug in the kernel/loadkeys
if (! $acm) {
$xkbsym_table{'Caps_Lock'} = 'Shift_Lock';
$xkbsym_table{'ISO_Lock'} = 'Shift_Lock';
}
which happen to be always executed as my system is UTF-8, just like all
future installed Debian systems. Why is this hack needed? We should
rather fix the bug where it belongs instead of introducing others on all
future installed systems... :)
If the reason has been lost in history (the code dates back from at
least 2005) then we should probably apply the patch to fix the common
case, and let the real bug reappear and get fixed the proper way.
Samuel
-- System Information:
Debian Release: 5.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.28 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages console-setup depends on:
ii console-terminus 4.26-2.1 Fixed-width fonts for fast reading
ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy
ii xkb-data 1.5-2 X Keyboard Extension (XKB) configu
Versions of packages console-setup recommends:
ii kbd 1.14.1-4 Linux console font and keytable ut
Versions of packages console-setup suggests:
ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip
-- debconf information:
* console-setup/variant: France
console-setup/modelcode:
console-setup/fontsize: 8
console-setup/layoutcode: fr
debian-installer/console-setup/title:
console-setup/codesetcode: Lat15
console-setup/dont_ask_layout:
* console-setup/altgr: Right Alt
* console-setup/ttys: /dev/tty[1-6]
* console-setup/codeset: # Latin1 and Latin5 - western Europe and Turkic
languages
console-setup/toggle: No toggling
* console-setup/fontface: VGA
* console-setup/fontsize-text: 8
* console-setup/compose: Right Logo key
console-setup/switch: No temporary switch
* console-setup/charmap: UTF-8
console-setup/optionscode: lv3:ralt_switch,compose:rwin
* console-setup/layout: France
console-setup/variantcode:
* console-setup/model: Generic 105-key (Intl) PC
console-setup/fontsize-fb: 8
--
Samuel
Be warned that typing \fBkillall \fIname\fP may not have the desired
effect on non-Linux systems, especially when done by a privileged user.
(From the killall manual page)
Index: Keyboard/ckbcomp
===
--- Keyboard/ckbcomp(révision 57453)
+++ Keyboard/ckbcomp(copie de travail)
@@ -2549,12 +2549,6 @@
close ACM;
}
-# A hack to work around a bug in the kernel/loadkeys
-if (! $acm) {
-$xkbsym_table{'Caps_Lock'} = 'Shift_Lock';
-$xkbsym_table{'ISO_Lock'} = 'Shift_Lock';
-}
-
### PARSING ###
# Report a syntax error in $filename. $_[0] should describe what was
Bug#514211: lenny not installable on sparc (Qemu)
On Thursday 05 February 2009, Michal Čihař wrote: I just wanted to test something on sparc and tried to install Lenny in Qemu and it fails, it looks like silo configuration is somehow broken, but I don't know the platform at all. 4.0r6 installation starts fine, so it looks like a regression. SILO fails with: Your imagename `install' and arguments `' have either wrong syntax, or describe a label which is not present in silo.conf Exactly which image was this (full URL please)? -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514211: lenny not installable on sparc (Qemu)
Hi Dne Thu, 5 Feb 2009 10:41:41 +0100 Frans Pop elen...@planet.nl napsal(a): On Thursday 05 February 2009, Michal Čihař wrote: I just wanted to test something on sparc and tried to install Lenny in Qemu and it fails, it looks like silo configuration is somehow broken, but I don't know the platform at all. 4.0r6 installation starts fine, so it looks like a regression. SILO fails with: Your imagename `install' and arguments `' have either wrong syntax, or describe a label which is not present in silo.conf Exactly which image was this (full URL please)? http://cdimage.debian.org/cdimage/lenny_di_rc2/sparc/iso-cd/debian-Lenny-DI-rc2-sparc-netinst.iso -- Michal Čihař | http://cihar.com | http://blog.cihar.com signature.asc Description: PGP signature
Bug#514211: marked as done (lenny not installable on sparc (Qemu))
Your message dated Thu, 5 Feb 2009 10:55:04 +0100 with message-id 200902051055.05091.elen...@planet.nl and subject line Re: Bug#514211: lenny not installable on sparc (Qemu) has caused the Debian Bug report #514211, regarding lenny not installable on sparc (Qemu) 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.) -- 514211: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=514211 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: debian-installer Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi I just wanted to test something on sparc and tried to install Lenny in Qemu and it fails, it looks like silo configuration is somehow broken, but I don't know the platform at all. 4.0r6 installation starts fine, so it looks like a regression. SILO fails with: Your imagename `install' and arguments `' have either wrong syntax, or describe a label which is not present in silo.conf Attaching screenshot of qemu... - -- Michal Čihař | http://cihar.com | http://blog.cihar.com - -- System Information: Debian Release: 5.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.25.20-0.1-default (SMP w/2 CPU cores) Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkmKpeYACgkQ3DVS6DbnVgRC7ACgrLys/AcPoPn63ZrYJhTkHc4u AzIAoINMytN041XP6anVO71iqR3huqUx =XwmE -END PGP SIGNATURE- attachment: qemu-sparc.png---End Message--- ---BeginMessage--- On Thursday 05 February 2009, Michal Čihař wrote: I just wanted to test something on sparc and tried to install Lenny in Qemu and it fails, it looks like silo configuration is somehow broken, but I don't know the platform at all. 4.0r6 installation starts fine, so it looks like a regression. I suspect your problem is that Lenny no longer supports sparc32, but you used the 32-bits variant of qemu for sparc. I'm closing the report on that basis. If this is not correct please let us know. Note that AFAIK the 64-bits sparc variant does not yet work, so ATM you cannot really test sparc images in qemu. Cheers, FJP ---End Message---
Bug#514212: console-setup: on UTF-8 console, caps lock is turned into a shift lock
On Thu, Feb 05, 2009 at 10:34:09AM +0100, Samuel Thibault wrote: If the reason has been lost in history (the code dates back from at least 2005) then we should probably apply the patch to fix the common case, and let the real bug reappear and get fixed the proper way. The reason is known - Caps_Lock works only for English letters. I think there was some patch that fixed the problem but I don't know if it is applied in the Debian kernel. I'll have to remember and check this. Anton Zinoviev -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514212: console-setup: on UTF-8 console, caps lock is turned into a shift lock
Anton Zinoviev, le Thu 05 Feb 2009 13:04:42 +0200, a écrit : On Thu, Feb 05, 2009 at 10:34:09AM +0100, Samuel Thibault wrote: If the reason has been lost in history (the code dates back from at least 2005) then we should probably apply the patch to fix the common case, and let the real bug reappear and get fixed the proper way. The reason is known - Caps_Lock works only for English letters. More precisely, as described in the bug report, it works only for the underlying 8bit charset, so in unicode it's latin1. Samuel -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bug#514211: lenny not installable on sparc (Qemu)
Michal Čihař ni...@debian.org writes: I just wanted to test something on sparc and tried to install Lenny in Qemu and it fails, it looks like silo configuration is somehow broken, but I don't know the platform at all. Do you try to boot the Lenny installer with a sparc32 qemu system? That won't work. Lenny only supports sun4u or sun4v systems. See http://d-i.alioth.debian.org/manual/en.sparc/ch02s01.html#sparc-cpus (and no, there is no sparc64 system support in Lenny's qemu either...) 4.0r6 installation starts fine, so it looks like a regression. Sort of. But it's documented and therefore not a bug. Etch do support sun4m: http://www.debian.org/releases/stable/sparc/ch02s01.html.en#id2529946 and can therefore be installed in qemu, yes. Bjørn -- It takes a fascist spaz like you to say that terrorists are fun pgptWL3ByxoEJ.pgp Description: PGP signature
Bug#514212: console-setup: on UTF-8 console, caps lock is turned into a shift lock
I found the patch that needs to be applied and it is relatively simple. http://lists.altlinux.org/pipermail/kbd/2008-April/000123.html Anton Zinoviev -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514212: console-setup: on UTF-8 console, caps lock is turned into a shift lock
Anton Zinoviev, le Thu 05 Feb 2009 13:28:07 +0200, a écrit : I found the patch that needs to be applied and it is relatively simple. http://lists.altlinux.org/pipermail/kbd/2008-April/000123.html Thanks, that's mine :) I don't have the time to develop right now, but the idea would then be to double the number of keymaps to 128, to have capsed versions of each of the current keycode translations. And about the led issue, we need to ask the kernel for an interface to be able to configure which lock should drive which led. Samuel -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514212: console-setup: on UTF-8 console, caps lock is turned into a shift lock
Samuel Thibault, le Thu 05 Feb 2009 12:39:08 +0100, a écrit : Anton Zinoviev, le Thu 05 Feb 2009 13:28:07 +0200, a écrit : I found the patch that needs to be applied and it is relatively simple. http://lists.altlinux.org/pipermail/kbd/2008-April/000123.html Thanks, that's mine :) That was bug #452103, now closed, and indeed the patch is applied so you can use it. Samuel -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514212: console-setup: on UTF-8 console, caps lock is turned into a shift lock
Samuel Thibault, le Thu 05 Feb 2009 10:34:09 +0100, a écrit : Why is this hack needed? Oh, that's probably due to http://bugzilla.kernel.org/show_bug.cgi?id=7746 Bummer, that's not an easy one. Samuel -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514218: d-i: [sparc] should list sun4v (niagara) in silo.conf
Package: debian-installer Version: 20090123 Severity: important The installation guide says that we support sun4v systems, but our silo.conf file for netboot and CDs only lists sun4u. Note that this should also be changed in debian-cd when it is added for D-I. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Meeting(s) at FOSDEM
On Sun, Feb 01, 2009 at 02:53:58PM +, Steve McIntyre wrote: Hi folks, Apologies for the massive cross-posting, but I'm trying to arrange some discussions between the various teams, or at least those members who will be at FOSDEM. Topics I'd like us to talk about include: 1. how the d-i daily builds are done and distributed 2. how the needs of the kernel d-i teams can better be reconciled I'm guessing that quite a number of people may be interested in these, and in other topics. Is there anything else I'm missing that you would like to discuss? Then: when and where would be a good time to meet up? Hello? Anyone? -- Steve McIntyre, Cambridge, UK.st...@einval.com I've only once written 'SQL is my bitch' in a comment. But that code is in use on a military site... -- Simon Booth -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Meeting(s) at FOSDEM
Hi, On Donnerstag, 5. Februar 2009, Steve McIntyre wrote: Then: when and where would be a good time to meet up? Hello? Anyone? Looking at http://wiki.debian.org/FosdemVideo2009 I'd suggest either Saturday from 17:30-18:15 (right before your talk, Steve) or sunday between 10 and 13. Or saturday evening for dinner, but I'm quite sure that wont work out. regards, Holger signature.asc Description: This is a digitally signed message part.
Bug#514212: console-setup: on UTF-8 console, caps lock is turned into a shift lock
On Thu, Feb 05, 2009 at 12:39:08PM +0100, Samuel Thibault wrote: I don't have the time to develop right now, but the idea would then be to double the number of keymaps to 128, to have capsed versions of each of the current keycode translations. A good idea. :) Idealy some future version of loadkeys should automaticaly double the keysyms and convert CapsLock to CapsShift and in order to do this no keymap should use CapsShift directly. In console-setup maybe it will be better to use CtrlL_Lock instead of CapsShift_Lock as CtrlL_Lock is supported by console-tools and by all kernels. Anton Zinoviev -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Meeting(s) at FOSDEM
On Thu, 05, Feb, 2009 at 12:30:46PM +, Steve McIntyre spoke thus.. Apologies for the massive cross-posting, but I'm trying to arrange some discussions between the various teams, or at least those members who will be at FOSDEM. Topics I'd like us to talk about include: 1. how the d-i daily builds are done and distributed 2. how the needs of the kernel d-i teams can better be reconciled I'm guessing that quite a number of people may be interested in these, and in other topics. Is there anything else I'm missing that you would like to discuss? Then: when and where would be a good time to meet up? Hello? Anyone? Hi, I agree that it'd be a good idea to meet up and I'll make sure I'm there wearing my ftpteam hat (note, not ftpmaster so I can't finally agree to anything, but I'm willing to put any work in on the ftp side which is needed). I'm around all weekend up until Sunday afternoon at about 3, so whatever works for everyone else will be fine by me. Cheers, Mark -- Mark Hymers mhy at debian dot org 'I regret nothing?' That's not a song, that's an idiots charter. Andy Hamilton, Old Harry's Game signature.asc Description: Digital signature
Re: Meeting(s) at FOSDEM
On Thursday 05 February 2009, Steve McIntyre wrote: On Sun, Feb 01, 2009 at 02:53:58PM +, Steve McIntyre wrote: Hi folks, Apologies for the massive cross-posting, but I'm trying to arrange some discussions between the various teams, or at least those members who will be at FOSDEM. Topics I'd like us to talk about include: 1. how the d-i daily builds are done and distributed 2. how the needs of the kernel d-i teams can better be reconciled I'm guessing that quite a number of people may be interested in these, and in other topics. Is there anything else I'm missing that you would like to discuss? Then: when and where would be a good time to meet up? Hello? Anyone? As I've already made my opinion clear by mail on the first issue I don't see much point in a meeting unless others show an interest in it. For the second issue I doubt that FOSDEM is the right venue. I'll be at FOSDEM and if there is a meeting I'm willing to attend. I can explain some of the technical issues involved and explain why IMO triggering daily builds by uploads is a very bad idea. signature.asc Description: This is a digitally signed message part.
Re: Meeting(s) at FOSDEM
On Thu, 2009-02-05 at 12:30 +, Steve McIntyre wrote: Then: when and where would be a good time to meet up? Given we all tend to arrive in dribs-and-drabs on Friday night, I'd suggest Saturday some time. Perhaps either have a working lunch or, if the group is likely to be too large, perhaps take over the back room of that bar with the black and white sign near the Atlas hotel in the evening on Saturday? Ultimately so long as it's after about 9pm Friday night, and before about 3pm Sunday afternoon, I'll happy :-) D. -- Daniel Silverstonehttp://www.debian.org/ PGP mail accepted and encouraged.Key Id: 2BC8 4016 2068 7895 signature.asc Description: This is a digitally signed message part
Bug#514190: installation-reports: d-i lenny RC2 amd64 on Compal FL90 (PM965): Success
Quoting Filipus Klutiero (chea...@gmail.com): This is an install on the same target as #497318. Everything went as expected, which means that the 3 issues mentioned there were fixed. Additionally, I used amd64 instead of i386. The test image I downloaded is supposed to be the same as the final RC2. Given that your installation was a complete success, I do as usual with reports for successful installations: I close the bug..:-) This does not of course mean you weren't right to report. Knowing the installations are correct is important for the d-i team. Many thanks for your time testing the Debian Installer and reporting your results. Have fun with your new Debian system! signature.asc Description: Digital signature
Re: Meeting(s) at FOSDEM
On Thu, Feb 05, 2009 at 12:30:46PM +, Steve McIntyre wrote: On Sun, Feb 01, 2009 at 02:53:58PM +, Steve McIntyre wrote: Hi folks, Apologies for the massive cross-posting, but I'm trying to arrange some discussions between the various teams, or at least those members who will be at FOSDEM. Topics I'd like us to talk about include: 1. how the d-i daily builds are done and distributed 2. how the needs of the kernel d-i teams can better be reconciled I'm guessing that quite a number of people may be interested in these, and in other topics. Is there anything else I'm missing that you would like to discuss? Then: when and where would be a good time to meet up? Hello? Anyone? Friday or Saturday evening in the centre, or perhaps lunch-time in/near ULB. Ben. -- Ben Hutchings Logic doesn't apply to the real world. - Marvin Minsky -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514211: lenny not installable on sparc (Qemu)
Dne Thu, 5 Feb 2009 10:55:04 +0100 Frans Pop elen...@planet.nl napsal(a): On Thursday 05 February 2009, Michal Čihař wrote: I just wanted to test something on sparc and tried to install Lenny in Qemu and it fails, it looks like silo configuration is somehow broken, but I don't know the platform at all. 4.0r6 installation starts fine, so it looks like a regression. I suspect your problem is that Lenny no longer supports sparc32, but you used the 32-bits variant of qemu for sparc. Ah, then sorry for mess. I should have read something about the platform before trying to use it... -- Michal Čihař | http://cihar.com | http://blog.cihar.com signature.asc Description: PGP signature
Re: Call for testing of RC2 images
On Fri, Jan 30, 2009 at 07:39:54PM -0200, Otavio Salvador wrote: Guido Günther a...@sigxcpu.org writes: Frans Pop schrieb: On Friday 30 January 2009, Guido Günther wrote: The i386 businesscard iso lacks the libaio1-udeb so multipath -l won't work due to lack of libaio.so.1 and the system fails to detect multipath. Can the libaio1-udeb be added? Why isn't it being pulled in as a dependency? The installer tries to, but it's not available on the CD: Jan 30 15:58:00 anna-install: Installing multipath-udeb Jan 30 15:58:00 anna[8103]: DEBUG: resolver (libaio1-udeb): package doesn't exist (ignored) Jan 30 15:58:00 anna[8103]: DEBUG: resolver (kernel-image-2.6.26-1-486-di): package doesn't exist (ignored) Jan 30 15:58:00 anna[8103]: DEBUG: retrieving multipath-modules-2.6.26-1-486-di 1.76 Jan 30 15:58:00 anna[8103]: DEBUG: retrieving multipath-udeb 0.4.8-13 It works fine when using netinst (at least the last time I checked). Cheers, I've fixed it in debian-cd SVN but I don't think a new full image build is worth just for it. This will be fixed in dailies and in final images, obviously ;-) Mind to test dailies and check if it works? Works like a charm now with the daily built i386 business card iso. Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Updated multipath patch for grub-legacy
On Thu, Jan 29, 2009 at 04:27:54PM +0100, Guido Günther wrote: Hi, Attached is an updated version of the multipath support patch for grub-legacy. It applies cleanly to 0.97-47lenny2. It's the only missing piece for getting multipath support to work in lenny's d-i: http://wiki.debian.org/DebianInstaller/MultipathSupport I just double checked that installing an accordingly patched grub into /target is enough to make d-i pass smoothly on a multipath setup with the business card iso as of today. -- Guido -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514248: installation-reports: lenny RC2 powerpc installation report
Package: installation-reports Severity: normal Just passing along a report of a smooth and successful installation of lenny RC2 for PPC. The only snag was when I tried to install onto an existing partition without re-creating the filesystem. I haven't managed to find any details in the logs regarding this failure. Creating a new filesystem worked fine and things proceded smoothly from there. -- Package-specific info: Boot method: CD Image version: RC2 netinst Date: 2009-02-04 Machine: Mac G4 Cube Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it 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] Comments/Problems: Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=5.0 (lenny) - installer build 20090123 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == umame -a: Linux rubik 2.6.26-1-powerpc #1 Sat Jan 10 14:00:38 CET 2009 ppc unknown lspci -knn: :00:0b.0 Host bridge [0600]: Apple Computer Inc. UniNorth AGP [106b:0020] lspci -knn: :00:10.0 VGA compatible controller [0300]: nVidia Corporation NV11 [GeForce2 MX/MX 400] [10de:0110] (rev a1) lspci -knn: Kernel driver in use: nvidiafb lspci -knn: 0001:10:0b.0 Host bridge [0600]: Apple Computer Inc. UniNorth PCI [106b:001f] lspci -knn: 0001:10:17.0 Class [ff00]: Apple Computer Inc. KeyLargo Mac I/O [106b:0022] (rev 03) lspci -knn: Kernel driver in use: macio lspci -knn: 0001:10:18.0 USB Controller [0c03]: Apple Computer Inc. KeyLargo USB [106b:0019] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 0001:10:19.0 USB Controller [0c03]: Apple Computer Inc. KeyLargo USB [106b:0019] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 0001:10:1a.0 FireWire (IEEE 1394) [0c00]: Texas Instruments TSB12LV26 IEEE-1394 Controller (Link) [104c:8020] lspci -knn: Kernel driver in use: ohci1394 lspci -knn: Kernel modules: ohci1394 lspci -knn: 0002:20:0b.0 Host bridge [0600]: Apple Computer Inc. UniNorth Internal PCI [106b:001e] lspci -knn: 0002:20:0f.0 Ethernet controller [0200]: Apple Computer Inc. UniNorth GMAC (Sun GEM) [106b:0021] (rev 01) lspci -knn: Kernel driver in use: gem lspci -knn: Kernel modules: sungem lsmod: Module Size Used by lsmod: nls_utf85248 0 lsmod: ufs83172 0 lsmod: hfsplus84228 0 lsmod: dm_mod 60524 0 lsmod: md_mod 88308 0 lsmod: xfs 521380 0 lsmod: reiserfs 259860 0 lsmod: jfs 179884 0 lsmod: hfs51364 0 lsmod: ext3 134056 1 lsmod: jbd49204 1 ext3 lsmod: vfat 14208 0 lsmod: fat52188 1 vfat lsmod: ext2 73224 0 lsmod: mbcache11136 2 ext3,ext2 lsmod: eth139418980 0 lsmod: sungem 32772 0 lsmod: sungem_phy 14848 1 sungem lsmod: isofs 35208 0 lsmod: nls_base 10496 7 nls_utf8,hfsplus,jfs,hfs,vfat,fat,isofs lsmod: zlib_inflate 18112 1 isofs lsmod: sbp2 22988 0 lsmod: usb_storage91688 0 lsmod: scsi_mod 153324 2 sbp2,usb_storage lsmod: usbhid 47812 0 lsmod: hid45032 1 usbhid lsmod: ff_memless 8360 1 usbhid lsmod: ohci1394 35728 0 lsmod: ide_cd_mod 35620 0 lsmod: ieee1394 91200 3 eth1394,sbp2,ohci1394 lsmod: cdrom 40088 1 ide_cd_mod lsmod: ide_disk 16320 3 df: Filesystem 1k-blocks Used Available Use% Mounted on df: tmpfs 25728068257212 0% /dev df: /dev/hda1110321208 3194800 6602120 33% /target df: /dev/hda1110321208 3194800 6602120 33% /dev/.static/dev df: tmpfs 25728068257212 0% /target/dev free: total used
debootstrap 1.0.10lenny1 MIGRATED to testing
FYI: The status of the debootstrap source package in Debian's testing distribution has changed. Previous version: 1.0.10 Current version: 1.0.10lenny1 -- This email is automatically generated; the Debian Release Team debian-rele...@lists.debian.org is responsible. See http://release.debian.org/testing-watch/ for more information. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514016: options for fixing
Hi,
just as an exercise what might be done to fix this:
It would seem that the options are
- not fix it (for now),
- find something in current tar that works (I didn't),
- switch off tar,
- try to do something with tar
(new upstream - vs. release: ugh - has a apply to symlink target
--transform flag, but that also might need post-processing of
symlinks at end of bootstrapping),
- try to do some ld-preload(?) trickery for changing the way symlinks
are read,
- try to find some way to chroot before calling tar, one possibility
would be copying required files to some temp CWD, make tar look there
for the libraries, chrooting to the target and calling tar from (the
unchanged) CWD,
- add chroot option to tar (see patch).
It would seem that in terms of total invasiveness, the last option is
minimal, but it might be unwise to add options without consulting
upstream (however, it once upstream agrees to have an option with a
given spec, one could implement that locally).
Of course, the patch introduces new strings (translator-:( ), but they
only shown with the new option.
But then, this is just an idea, I'm sure you'll come up with a good, and
probably better solution.
Kind regards
T.
--
Thomas Viehmann, http://thomas.viehmann.net/
reverted:
diff -u tar-1.20/src/list.c tar-1.20/src/list.c
--- tar-1.20/src/list.c
+++ tar-1.20/src/list.c
@@ -72,6 +72,11 @@
name_gather ();
open_archive (ACCESS_READ);
+ if (chroot_option)
+ {
+ sys_chroot(chroot_option);
+ }
+
do
{
prev_status = status;
diff -u tar-1.20/debian/changelog tar-1.20/debian/changelog
--- tar-1.20/debian/changelog
+++ tar-1.20/debian/changelog
@@ -1,3 +1,10 @@
+tar (1.20-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Implement --chroot option for extraction.
+
+ -- Thomas Viehmann t...@beamnet.de Thu, 05 Feb 2009 17:32:49 +0100
+
tar (1.20-1) unstable; urgency=low
* new upstream version
only in patch2:
unchanged:
--- tar-1.20.orig/src/system.c
+++ tar-1.20/src/system.c
@@ -24,6 +24,11 @@
#if MSDOS
+void
+sys_chroot (char* dir)
+{
+}
+
bool
sys_get_archive_stat (void)
{
@@ -120,6 +125,21 @@
static struct stat archive_stat; /* stat block for archive file */
+void
+sys_chroot (char* dir)
+{
+ if (chroot(dir) 0)
+{
+ int e = errno;
+ FATAL_ERROR ((0, e, _(Cannot chroot to %s), dir));
+}
+ if (chdir(/) 0)
+{
+ int e = errno;
+ FATAL_ERROR ((0, e, _(Cannot chdir to '/' after chroot to %s), dir));
+}
+}
+
bool
sys_get_archive_stat (void)
{
only in patch2:
unchanged:
--- tar-1.20.orig/src/tar.c
+++ tar-1.20/src/tar.c
@@ -252,6 +252,7 @@
CHECK_DEVICE_OPTION,
CHECKPOINT_OPTION,
CHECKPOINT_ACTION_OPTION,
+ CHROOT_OPTION,
DELAY_DIRECTORY_RESTORE_OPTION,
HARD_DEREFERENCE_OPTION,
DELETE_OPTION,
@@ -613,6 +614,8 @@
{add-file, ARGP_KEY_ARG, N_(FILE), 0,
N_(add given FILE to the archive (useful if its name starts with a dash)), GRID+1 },
+ {chroot, CHROOT_OPTION, N_(DIR), 0,
+ N_(chroot to directory DIR for extraction), GRID+1 },
{directory, 'C', N_(DIR), 0,
N_(change to directory DIR), GRID+1 },
{files-from, 'T', N_(FILE), 0,
@@ -1590,6 +1593,10 @@
args-version_control_string = arg;
break;
+case CHROOT_OPTION:
+ chroot_option = arg;
+ break;
+
case DELAY_DIRECTORY_RESTORE_OPTION:
delay_directory_restore_option = true;
break;
only in patch2:
unchanged:
--- tar-1.20.orig/src/common.h
+++ tar-1.20/src/common.h
@@ -141,6 +141,9 @@
/* Print a message if not all links are dumped */
GLOBAL int check_links_option;
+/* Chroot option value. */
+GLOBAL char const *chroot_option;
+
/* Patterns that match file names to be excluded. */
GLOBAL struct exclude *excluded;
@@ -293,6 +296,7 @@
/* Specified value or pattern. */
GLOBAL const char *volume_label_option;
+
/* Other global variables. */
@@ -700,6 +704,7 @@
/* Module system.c */
+void sys_chroot (char* dir);
void sys_detect_dev_null_output (void);
void sys_save_archive_dev_ino (void);
void sys_drain_input_pipe (void);
only in patch2:
unchanged:
Bug#514016: options for fixing
On Thu, 2009-02-05 at 18:20 +0100, Thomas Viehmann wrote: just as an exercise what might be done to fix this: It would seem that the options are - not fix it (for now), - find something in current tar that works (I didn't), - switch off tar, - try to do something with tar (new upstream - vs. release: ugh - has a apply to symlink target --transform flag, but that also might need post-processing of symlinks at end of bootstrapping), - try to do some ld-preload(?) trickery for changing the way symlinks are read, - try to find some way to chroot before calling tar, one possibility would be copying required files to some temp CWD, make tar look there for the libraries, chrooting to the target and calling tar from (the unchanged) CWD, - add chroot option to tar (see patch). How about just fixing the offending package to use a relative symlink, like /lib64 - lib? This is well within policy since they're adjacent objects in the same directory, and is less likely to break things or be a pain to maintain over time than any of the options above. I can't think of any negative consequence to this change, offhand? Adding a Debian-specific option to tar would certainly not be my first choice. Bdale -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514016: Bug#514015: options for fixing
On Thu, Feb 05, 2009 at 06:20:24PM +0100, Thomas Viehmann wrote: just as an exercise what might be done to fix this: It would seem that the options are - find something in current tar that works (I didn't), There is nothing. - switch off tar, I intend to replace tar with a custom unpack routine in cdebootstrap. - try to do something with tar (new upstream - vs. release: ugh - has a apply to symlink target --transform flag, but that also might need post-processing of symlinks at end of bootstrapping), What would dpkg do with the symlinks in the the unpack phase? - try to do some ld-preload(?) trickery for changing the way symlinks are read, fakechroot have to do this someway, but I was unable to grok that code yet. - try to find some way to chroot before calling tar, one possibility would be copying required files to some temp CWD, make tar look there for the libraries, chrooting to the target and calling tar from (the unchanged) CWD, Rather hacky. Would mean to include mklibs-copy or similar functionality. - add chroot option to tar (see patch). This is a root only option. Bastian -- Conquest is easy. Control is not. -- Kirk, Mirror, Mirror, stardate unknown -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514016: Bug#514015: options for fixing
On Thu, Feb 05, 2009 at 10:44:25AM -0700, Bdale Garbee wrote: How about just fixing the offending package to use a relative symlink, like /lib64 - lib? This would only affect one part of the problem. But this bug is about the problem that it will write outside of the new root if it encounters symlinks not that they currently exist. Bastian -- Is truth not truth for all? -- Natira, For the World is Hollow and I have Touched the Sky, stardate 5476.4. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Meeting(s) at FOSDEM
Steve McIntyre st...@einval.com writes: Then: when and where would be a good time to meet up? Hello? Anyone? I won't be at FOSDEM :( -- O T A V I OS A L V A D O R - E-mail: ota...@debian.org UIN: 5906116 GNU/Linux User: 239058 GPG ID: 49A5F855 Home Page: http://otavio.ossystems.com.br - Microsoft sells you Windows ... Linux gives you the whole house. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Meeting(s) at FOSDEM
Hi, On Thu Feb 05, 2009 at 12:30:46 +, Steve McIntyre wrote: On Sun, Feb 01, 2009 at 02:53:58PM +, Steve McIntyre wrote: Hi folks, Apologies for the massive cross-posting, but I'm trying to arrange some discussions between the various teams, or at least those members who will be at FOSDEM. Topics I'd like us to talk about include: 1. how the d-i daily builds are done and distributed 2. how the needs of the kernel d-i teams can better be reconciled I'm guessing that quite a number of people may be interested in these, and in other topics. Is there anything else I'm missing that you would like to discuss? Then: when and where would be a good time to meet up? Hello? Anyone? not sure if i am going to fosdem at all. MAYBE i will go on sunday, but that is not carved in stone yet. Greetings Martin -- Martin Zobel-Helas zo...@debian.org | Debian System Administrator Debian GNU/Linux Developer | Debian Listmaster Public key http://zobel.ftbfs.de/5d64f870.asc - KeyID: 5D64 F870 GPG Fingerprint: 5DB3 1301 375A A50F 07E7 302F 493E FB8E 5D64 F870 -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Meeting(s) at FOSDEM
This one time, at band camp, Mark Hymers said: On Thu, 05, Feb, 2009 at 12:30:46PM +, Steve McIntyre spoke thus.. Apologies for the massive cross-posting, but I'm trying to arrange some discussions between the various teams, or at least those members who will be at FOSDEM. Topics I'd like us to talk about include: 1. how the d-i daily builds are done and distributed 2. how the needs of the kernel d-i teams can better be reconciled I'm guessing that quite a number of people may be interested in these, and in other topics. Is there anything else I'm missing that you would like to discuss? Then: when and where would be a good time to meet up? Hello? Anyone? Hi, I agree that it'd be a good idea to meet up and I'll make sure I'm there wearing my ftpteam hat (note, not ftpmaster so I can't finally agree to anything, but I'm willing to put any work in on the ftp side which is needed). I'm around all weekend up until Sunday afternoon at about 3, so whatever works for everyone else will be fine by me. I'll be around from ~1800 on Friday until midafteroon on Sunday, and think a meetup would be a good thing. Cheers, -- - | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
mdadm 2.6.7.2-1 uploaded, please unblock
Following my recent call for testers, I've had 7 positive and 0 negative reports, so I've uploaded mdadm 2.6.7.2-1 to unstable, which should hopefully take care of those RC bugs once and for all. The new version should not have any effect on the operation within D-I at all. Please unblock. -- .''`. martin f. krafft madd...@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems i wish i hadn't slept all day, it's really lowered my productivity -- robert mcqueen digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#514016: options for fixing
Hi, thanks for your replies. Again, this is mostly because I needed some idle occupation and am not into sudoku. Apologies for presenting it a way that looked like a proposal. Bdale Garbee wrote: How about just fixing the offending package to use a relative symlink, like /lib64 - lib? This is well within policy since they're adjacent objects in the same directory, and is less likely to break things or be a pain to maintain over time than any of the options above. I can't think of any negative consequence to this change, offhand? Well, having 1000 maintainers do the right thing is difficult, as proven by the release process. Adding a Debian-specific option to tar would certainly not be my first choice. Other options do exist, my list probably is not exhaustive, but I would think that they cost a lot of code with a lot of opportunity to add bugs where things work now and it might be interesting to have an upper bound for how involved a minimal fix is. Thinking on a larger scale, what we actually want to do here is unpack a tarball into a chroot. I venture that this is a reasonable use case of tar and that it might just be possible to try to have upstream agree to have such an option in principle so that there is a plan to get rid of the debian-specificity of the option. Bastian Blank wrote: - switch off tar, I intend to replace tar with a custom unpack routine in cdebootstrap. TBH, I'm not that impressed by the implementation of ar (or a subset) in dpkg and am not sure that reimplementing tar extraction it is a good path to take when I would think that an option for tar to do the right thing (whether internally munging symlinks when resolving paths or using chroot) might have a general use beyond bootstrapping Debian systems. - try to do something with tar (new upstream - vs. release: ugh - has a apply to symlink target --transform flag, but that also might need post-processing of symlinks at end of bootstrapping), What would dpkg do with the symlinks in the the unpack phase? I have not tested it, but I would venture the same thing (calling tar, ergo having the same problem) from when I last looked at it. - try to do some ld-preload(?) trickery for changing the way symlinks are read, fakechroot have to do this someway, but I was unable to grok that code yet. Well, you'd have to intercept all the relevant calls (for dereferencing/reading symlinks). Seems doable, but IMO tar would be the better place. But if the masses want funny business, so be it. ... - add chroot option to tar (see patch). This is a root only option. Yes. It was my impression that (c)debootstrap are supposed to be called by root. At least I always used to call them as root when I was a developer. Kind regards T. -- Thomas Viehmann, http://thomas.viehmann.net/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
