As part of the release process for Debian Installer, a string freeze
from July 20th 00:00UTC up to July 25th 00:00 UTC was decided. The
goal is currently a release at the very end of July.
We start in a quite very good shape : 19 languages have already
reached 100%.
Since last release attempts
On Tue, Jul 20, 2004 at 10:33:18AM +1000, Sara Falamaki wrote:
On Mon, Jul 19, 2004 at 04:15:36PM -0400, Rick Thomas wrote:
I don't know if this is relevant, but some IDE controllers only
recognize the first 128 GB(binary) = 137*10^9 bytes.
Is it possible that your controller has two
Steve Langasek wrote:
On Tue, Jul 20, 2004 at 11:51:25AM +0800, John Summerfield wrote:
It's kind of dumb to show the Bootable flag for certain partition
types (like swap), I think it would be better to not show it when it
makes no difference, so as not to confuse the user unnecesarily.
Joshua Kwan wrote:
On Mon, 19 Jul 2004 17:33:48 -0300, Margarita Manterola wrote:
I know we are really really close to release time, but I'm worried about
partman usability. We talked about some of these issues during debconf4,
but I've seen that partman is still the same.
The problem is
Rick Thomas wrote:
Controllers that don't believe in disks larger than 137 GB(decimal)
report any disk larger than that as being exactly 137 GB in size.
This is probably why cfdisk et al are telling you that your partitions
go beyond the end of the disk -- as far as they know, the disk ends
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.7.95.1
severity 259786 important
Bug#259786: xserver-xfree86: Mouse is blocking
Severity set to `important'.
severity 259876 wishlist
Bug#259876: netcfg doesn't ask for manual settings
On (20/07/04 01:03), Colin Watson wrote:
On Mon, Jul 19, 2004 at 11:03:00PM +0100, Clive Menzies wrote:
I also tried to boot the installer (from the RamDisk option) using the
2.6 initrd.gz and vmlinux files and got the following (again I don't
know how to get this serial log and so I copied
Colin Watson wrote:
On Thu, Jul 15, 2004 at 08:40:52PM +0800, John Summerfield wrote:
Could choose-mirror be changed so that if certain environment variables
are set then it uses values from those rather than prompt for them?
II suggest that the proxy information be specified thus:
Hi!
DHCP autoconfiguration fails and I have the option to try again, try it
with a dhcp-hostname or do a manual config. When trying with a hostname:
You may need to supply a DHCP host name. If you are using a cable modem, you
might need to specify an account number here.
Most other
Hello everybody,
Please forgive me if I ask this question in unproper list:
I have new empty machine with usb-cdrom only. How is it possible to run
Sarge installer from this device?
Thank you for any help
Marcin Kaczmarski
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
Package: busybox-cvs
Followup-For: Bug #250047
I have observed the same behavior. I have trouble loading modules
under 2.6 Probably time to update from CVS again, where I see that the
code in insmod.c has changed quite a bit from what's in the Debian
distributed file.
-- System Information:
Package: installation-reports
INSTALL REPORT
Debian-installer-version:
daily built CD image from Jul 18, 2004:
http://cdimage.debian.org/pub/cdimage-testing/daily/powerpc/20040718/sarge-powerpc-netinst.iso
uname -a: Linux veggie 2.6.7-powerpc #1 Sat Jul 10 03:47:45 CEST 2004 ppc GNU/Linux
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
first and foremost: thank you for your bug report.
I'm currently processing old installation reports, and since you
reported some problems with the debian-installer back in March, I would
very much appreciate it, if you could find time to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
first and foremost: thank you for your bug report.
I'm currently processing old installation reports, and since you
reported some problems with the debian installer back in March, I would
very much appreciate it, if you could find time to
Package: installation-reports
Debian-installer-version:
sarge-powerpc-netinst.iso 18-Jul-2004 22:56 206M
from:
http://cdimage.debian.org/pub/cdimage-testing/daily/powerpc/current/
uname -a: 2.6.7 kernel
Date: 20 July 2004 circa 10am BST
Method: Installed BootX 1.2.2 from
Your message dated Tue, 20 Jul 2004 13:37:30 +0200
with message-id [EMAIL PROTECTED]
and subject line Processed: Bug#237618: Installation successful
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
Marcin Kaczmarski wrote:
Hello everybody,
Please forgive me if I ask this question in unproper list:
I have new empty machine with usb-cdrom only. How is it possible to run
Sarge installer from this device?
It should work. It might be necessary to manually load
ehci-hcd or ohci-hcd on console 2.
Package: debian-installer
I attempted to install sarge on my powerpc RS/6000 7043-140 machine, which
is a PReP box. I used the nightly prep netboot image produced by Sven
Luther.
I was unable to proceed past the partitioning stage as the SCSI controller
was not correctly detected. Please see
On Tue, Jul 20, 2004 at 12:44:51PM +0100, Clive Menzies wrote:
Configure network HW: [E] didn't auto detect the ethernet card
and couldn't see an appropriate driver on the list provided
[...]
It's great that BootX will now boot the 2.6.7 version of the installer.
If I can get a
Quoting Helmut Wollmersdorfer ([EMAIL PROTECTED]):
To late, to step in? Is there a rough timeline, milestones? I think, the
side effects to translations would be minimal, because the meaning will
not change, only the wording. But from my last impression on d-i daily
2004-06-07 I estimate
Quoting Martin Pitt ([EMAIL PROTECTED]):
- when configuring the base system, the first debconf template (from
console-data) is obviously encoded in UTF-8, but shown as latin1, i.
e. the umlauts were totally scrambled. All other templates work
normally.
There is something bad which
rootskel_0.87_powerpc.changes uploaded successfully to localhost
along with the files:
rootskel_0.87.dsc
rootskel_0.87.tar.gz
rootskel_0.87_powerpc.udeb
rootskel-bootfloppy_0.87_powerpc.udeb
rootskel-locale_0.87_powerpc.udeb
Greetings,
Your Debian queue daemon
--
To
On (20/07/04 13:12), Colin Watson wrote:
On Tue, Jul 20, 2004 at 12:44:51PM +0100, Clive Menzies wrote:
Configure network HW: [E] didn't auto detect the ethernet card
and couldn't see an appropriate driver on the list provided
[...]
It's great that BootX will now boot the 2.6.7
Accepted:
rootskel-bootfloppy_0.87_powerpc.udeb
to pool/main/r/rootskel/rootskel-bootfloppy_0.87_powerpc.udeb
rootskel-locale_0.87_powerpc.udeb
to pool/main/r/rootskel/rootskel-locale_0.87_powerpc.udeb
rootskel_0.87.dsc
to pool/main/r/rootskel/rootskel_0.87.dsc
rootskel_0.87.tar.gz
to
On (20/07/04 13:12), Colin Watson wrote:
On Tue, Jul 20, 2004 at 12:44:51PM +0100, Clive Menzies wrote:
Configure network HW: [E] didn't auto detect the ethernet card
and couldn't see an appropriate driver on the list provided
[...]
It's great that BootX will now boot the 2.6.7
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry to bother I was wondering if it is possible to use the CD net install
with the beta 4 as a rescue disk
I had to make a dual boot with some windows and cannot get debian to boot
back.
- --
Xavier Leoncini
Laboratoire PIIM - Equipe Dynamique
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 20 July 2004 15:28, Xavier Leoncini wrote:
Sorry to bother I was wondering if it is possible to use the CD net install
with the beta 4 as a rescue disk
I had to make a dual boot with some windows and cannot get debian to boot
back.
Hi Christian!
On 2004-07-20 14:54 +0200, Christian Perrier wrote:
Quoting Martin Pitt ([EMAIL PROTECTED]):
- when configuring the base system, the first debconf template (from
console-data) is obviously encoded in UTF-8, but shown as latin1, i.
e. the umlauts were totally
[Please keep the discussion CCed to the bug report; that way we don't
lose things.]
On Tue, Jul 20, 2004 at 02:16:54PM +0100, Clive Menzies wrote:
On (20/07/04 13:12), Colin Watson wrote:
On Tue, Jul 20, 2004 at 12:44:51PM +0100, Clive Menzies wrote:
Configure network HW: [E] didn't
using 2.6 kernel) -Quik Install
Reply-To:
The installer won't install quik and displays the message:
Failed to resolve kernel symlink
/vmlinux or /boot/vmlinux in the installed system appears not to be a
symlink to a kernel image. This is probably a bug.
This is also happened using 2.4.25
On (20/07/04 15:34), Colin Watson wrote:
On Tue, Jul 20, 2004 at 03:13:04PM +0100, Clive Menzies wrote:
The installer won't install quik and displays the message:
Failed to resolve kernel symlink
/vmlinux or /boot/vmlinux in the installed system appears not to be a
symlink to a kernel
On Tue, Jul 20, 2004 at 03:13:04PM +0100, Clive Menzies wrote:
The installer won't install quik and displays the message:
Failed to resolve kernel symlink
/vmlinux or /boot/vmlinux in the installed system appears not to be a
symlink to a kernel image. This is probably a bug.
That's a bug in
On (20/07/04 15:14), Colin Watson wrote:
[Please keep the discussion CCed to the bug report; that way we don't
lose things.]
On Tue, Jul 20, 2004 at 02:16:54PM +0100, Clive Menzies wrote:
On (20/07/04 13:12), Colin Watson wrote:
On Tue, Jul 20, 2004 at 12:44:51PM +0100, Clive Menzies
quik-installer_0.0.4_powerpc.changes uploaded successfully to localhost
along with the files:
quik-installer_0.0.4.dsc
quik-installer_0.0.4.tar.gz
quik-installer_0.0.4_powerpc.udeb
Greetings,
Your Debian queue daemon
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
Accepted:
quik-installer_0.0.4.dsc
to pool/main/q/quik-installer/quik-installer_0.0.4.dsc
quik-installer_0.0.4.tar.gz
to pool/main/q/quik-installer/quik-installer_0.0.4.tar.gz
quik-installer_0.0.4_powerpc.udeb
to pool/main/q/quik-installer/quik-installer_0.0.4_powerpc.udeb
Announcing to
Your message dated Tue, 20 Jul 2004 10:47:06 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#260396: fixed in quik-installer 0.0.4
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
On Tue, Jul 20, 2004 at 03:44:18PM +0100, Clive Menzies wrote:
On (20/07/04 15:14), Colin Watson wrote:
OK, we can fix that. Just to confirm, can you show me the output of the
following two commands on that system:
ls -l /proc/device-tree$(cat /proc/device-tree/aliases/mac-io)/bmac
Processing commands for [EMAIL PROTECTED]:
clone 260396 -1
Bug#260396: PowerMac G3 (beige) sarge d-i (18 July 2004) Installation Report using 2.6
kernel
Bug 260396 cloned as bug 260427.
reopen -1
Bug#260427: PowerMac G3 (beige) sarge d-i (18 July 2004) Installation Report using 2.6
kernel
Quoting Martin Pitt ([EMAIL PROTECTED]):
Is this bug platform dependend? I can easily try an installation on
i386 (I have a spare partition there), but I don't want to delete the
current installation on my iBook again (no spare partition).
You can reproduce it on i386
--
--
To
partman-auto_25_i386.changes uploaded successfully to localhost
along with the files:
partman-auto_25.dsc
partman-auto_25.tar.gz
partman-auto_25_all.udeb
Greetings,
Your Debian queue daemon
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble?
partman_42_i386.changes uploaded successfully to localhost
along with the files:
partman_42.dsc
partman_42.tar.gz
partman_42_i386.udeb
Greetings,
Your Debian queue daemon
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
partman-basicfilesystems_27_i386.changes uploaded successfully to localhost
along with the files:
partman-basicfilesystems_27.dsc
partman-basicfilesystems_27.tar.gz
partman-basicfilesystems_27_all.udeb
Greetings,
Your Debian queue daemon
--
To UNSUBSCRIBE, email to [EMAIL
partman-basicmethods_18_i386.changes uploaded successfully to localhost
along with the files:
partman-basicmethods_18.dsc
partman-basicmethods_18.tar.gz
partman-basicmethods_18_all.udeb
Greetings,
Your Debian queue daemon
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
On Tue, Jul 20, 2004 at 03:56:12PM +0100, Colin Watson wrote:
On Tue, Jul 20, 2004 at 03:44:18PM +0100, Clive Menzies wrote:
again tomorrow. Meanwhile, assuming I can get a network connection
what's the best way to issue the above commands from my workstation
(which will allow me to cut
partman-ext3_27_i386.changes uploaded successfully to localhost
along with the files:
partman-ext3_27.dsc
partman-ext3_27.tar.gz
partman-ext3_27_all.udeb
Greetings,
Your Debian queue daemon
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble?
partman-jfs_3_i386.changes uploaded successfully to localhost
along with the files:
partman-jfs_3.dsc
partman-jfs_3.tar.gz
partman-jfs_3_all.udeb
Greetings,
Your Debian queue daemon
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
partman-lvm_19_i386.changes uploaded successfully to localhost
along with the files:
partman-lvm_19.dsc
partman-lvm_19.tar.gz
partman-lvm_19_all.udeb
Greetings,
Your Debian queue daemon
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
partman-partitioning_22_i386.changes uploaded successfully to localhost
along with the files:
partman-partitioning_22.dsc
partman-partitioning_22.tar.gz
partman-partitioning_22_all.udeb
Greetings,
Your Debian queue daemon
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
partman-target_25_i386.changes uploaded successfully to localhost
along with the files:
partman-target_25.dsc
partman-target_25.tar.gz
partman-target_25_all.udeb
Greetings,
Your Debian queue daemon
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe.
partman-reiserfs_14_i386.changes uploaded successfully to localhost
along with the files:
partman-reiserfs_14.dsc
partman-reiserfs_14.tar.gz
partman-reiserfs_14_all.udeb
Greetings,
Your Debian queue daemon
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
partman-xfs_14_i386.changes uploaded successfully to localhost
along with the files:
partman-xfs_14.dsc
partman-xfs_14.tar.gz
partman-xfs_14_all.udeb
Greetings,
Your Debian queue daemon
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
apygbgxeaplqcigxzkhajfnhepstmrewardvxywodsvfjxwpzmiixxxwsmvovlclaremont
Need a little spice in your life? having problems with your male parts?
Wana go for days? Keep the wife at home happy. Be happy.
I keep it hard here www.hardandbetter.com
Your message dated Tue, 20 Jul 2004 11:47:25 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#256090: fixed in partman-target 25
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 message dated Tue, 20 Jul 2004 11:47:14 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#255102: fixed in partman 42
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
Your message dated Tue, 20 Jul 2004 11:47:25 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#251487: fixed in partman-target 25
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 message dated Tue, 20 Jul 2004 11:47:14 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#251549: fixed in partman 42
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
Your message dated Tue, 20 Jul 2004 11:47:25 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#250453: fixed in partman-target 25
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 message dated Tue, 20 Jul 2004 11:47:25 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#250190: fixed in partman-target 25
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 message dated Tue, 20 Jul 2004 11:47:26 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#249322: fixed in partman-xfs 14
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
Your message dated Tue, 20 Jul 2004 11:47:26 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#249322: fixed in partman-xfs 14
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
Your message dated Tue, 20 Jul 2004 11:47:17 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#248874: fixed in partman-basicmethods 18
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
Your message dated Tue, 20 Jul 2004 11:47:23 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#246998: fixed in partman-partitioning 22
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
Accepted:
partman-xfs_14.dsc
to pool/main/p/partman-xfs/partman-xfs_14.dsc
partman-xfs_14.tar.gz
to pool/main/p/partman-xfs/partman-xfs_14.tar.gz
partman-xfs_14_all.udeb
to pool/main/p/partman-xfs/partman-xfs_14_all.udeb
Announcing to [EMAIL PROTECTED]
Closing bugs: 249322 255135 258117
Accepted:
partman-reiserfs_14.dsc
to pool/main/p/partman-reiserfs/partman-reiserfs_14.dsc
partman-reiserfs_14.tar.gz
to pool/main/p/partman-reiserfs/partman-reiserfs_14.tar.gz
partman-reiserfs_14_all.udeb
to pool/main/p/partman-reiserfs/partman-reiserfs_14_all.udeb
Announcing to [EMAIL
Your message dated Tue, 20 Jul 2004 08:51:39 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#245515: more info, please
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
Accepted:
partman-partitioning_22.dsc
to pool/main/p/partman-partitioning/partman-partitioning_22.dsc
partman-partitioning_22.tar.gz
to pool/main/p/partman-partitioning/partman-partitioning_22.tar.gz
partman-partitioning_22_all.udeb
to
Accepted:
partman-jfs_3.dsc
to pool/main/p/partman-jfs/partman-jfs_3.dsc
partman-jfs_3.tar.gz
to pool/main/p/partman-jfs/partman-jfs_3.tar.gz
partman-jfs_3_all.udeb
to pool/main/p/partman-jfs/partman-jfs_3_all.udeb
Announcing to [EMAIL PROTECTED]
Closing bugs: 249322 255135 258117
Thank
Accepted:
partman-auto_25.dsc
to pool/main/p/partman-auto/partman-auto_25.dsc
partman-auto_25.tar.gz
to pool/main/p/partman-auto/partman-auto_25.tar.gz
partman-auto_25_all.udeb
to pool/main/p/partman-auto/partman-auto_25_all.udeb
Announcing to [EMAIL PROTECTED]
Thank you for your
Your message dated Tue, 20 Jul 2004 11:47:14 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#254814: fixed in partman 42
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
Your message dated Tue, 20 Jul 2004 11:47:19 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#238179: fixed in partman-ext3 27
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 message dated Tue, 20 Jul 2004 11:47:14 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#250969: fixed in partman 42
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
Your message dated Tue, 20 Jul 2004 11:47:19 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#238179: fixed in partman-ext3 27
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 message dated Tue, 20 Jul 2004 11:47:16 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#243648: fixed in partman-basicfilesystems 27
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
Accepted:
partman_42.dsc
to pool/main/p/partman/partman_42.dsc
partman_42.tar.gz
to pool/main/p/partman/partman_42.tar.gz
partman_42_i386.udeb
to pool/main/p/partman/partman_42_i386.udeb
Announcing to [EMAIL PROTECTED]
Closing bugs: 241476 246523 250895 250969 251549 254814 255102
Thank
Package: installation-reports
Version: sarge-netinstall powerpc 20040718
architecture: powerpc
model: JS20 Blade
memory:2 Gig
scsi: none
cd-rom:USB over ISD200
network card: broadcom 5704
pcmcia:none
I tried using the sarge netinstall for powerpc on a
Your message dated Tue, 20 Jul 2004 11:47:13 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#241476: fixed in partman 42
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
Your message dated Tue, 20 Jul 2004 11:47:21 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#248062: fixed in partman-lvm 19
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
Your message dated Tue, 20 Jul 2004 11:47:16 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#243648: fixed in partman-basicfilesystems 27
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
Accepted:
partman-ext3_27.dsc
to pool/main/p/partman-ext3/partman-ext3_27.dsc
partman-ext3_27.tar.gz
to pool/main/p/partman-ext3/partman-ext3_27.tar.gz
partman-ext3_27_all.udeb
to pool/main/p/partman-ext3/partman-ext3_27_all.udeb
Announcing to [EMAIL PROTECTED]
Closing bugs: 238179 249322
Accepted:
partman-basicfilesystems_27.dsc
to pool/main/p/partman-basicfilesystems/partman-basicfilesystems_27.dsc
partman-basicfilesystems_27.tar.gz
to pool/main/p/partman-basicfilesystems/partman-basicfilesystems_27.tar.gz
partman-basicfilesystems_27_all.udeb
to
Accepted:
partman-basicmethods_18.dsc
to pool/main/p/partman-basicmethods/partman-basicmethods_18.dsc
partman-basicmethods_18.tar.gz
to pool/main/p/partman-basicmethods/partman-basicmethods_18.tar.gz
partman-basicmethods_18_all.udeb
to
Accepted:
partman-lvm_19.dsc
to pool/main/p/partman-lvm/partman-lvm_19.dsc
partman-lvm_19.tar.gz
to pool/main/p/partman-lvm/partman-lvm_19.tar.gz
partman-lvm_19_all.udeb
to pool/main/p/partman-lvm/partman-lvm_19_all.udeb
Announcing to [EMAIL PROTECTED]
Closing bugs: 248062 250033 250971
Accepted:
partman-target_25.dsc
to pool/main/p/partman-target/partman-target_25.dsc
partman-target_25.tar.gz
to pool/main/p/partman-target/partman-target_25.tar.gz
partman-target_25_all.udeb
to pool/main/p/partman-target/partman-target_25_all.udeb
Announcing to [EMAIL PROTECTED]
Closing
Your message dated Tue, 20 Jul 2004 11:47:26 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#249322: fixed in partman-xfs 14
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
Your message dated Tue, 20 Jul 2004 11:47:21 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#250033: fixed in partman-lvm 19
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
Your message dated Tue, 20 Jul 2004 11:47:13 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#250895: fixed in partman 42
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
Hi!
In general Partman suffers from two things.
First - it is very slow. I'd say it was designed to be slow because
when I started thinking about it I didn't expect that it will become as
slow as it is now. Moreover adding additional components to it make it
even slower...
Second - its
Your message dated Tue, 20 Jul 2004 12:44:01 -0400
with message-id [EMAIL PROTECTED]
and subject line Report cleanup
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
On Tuesday 20 July 2004 12:47, Jake Moilanen wrote:
...
- yaboot.conf is not located at /etc/yaboot.conf. If you are booting a
chrp box, yaboot expects yaboot.conf to be at /etc/yaboot.conf. I got
around this problem by doing a hardlink.
- The device in yaboot.conf is set to 'cd' and newer
dann frazier wrote:
Jim Lieb filed a patch for #257910 which adds the partman-efi package
and adds efi support to partman-auto. I've tested an image he made
for us, and it worked fine on my system.
I'd appreciate if someone more partman knowledgable than I could
take a look at the
I'm the implementor of partman.efi.
Let's get this down to specifics. All IA64 platforms and
newer server class Xeon and bigger systems use EFI instead
of the traditional BIOS that PC users are expecting.
This patch set is IA64 architecture and IA32+EFI specific.
Other partitioning methods are
I apologize for making string changes in partman today. I didn't guess
that Tuesday means probably 0:00 GMT and not 23:59 GMT (and I was
offline since the IRC-meeting so I missed the announcement in
debian-boot).
On Mon, Jul 19, 2004 at 11:45:42PM -0300, Margarita Manterola wrote:
The problem
On Tuesday 20 July 2004 10:05, Joey Hess wrote:
dann frazier wrote:
Jim Lieb filed a patch for #257910 which adds the partman-efi
package and adds efi support to partman-auto. I've tested an image
he made for us, and it worked fine on my system.
I'd appreciate if someone more
Anton Zinoviev wrote:
Then, I think that a GREAT difference could be made by transforming the Help
and Finish options into buttons at the bottom of the screen.
This is something that cdebconf doesn't allow (for now).
Martin and I kicked around an idea for a debconf extention that would
Anton Zinoviev wrote:
In order to solve the first problem we have two choices:
1. Wait until the computers became faster. At 2009 when sarge+1 will be
released [;-)] they will be about 5 times faster than now.
2. Rewrite it in some other language. If we take this approach I would
Jim Lieb wrote:
The strings in the template have already been translated for the
most part. I picked the strings from the hppa/palo boot and did an
s/palo/efi/g on them. The big translation part is patch set I made for
the manual.
As far as I can tell, this string is not translated at all:
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.7.95.1
reassign 260403 installation-reports
Bug#260403: sarge install on powerpc RS/6000 7043-140 failed
Bug reassigned from package `debian-installer' to `installation-reports'.
End of
Matt Kraai wrote:
After each failed download, anna asks whether I want to retry,
change the mirror, or cancel. Since the network connection here
is poor, I see this question a lot. It would be nice to have an
option to always retry failed downloads.
The right package is probably the
On Mon, Jul 19, 2004 at 09:36:15PM -0600, dann frazier wrote:
I'd appreciate if someone more partman knowledgable than I could
take a look at the patch; if it looks reasonable to such a person,
I'll be happy to commit these changes and do an upload.
Unfortunately you based your package on
Package: installation-reports
INSTALL REPORT
Debian-installer-version:
http://cdimage.debian.org/pub/cdimage-testing/sarge_d-i/i386/beta4/sarge-i386-netinst.iso
uname -a: uname -a: Linux ledzep 2.4.25-1-386 #2 Wed Apr 14 19:38:08 EST 2004 i686
GNU/Linux
Date: 19/07/2004 - 18h
Method: How did
1 - 100 of 134 matches
Mail list logo
