Re: Bug#325218: New patch for the tasks normalization bug

2006-06-19 Thread Christian Perrier
Quoting Joey Hess ([EMAIL PROTECTED]): Christian Perrier wrote: After discussing it with Joey on IRC, I come up with this patch which adds language and language-desktop tasks for languages which we currently support and for which no task is available. In shot, it does not modify any

Re: Status of debian-installer for the native ppc64 port

2006-06-19 Thread Andreas Jochens
Hello, Holger Levsen wrote: Can you please point us to the relevant bug numbers (or give a usertag-link)?! here are the relevant bug numbers for the ppc64 related patches: clock-setup : #365345 gtk+2.0-directfb: #301120 kbd-chooser : #339716 partman-newworld: #301103 rootskel

stagger forced fsck on reboot

2006-06-19 Thread Drew Parsons
Hi debian-installer people, Partitions have a counter so that an fsck is forced on them at reboot after they have have mounted as certain number of times (I think it's after 20 or 30 mounts). The last time I checked, on a default installation with multiple partition this forced fsck occured

Re: stagger forced fsck on reboot

2006-06-19 Thread Frans Pop
On Monday 19 June 2006 08:40, Drew Parsons wrote: The inconvenience could be ameliorated if the force-fsck mount counter could be staggered for each partition. For instance, the first partition on every 20 mounts, the second on every 21, and so on. Then on a given reboot, on average you'd

Re: finding a technical workaround

2006-06-19 Thread Frans Pop
On Sunday 18 June 2006 22:54, Sven Luther wrote: Just for information, the freedi project was never intented to be a fork, it was a place for holding more experimental d-i stuff, which the d-i team doesn't want into d-i proper for whatever reasons, as you can see in the desciption. Thank you

Bug#374228: installation-reports: Installation failed with base-installer/no_codename on AMD64

2006-06-19 Thread Frans Pop
On Monday 19 June 2006 04:53, you wrote: This latest image does indeed have version 1.16 of cdrom-detect, but it appears to have a kernel version issue. The installer is running version 2.6.15, while all the udebs on the cd image are for kernel 2.6.16. Right. That was a change that needed to

Re: stagger forced fsck on reboot

2006-06-19 Thread Drew Parsons
On Mon, 2006-06-19 at 09:57 +0200, Frans Pop wrote: On Monday 19 June 2006 08:40, Drew Parsons wrote: The inconvenience could be ameliorated if the force-fsck mount counter could be staggered for each partition. For instance, the first partition on every 20 mounts, the second on every 21,

Bug#374278: Install report: 12Ã PowerBook G4 1.33Ghz

2006-06-19 Thread Wouter Verhelst
On Mon, Jun 19, 2006 at 12:51:53AM +0200, Frans Pop wrote: Hoi Wouter, On Sunday 18 June 2006 12:48, Wouter Verhelst wrote: I couldn't find the install-report template on my hard disk (maybe I'm not looking at the right place; it used to be in /root, but it's not there now), so I'm doing

Re: stagger forced fsck on reboot

2006-06-19 Thread Frans Pop
On Monday 19 June 2006 10:10, Drew Parsons wrote: So the question comes down to what set of defaults provides the nicest experience for less confident users? Will it be nicer for them if we provide an arrangement that can occasionally reduce their reboot time? Inexperienced users will

Re: stagger forced fsck on reboot

2006-06-19 Thread Geert Stappers
On Mon, Jun 19, 2006 at 06:10:04PM +1000, Drew Parsons wrote: On Mon, 2006-06-19 at 09:57 +0200, Frans Pop wrote: On Monday 19 June 2006 08:40, Drew Parsons wrote: [ change the force-fsck mount behaviour ] My first reaction is that this falls under the header of tuning to be done by

Re: Status of debian-installer for the native ppc64 port

2006-06-19 Thread Frans Pop
On Monday 19 June 2006 08:29, Andreas Jochens wrote: Please give me hint if I should file the missing patches now or if I should wait for a decision at the d-i meeting. Thank you for the overview. Please wait a bit before filing any new bugs as we should first revert the decision made earlier.

Re: stagger forced fsck on reboot

2006-06-19 Thread Wouter Verhelst
On Mon, Jun 19, 2006 at 04:40:05PM +1000, Drew Parsons wrote: Hi debian-installer people, Partitions have a counter so that an fsck is forced on them at reboot after they have have mounted as certain number of times (I think it's after 20 or 30 mounts). The last time I checked, on a

Bug#200529: constantly broke and need more income?

2006-06-19 Thread Shelley Lara
How have you been, If you are like most people, you are more than qual^ified with your experience, but you are lacking that prest^igious piece of paper known as a DI^PLOMA that is often the passport to success^. ^Call us today^ 1^2^0^6-984-4433 24 hours a day, 7 days a week including

Re: Status of debian-installer for the native ppc64 port

2006-06-19 Thread Andreas Jochens
Hello Frans, thank you for your detailed look at the summary and at the ppc64 port page. On 06-Jun-19 11:07, Frans Pop wrote: On Monday 19 June 2006 08:29, Andreas Jochens wrote: Please give me hint if I should file the missing patches now or if I should wait for a decision at the d-i

[g-i]GTK 2.8.18 with directfb support packages [was: Re: [directfb-dev] [g-i] Graphical installer and PPC systems]

2006-06-19 Thread Eddy Petrişor
On 5/25/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Mike Emmel wrote: I think a lot of the issues were actually 64 bit stuff thats recently been fixed any chance you could try 25.1 ? or a cvs build just to see. I believe the problems were down in the directfb layer so it would be nice to

[HELP] Is separate lib package needed for libcairo directfb variant

2006-06-19 Thread Frans Pop
Hi all, Dave Beckett is preparing a new release of libcairo2 (see [1]) after a request from the Debian Installer team to add a udeb compiled against the directfb backend and not against the X backend. This udeb will be used by the d-i team for the graphical installer. There is one issue that

Re: [HELP] Is separate lib package needed for libcairo directfb variant

2006-06-19 Thread Attilio Fiandrotti
Frans Pop wrote: Hi all, Dave Beckett is preparing a new release of libcairo2 (see [1]) after a request from the Debian Installer team to add a udeb compiled against the directfb backend and not against the X backend. This udeb will be used by the d-i team for the graphical installer. snip

Re: Request for a DFB version of libcairo2 - time for gtk+-directfb

2006-06-19 Thread Frans Pop
Hi Dave, On Wednesday 14 June 2006 18:33, Dave Beckett wrote: Cairo 1.1.8 snapshot was just released so I've made a new set of experimental debs for it at: http://download.dajobe.org/debian/experimental/ The patch below adds the correct line to the shlibs file in the lib package so that

Re: stagger forced fsck on reboot

2006-06-19 Thread Joey Hess
Drew Parsons wrote: The inconvenience could be ameliorated if the force-fsck mount counter could be staggered for each partition. For instance, the first partition on every 20 mounts, the second on every 21, and so on. Then on a given reboot, on average you'd only have to put up with one

[D-I] Call for translation update for next Beta release

2006-06-19 Thread Frans Pop
Hello all, We will soon be starting the preparations for the next Beta release of the installer for Etch. When exactly depends on the migration of the 2.6.16 kernel to testing. As with past Beta releases, we will not have a formal string freeze and we do not guarantee that all translation

Bug#361872: debconf-copydb: Trashes debconf database in /target

2006-06-19 Thread Steinar H. Gunderson
On Thu, Jun 15, 2006 at 10:44:23PM +0200, Frans Pop wrote: The relevant files (hope the filenames speak for themselves) and an strace are available from: http://people.debian.org/~fjp/d-i/debconf-copydb.tgz (uploaded instead of attached because of size) I figured out the bug. If you tweak

Bug#361872: debconf-copydb: Trashes debconf database in /target

2006-06-19 Thread Steinar H. Gunderson
On Mon, Jun 19, 2006 at 01:10:47PM -0400, Joey Hess wrote: If it's using ascii that's valid, anyway cdebconf should also be sure to copy Description-xx[_XX] fields too, as debconf will store them that way if the package doesn't specifiy an encoding. Well, some of the fields seem to be ASCII;

Bug#361872: debconf-copydb: Trashes debconf database in /target

2006-06-19 Thread Joey Hess
Steinar H. Gunderson wrote: shouldn't be all that hard), but I don't think one would want pulling iconv into d-i, and I've never seen any templates _not_ in UTF-8 or ASCII, so I guess it would be a bit pointless. However, it special-cases fields like Description-xx.UTF-8, so this should really

Processed: tagging 361872

2006-06-19 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.20 tags 361872 + patch Bug#361872: debconf-copydb: Trashes debconf database in /target There were no tags set. Tags added: patch End of message, stopping processing here. Please

Re: Status of debian-installer for the native ppc64 port

2006-06-19 Thread Sven Luther
On Mon, Jun 19, 2006 at 12:46:10PM +0200, Andreas Jochens wrote: Hello Frans, thank you for your detailed look at the summary and at the ppc64 port page. Andreas, the powerpc 64bit archive may or may not be of interest, but since it is perfectly ok to install a native powerpc 64bit system

Re: finding a technical workaround

2006-06-19 Thread Sven Luther
On Mon, Jun 19, 2006 at 09:58:21AM +0200, Frans Pop wrote: On Sunday 18 June 2006 22:54, Sven Luther wrote: Just for information, the freedi project was never intented to be a fork, it was a place for holding more experimental d-i stuff, which the d-i team doesn't want into d-i proper for

Bug#361872: debconf-copydb: Trashes debconf database in /target

2006-06-19 Thread Joey Hess
Steinar H. Gunderson wrote: Well, some of the fields seem to be ASCII; some of them are UTF-8. What do you propose in this case -- hacking support for this kind of undefined encoding stuff into cdebconf? No, I don't think that cdebconf should worry about supporting this stuff beyond not

Bug#374278: Install report: 12Ã PowerBook G4 1.33Ghz

2006-06-19 Thread Sven Luther
On Sun, Jun 18, 2006 at 12:48:28PM +0200, Wouter Verhelst wrote: Package: installation-reports Severity: normal I couldn't find the install-report template on my hard disk (maybe I'm not looking at the right place; it used to be in /root, but it's not there now), so I'm doing things

Bug#361872: debconf-copydb: Trashes debconf database in /target

2006-06-19 Thread Steinar H. Gunderson
On Mon, Jun 19, 2006 at 01:23:17PM -0400, Joey Hess wrote: What do you propose in this case -- hacking support for this kind of undefined encoding stuff into cdebconf? No, I don't think that cdebconf should worry about supporting this stuff beyond not corrupting it if reading a debconf

Bug#361872: debconf-copydb: Trashes debconf database in /target

2006-06-19 Thread Joey Hess
First of all, this is a bit of a side issue since as noted any reasonable current package that's translated with po-debconf is going to use proper utf-8 fields. Steinar H. Gunderson wrote: Well, debconf-copydb does: - Read in first and second config.dat. - Read in first and second

Re: Status of debian-installer for the native ppc64 port

2006-06-19 Thread Andreas Jochens
Hello, On 06-Jun-19 19:26, Sven Luther wrote: Andreas, the powerpc 64bit archive may or may not be of interest, but since it is perfectly ok to install a native powerpc 64bit system from the 32bit installer, would your effort not be better invested in adding functionality to the normal 32bit

Re: Status of debian-installer for the native ppc64 port

2006-06-19 Thread Sven Luther
On Mon, Jun 19, 2006 at 08:02:29PM +0200, Andreas Jochens wrote: Hello, On 06-Jun-19 19:26, Sven Luther wrote: Andreas, the powerpc 64bit archive may or may not be of interest, but since it is perfectly ok to install a native powerpc 64bit system from the 32bit installer, would your

Bug#361872: debconf-copydb: Trashes debconf database in /target

2006-06-19 Thread Steinar H. Gunderson
On Mon, Jun 19, 2006 at 01:42:53PM -0400, Joey Hess wrote: The easiest way would probably be to not track the information and store (and output) the field as utf-8 without doing any transcoding. This is not exactly what debconf does, but fields that do not define an encoding are basically

Bug#374522: installation-reports

2006-06-19 Thread Daniel Siboska
Package: installation-reports INSTALL REPORT Debian-installer-version: Debian 3.1r2 i386 binary1 downloaded 2006-06-14 from debian.org uname -a: Linux zeta 2.6.16.18 #1 Sat May 27 15:21:02 CEST 2006 i686 GNU/Linux Date: 2006-06-15 Method: Install from Binary1 CD initially with 2.4 kernel.

Re: Status of debian-installer for the native ppc64 port

2006-06-19 Thread Otavio Salvador
Sven Luther [EMAIL PROTECTED] writes: On Mon, Jun 19, 2006 at 12:46:10PM +0200, Andreas Jochens wrote: Hello Frans, thank you for your detailed look at the summary and at the ppc64 port page. Andreas, the powerpc 64bit archive may or may not be of interest, but since it is perfectly ok

Bug#374522: marked as done (installation-reports)

2006-06-19 Thread Debian Bug Tracking System
Your message dated Mon, 19 Jun 2006 21:59:11 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#374522: installation-reports 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

Bug#361872: debconf-copydb: Trashes debconf database in /target

2006-06-19 Thread Steinar H. Gunderson
On Mon, Jun 19, 2006 at 09:58:17PM +0200, Denis Barbier wrote: I am not sure that this is desirable, next time you will encounter utf8 instances, and maybe other names too (except that I cannot find another one ;)) Well, either we'll have to keep adding special-casing of UTF-8, or we'll have

Bug#361872: debconf-copydb: Trashes debconf database in /target

2006-06-19 Thread Denis Barbier
On Mon, Jun 19, 2006 at 08:57:02PM +0200, Steinar H. Gunderson wrote: On Mon, Jun 19, 2006 at 01:42:53PM -0400, Joey Hess wrote: The easiest way would probably be to not track the information and store (and output) the field as utf-8 without doing any transcoding. This is not exactly what

Re: Status of debian-installer for the native {ppc,amd}64 port

2006-06-19 Thread Geert Stappers
On Mon, Jun 19, 2006 at 05:17:50PM -0300, Otavio Salvador wrote: Sven Luther [EMAIL PROTECTED] writes: Andreas, the powerpc 64bit archive may or may not be of interest, but since it is perfectly ok to install a native powerpc 64bit system from the 32bit installer, would your effort not

Bug#316501: trailing characters when displaying long multiline descriptions

2006-06-19 Thread Joey Hess
You wrote: When cdebconf displays a template with multiline descriptions, the last n(n== the number of of newlines in the original extended_description) characters of the description will be shown after it. The origin of the problem is the remove_newline function in template.c, which doeasn't

Bug#361872: debconf-copydb: Trashes debconf database in /target

2006-06-19 Thread Joey Hess
Denis Barbier wrote: After some discussion on IRC, here's the updated patch. --- cdebconf-0.102.orig/src/template.c 2005-09-21 19:07:46.0 +0200 +++ cdebconf-0.102/src/template.c 2006-06-19 20:54:35.0 +0200 @@ -354,7 +354,7 @@

confirm_changes

2006-06-19 Thread David Härdeman
Hi all, currently at least partman-lvm, partman-crypto and partman-md seem to contain copies of confirm_changes() from partman-base/partman. Would it perhaps be an idea to move confirm_changes into /lib/partman/definitions.sh or is there a reason for the duplication? -- To UNSUBSCRIBE,

Re: Status of debian-installer for the native ppc64 port

2006-06-19 Thread Sven Luther
On Mon, Jun 19, 2006 at 10:45:23PM +0200, Andreas Jochens wrote: Hello, On 06-Jun-19 20:16, Sven Luther wrote: Ok. I am ready to work on this with you, can you give me details on what problems you did encounter and some kind of status report. the last time I tried to implement the

Re: Status of debian-installer for the native ppc64 port

2006-06-19 Thread Andreas Jochens
Hello, On 06-Jun-19 20:16, Sven Luther wrote: Ok. I am ready to work on this with you, can you give me details on what problems you did encounter and some kind of status report. the last time I tried to implement the cross-installation was quite a while ago. I do not remember all the details

Re: confirm_changes

2006-06-19 Thread Frans Pop
On Monday 19 June 2006 22:56, David Härdeman wrote: currently at least partman-lvm, partman-crypto and partman-md seem to contain copies of confirm_changes() from partman-base/partman. They are at least different in that they use some differently named templates at some points. Would it

Re: Status of debian-installer for the native ppc64 port

2006-06-19 Thread Andreas Jochens
On 06-Jun-19 17:17, Otavio Salvador wrote: Andreas, the powerpc 64bit archive may or may not be of interest, but since it is perfectly ok to install a native powerpc 64bit system from the 32bit installer, would your effort not be better invested in adding functionality to the normal

Re: confirm_changes

2006-06-19 Thread David Härdeman
On Mon, Jun 19, 2006 at 11:15:54PM +0200, Frans Pop wrote: On Monday 19 June 2006 22:56, David Härdeman wrote: Would it perhaps be an idea to move confirm_changes into /lib/partman/definitions.sh or is there a reason for the duplication? If that is the only difference though, it should be

Bug#374278: Install report: 12Ã PowerBook G4 1.33Ghz

2006-06-19 Thread Sven Luther
On Mon, Jun 19, 2006 at 09:18:39PM +0200, Wouter Verhelst wrote: On Mon, Jun 19, 2006 at 07:34:55PM +0200, Sven Luther wrote: On Sun, Jun 18, 2006 at 12:48:28PM +0200, Wouter Verhelst wrote: The reboot didn't work, however. The first message I got was one of RAMDISK: Compressed image

Re: Status of debian-installer for the native ppc64 port

2006-06-19 Thread Andreas Jochens
On 06-Jun-19 22:56, Sven Luther wrote: BTW, is there a profund difference between the ppc64 kernels and the powerpc64 powerpc arch kernels ? The ppc64 kernels are almost exactly the same as the powerpc64 kernels. I had to change the package names from linux-image-*-powerpc64 to

Bug#374278: Install report: 12Ã PowerBook G4 1.33Ghz

2006-06-19 Thread Wouter Verhelst
On Mon, Jun 19, 2006 at 07:34:55PM +0200, Sven Luther wrote: On Sun, Jun 18, 2006 at 12:48:28PM +0200, Wouter Verhelst wrote: The reboot didn't work, however. The first message I got was one of RAMDISK: Compressed image found at block 0 RAMDISK: incomplete write (-28 != 32768) 8388608

preseed_1.17_i386.changes ACCEPTED

2006-06-19 Thread Debian Installer
Accepted: env-preseed_1.17_all.udeb to pool/main/p/preseed/env-preseed_1.17_all.udeb file-preseed_1.17_all.udeb to pool/main/p/preseed/file-preseed_1.17_all.udeb initrd-preseed_1.17_all.udeb to pool/main/p/preseed/initrd-preseed_1.17_all.udeb network-preseed_1.17_all.udeb to

Bug#374278: Install report: 12 PowerBook G4 1.33Ghz

2006-06-19 Thread Wouter Verhelst
On Mon, Jun 19, 2006 at 11:26:18PM +0200, Sven Luther wrote: On Mon, Jun 19, 2006 at 09:18:39PM +0200, Wouter Verhelst wrote: Nothing else, the yaboot.conf built with the installer. Ah, sorry, this is the already installed system, you are not trying to boot the d-i image, right ? Yes.

Processing of preseed_1.17_i386.changes

2006-06-19 Thread Archive Administrator
preseed_1.17_i386.changes uploaded successfully to localhost along with the files: preseed_1.17.dsc preseed_1.17.tar.gz preseed-common_1.17_all.udeb network-preseed_1.17_all.udeb file-preseed_1.17_all.udeb initrd-preseed_1.17_all.udeb env-preseed_1.17_all.udeb Greetings,

Re: Status of debian-installer for the native ppc64 port

2006-06-19 Thread Otavio Salvador
Sven Luther [EMAIL PROTECTED] writes: In the end I gave up and stopped working on that approach. A few month later I started again to work on the installer, but this time I tried to create a separate native ppc64 d-i port. This turned out to be pretty easy and the resulting installer almost

Bug#251424: marked as done (Please use a short alias for the noframebuffer option at boot)

2006-06-19 Thread Debian Bug Tracking System
Your message dated Mon, 19 Jun 2006 15:47:21 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#251424: fixed in preseed 1.17 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

Bug#349636: marked as done (preseed/early_command is not working with initrd preseeding)

2006-06-19 Thread Debian Bug Tracking System
Your message dated Mon, 19 Jun 2006 15:47:21 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#349636: fixed in preseed 1.17 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

Bug#374228: installation-reports: Installation failed with base-installer/no_codename on AMD64

2006-06-19 Thread Anthony Juckel
FYI, the 2006-06-20 amd64 netinst image is still using a 2.6.15 kernel, so I still get the same module load error. I've got a vested interest in testing the nightlies until I get a version that works for me, so I'll keep relating my experience until I get the system up and running. I've