Re: release update and branching
On Fri, Dec 03, 2004 at 12:31:43AM -0500, martin yazdzik wrote: Dear Friends, THe question I would like to have had answered, to wit, is the dual boot disk geometry problem solved, has been. Thanks. For the record, when using 2.6 to boot the cd, one sees that no matter what, when checking the c,h,s before committing to the formatting, it remains x,16,63, in rc2. It rather sounds to me from the exchange herein as were the coders either amused at the pain they will inflict upon the unsuspecting, or willing to release an installer which they know full well will cost hundreds of people thousands of hours simply because non-coders are somehow less than human. This issue has been discussed since at least Ah, no, it is just part of a master plan to have people get ride of windows :) No, seriously, it is not that, but the CHS issue is less than evident to solve, as i believe in particular that it is linked with the various hacks that were done back then to break the 528MB barrier. June. At the moment, neither Ubuntu nor Debian can be installed on a non LBA bios to dual boot with a pre-existing windows installation using the ntloader. Can you do an install without touching the partition table, and then try the experimental version of parted, and see if it fixes your issue ? The packages are : ftp://ftp.debian.org/debian/pool/main/p/parted/parted_1.6.19-0.exp.1_i386.deb and : ftp://ftp.debian.org/debian/pool/main/p/parted/libparted1.6-12_1.6.19-0.exp.1_i386.deb As recently as yesterday, the issue came up in the DSLReports unix forum, http://www.dslreports.com/forum/remark,12006676~mode=flat. While no one respects the work here more than I, there is a lingering prejudice that non-coders do not count. So, the d-i sort of works. I have checked every week or so, getting as far as the partitioning, and, when I see x.16.63, stop, as I know the result. Well, windows made a mess of it, they should pay by getting erased :) Seriously again, i think the issues are more involved than that That is is silly that many notebook manufacturers use the non-user-changeable Phoenix bios, or that windows uses the legacy interrupts, c, may be well true, but there has to be a solution before the final, in my opinion. Obviously, the opinion of non-hackers is also taken to be irrelevant, since the attitude has become more and more that the only valid use of human intelligence is coding, and those who choose to be lawyers, or musicians, or physicians who merely want to use debian as they would windows must be somehow mentally deficient. We are not, and actually understand the problem rather well. Please calm done a bit, and help test the above packages. Therefore, I will admit my sheer stupidity and ask if someone could explain to the village idiot why one cannot simply prepare the free space, have the d-i format the free space without touching the partition This is absolutely no problem. i believe you have to do manual partitioning in partman, chose the partitions you want to use, and select them for root, swap, etc. Notice that on my pegasos box, which uses amiga partition tables, i have no such stupid CHS problems, and me lacking x86 hardware, it makes it a bit difficult for me to play with these issues. You are welcome to help out in the maintenance of the parted package, it is well known that i have asked for help on this since a while. Also, it is not known that the trunk version of parted does fix 100% of those cases, but it fixes more than the version currently in sarge/sid. Skipped load of other angry stuff Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: release update and branching
On Fri, Dec 03, 2004 at 06:34:55AM +0100, Christian Perrier wrote: That said, if we had done the change in august, then we would not have this problem anymore now, so the whole discussion comes down to if we will release this year yet (highly unlikely), or 6 or more onth from now. As a side remark in this thread, it would certainly be nice if we don't read such remark (it's unlikely that we release in less than 6 months) too often. I'm sometimes thinkink that part of our release No, i said it is unlikely that we release this year yet, i would bet for january/feburary if all goes well, but this year is in 28 days, and i believe this is less than the RMs post t-p-u fixing schedule, so ... And the main thing is that for cases where not much packages are involved, holding back for a maybe release that never happens is not a nice thing to do, and create more work for the maintainers, and more frustration than it is worth. Notice that i was told, we will release imminently and held back progress in packages two times already. Once for kernel-pckage in december 2003, and once about this selfsame issue in august, problems is because there is a strange feeling among developers that we cannot release. We should always be in a release mood...even two days after a release happened..:-) Well, but not to the point of freezing progress. In this case, if it was not for d-i, i believe that solving the issues involved takes less time that any upto freeze schedule we might have, so it is worth it. Even for d-i, i don't think the issues are all that complicated, but let's wait and hear back from Colin's tests in ubuntu, if that can make joeyh happier. On my own side, given the recent release update, I'm still optimistic about the release. I bet you a champaign bottle that we will not release in 2004 :) Given the arguments exchanged in this thread, I'm also not really in favour of a parted change now, for d-i sarge release. fine, you just volunteered with joeyh to hand-hold all those users whose windows will have become unusable to fix it :) Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#284058: Package: installation-reports
Package: installation-reports INSTALL REPORT Debian-installer-version: sarge-powerpc-netinst.iso (debian-installer rc2) uname -a: 2.6.8-powerpc #1 Sun Oct 3 13:22:21 CEST 2004 ppc GNU/Linux Date: December 2nd, 2004 Method: cd Machine: iBook G4 Processor: PowerPC G4 (7447A, altivec supported, clock 1066MHz) Memory: 256 MB Root Device: IDE Root Size/partition table: #type name length base ( size ) system /dev/hda1 Apple_partition_map Apple63 @ 1 ( 31.5k) Partition map /dev/hda2 Apple_Boot eXternal booter 17408 @ 64 ( 8.5M) Unknown /dev/hda3 Apple_UFS Apple_UFS_Untitled_2 8443192 @ 17472 ( 4.0G) Unknown /dev/hda4 Apple_Bootstrap untitled 1954 @ 8460664 (977.0k) NewWorld bootblock /dev/hda5 Apple_UNIX_SVR2 untitled9765625 @ 8462618 ( 4.7G) Linux native /dev/hda6 Apple_UNIX_SVR2 untitled 38476563 @ 18228243 ( 18.3G) Linux native /dev/hda7 Apple_UNIX_SVR2 swap1900314 @ 56704806 (927.9M) Linux swap Root is mounted on /dev/hda5, home on /dev/hda6, MAC OS X shipped with the computer is on /dev/hda3. Output of lspci and lspci -n: #lspci :00:0b.0 Host bridge: Apple Computer Inc. UniNorth 2 AGP :00:10.0 VGA compatible controller: ATI Technologies Inc RV250 5c63 [Radeon Mobility 9200 M9+] (rev 01) 0001:10:0b.0 Host bridge: Apple Computer Inc. UniNorth 2 PCI 0001:10:17.0 ff00: Apple Computer Inc. KeyLargo/Intrepid Mac I/O 0001:10:18.0 USB Controller: Apple Computer Inc. KeyLargo/Intrepid USB 0001:10:19.0 USB Controller: Apple Computer Inc. KeyLargo/Intrepid USB 0001:10:1a.0 USB Controller: Apple Computer Inc. KeyLargo/Intrepid USB 0001:10:1b.0 USB Controller: NEC Corporation USB (rev 43) 0001:10:1b.1 USB Controller: NEC Corporation USB (rev 43) 0001:10:1b.2 USB Controller: NEC Corporation USB 2.0 (rev 04) 0002:20:0b.0 Host bridge: Apple Computer Inc. UniNorth 2 Internal PCI 0002:20:0d.0 ff00: Apple Computer Inc. UniNorth/Intrepid ATA/100 0002:20:0e.0 FireWire (IEEE 1394): Apple Computer Inc. UniNorth 2 FireWire (rev 81) 0002:20:0f.0 Ethernet controller: Apple Computer Inc. UniNorth 2 GMAC (Sun GEM) (rev 80) #lspci -n :00:0b.0 0600: 106b:0034 :00:10.0 0300: 1002:5c63 (rev 01) 0001:10:0b.0 0600: 106b:0035 0001:10:17.0 ff00: 106b:003e 0001:10:18.0 0c03: 106b:003f 0001:10:19.0 0c03: 106b:003f 0001:10:1a.0 0c03: 106b:003f 0001:10:1b.0 0c03: 1033:0035 (rev 43) 0001:10:1b.1 0c03: 1033:0035 (rev 43) 0001:10:1b.2 0c03: 1033:00e0 (rev 04) 0002:20:0b.0 0600: 106b:0036 0002:20:0d.0 ff00: 106b:003b 0002:20:0e.0 0c00: 106b:0031 (rev 81) 0002:20:0f.0 0200: 106b:0032 (rev 80) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [O] Comments/Problems: Installer does not add existing MAC OS X installation to yaboot. On intels grub is able to add existing Windows to its config, it would be nice for yaboot to also have such option. Also debian-installer might be used as a very reliable hardware test - I got a computer which failed many times on installation procedure. Apple's hardware test CD stated that the computer was OK. But clearly it was not. Later it started to hang on MAC OS X and finally Apple replaced the unit for the good one. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#269036: Sarge: debian-installer partitioning failure
On Thu, Dec 02, 2004 at 08:43:35PM +0100, Frans Pop wrote: On Thursday 02 December 2004 15:28, Anton Zinoviev wrote: Notice that hda7 and hda8 start before the end of hda6. This partition table is broken (some partitioning tools are making such partition tables) and in order to be safe the partitioning program of the installer refuses to work with it. If you remove hda7 and hda8 the problem (I hope) will disappear. Well Actually, partman does just that itself if you for instance delete a large partition that's not on the end of the disk and create one or two new partitions in it's place. Hm, I wasn't clear enough. The problem is not that the partitions are not numbered acording to their disk order. Device BootStart EndBlocks Id System /dev/hda1 * 1 2349 17758408+ 7 HPFS/NTFS /dev/hda2 4695 5168 3583440 41 PPC PReP Boot /dev/hda3 2350 3321 7348320c Win95 FAT32 (LBA) /dev/hda4 3738 4694 7234920f Win95 Ext'd (LBA) /dev/hda5 3738 3805514048+ 82 Linux swap /dev/hda6 3806 4694 6720808+ 83 Linux /dev/hda7 3738 373830+ 83 Linux /dev/hda8 3806 380631 83 Linux Notice that hda7 is inside hda5 and hda8 is inside hda6. The start and the end here are measured in cylinders, so although I can not be sure, I suppose that hda7 and hda8 lay in the first track of the first cylinder of hda5 and hda6. Parted is not happy with such partitions so it is possible that this bug is the same as #242114, #258880, #263208 and #268580. Now I remember that parted allows creation of partitions in this forbiden area but partman has internal protection against this. I suppose that the partitioning tools of Mandrake and SuSE do not have such a protection. Anton Zinoviev -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Which package versions a d-i release contains?
On Thu, Dec 02, 2004 at 08:34:58PM +0100, Frans Pop wrote:
On Thursday 02 December 2004 14:39, Anton Zinoviev wrote:
How I can determine which version of partman was in rc1, beta4, etc.?
One way would be to download the netinst CD and see what version is
in /pool.
If that's a problem for you, I still have copies of all the netinsts from
beta3 onwards, so I could look the versions up for you.
No, thanks. We definitely need a better instrument to keep our history.
Would you mind if I create files
installer/history/sarge-rc2/Packages-{arm,i386,m68k,}
in trunk. The directory sarge-rc2/ could contain also other
information for rc2.
Anton Zinoviev
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#284070: Package: installation-reports
Package: installation-reports Debian-installer-version: 18-Nov-2004 16:28 http://ftp.debian.org/debian/dists/testing/main/installer-powerpc/rc2/images/powerpc/netboot/vmlinuz-prep.initrd uname -a: Linux powerstack 2.6.8-powerpc #1 Sun Oct 3 13:22:21 CEST 2004 pc unknown Date: 1-Dec-2004 19:00 Method: tftpboot with LAN tftp-server, network-installation without proxy using http://ftp2.de.debian.org Machine: Motorola PowerStack Series E Processor: PowerPC 604e Memory: 64M Root Device: SCSI 0:1:0 Root Size/partition table: Fügen Sie einfach die komplette Partitions- Tabelle ein, mit Notizen, welche Partition wo eingebunden wurde. Output of lspci and lspci -n: Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[O] Configure network HW: [O] Config network: [O] DHCP Detect CD: [ ] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [E] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[E] Reboot: [E] Comments/Problems: There is no way to add a PReP Boot Partition while partitioning the hard drive. I had to add a boot partition manually but was unable to set it to partition type PReP Boot. During installation process Thus no bootloader has been installed and reboot failed. Greetings, Nilz. -- http://nilz.hoschi.de
Bug#284082: Incomplete entry in the errata of rc2
Package: debian-installer Severity: critical Merit for the severity: may cause serious data loss. The current text in the errata is: * LVM failure on Sparc32 (at least). If you want to create LVM volume groups, the physical volumes must not reside at the beginning of the disk, or else activating new logical volumes within the volume group will fail. This is due to some unforeseen quirks in Sun disk labels. This failure happened because the the sun disk label resides at the beginning of the disk and the first partition may start from the beginning of the disk. Hence the partition table becomes part of the first partition. Most file systems are smart enough not to write data at the beginning of their place but this is not the case with the phisical volumes for LVM or RAID and not the case with the swap spaces. The users MAY NOT create swap spaces or partitions for LVM and RAID at the beginning of the disk or the partition table will be subsequently completely erased. Anton Zinoviev -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: installing debian on IBM 43P-150 (CHRP)
On Fri, Dec 03, 2004 at 12:51:13PM -, Leigh Brown wrote: Sven Luther said: On Fri, Dec 03, 2004 at 12:10:31PM -, Leigh Brown wrote: Sven Luther said: On Wed, Dec 01, 2004 at 01:25:46PM -, Leigh Brown wrote: [...] You can't boot from the CD's because they haven't been built to work on AIX firmware. To work on AIX firmware, they require the -U option to be specified in the mkisofs command. Huh, and you tell us only now :) No :-) http://lists.debian.org/debian-powerpc/2004/01/msg01031.html Let's fix that, or will it break other subarches booting ? I don't believe so, but testing might be an idea ;-) Colin mentioned that the -U option has to be used with great care though. It may be that a subset of the options enabled by -U will work. I will investigate. Ok, that would be nice, CCing Colin as he isn't actively following here right now ... Can we also add /ppc/bootinfo.txt onto the image? This will allow RS/6000's to autoboot, and, on newer ones, to display a nice message indicating what O/S is on the CD. Ok. What should be the content pf this file then ? Exactly as I described in the email I referenced ;-) (you need the icon data, even though it isn't used) I suppose any icon data would do, no ? Could we use a debian swirl of some kind instead ? or do you mean it will never be showed or something ? Friendly, Sven Luther description can be anything you like, as can os-name os-name is displayed by newer RS/6000 firmware. I put yaboot in /ppc/chrp, as that's where AIX's boot image goes. However, I think you could specify another path. Note, also, that the yaboot needs to have the note section added in order to work (ybin does this when it installs it normally). --- cut here --- chrp-boot descriptionDebian/GNU Linux Installation/description os-nameDebian/GNU Linux/os-name boot-scriptboot device;:\ppc\chrp\yaboot/boot-script icon size=64,64 color-space=3,3,2 bitmap FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Bug#273343: About you failed installation attempt on SPARC64
Hi! Thanks about your installation report. You sent it on 25 Sep 2004: http://bugs.debian.org/273343 You wrote: I have two SCSI hard drives of 2.2GB each. The plan was as follows: sda1 50MB /boot sda2 200MB swap sda4 1.9GB RAID0 storage \ sdb1 250MB swap/ (root) sdb2 1.9GB RAID0 storage / The problem was that you put swap space (sdb1) at the beginning of the disk. This is not allowed on sun disk labels because if the first partition start at the beginning of the disk then the partition table is part of the first partition. This is OK if the first partition contains some file system but it is not allowed if the first partition is swap or phisical volume for LVM or RAID. I selected Configure Software Raid, it wrote the partition layout to disk, created filesystems etc. Then it complained that there were no partition for RAID available, so I went back to the partitioning menu. Now my layout looked like this: sda1 51.0MB /boot sda2 199.9MB swap sda4 1.9GB physical volume (LVM) sdb1 2.2GB swap Where did my second physical volume go??? Because the partition table was part of sdb1 it was erased when the partitioner formatted the swap space. We definitely need a warning message if the user tries to put swap, LVM or RAID at the beginning of the disk. Thanks again for you report. Anton Zinoviev -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#273982: partman: Broken display during Arabic installs
On Wed, Sep 29, 2004 at 07:38:19AM +0200, Christian Perrier wrote: The attached screen captures show the main partman screen and the partition aditiing screen during an Arabic install. As you may see, the display is somewhat broken. For instance the partition size and the unit are not close together and the display is not properly aligned. This is probably a consequence of formatting with a left-to-right reasoning and will probably affect all install with right-to-left languages. What algorithms are used to format the screen for such languages? Anton Zinoviev -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#273867: marked as done (Sarge partman unable to reuse Woody swap partition successfully)
Your message dated Fri, 3 Dec 2004 17:04:17 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#273867: Sarge partman unable to reuse Woody swap partition successfully has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 28 Sep 2004 14:58:36 + From [EMAIL PROTECTED] Tue Sep 28 07:58:36 2004 Return-path: [EMAIL PROTECTED] Received: from pxy2allmi.all.mi.charter.com (proxy2-grandhaven.chartermi.net) [24.247.15.40] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1CCJR6-0003Y2-00; Tue, 28 Sep 2004 07:58:36 -0700 Received: from HEATHER (24.247.116.250.kzo.mi.chartermi.net [24.247.116.250]) by proxy2-grandhaven.chartermi.net (8.12.10+Sun/8.12.10) with ESMTP id i8SEvudm023914 for [EMAIL PROTECTED]; Tue, 28 Sep 2004 10:57:57 -0400 (EDT) Message-Id: [EMAIL PROTECTED] From: Michael Lueck [EMAIL PROTECTED] To: [EMAIL PROTECTED] [EMAIL PROTECTED] Date: Tue, 28 Sep 2004 10:59:16 -0400 Priority: Normal X-Mailer: PMMail 2000 Professional (2.20.2717) For Windows 2000 (5.0.2195;4) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Sarge partman unable to reuse Woody swap partition successfully X-Charter-Information: X-Charter-Scan: X-Charter-Score: s Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-4.7 required=4.0 tests=BAYES_30,HAS_PACKAGE, TO_ADDRESS_EQ_REAL autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Package: partman I downloaded and burned a Sarge CD on 20040923. I booted expert26 mode. The PC I was installing on had already been partitioned / used by Woody, then pointed at the testing files and updated to testing. I reformatted existing Linux partitions from ReiserFS to XFS successfully. However, swap came up with the smiley face, and so I did nothing with it. Committing the partitioning was successful other than swap which made it through to 100% on its progress bar, then a failure message came up. I had tried to allow it to prepare swap multiple times without success. I had to physically delete the partition and recreate it as a swap partition. I have reinstalled Sarge, smiley face for swap, and all was well. So I guess I would have to drop back to Woody, then up to Sarge to recreate this, or does someone know of an incompatibility in swap format off the top of your head and you don't need me to do a recreate on this one? Thanks! Michael Lueck Lueck Data Systems http://www.lueckdatasystems.com/ --- Received: (at 273867-done) by bugs.debian.org; 3 Dec 2004 14:00:56 + From [EMAIL PROTECTED] Fri Dec 03 06:00:56 2004 Return-path: [EMAIL PROTECTED] Received: from lio.fmi.uni-sofia.bg (smtp.fmi.uni-sofia.bg) [62.44.101.7] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1CaDzU-pu-00; Fri, 03 Dec 2004 06:00:56 -0800 Received: from logic.fmi.uni-sofia.bg ([62.44.100.59]) by smtp.fmi.uni-sofia.bg; Fri, 3 Dec 2004 15:55:43 +0200 Received: from zinoviev by logic.fmi.uni-sofia.bg with local (Exim 3.35 #1 (Debian)) id 1CaEyn-0006d0-00; Fri, 03 Dec 2004 17:04:17 +0200 Date: Fri, 3 Dec 2004 17:04:17 +0200 From: Anton Zinoviev [EMAIL PROTECTED] To: Michael Lueck [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: Bug#273867: Sarge partman unable to reuse Woody swap partition successfully Message-ID: [EMAIL PROTECTED] References: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: [EMAIL PROTECTED] User-Agent: Mutt/1.3.28i Sender: Anton Zinoviev [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Thanks for your installation report. On Tue, Sep 28, 2004 at 10:59:16AM -0400, Michael Lueck wrote: However, swap came up with the smiley face, and so I did nothing with it. Committing the partitioning was successful other than swap which made it through to 100% on its progress bar, then a failure message came up. In the resent verions of the installer partman always reformats the swap
Bug#283967: installation-reports: languagechooser error on alpha
On Fri, 3 Dec 2004, Christian Perrier wrote: rc2 businesscard install, automated via preseed/url file. On my initial attempt I booted with: 0 languagechooser/language-name=English preseed/url=http://url debconf/priority=critical That one may be tricky...as I'm doing nearly the same with my babelbox which autoinstalls itself in all languages. The only difference is that I use DEBCONF_PRIORITY=critical...and it is a i386 machine, not alpha. Agreed.. I think it may ba alpha specific. I've booted with the exact same arguments dozens of times on i386, and several times each on hppa and ia64 all with no problems. Thanks, -- Paul Telford | 1024D/431B38BA | [EMAIL PROTECTED] | [EMAIL PROTECTED] C903 0E85 9AF5 1B80 6A5F F169 D7E9 4363 431B 38BA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#274290: FWD: Re: Bug#274290: debian-installer: Manual partitioning does not give full control
On Fri, Oct 01, 2004 you wrote: * I miss the exact partition sizes that cfdisk gives me. The new one says things like 1.9GB, whereas cfdisk says e.g. 5996.23MB. This is a good wishlist - give the user the chance to change the format of the screen and in particular the precision and measure units. * I like to be able to see the partition data for all partitions at once. Would it be enough if the user is able to hide the explanatory messages in the upper part of the screen? * I like cfdisk's ability tho show partitions either by their size, or by cylinders/sectors. A very long time ago the partitioner was able to do so. Then this possibility was removed but you still are able to check the cylinder/sector start and end of the free spaces. How stupid... ;-) * I like to be able to specify partitions by their starting and ending * cylinders. OK. * And in addition: cfdisk is available (also) after installation. The new is not(?). It is available on your installation media. ;-) Anton Zinoviev -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#275089: sarge-i386-netinst: bug report
Thanks for your installation report. On Tue, Oct 05, 2004 at 03:58:31PM -0700, Charles Lear wrote: Device Boot Start End Blocks Id System /dev/hda1 * 14857390138217 HPFS/NTFS /dev/hda26690996426306437+ 5 Extended /dev/hda34858668914715536+ 83 Linux [Suse Linux] /dev/hda46822812810498477+ 83 Linux [Slack /home] /dev/hda566906821 1060258+ 82 Linux swap /dev/hda681299178 8434092+ 83 Linux [Slackware /] /dev/hda791799964 6313513+ 83 Linux Some partitioning tools (probably SuSE in your case) create broken partition tables. Notice that the primary partition hda4 is inside the extended partition hda2. Thats why the Debian installer does not recognise the partition table. It is a good idea however to show the user an informational message about the reasons why the partition table was not recognised. Anton Zinoviev -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#276482: marked as done (installer creates too small extended partition)
Your message dated Fri, 3 Dec 2004 18:07:49 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#276482: installer creates too small extended partition has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 14 Oct 2004 13:33:20 + From [EMAIL PROTECTED] Thu Oct 14 06:33:20 2004 Return-path: [EMAIL PROTECTED] Received: from mx2.perftech.si (butn.net) [195.246.0.30] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1CI5jM-6h-00; Thu, 14 Oct 2004 06:33:20 -0700 Received: from WorldClient ([127.0.0.1]) (authenticated user [EMAIL PROTECTED]) by butn.net (butn.net [195.246.0.30]) (MDaemon.PRO.v6.8.5.R) with ESMTP id 40-md5000124.tmp for [EMAIL PROTECTED]; Thu, 14 Oct 2004 15:33:15 +0200 Received: from [213.253.102.145] via WorldClient with HTTP; Thu, 14 Oct 2004 15:33:14 +0200 Date: Thu, 14 Oct 2004 15:33:14 +0200 From: xerces8 [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: installer creates too small extended partition Message-ID: [EMAIL PROTECTED] X-Mailer: WorldClient 6.8.5 X-Authenticated-Sender: [EMAIL PROTECTED] X-Spam-Processed: butn.net, Thu, 14 Oct 2004 15:33:15 +0200 (not processed: message from valid local sender) X-MDRemoteIP: 127.0.0.1 X-Return-Path: [EMAIL PROTECTED] X-MDaemon-Deliver-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Package: installation-reports Debian-installer-version: 20040930 ( rc2 from web ) uname -a: Linux slave13 2.4.27-1-386 #1 Fri Sep 3 06:24:46 UTC 2004 i686 GNU/Linux Date: 2004-oct-02 Method: boot CD (Debian GNU/Linux testing Sarge - Official Snapshot i386 Binary-1 (20040930)) Machine: desktop PC ( MB : Gigabyte GA-7VAXP Ultra , BIOS version F7 ) Processor: AMD K-7 Athlon XP2200+ Memory: 768 MB DDR (2x133 MHz) Root Device: Maxtor 6Y160P0, ATA DISK drive, partition /dev/hdg5 Root Size/partition table: # fdisk -l /dev/hdg Disk /dev/hdg: 163.9 GB, 163928604672 bytes 255 heads, 63 sectors/track, 19929 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdg1 1 608 4883728+ 82 Linux swap /dev/hdg2 609304019535040f W95 Ext'd (LBA) /dev/hdg33041547319543072+ 83 Linux ( this is not used ) /dev/hdg5 609304019535008+ 83 Linux ( this it root ) Output of lspci and lspci -n: :00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400/KT600 AGP] Host Bridge :00:01.0 PCI bridge: VIA Technologies, Inc. VT8235 PCI Bridge :00:0c.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11) :00:0c.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11) :00:0f.0 RAID bus controller: Promise Technology, Inc. PDC20276 (MBFastTrak133 Lite) (rev 01) :00:10.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 80) :00:10.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 80) :00:10.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 80) :00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) :00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge :00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) :00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50) :00:13.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) :00:14.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46) :01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R200 QL [Radeon 8500 LE] :00:00.0 0600: 1106:3189 :00:01.0 0604: 1106:b168 :00:0c.0 0400: 109e:036e (rev 11) :00:0c.1 0480: 109e:0878 (rev 11) :00:0f.0 0104: 105a:5275 (rev 01) :00:10.0 0c03: 1106:3038 (rev 80) :00:10.1 0c03: 1106:3038 (rev 80) :00:10.2 0c03: 1106:3038 (rev 80) :00:10.3 0c03: 1106:3104 (rev 82) :00:11.0 0601: 1106:3177 :00:11.1 0101: 1106:0571
Summary / new quik available (was Re: please test new quik with initrd-support (was: Re: getting quik into sarge?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Peter 'p2' De Schrijver has made some new updates to the quik - you can get it (.deb and source) at the http://www.ulyssis.org/~p2/debjes/ changes include: - manpage tells about initrd - compiles with gcc3 - sprintf bug fixed - ANS raid support quik with initrd has been tested on - - ANS (Peter 'p2' De Schrijver) - - PMac 4400/200 (me) - - PMac 6500/250 (Romain Francoise) - - PMac 7200/90 (Peter 'p2' De Schrijver, me) - - PMac 9500 (Jaakko Niemi) - - PMac Beige G3 Rev II (Simon Vallet) If you got an(other) oldworld machine, please test this quik while installing the latest kernel-image-2.6.8-powerpc.deb (contains an initrd). Nobody mentioned to have tried with less than 32mb ram, if you do, please report your results as well. Colin Watson wrote: This seems to be inappropriately built as a native package. If it were built non-native then it would be easier for me to look over the .diff.gz to see the changes from upstream. Still on the todo list - should be done as fast as possible to be able to achieve the goal of inclusion in sarge.. ;-) regards, Holger -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBsIxXUHLQNqxYNSARApY3AJ992wMaZX5fF7xK0Uly9zvv6JRvhgCfZfhy FUBb29pI2Wc4+msxMRyw8mY= =u/oi -END PGP SIGNATURE-
Bug#284058: Package: installation-reports
reassign 284058 os-prober retitle 284058 Did not detect a Mac OS/X install thanks Installer does not add existing MAC OS X installation to yaboot. On intels grub is able to add existing Windows to its config, it would be nice for yaboot to also have such option. As far as I can see, os-prober is supposed to detect OS/X installs. The test is by trying to find a file named mach_kernel at the root of the tested partitions. I have no clue on PPC systems...just quickly analysing your install report. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: release update and branching
Sven Luther wrote: That said, if we had done the change in august, then we would not have this problem anymore now, so the whole discussion comes down to if we will release this year yet (highly unlikely), or 6 or more onth from now. I'm sorry, but I regard that attitude as such complete bullshit that I cannot talk to people who have it. Bye. -- see shy jo signature.asc Description: Digital signature
Processed: reassign 284082 to www.debian.org
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.8.5 reassign 284082 www.debian.org Bug#284082: Incomplete entry in the errata of rc2 Bug reassigned from package `debian-installer' to `www.debian.org'. 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 [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
FWD: megaraid2 issue debian sarge
- Forwarded message from Mike Müller - MySign AG [EMAIL PROTECTED] - From: Mike Müller - MySign AG [EMAIL PROTECTED] Date: Fri, 3 Dec 2004 12:07:34 +0100 To: [EMAIL PROTECTED] Subject: megaraid2 issue debian sarge Hi Joey I read the workaround to install debian sarge on a dell 2850 on the debian list, but couldn't figure out, how exactly I can do that. Do you can give me some more details how I get the megaraid2 controller working with debian sarge? thanks a lot. best regards mike müller MySign AG Schachenallee 29 CH-5000 Aarau Tel.: 0878 877 000 Email: [EMAIL PROTECTED] Web: http://www.mysign.ch MySign - setzt Zeichen im Internet - End forwarded message - -- see shy jo signature.asc Description: Digital signature
Bug#284082: Incomplete entry in the errata of rc2
Please don't file RC bug reports about the WEB SITE on the debian-installer pseudo package. We have a pasudo-package for the web site, and the d=-i psudo package is abused enough as it is, and huge time sink for me to reassign all the crap that is assigned here to the correct package. Anton Zinoviev wrote: The current text in the errata is: * LVM failure on Sparc32 (at least). If you want to create LVM volume groups, the physical volumes must not reside at the beginning of the disk, or else activating new logical volumes within the volume group will fail. This is due to some unforeseen quirks in Sun disk labels. This failure happened because the the sun disk label resides at the beginning of the disk and the first partition may start from the beginning of the disk. Hence the partition table becomes part of the first partition. Most file systems are smart enough not to write data at the beginning of their place but this is not the case with the phisical volumes for LVM or RAID and not the case with the swap spaces. The users MAY NOT create swap spaces or partitions for LVM and RAID at the beginning of the disk or the partition table will be subsequently completely erased. Two words: Unified diff. -- see shy jo signature.asc Description: Digital signature
Bug#284112: installation-reports
Package: installation-reports Debian-installer-version: rc2 dated 18-11-2004 uname -a: Linux indeb005 2.6.8-1-686 #1 Thu Nov 25 04:34:30 UTC 2004 i686 GNU/Linux Date: 2004-12-03 16:00 Method: netboot using a dhcp-ed pxe nic (tg3) with tftp-hpa from a local apt mirror through apt-proxy Machine: Compaq/HP DL-380 dual processor Processor: Intel(R) Xeon(TM) CPU 2.80GHz (2x) Memory: 1GB RAM Root Device: Compaq Smart Array 5i/532 with 2 x 72GB scsi hd's in mirror Root Size/partition table: indeb005:~# fdisk -l /dev/cciss/c0d0 Disk /dev/cciss/c0d0: 72.8 GB, 72826629120 bytes 255 heads, 63 sectors/track, 8854 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/cciss/c0d0p1 1 34 273073+ 83 Linux /dev/cciss/c0d0p2 351994157437005 Extended /dev/cciss/c0d0p3 *19952116 979965 83 Linux /dev/cciss/c0d0p5 35 642 4883728+ 83 Linux /dev/cciss/c0d0p6 6431007 2931831 83 Linux /dev/cciss/c0d0p710081337 2650693+ 82 Linux swap /dev/cciss/c0d0p813381386 393561 83 Linux /dev/cciss/c0d0p913871994 4883728+ 83 Linux Output of lspci and lspci -n: indeb005:~# lspci :00:00.0 Host bridge: ServerWorks CMIC-LE Host Bridge (GC-LE chipset) (rev 33) :00:00.1 Host bridge: ServerWorks CMIC-LE Host Bridge (GC-LE chipset) :00:00.2 Host bridge: ServerWorks CMIC-LE Host Bridge (GC-LE chipset) :00:03.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27) :00:04.0 System peripheral: Compaq Computer Corporation Integrated Lights Out Controller (rev 01) :00:04.2 System peripheral: Compaq Computer Corporation Integrated Lights Out Processor (rev 01) :00:0f.0 ISA bridge: ServerWorks CSB5 South Bridge (rev 93) :00:0f.1 IDE interface: ServerWorks CSB5 IDE Controller (rev 93) :00:0f.2 USB Controller: ServerWorks OSB4/CSB5 OHCI USB Controller (rev 05) :00:0f.3 Host bridge: ServerWorks CSB5 LPC bridge :00:10.0 Host bridge: ServerWorks CIOB-X2 PCI-X I/O Bridge (rev 05) :00:10.2 Host bridge: ServerWorks CIOB-X2 PCI-X I/O Bridge (rev 05) :00:11.0 Host bridge: ServerWorks CIOB-X2 PCI-X I/O Bridge (rev 05) :00:11.2 Host bridge: ServerWorks CIOB-X2 PCI-X I/O Bridge (rev 05) :01:03.0 RAID bus controller: Compaq Computer Corporation Smart Array 5i/532 (rev 01) :02:01.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5703X Gigabit Ethernet (rev 02) :02:02.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5703X Gigabit Ethernet (rev 02) :06:1e.0 PCI Hot-plug controller: Compaq Computer Corporation PCI Hotplug Controller (rev 14) indeb005:~# lspci -n :00:00.0 0600: 1166:0014 (rev 33) :00:00.1 0600: 1166:0014 :00:00.2 0600: 1166:0014 :00:03.0 0300: 1002:4752 (rev 27) :00:04.0 0880: 0e11:b203 (rev 01) :00:04.2 0880: 0e11:b204 (rev 01) :00:0f.0 0601: 1166:0201 (rev 93) :00:0f.1 0101: 1166:0212 (rev 93) :00:0f.2 0c03: 1166:0220 (rev 05) :00:0f.3 0600: 1166:0225 :00:10.0 0600: 1166:0101 (rev 05) :00:10.2 0600: 1166:0101 (rev 05) :00:11.0 0600: 1166:0101 (rev 05) :00:11.2 0600: 1166:0101 (rev 05) :01:03.0 0104: 0e11:b178 (rev 01) :02:01.0 0200: 14e4:16a7 (rev 02) :02:02.0 0200: 14e4:16a7 (rev 02) :06:1e.0 0804: 0e11:a0f7 (rev 14) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [ ] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[E] Reboot: [O] Comments/Problems: Grub still does not install on these kind (scsi?) of machines. The file /boot/grub/stage1 not read correctly. is the main error message, I think. Worked around it by installing lilo. Does anybody know of a way to install grub? debian-installer logs available on request. Have control of this beast, when asked, available for debugging. Screens (typos possible, had to copy it the chinese way ;-)) : tty1: [!!] Install the GRUB boot loader on a Unable to install GRUB in (hd0) Executing 'grub-install (hd0)' failed. This is a fatal error. Go Back Continue tty3: Setting up usbutils (0.11+==cvs20041108-1) ... Reading Package Lists... Building Dependency Tree... e2fsprogs is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Reading Package Lists... Building Dependency Tree... Suggested packages: grub-doc grubconf The following NEW packages will be installed: grub 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 350kB of archives. After unpacking
Re: release update and branching
On Fri, Dec 03, 2004 at 01:39:49PM -0500, Joey Hess wrote: Sven Luther wrote: That said, if we had done the change in august, then we would not have this problem anymore now, so the whole discussion comes down to if we will release this year yet (highly unlikely), or 6 or more onth from now. I'm sorry, but I regard that attitude as such complete bullshit that I cannot talk to people who have it. Bye. Joeyh, do you seriously think we can release this year yet (as in the next 4 weeks) ? I don't think there is time for this even if t-p-u was fixed today. I agree on a january-feburary timeframe, and even in this case, using the new parted would be problematic, as you well know. On the other hand, if the release is going to happen months from now, as already happened two times in the past (december 2003, august 2004), then we will have time to do the switch. I am right now making sure that we have a version in experimental of all the rdepends of libparted, so that this second solution is doable if we go that way, but this is seriously no particular reason to take it that way, is it ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#283793: marked as done (debian-installer: quik is still installed and trying to do unwanted things on my harddisk which my break.)
Your message dated Fri, 3 Dec 2004 19:23:57 + with message-id [EMAIL PROTECTED] and subject line Bug#283793: debian-installer: quik is still installed and trying to do unwanted things on my harddisk which my break. has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 1 Dec 2004 12:02:18 + From [EMAIL PROTECTED] Wed Dec 01 04:02:18 2004 Return-path: [EMAIL PROTECTED] Received: from smtp6.wanadoo.fr [193.252.22.25] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1CZTBa-vD-00; Wed, 01 Dec 2004 04:02:18 -0800 Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf0603.wanadoo.fr (SMTP Server) with SMTP id 715091C001E1; Wed, 1 Dec 2004 13:01:46 +0100 (CET) Received: from pegasos (AStrasbourg-251-1-46-108.w82-126.abo.wanadoo.fr [82.126.219.108]) by mwinf0603.wanadoo.fr (SMTP Server) with ESMTP id 463761C001F1; Wed, 1 Dec 2004 13:01:46 +0100 (CET) Received: from luther by pegasos with local (Exim 4.34) id 1CZTBN-0002a9-EA; Wed, 01 Dec 2004 13:02:05 +0100 Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Sven Luther [EMAIL PROTECTED] To: Debian Bug Tracking System [EMAIL PROTECTED] Subject: debian-installer: quik is still installed and trying to do unwanted things on my harddisk which my break. X-Mailer: reportbug 3.0 Date: Wed, 01 Dec 2004 13:02:05 +0100 Message-Id: [EMAIL PROTECTED] Sender: Sven Luther [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Package: debian-installer Severity: important I am doing a install of the jigdo DVD images for powerpc, using the 24.11.2004 jigdo images, which should use RC2. Quik is still installed on my chrp/pegasos system, even though it should only be installed on oldworld powerpc hardware. It has been month since this is a known problem, and nothing happened to solve this issue, which i hear has to do with the override file, or something such. Friendly, Sven Luther -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: powerpc (ppc) Kernel: Linux 2.4.27-powerpc Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) --- Received: (at 283793-done) by bugs.debian.org; 3 Dec 2004 19:24:01 + From [EMAIL PROTECTED] Fri Dec 03 11:24:00 2004 Return-path: [EMAIL PROTECTED] Received: from chiark.greenend.org.uk [193.201.200.170] (mail) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1CaJ28-0004Rm-00; Fri, 03 Dec 2004 11:24:00 -0800 Received: from [192.168.124.112] (helo=riva.lab.dotat.at) by chiark.greenend.org.uk (Debian Exim 3.35 #1) with esmtp (return-path [EMAIL PROTECTED]) id 1CaJ26-0005ZP-00 for [EMAIL PROTECTED]; Fri, 03 Dec 2004 19:23:58 + Received: from cjwatson by riva.lab.dotat.at with local (Exim 3.35 #1 (Debian)) for [EMAIL PROTECTED] id 1CaJ25-0003K9-00; Fri, 03 Dec 2004 19:23:57 + Date: Fri, 3 Dec 2004 19:23:57 + From: Colin Watson [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Bug#283793: debian-installer: quik is still installed and trying to do unwanted things on my harddisk which my break. Message-ID: [EMAIL PROTECTED] References: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: [EMAIL PROTECTED] User-Agent: Mutt/1.3.28i Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: On Wed, Dec 01, 2004 at 07:52:13PM +, Colin Watson wrote: The bug is that quik is Priority: important when it should be extra (as a package only appropriate to specific hardware); this is bug #278187 against ftp.debian.org. However, the current version of quik in unstable works around this, and I've approved that for testing, so that should fix this bug too. It's still ugly that quik is installed, but
Bug#284128: GRUB fails with Sarge RC2
Package: installation-reports Debian-installer-version: Sarge i386 RC2 Downloaded the 2004/12/01 on http://ftp.acc.umu.se/pub/cd-images/debian-weekly/i386/sarge-i386-1.iso uname -a: Date: 2004/12/02 Method: install from cd-rom Machine: Acer Aspire 1300 Processor: Athlon Memory: 256MB Root Device: IDE Root Size/partition table: Device Boot Start End Blocks Id System /dev/hda1 * 1 608 4883728+ b W95 FAT32 /dev/hda2 609243214651280f W95 Ext'd (LBA) /dev/hda5 609 632 192748+ 82 Linux swap / Solaris /dev/hda6 6331440 6490228+ 83 Linux /dev/hda714412092 5237158+ 83 Linux /dev/hda820932432 2731018+ 83 Linux Output of lspci and lspci -n: Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[E] Reboot: [ ] Comments/Problems: /dev/hda6 contains a previously installed Sarge RC1, ReiserFS I try an install of Sarge RC2 on /dev/hda7, ReiserFS GRUB seems to fail when it seeks partitions -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
sarge installer and 3rd party modules
Hi all, I've been trying to get my system installed with the latest sarge-netinst image using a USB flashdisk. I have a supermicro system containing a marvell 4-port SATA controller, I received the driver source from supermicro compiled it for 2.6.8-1-386 and put the resulting module on the USB stick. The installer boots allows me to configure country/language/keyboard, before the install program itself starts I exit to a shell and load the mv_sata.ko driver, it loads correctly and disks are detected. I can continue to setup the system (even the RAID ; it surprised me but you guys made really a great installer). But when installing the base system, there suddendly comes an error while creating the initrd image that it cannot find the mv_sata module and the installer stops. What is the best way to include a 3rd party module that works as it should in the installer process ? regards, Bart Duchesne -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: please test new quik with initrd-support (was: Re: getting quik into sarge?
Ce jour Sun, 28 Nov 2004, Christian Leimer a dit: Hi! Can someone please post a sample quik.conf? Do you use the ramdisk option or the append string one, any other settings? I have an Umax S900 and it does not work here. Says something about can not find the root device. I use an adaptec uw2940 and a ext3 formated hd. Maybe this is the troublemaker. adaptec 2940uw can't boot from. and do not use anything BUT ext2 for quik, it does not have ext3 or other support. And what is that chosen/bootargs= for? that gets initialised only when a client OS (e.g., like linux) gets loaded into memory. Thanks. Bye chris. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] signature.asc Description: Digital signature
Processed: reassign 283233 to base-passwd ...
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.8.5 reassign 283233 base-passwd Bug#283233: base-config: Adding the first user to the plugdev group Bug reassigned from package `base-config' to `base-passwd'. retitle 283233 add a static plugdev group so newly installed systems can add the first user account to this group (which it already tries to do) Bug#283233: base-config: Adding the first user to the plugdev group Changed Bug title. 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 [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#276482: acknowledged by developer (Re: Bug#276482: installer creates too small extended partition)
Anton Zinoviev [EMAIL PROTECTED] wrote : Yes, the installer creates the extended partition as small as possible. This is not a problem because the extended partition can always be resized provided it doesn't cover some primary partition. Most partitioning programs can resize the extended partition. For example cfdisk does this for you whithout your knowledge. Parted also can resize the extended partition. I must disagree here. No tool that I tried could extend the partition. It is not the job of the user to go around and hunt for a tool that happens to work. Especially if he used for 15 years partitions that did not require such an exercise. For the record, I tried fdisk ( util-linux ) and Disk Manegement under Windows XP. Maybe some other tool too, I don't remember. So what are the advantegs of this, let's say unusual, partitioning ? Because this is the first time I see such a thing. Thanks for your time, David -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#283233: static user needed; rest done in base-config
I have made base-config add the first user to plugdev, if that group exists. So we only need a static plugdev group to be added in base-passwd and this will be fixed. See http://oskuro.net/blog/freesoftware/gnome-2.8-sarge-2004-12-03-18-19 for some good reasoning about why this will become a FAQ if it's not fixed. Note that pmount's postinst does this, which should not break or even complain if the group already exists: addgroup --quiet --system plugdev || true The group is not deleted when plugdev is removed, so that's ok too. -- see shy jo signature.asc Description: Digital signature
Re: please test new quik with initrd-support
Ce jour Sun, 28 Nov 2004, Simon Vallet a dit: On Fri, 26 Nov 2004 10:58:48 +0100 Holger Levsen [EMAIL PROTECTED] wrote: kernel-image-2.6.9-powerpc and initrd : I get stuck at VFS : Unable to mount root fs on unknown-block (1,0), which is what I experienced with previous quik versions. do you have support for the device you're trying to boot from? adaptec 2940 isn't bootable, period. it's missing an OF 'open' word. Here are the relevant quik.conf options I used : image=/boot/vmlinux-2.6.9-powerpc append=root=/dev/ram0 initrd=/boot/initrd.img-2.6.9-powerpc video=radeonfb:1024 [EMAIL PROTECTED] Label=Test Are there other kernel command-line options to try ? read man quik.conf. also an option that was added with the new code, is that pause-after= option another list member posted. probably should go in the same section as the root= and partition= options. eric Simon -- Simon Vallet Due to massive spam, the address shown in the From: header only accepts mail from Debian hosts. If you wish to mail me privately, just use the 'user' local part. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- I believe that part of what propels science is the thirst for wonder. It's a very powerful emotion. All children feel it. In a first grade classroom everybody feels it; in a twelfth grade classroom almost nobody feels it, or at least acknowledges it. Something happens between first and twelfth grade, and it's not just puberty. Not only do the schools and the media not teach much skepticism, there is also little encouragement of this stirring sense of wonder. Science and pseudoscience both arouse that feeling. Poor popularizations of science establish an ecological niche for pseudoscience. - Carl Sagan, The Burden Of Skepticism, The Skeptical Inquirer, Vol. 12, Fall 87 signature.asc Description: Digital signature
Re: please test new quik with initrd-support
Ce jour Tue, 30 Nov 2004, Simon Vallet a dit: On Mon, 29 Nov 2004 23:05:03 +0100 Peter 'p2' De Schrijver [EMAIL PROTECTED] wrote: The quik.conf should be : image=/boot/vmlinux-2.6.9-powerpc append=root=/dev/ram video=radeonfb:[EMAIL PROTECTED] initrd=/boot/initrd.img-2.6.9-powerpc Label=test this works indeed *much* better :-) The kernel boots fine,with some glitches : - the video output is not sent to the third party video card, despite the video= option. This is a Radeon 7000, which is set as OF output-device. I get kernel messages and login prompt on the built-in RageII, although the radeon is recognized by the kernel. - neither network adapter is recognized -- eth0 is a natsemi card, and eth1 is a BMAC -- but I suppose this is purely a missing module problem Could you send me the boot log ? Attached are the boot.log, relevant kern.log parts, and a dmesg output 2.6.9 boots on yours? i get a kernel segfault when route sets up the ipv6 routes eric HTH, Simon -- Simon Vallet signature.asc Description: Digital signature
Re: please test new quik with initrd-support (was: Re: getting quik into sarge?
Ce jour Sun, 28 Nov 2004, Colin Watson a dit: On Fri, Nov 26, 2004 at 10:58:48AM +0100, Holger Levsen wrote: and, better not to forget, the new quik.deb is available at http://www.ulyssis.org/~p2/debjes/ Could the quik.conf(5) man page also be modified to include documentation of the initrd option? I'd be more comfortable with modifying quik-installer to match then. i meant to do some doc updates in my last update, but i ran out of time (was leaving for ottawa), so i didn't get a chance to do so :(. in my next upload i will have the updated docs (initrd= and pause-after= included). eric Thanks, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Microsoft is to operating systems security what McDonalds is to gourmet cooking. signature.asc Description: Digital signature
Processing of base-config_2.59_i386.changes
base-config_2.59_i386.changes uploaded successfully to localhost along with the files: base-config_2.59.dsc base-config_2.59.tar.gz base-config_2.59_all.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing of base-config_2.53.5_i386.changes
base-config_2.53.5_i386.changes uploaded successfully to localhost along with the files: base-config_2.53.5.dsc base-config_2.53.5.tar.gz base-config_2.53.5_all.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
[d-i manual] Call to update translation (es and pt_BR)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello fellow translators, Currently the Portuguese and Spanish translations of the installation manual are somewhat outdated: es: 21 files not up-to-date pt_BR : 58 files not up-to-date (The other languages are fairly up-to-date AFAICT. Not sure about Czech.) As there will be (at least) one more build of the initrd's before the release of Sarge, you still have time to update your translations. Although the changes are not major, there are some fairly important updates for a few architectures. As you may know, the SVN repository has been branched for Sarge. However, as there currently are no differences for the manual between trunk and the branches, you can still commit your translation to the main trunk. For the short term at least I plan to synchronize the Sarge branch with trunk at least once a week. Cheers, FJP -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBsO03gm/Kwh6ICoQRAg0RAJ9AmuBrS5oLwVfQpV9Mekx3Z+PD6gCfTqEP RFm9uO8M+t6iqjzovBIPlP4= =BG9C -END PGP SIGNATURE-
Re: Summary / new quik available (was Re: please test new quik with initrd-support (was: Re: getting quik into sarge?
Ce jour Fri, 03 Dec 2004, Holger Levsen a dit: i'd appreciate not having it hijacked from under me. i don't mind getting help, and i do appreciate that, but i get the feeling it's being hijacked from me. you could at least tell me WTF is going on. eric (the current quik maintainer) -- Microsoft is to operating systems security what McDonalds is to gourmet cooking. signature.asc Description: Digital signature
Processed: reassign 283983 to rootskel
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.8.5 reassign 283983 rootskel Bug#283983: installation-reports: ia64 rc2 businesscard w/ 2.6 kernel Bug reassigned from package `installation-reports' to `rootskel'. 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 [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
base-config_2.53.5_i386.changes ACCEPTED
Accepted: base-config_2.53.5.dsc to pool/main/b/base-config/base-config_2.53.5.dsc base-config_2.53.5.tar.gz to pool/main/b/base-config/base-config_2.53.5.tar.gz base-config_2.53.5_all.deb to pool/main/b/base-config/base-config_2.53.5_all.deb Closing bugs: 282632 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
base-config_2.59_i386.changes REJECTED
Rejected: base-config_2.59_i386.changes: a file with this name already exists in the Done directory. Rejected: base-config_2.59_all.deb: old version (2.59) in unstable = new version (2.59) targeted at unstable. Rejected: base-config_2.59_all.deb: can not overwrite existing copy already in the archive. Rejected: md5sum and/or size mismatch on existing copy of base-config_2.59_all.deb. Rejected: md5sum and/or size mismatch on existing copy of base-config_2.59.dsc. Rejected: md5sum and/or size mismatch on existing copy of base-config_2.59.tar.gz. Rejected: base-config_2.59.dsc: old version (2.59) in unstable = new version (2.59) targeted at unstable. Rejected: can not overwrite existing copy of 'base-config_2.59.tar.gz' already in the archive. === If you don't understand why your files were rejected, or if the override file requires editing, reply to this email. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing of base-config_2.60_i386.changes
base-config_2.60_i386.changes uploaded successfully to localhost along with the files: base-config_2.60.dsc base-config_2.60.tar.gz base-config_2.60_all.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#283983: FWD: Sarge debian-installer
- Forwarded message from Emeric Maschino [EMAIL PROTECTED] - From: Emeric Maschino [EMAIL PROTECTED] Date: 03 Dec 2004 10:08:43 +0100 To: [EMAIL PROTECTED] Subject: Sarge debian-installer Organization: X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Hello, Am I the only one having problems with the RC2 or daily-built Sarge debian-installer? It works flawlessly if you choose 2.4 VGA console in the install menu, but 2.6 VGA console is an other story. On my hp workstation i2000, the only way to install Sarge using a 2.6 kernel is with a serial console (the keyboard isn't working with 2.6 VGA console). Once the base system is installed and I'm asked to reboot, if I switch back to a VGA console by removing the line append=console=ttyS0,115200n8 from elilo.conf, I'm given a completely unusable system since the keyboard is still not responding. Please note this is PS/2 keyboard, not a USB device. I already noticed this problem 3 months back (see the Linux kernel 2.6 freezes on my hp workstation i2000 post on the www.gelato.org website). The problem is due to the fact that the i8042 and AT keyboard supports are compiled as modules and are not loaded. I had to boot with a recovery CD to manually add i8042, atkbd and psmouse lines in the /etc/modules file to have a usable system. Is there a good reason to build the i8042 and keyboard support as modules? In this case, why isn't the /etc/modules file automatically adjusted? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] - End forwarded message - -- see shy jo signature.asc Description: Digital signature
Bug#283983: ia64 ps2 keyboard no worky
See the forwarded mail from debian-ia64 for some details. I notice that rootskel has some code for powerpc to modprobe i8042 and atkbd on chrp|chrp_pegasos|prep. Seems we should do this for ia64 too, but I'm puzzled how that manages to get the modules loaded after these system reboot, since it does not register-module those modules. -- see shy jo signature.asc Description: Digital signature
Processed: reassign 284112 to grub
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.8.5 reassign 284112 grub Bug#284112: installation-reports Bug reassigned from package `installation-reports' to `grub'. 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 [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing of linux-kernel-di-i386_1.01_i386.changes
linux-kernel-di-i386_1.01_i386.changes uploaded successfully to localhost along with the files: linux-kernel-di-i386_1.01.dsc linux-kernel-di-i386_1.01.tar.gz kernel-image-2.4.27-1-386-di_1.01_i386.udeb nic-modules-2.4.27-1-386-di_1.01_i386.udeb nic-extra-modules-2.4.27-1-386-di_1.01_i386.udeb nic-shared-modules-2.4.27-1-386-di_1.01_i386.udeb serial-modules-2.4.27-1-386-di_1.01_i386.udeb ppp-modules-2.4.27-1-386-di_1.01_i386.udeb isa-pnp-modules-2.4.27-1-386-di_1.01_i386.udeb socket-modules-2.4.27-1-386-di_1.01_i386.udeb ide-modules-2.4.27-1-386-di_1.01_i386.udeb ide-core-modules-2.4.27-1-386-di_1.01_i386.udeb cdrom-core-modules-2.4.27-1-386-di_1.01_i386.udeb cdrom-modules-2.4.27-1-386-di_1.01_i386.udeb firewire-core-modules-2.4.27-1-386-di_1.01_i386.udeb scsi-core-modules-2.4.27-1-386-di_1.01_i386.udeb scsi-modules-2.4.27-1-386-di_1.01_i386.udeb scsi-common-modules-2.4.27-1-386-di_1.01_i386.udeb scsi-extra-modules-2.4.27-1-386-di_1.01_i386.udeb plip-modules-2.4.27-1-386-di_1.01_i386.udeb floppy-modules-2.4.27-1-386-di_1.01_i386.udeb loop-modules-2.4.27-1-386-di_1.01_i386.udeb ipv6-modules-2.4.27-1-386-di_1.01_i386.udeb ext3-modules-2.4.27-1-386-di_1.01_i386.udeb jfs-modules-2.4.27-1-386-di_1.01_i386.udeb ntfs-modules-2.4.27-1-386-di_1.01_i386.udeb reiserfs-modules-2.4.27-1-386-di_1.01_i386.udeb xfs-modules-2.4.27-1-386-di_1.01_i386.udeb fat-modules-2.4.27-1-386-di_1.01_i386.udeb ufs-modules-2.4.27-1-386-di_1.01_i386.udeb md-modules-2.4.27-1-386-di_1.01_i386.udeb usb-modules-2.4.27-1-386-di_1.01_i386.udeb usb-storage-modules-2.4.27-1-386-di_1.01_i386.udeb pcmcia-storage-modules-2.4.27-1-386-di_1.01_i386.udeb brltty-modules-2.4.27-1-386-di_1.01_i386.udeb fb-modules-2.4.27-1-386-di_1.01_i386.udeb input-modules-2.4.27-1-386-di_1.01_i386.udeb irda-modules-2.4.27-1-386-di_1.01_i386.udeb parport-modules-2.4.27-1-386-di_1.01_i386.udeb nic-pcmcia-modules-2.4.27-1-386-di_1.01_i386.udeb pcmcia-modules-2.4.27-1-386-di_1.01_i386.udeb nic-usb-modules-2.4.27-1-386-di_1.01_i386.udeb sata-modules-2.4.27-1-386-di_1.01_i386.udeb firmware-modules-2.4.27-1-386-di_1.01_i386.udeb kernel-image-2.4.27-speakup-di_1.01_i386.udeb nic-modules-2.4.27-speakup-di_1.01_i386.udeb nic-extra-modules-2.4.27-speakup-di_1.01_i386.udeb nic-shared-modules-2.4.27-speakup-di_1.01_i386.udeb serial-modules-2.4.27-speakup-di_1.01_i386.udeb ppp-modules-2.4.27-speakup-di_1.01_i386.udeb isa-pnp-modules-2.4.27-speakup-di_1.01_i386.udeb socket-modules-2.4.27-speakup-di_1.01_i386.udeb ide-modules-2.4.27-speakup-di_1.01_i386.udeb ide-core-modules-2.4.27-speakup-di_1.01_i386.udeb cdrom-core-modules-2.4.27-speakup-di_1.01_i386.udeb cdrom-modules-2.4.27-speakup-di_1.01_i386.udeb firewire-core-modules-2.4.27-speakup-di_1.01_i386.udeb scsi-core-modules-2.4.27-speakup-di_1.01_i386.udeb scsi-modules-2.4.27-speakup-di_1.01_i386.udeb scsi-common-modules-2.4.27-speakup-di_1.01_i386.udeb scsi-extra-modules-2.4.27-speakup-di_1.01_i386.udeb plip-modules-2.4.27-speakup-di_1.01_i386.udeb floppy-modules-2.4.27-speakup-di_1.01_i386.udeb loop-modules-2.4.27-speakup-di_1.01_i386.udeb ipv6-modules-2.4.27-speakup-di_1.01_i386.udeb ext3-modules-2.4.27-speakup-di_1.01_i386.udeb jfs-modules-2.4.27-speakup-di_1.01_i386.udeb reiserfs-modules-2.4.27-speakup-di_1.01_i386.udeb fat-modules-2.4.27-speakup-di_1.01_i386.udeb ufs-modules-2.4.27-speakup-di_1.01_i386.udeb md-modules-2.4.27-speakup-di_1.01_i386.udeb usb-modules-2.4.27-speakup-di_1.01_i386.udeb usb-storage-modules-2.4.27-speakup-di_1.01_i386.udeb pcmcia-storage-modules-2.4.27-speakup-di_1.01_i386.udeb brltty-modules-2.4.27-speakup-di_1.01_i386.udeb fb-modules-2.4.27-speakup-di_1.01_i386.udeb input-modules-2.4.27-speakup-di_1.01_i386.udeb irda-modules-2.4.27-speakup-di_1.01_i386.udeb parport-modules-2.4.27-speakup-di_1.01_i386.udeb nic-pcmcia-modules-2.4.27-speakup-di_1.01_i386.udeb pcmcia-modules-2.4.27-speakup-di_1.01_i386.udeb nic-usb-modules-2.4.27-speakup-di_1.01_i386.udeb firmware-modules-2.4.27-speakup-di_1.01_i386.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
base-config_2.60_i386.changes ACCEPTED
Accepted: base-config_2.60.dsc to pool/main/b/base-config/base-config_2.60.dsc base-config_2.60.tar.gz to pool/main/b/base-config/base-config_2.60.tar.gz base-config_2.60_all.deb to pool/main/b/base-config/base-config_2.60_all.deb Announcing to [EMAIL PROTECTED] Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
linux-kernel-di-i386_1.01_i386.changes ACCEPTED
Accepted: brltty-modules-2.4.27-1-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386/brltty-modules-2.4.27-1-386-di_1.01_i386.udeb brltty-modules-2.4.27-speakup-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386/brltty-modules-2.4.27-speakup-di_1.01_i386.udeb cdrom-core-modules-2.4.27-1-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386/cdrom-core-modules-2.4.27-1-386-di_1.01_i386.udeb cdrom-core-modules-2.4.27-speakup-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386/cdrom-core-modules-2.4.27-speakup-di_1.01_i386.udeb cdrom-modules-2.4.27-1-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386/cdrom-modules-2.4.27-1-386-di_1.01_i386.udeb cdrom-modules-2.4.27-speakup-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386/cdrom-modules-2.4.27-speakup-di_1.01_i386.udeb ext3-modules-2.4.27-1-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386/ext3-modules-2.4.27-1-386-di_1.01_i386.udeb ext3-modules-2.4.27-speakup-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386/ext3-modules-2.4.27-speakup-di_1.01_i386.udeb fat-modules-2.4.27-1-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386/fat-modules-2.4.27-1-386-di_1.01_i386.udeb fat-modules-2.4.27-speakup-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386/fat-modules-2.4.27-speakup-di_1.01_i386.udeb fb-modules-2.4.27-1-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386/fb-modules-2.4.27-1-386-di_1.01_i386.udeb fb-modules-2.4.27-speakup-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386/fb-modules-2.4.27-speakup-di_1.01_i386.udeb firewire-core-modules-2.4.27-1-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386/firewire-core-modules-2.4.27-1-386-di_1.01_i386.udeb firewire-core-modules-2.4.27-speakup-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386/firewire-core-modules-2.4.27-speakup-di_1.01_i386.udeb firmware-modules-2.4.27-1-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386/firmware-modules-2.4.27-1-386-di_1.01_i386.udeb firmware-modules-2.4.27-speakup-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386/firmware-modules-2.4.27-speakup-di_1.01_i386.udeb floppy-modules-2.4.27-1-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386/floppy-modules-2.4.27-1-386-di_1.01_i386.udeb floppy-modules-2.4.27-speakup-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386/floppy-modules-2.4.27-speakup-di_1.01_i386.udeb ide-core-modules-2.4.27-1-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386/ide-core-modules-2.4.27-1-386-di_1.01_i386.udeb ide-core-modules-2.4.27-speakup-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386/ide-core-modules-2.4.27-speakup-di_1.01_i386.udeb ide-modules-2.4.27-1-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386/ide-modules-2.4.27-1-386-di_1.01_i386.udeb ide-modules-2.4.27-speakup-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386/ide-modules-2.4.27-speakup-di_1.01_i386.udeb input-modules-2.4.27-1-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386/input-modules-2.4.27-1-386-di_1.01_i386.udeb input-modules-2.4.27-speakup-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386/input-modules-2.4.27-speakup-di_1.01_i386.udeb ipv6-modules-2.4.27-1-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386/ipv6-modules-2.4.27-1-386-di_1.01_i386.udeb ipv6-modules-2.4.27-speakup-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386/ipv6-modules-2.4.27-speakup-di_1.01_i386.udeb irda-modules-2.4.27-1-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386/irda-modules-2.4.27-1-386-di_1.01_i386.udeb irda-modules-2.4.27-speakup-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386/irda-modules-2.4.27-speakup-di_1.01_i386.udeb isa-pnp-modules-2.4.27-1-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386/isa-pnp-modules-2.4.27-1-386-di_1.01_i386.udeb isa-pnp-modules-2.4.27-speakup-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386/isa-pnp-modules-2.4.27-speakup-di_1.01_i386.udeb jfs-modules-2.4.27-1-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386/jfs-modules-2.4.27-1-386-di_1.01_i386.udeb jfs-modules-2.4.27-speakup-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386/jfs-modules-2.4.27-speakup-di_1.01_i386.udeb kernel-image-2.4.27-1-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386/kernel-image-2.4.27-1-386-di_1.01_i386.udeb kernel-image-2.4.27-speakup-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386/kernel-image-2.4.27-speakup-di_1.01_i386.udeb linux-kernel-di-i386_1.01.dsc to pool/main/l/linux-kernel-di-i386/linux-kernel-di-i386_1.01.dsc linux-kernel-di-i386_1.01.tar.gz to pool/main/l/linux-kernel-di-i386/linux-kernel-di-i386_1.01.tar.gz loop-modules-2.4.27-1-386-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386/loop-modules-2.4.27-1-386-di_1.01_i386.udeb loop-modules-2.4.27-speakup-di_1.01_i386.udeb to pool/main/l/linux-kernel-di-i386/loop-modules-2.4.27-speakup-di_1.01_i386.udeb
Bug#283142: Quik fails to install on beige G3
Ce jour Sat, 27 Nov 2004, Sven Luther a dit: On Fri, Nov 26, 2004 at 11:55:30PM +, Clive Menzies wrote: On (26/11/04 22:39), [EMAIL PROTECTED] wrote: reassign #283142 debian-installer thanks installer and may have imagined I saw vmlinuz and unfortunately I didn't have time to repeat the process to make sure. Actually, there is a vmlinuz on prep and chrp machines, and even for oldworld .coff kernels. The vmlinuz symlink (actually it is /boot/vmlinuz, not /vmlinuz) is provided by the 2.4 kernel, both the -chrp and -prep one, and probably by the -pmac also, since it provides the .coff vmlinuz kernel. ah, i see. thank you for the info. Friendly, Sven Luther -- We're not talking about the same thing, he said. For you the world is weird because if you're not bored with it you're at odds with it. For me the world is weird because it is stupendous, awesome, mysterious, unfathomable; my interest has been to convince you that you must accept responsibility for being here, in this marvelous world, in this marvelous desert, in this marvelous time. I wanted to convince you that you must learn to make every act count, since you are going to be here for only a short while, in fact, too short for witnessing all the marvels of it. -- Don Juan signature.asc Description: Digital signature
Re: Re: Debian-install kernel and AIC-7901
Joey Hess wrote: Jan Medlock wrote: I tried the d-i daily for 23 Nov 2004, which seems to use the same kernel source (2.6.8-1) and, thus, has the same problem. Can anyone confirm this is the case? IIRC this is a known problem with the 2.6.8 kernel and it's fixed in the newest kernel debs and udebs. Those udebs were uploaded yesterday, and should be on tomorrow's daily build of the installer. I'm still having the same trouble with the latest (02.Dec) installer with an AIC-7901 SCSI controller. The following changelog entry is from the latest kernel-source-2.6.8 update (-10): * Fix missing backport of ssleep declaration so that new aic7xxx works. Thanks Matt Taggart for pointing out the problem. (Joshua Kwan) I wonder if this is still causing the problem. Any ideas? On a related note, I've been trying to use the linux-kernel-di-i386-2.6 and debian-installer source packages to make a 2.6.9 kernel image to use with d-i with no success. Using either the images in sid or ones I compile myself, the kernel is unable to load the root filesystem and panics. How can I find out what version of kernel-source-2.6.8 is used to generate the d-i kernels? How can see the .config used? Thanks, Jan Medlock -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#273982: partman: Broken display during Arabic installs
On Fri, Dec 03, 2004 at 05:08:16PM +0200, Anton Zinoviev wrote: On Wed, Sep 29, 2004 at 07:38:19AM +0200, Christian Perrier wrote: The attached screen captures show the main partman screen and the partition aditiing screen during an Arabic install. As you may see, the display is somewhat broken. For instance the partition size and the unit are not close together and the display is not properly aligned. This is probably a consequence of formatting with a left-to-right reasoning and will probably affect all install with right-to-left languages. What algorithms are used to format the screen for such languages? One problem with Arabic displays is simply that RTL text ought to be *right*-justified, instead of left-justified, within a field; this is a low-level issue with the way information is being passed to libslang about how much screen real estate a given string should occupy. Fixing this means that libslang should know how wide the available field is, and pad the string with spaces at the end to get the desired formatting effect. Another issue is that some of the Arabic translations for partman seem to be just plain screwy: #. Type: text #. Description #: ../partman.templates:252 #, no-c-format msgid SCSI%s (%s,%s,%s) (%s) msgstr SCSI%s )%s%s%s( #. Type: text #. Description #: ../partman.templates:256 #, no-c-format msgid SCSI%s (%s,%s,%s), partition #%s (%s) msgstr %s (%s,%s,%s), #%s (%s) While the rules regarding bidi transitions are rather complex (and setting aside for the moment the inconsistency of whether or not to translate SCSI), it's clear that these translation's can't *both* be right: the parentheses need to go one way or the other, not just picking one at random. Which way to go is up to the Arabic translators, I think, but if they decide to use the parenthesis inversion (which I imagine is the more natural style in Arabic), they will also need to use a direction marker so that the string actually gets formatted right-to-left! The necessary marker appears to be Unicode character U+200f, RIGHT-TO-LEFT MARK. Unfortunately, I can't seem to actually make this work in testing here (outside of d-i); I'm happy to float some patched po files to you, Christian, if you have time to look into this further to confirm whether the results are correct under d-i itself. Oh, and the fact that the translation of the first string above has a different number of %s substitutions than the original can't help matters... -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Bug#273982: partman: Broken display during Arabic installs
On Fri, Dec 03, 2004 at 07:21:40PM -0800, Steve Langasek wrote: While the rules regarding bidi transitions are rather complex (and setting aside for the moment the inconsistency of whether or not to translate SCSI), it's clear that these translation's can't *both* be right: the parentheses need to go one way or the other, not just picking one at random. Which way to go is up to the Arabic translators, I think, but if they decide to use the parenthesis inversion (which I imagine is the more natural style in Arabic), they will also need to use a direction marker so that the string actually gets formatted right-to-left! The necessary marker appears to be Unicode character U+200f, RIGHT-TO-LEFT MARK. Unfortunately, I can't seem to actually make this work in testing here (outside of d-i); I'm happy to float some patched po files to you, Christian, if you have time to look into this further to confirm whether the results are correct under d-i itself. Further research shows that RIGHT-TO-LEFT MARK is used for modifying the RTL property of the preceding character; two other modifiers, RIGHT-TO-LEFT EMBEDDING and RIGHT-TO-LEFT OVERRIDE, are more relevant to changing the orientation of strings. http://www.microsoft.com/middleeast/msdn/Control.aspx has some information about these control characters, though I'm afraid I didn't find it very enlightening about the difference between EMBEDDING and OVERRIDE here. I'm still trying to trial-and-error my way to something that turns the string the right way around. -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Bug#273982: partman: Broken display during Arabic installs
The attached patch is a proof-of-concept of fixing the muddled Arabic displays in partman using Unicode bidi control characters. It's not comprehensive, and it's actually not suitable for use as-is because the two strings involved are still inconsistent in their handling of the text SCSI; but it does introduce consistent use of parentheses and Arabic punctuation, and demonstrates how various control characters (U+202E, U+202A, U+202C) can be used to override the direction of otherwise LTR character sequences. Christian, any chance you'd be able to test this out in d-i? My main d-i box remains an alpha w/o bterm support. Thanks, -- Steve Langasek postmodern programmer Index: partman/debian/po/ar.po === --- partman/debian/po/ar.po (revision 24176) +++ partman/debian/po/ar.po (working copy) @@ -439,14 +439,14 @@ #: ../partman.templates:252 #, no-c-format msgid SCSI%s (%s,%s,%s) (%s) -msgstr SCSI%s )%s%s%s( +msgstr SCSI%s (%s%s%s) (%s) #. Type: text #. Description #: ../partman.templates:256 #, no-c-format msgid SCSI%s (%s,%s,%s), partition #%s (%s) -msgstr %s (%s,%s,%s), #%s (%s) +msgstr %s (%s%s%s) #%s (%s) #. Type: text #. Description signature.asc Description: Digital signature
Bug#273982: partman: Broken display during Arabic installs
Quoting Steve Langasek ([EMAIL PROTECTED]): Christian, any chance you'd be able to test this out in d-i? My main d-i box remains an alpha w/o bterm support. Hmmm, maybe but I can't promise anything. My week-end will have few windows for hacking. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
