On Monday 20 October 2008, 20:33:03, you wrote:
Marco Amadori wrote:
Is this the preferred way to achieve it? To embed the deb in the cdrom
media? Or shall a udeb be produced from deb source, or unpack and add it
to the initramfs (where it could satify also netboot use case)?
The only
Package: installation-reports
Boot method: CD
Image version: Debian GNU/Linux testing Lenny - Official Snapshot
amd64 kde-CD Binary-1 20081006-15:04
Date: 2008-10-20
Machine: Dell Precision 380
Processor: Intel Pentium D CPU 3.00GHz stepping 7
Memory: 2.95 GB
Partitions:
Dateisystem Typ
Hi,
just wanna inform that now also our formerly working 32 bit machine
has that problem permanently, even after scratching the whole disk
with dd if=/dev/zero of=/dev/sda over night before. (We formerly
suspected the previous existence of an LVM on the disk caused that
behaviour.) The strange
Package: debian-installer
Severity: normal
There are multiple wireless spots around my house. Debian defaults to an
unsecured network(see later how I discovered this), but that network needs a
web-based login (only
available to paying customers), so it doesn't actually work. My own
wireless
reassign 502955 netcfg
forcemerge 284799 502955
thanks
Quoting Mate Soos ([EMAIL PROTECTED]):
Package: debian-installer
Severity: normal
There are multiple wireless spots around my house. Debian defaults to an
unsecured network(see later how I discovered this), but that network needs a
Processing commands for [EMAIL PROTECTED]:
reassign 502955 netcfg
Bug#502955: debian-installer: essid cannot be chosen
Bug reassigned from package `debian-installer' to `netcfg'.
forcemerge 284799 502955
Bug#284799: installation-reports: Choosing the WIFI ESSID in the non expert
mode of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christian Perrier wrote:
reassign 502955 netcfg
forcemerge 284799 502955
thanks
Quoting Mate Soos ([EMAIL PROTECTED]):
Package: debian-installer
Severity: normal
There are multiple wireless spots around my house. Debian defaults to an
reopen 502850
reassign 502850 preseed
severity 502850 important
thanks
On Tuesday 21 October 2008, Durk Strooisma wrote:
bad.di stops really early when it's parsed by debconf-set-selections.
It already stops parsing on the first lines and doesn't reach the
pkgsel/include question. Which is
Processing commands for [EMAIL PROTECTED]:
reopen 502850
Bug#502850: debian-installer: D-I fails to process some correct (!) preseed
files
Bug is already open, cannot reopen.
reassign 502850 preseed
Bug#502850: debian-installer: D-I fails to process some correct (!) preseed
files
Bug
Hi,
For Bug #502446: http://bugs.debian.org/502446
Here is updated patch which takes care odd partition offset of grub
legacy. Around frdev, I may have been too aggressive
I will test this later ...
Osamu
diff -Nru grub-installer-1.35/debian/changelog
Note that $line at that point is the three lines concatenated, minus
the line continuation character.
What we're now going to need is a simplified, reproducible testcase;
probably just a simple script that sets a variable to a bad value and
then executes the test above.
Hmm I didn't exactly
Hi,
this bug is very likely the same bug as #502618 and #502432.
Kind regards, Axel Beckert
--
Axel Beckert [EMAIL PROTECTED] support: +41 44 633 2668
IT Support Group, HPT D17 (new address!) voice: +41 44 633 4189
Departement Physik, ETH Zurichfax: +41
Hi,
On Tuesday 21 October 2008 13:46, Glenn Saberton wrote:
I actually tend to agree that asking for an essid should be default
these days. Wifi use has grown a lot since the netcfg stuff was done,
and default to associating with any open AP is really a security risk.
Then again, some people
On Saturday 18 October 2008, Jeroen Dekkers wrote:
I currently have the same problem. The reason the logical volume is in
use seems to be that when you finish partitioning and partman goes to
the stage of creating the filesystems, the system has suddenly created
partitions on top of the
Marco Amadori wrote:
Just a two lines patch in hw-detect/check-missing-firmware.sh to
include /cdrom/firmware in the scan could hit lenny d-i in your opinion?
It would still prompt for removable media before looking there. Maybe
the prompt is generic enough that a CD can meet the bill, but it
On Tue, Oct 21, 2008 at 06:16:46PM +0200, Frans Pop wrote:
On Saturday 18 October 2008, Jeroen Dekkers wrote:
I currently have the same problem. The reason the logical volume is in
use seems to be that when you finish partitioning and partman goes to
the stage of creating the filesystems,
Package: installation-reports
Version: 2.35
Severity: normal
-- Package-specific info:
Boot method: CD
Image version:
http://cdimage.debian.org/cdimage/lenny_di_beta2/i386/iso-cd/debian-LennyBeta2-i386-netinst.iso
Date: 2008-10-16 16:14 CEST
Machine: seflmade i386 based PC
Partitions: df -Tl
Hi,
On Tue, Oct 21, 2008 at 06:16:46PM +0200, Frans Pop wrote:
The cause looks to be a recent change by Colin Watson in partman-base
(128). If I rebuild parted_server without that change, I can no longer
reproduce the error.
Interesting. We at least had a few successful installations where
Your message dated Tue, 21 Oct 2008 19:48:45 +0200
with message-id [EMAIL PROTECTED]
and subject line Re: Bug#502999: installation-report: successfull instalaltion
report
has caused the Debian Bug report #502999,
regarding installation-report: successfull instalaltion report
to be marked as
On Tuesday 21 October 2008, Colin Watson wrote:
That may be the proximate cause, but at most it's just exposing
breakage elsewhere. The actual incorrect code is in libparted itself,
not parted_server. It should not be generating p1-type device names
for LVM logical volumes.
Problem is that
On Tuesday 21 October 2008, Frans Pop wrote:
I've taken a look at the two manual runs and it looks like there is
some weird issue in busybox.
[...]
In the bad case $package is correctly determined as d-i, but after
that the following comparison in the script evaluates to true:
[ $line !=
On Tue, Oct 21, 2008 at 09:02:57PM +0200, Frans Pop wrote:
On Tuesday 21 October 2008, Colin Watson wrote:
That may be the proximate cause, but at most it's just exposing
breakage elsewhere. The actual incorrect code is in libparted itself,
not parted_server. It should not be generating
Processing commands for [EMAIL PROTECTED]:
reassign 502913 partman-lvm
Bug#502913: debian-installer: mkfs.ext3 fails with raid10+dmcrypt+lvm
Bug reassigned from package `debian-installer' to `partman-lvm'.
reassign 502432 partman-lvm
Bug#502432: Lenny AMD64: netinst/partman/expert recipe: FS
On Tuesday 21 October 2008, Colin Watson wrote:
Maybe something like this?
Thanks for the patch. I'll give it a try tomorrow.
If that is correct, we can probably remove a few tests for loop devices in
partman:
- partman-base/choose_partition/partition_tree/do_option: 55
-
I can confirm that Colin's patch of Tue, 21 Oct 2008 22:57:45 +0100 fixes
the problem for me on a test install on amd64. I tested by building parted
and then putting the udeb into localudebs and putting it into the initrd.
- Matt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
I wasn't sure if adding an extra udeb into the initrd was acceptable; since
it's OK, I've reworked the patch to do that instead. New patch attached,
with tests this time (I forgot to include them in the diff last time).
- Matt
unchanged:
---
Package: debian-installer
Severity: normal
Tags: patch
The attached patch extends d-i firmware building for armel to build initrd
and kernel uBoot files, and a complete firmware image, for the DNS-323 and
CH3SNAS devices. The patch requires a new package dns323-firmware-tools,
which is currently
Processing commands for [EMAIL PROTECTED]:
tag 502936 +patch
Bug#502936: Include minix-modules in the armel-orion5x d-i kernel
There were no tags set.
Tags added: patch
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
A build of the Debian Installer Manual was triggered by an update to SVN.
There were no errors during the build process.
The new version of the manual has been uploaded successfully.
A log of the build is available at:
- http://d-i.alioth.debian.org/manual/logs/en.log
===
It is possible to use
As further confirmation, I've just tested an install on an armel box with
Colin's patch, and it worked nicely there, too.
- Matt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
30 matches
Mail list logo
