Re: PowerPC kernel repository (was: Woody on IBM RS/6000 7025 F50)
On Tue, 3 Sep 2002 20:44:03 -0700 Chris Tillman [EMAIL PROTECTED] wrote: There was no response to this request on the debian-powerpc list, I guess it really belongs to debian-boot (cc'd). Since the consensus is that the current prep and chrp kernels which we supply as part of boot-floppies are badly broken and unusable, would something like this be considered for a stable point release? Does that mean there will be new kernel-image packages for woody point release? If that is what is required for making this thing install, that probably is a good enough reason to add a new one, if it doesn't intrude with existing installs. Comments? regards, junichi -- [EMAIL PROTECTED] http://www.netfort.gr.jp/~dancer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: PowerPC kernel repository (was: Woody on IBM RS/6000 7025 F50)
On Tue, 2002-09-03 at 23:44, Chris Tillman wrote: Since the consensus is that the current prep and chrp kernels which we supply as part of boot-floppies are badly broken and unusable, would something like this be considered for a stable point release? I think it should be. I've only heard negative feedback about the kernels we supply. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
PO files location (Was Re: [d-i] Problems with various debconf templates)
On Sun, Sep 01, 2002 at 10:45:20PM +0200, Denis Barbier wrote: [...] Also in retriever/choose-mirror/debian/templates the mirror list is set via a variable, which certainly make its translation impossible. Here is a patch against retriever/choose-mirror/makeheader.pl But where must PO files go? There are at least 2 ways: * all messages in a central place (debian-installer/po/ or debian-installer/libdebian-installer/po/ so that PO catalogs may be shipped with libdebian-installer-dev and used by all modules to generate module-dependent MO files) * each component ships its own po subdirectory IMO the first one is more translator-friendly. Denis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#158947: Installation on new Ibooks
On Sat, 2002-08-31 at 17:56, Chris Tillman wrote: I _thought_ I was missing something. Makes sense to me... Well, I am very hesitant to make such a potentially intrusive change for boot-floppies. I guess it would be up to the main b-f maintainer to decide whether or not this change should be made...which would be...Eduard? However, I will soon make this change for at least yaboot-installer for d-i. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: PO files location (Was Re: [d-i] Problems with various debconf templates)
On Wed, Sep 04, 2002 at 09:30:32AM +0200, Denis Barbier wrote:
[...]
Here is a patch against retriever/choose-mirror/makeheader.pl
Here it is.
Denis
Index: makeheader.pl
===
RCS file: /cvs/debian-boot/debian-installer/retriever/choose-mirror/makeheader.pl,v
retrieving revision 1.4
diff -u -u -r1.4 makeheader.pl
--- makeheader.pl 29 Aug 2002 11:37:15 - 1.4
+++ makeheader.pl 4 Sep 2002 07:16:35 -
-46,6 +46,9
open (OUT, mirrors_$type.h) or die mirrors_$type.h: $!;
print OUT /* Automatically generated; do not edit. */\n;
+print OUT #ifndef _\n;
+print OUT #define _(ARG) ARG\n;
+print OUT #endif\n;
# Poor man's mirror rating system: push-primary, push* (-secondary), others
foreach my $site (keys %data) {
-65,7 +68,8
next unless exists $data{$site}-{archive-$type} and
exists $data{$site}-{country};
print OUT \t{,
- join(, , $q.$site.$q, $q.$data{$site}-{country}.$q,
+ join(, , $q.$site.$q,
+ _(.$q.$data{$site}-{country}.$q.),
$q.$data{$site}-{archive-$type}.$q),
},\n;
$used_country{$data{$site}-{country}}=1;
Re: PO files location (Was Re: [d-i] Problems with various debconf templates)
On Wed, 4 Sep 2002 09:30:32 +0200 [EMAIL PROTECTED] (Denis Barbier) wrote: But where must PO files go? There are at least 2 ways: * all messages in a central place (debian-installer/po/ or debian-installer/libdebian-installer/po/ so that PO catalogs may be shipped with libdebian-installer-dev and used by all modules to generate module-dependent MO files) * each component ships its own po subdirectory IMO the first one is more translator-friendly. It's rather a design decision, but it might be better to collect it in one place, and generate a debian-installer-locales package which has the po files. regards, junichi -- [EMAIL PROTECTED] http://www.netfort.gr.jp/~dancer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
dselect-beginner.txt
First, let me thank the authors for a clear and informative document. I have some minor complaints: 0. Which versions of dselect are described? 1. The document contains no (visible) revision date. 2. Access - multi_cd section: Insert the CD in your CD-ROM drive Judging from later statements, I would conclude that the first CD of the set is meant. If this is correct, can we say that explicitly? 3. Update section: Talks about the mirror; what is the mirror if one uses multi_cd as Access method? 4. Select section _R_ Cancels all selections at this level. What does this level refer to? Greetings Sven P.S. Is the description of Access - multi_cd accurate for upgrades from 2.2r6 to 3.0r0? (i.e. with dselect, apt-get, dpkg from 2.2r6 packages) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dselect-beginner.txt
On Wed, Sep 04, 2002 at 08:49:48PM +0200, Sven Hartrumpf wrote: First, let me thank the authors for a clear and informative document. I have some minor complaints: 0. Which versions of dselect are described? 1. The document contains no (visible) revision date. This document was first put together in early '99, and has not been frequently updated. It's safe to say that it refers to the dselect available at that time, but that hasn't changed much either :-) 2. Access - multi_cd section: Insert the CD in your CD-ROM drive Judging from later statements, I would conclude that the first CD of the set is meant. If this is correct, can we say that explicitly? Sounds reasonable. 3. Update section: Talks about the mirror; what is the mirror if one uses multi_cd as Access method? The mirror refers to the source for the software, you are correct. 4. Select section _R_ Cancels all selections at this level. What does this level refer to? If the highlight is on a 'header', then actions affect all the subs within the heading. Greetings Sven P.S. Is the description of Access - multi_cd accurate for upgrades from 2.2r6 to 3.0r0? (i.e. with dselect, apt-get, dpkg from 2.2r6 packages) Yes, the doc was written early in 2.2's life. BTW, even though it wasn't judged ready to be included as default in the new release, you will probably like aptitude much better. It's the next generation of dselect, and acts much the same, but gives more feedback. -- *--v- Installing Debian GNU/Linux 3.0 v--* | http://www.debian.org/releases/stable/installmanual | |debian-imac: http://debian-imac.sourceforge.net | |Chris Tillman[EMAIL PROTECTED] | | To Have, Give All to All (ACIM) | ** -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dselect-beginner.txt
On Wed, Sep 04, 2002 at 01:10:20PM -0700, Chris Tillman wrote: On Wed, Sep 04, 2002 at 08:49:48PM +0200, Sven Hartrumpf wrote: 4. Select section _R_ Cancels all selections at this level. What does this level refer to? If the highlight is on a 'header', then actions affect all the subs within the heading. Actually, while that's true for '+', '-', and so on, it's not true for keys like 'R' that are in the Quit, exit, overwrite section of dselect's keystroke help screen. As far as I know, this level means that if you're in the main package selection view then it applies to all packages, while if you're in a conflict resolution display then it applies only to packages in that display. -- Colin Watson [[EMAIL PROTECTED]] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
