On Sat, 2013-09-28 at 20:51 +0200, Thiemo Nagel wrote:
> For what it's worth, the patches look good to me but I didn't
> test them.
>
>
> Thanks for looking! Is there anything still required for the patches
> to be committed?
Dmitrijs, please can you review Thiemo's patches and a
Processing commands for cont...@bugs.debian.org:
> # submitter made a proper report as #724840
> close 724838
Bug #724838 [installation-reports] testing installation bug report
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
724838: http://bugs.
On Sat, 28 Sep 2013 20:55:29 +0200
Chris Debian wrote:
> I did test both GRUB_DISABLE_OS_PROBER=true and
> GRUB_DISABLE_OS_PROBER=false followed by a 'sudo update-grub', but it
> did not changed anything : my other OS is not detected.
>
> It seems that os-prober does not succeed in detecting the
I had time to do some more testing.
In the file keyboard-configuration.config I saw the following line:
sg) XKBLAYOUT="ch"; XKBVARIANT="de";;
So I tried the following settings:
language=en country=CH locale=en_US.UTF-8 debian-installer/keymap=sg keymap=sg
Unfortunately the settings were not set
ian_br...@fastmail.net a écrit le 28/09/2013 10:25:
>
> [...]
> There's an option called "GRUB_DISABLE_OS_PROBER" in /etc/default/grub
> which may be relevant to your problem. See here:
>
> http://www.gnu.org/software/grub/manual/html_node/Simple-configuration.html
>
> https://www.google.com/search
>
> For what it's worth, the patches look good to me but I didn't test them.
>
Thanks for looking! Is there anything still required for the patches to be
committed?
Cheers,
Thiemo
Hello,
I've benchmarked two different resync speed settings in several
configurations by test-installing a base system with debootstrap and
determining the running time of the package installation phase from
dpkg.log. All tests were run on an Athlon II X4 640 with 4 GB RAM.
The first test setup c
Package: installation-reports
Boot method: jessie + firmware netinstall cd
Image version:
http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/weekly-builds/amd64/iso-cd/firmware-testing-amd64-netinst.iso
Date: 27/09/2013
Machine: custom built pc with asrock fm2a75 pro 4 m
Package: installation-reports
Boot method: jessie + firmware netinstall cd
Image version:
http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/weekly-builds/amd64/iso-cd/firmware-testing-amd64-netinst.iso
Date: 27/09/2013
Machine: custom built pc with asrock fm2a75 pro 4 m
Package: os-prober
Version: 1.63
Followup-For: Bug #592834
Dear Maintainer,
I've just encountered the same scary message while installing memtest86+ :
$ sudo aptitude install memtest86+
Les NOUVEAUX paquets suivants vont être installés :
memtest86+
0 paquets mis à jour, 1 nouvellement instal
On 28/09/13 11:07, Cyril Brulebois wrote:
> [...] supported cdrom settings went from
> kfreebsd + kfreebsd-9 to kfreebsd-9 only; when adding kfreebsd-10
> support, the cdrom settings weren't added kfreebsd-10, and the patch
> below isn't adding it either (so the build should be OK since that part
>
This patch introduces a boot parameter, "loopmount=", which allows the
specification of a full pathname (relative to the root directory of some
block device) of an ISO image file which should be loop-mounted as the
Debian installer root filesystem.
The main purpose of this feature is to facilitate
Robert Millan (2013-09-28):
> Here, attached patch should get jessie builds working again. Would you
> be kind enough to commit it?
Steve (from debian-cd@) is likely the one who's going to check it. I
wonder, however, if the -boot/-cd changes are actually correct.
When removing kfreebsd 8 suppor
Cyril Brulebois:
> Robert Millan (2013-09-26):
>>> so you broke cdimage building for kfreebsd-*:
>>> http://anonscm.debian.org/gitweb/?p=d-i/debian-installer.git;a=commitdiff;h=c5a8de108e7828cc3e2694309cbb045eb8db521c
>>>
>>>
>> http://anonscm.debian.org/gitweb/?p=d-i/debian-installer.git;a=commi
you wrote:
> When I run a 'sudo update-grub', it only finds the Debian kernel and
> does not create any entry for my Ubuntu install.
There's an option called "GRUB_DISABLE_OS_PROBER" in /etc/default/grub
which may be relevant to your problem. See here:
http://www.gnu.org/software/grub/manual/htm
15 matches
Mail list logo
