Hi Thiemo
Thanks for working on this.
Thiemo Nagel writes:
> Hello Ben,
>
> thanks for your input! I'm attaching a series of patches to wrap up what
> we've discussed so far, more details are in the commit messages quoted
> below.
>
> I've tested the patches by running blockdev-wipe, they are
Package: arcboot-installer
Version: 1.21
X-Debbugs-CC: wzss...@gmail.com
This package has one or more -L/usr/lib in its build system,
which will make it ftbfs if there is libraries under /usr/lib,
while is not the default architecture, mips* for example.
On mips* systems, /usr/lib is defined as p
Package: colo-installer
Version: 1.25
X-Debbugs-CC: wzss...@gmail.com
This package has one or more -L/usr/lib in its build system,
which will make it ftbfs if there is libraries under /usr/lib,
while is not the default architecture, mips* for example.
On mips* systems, /usr/lib is defined as plac
Package: elilo-installer
Version: 1.23
X-Debbugs-CC: wzss...@gmail.com
This package has one or more -L/usr/lib in its build system,
which will make it ftbfs if there is libraries under /usr/lib,
while is not the default architecture, mips* for example.
On mips* systems, /usr/lib is defined as pla
Package: flash-kernel
Version: 3.11
X-Debbugs-CC: wzss...@gmail.com
This package has one or more -L/usr/lib in its build system,
which will make it ftbfs if there is libraries under /usr/lib,
while is not the default architecture, mips* for example.
On mips* systems, /usr/lib is defined as place
On 17/09/13 00:15, Cyril Brulebois wrote:
> The "Err" issue while downloading some files ("21: Is a directory") only
> appears on kfreebsd AFAICT, so might be an arch-specific issue.
I saw it happen on Linux i386 too. I now realise the buildd log URIs
are not valid for very long (could /daily/ be
Hello Gaudenz,
thank you for your email!
Any reason why you choose 512k? If I understand your benchmarks right,
> doubling this to 1M yelds about another 27% gain.
I'm sorry, I forgot to mention that I've re-run the benchmarks. After
removing O_SYNC, the performance was identical for block size
Package: mdcfg
Severity: wishlist
Tags: d-i patch
Hello,
from benchmarks in bug #722898 it has emerged that blockdev-wipe is approx. 20%
faster when the guaranteed md resync speed [*] is zero, meaning that userspace
I/O will always be scheduled ahead of resync I/O. The default setting enforces
10
The issue of the raid speed limit is now tracked in bug #723566.
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/CAOGcq_58haAa82Lpp+AEYH=pwhtx81mlh65gpmjjxunyufr...@ma
On Sep 16, 2013, at 5:18 PM, Cyril Brulebois wrote:
> The default installation should have left you using nouveau already.
> What did you change when you "configured X with the nouveau driver"?
I added the attached files to /usr/share/X11.
50-layout.conf
Description: Binary data
30-monito
Hi
Thiemo Nagel writes:
> Hello Gaudenz,
>
> thank you for your email!
>
> Any reason why you choose 512k? If I understand your benchmarks right,
>> doubling this to 1M yelds about another 27% gain.
>
>
> I'm sorry, I forgot to mention that I've re-run the benchmarks. After
> removing O_SYNC, t
> If we are changing this anyway, maybe it's a good time to also make the
> template partman-crypto/progress/erase a bit more explicit about
> canceling.
I fully agree!
> It currently reads: "Erasing data on ${DEVICE}". Maybe something like
> "Erasing data on ${DEVICE}. To continue without ereasi
On Mon, Sep 16, 2013 at 07:02:48PM +0200, Andrey Gursky wrote:
>Hi!
>
>> Are you aware the automatic building of the weekly build is failing for some
>> architectures (amd64, i386, kFreeBSD/i386, kFreeBSD/amd64) from three weeks
>> ago?
>>
>> http://cdimage.debian.org/cdimage/weekly-builds/amd64/
[ Just seen this thread, apologies for delayed responses ]
On Fri, Jul 05, 2013 at 11:40:54PM -0700, Rick Thomas wrote:
>
>On Jul 5, 2013, at 1:25 PM, Brian wrote:
>
>>Well wouldn't documentation for Jigdo template be in Jigdo package?
>
>The jigdo template is a lot lower level than I was hoping f
Debian installer build overview
---
Failed or old builds:
* FAILED BUILD: amd64 Sep 18 00:02 buildd@barber build_cdrom_isolinux
http://d-i.debian.org/daily-images/amd64/daily/build_cdrom_isolinux.log
* FAILED BUILD: amd64 Sep 18 00:03 buildd@barber b
Quoting Steve McIntyre (st...@einval.com):
> CCing the debian-boot list where people are likely to know more. I
> *think* this is a know bug in the build scripts that has been causing
> a lot of failing builds lately. KiBi?
Yes, there is a thread in debian-boot about the daily builds
failures. C
(let's drop CC: I believe that all participants to this discussion are
subscribed to debian-boot, that receves the bug contributions for D-I packages)
Quoting Thiemo Nagel (thiemo.na...@gmail.com):
> > It currently reads: "Erasing data on ${DEVICE}". Maybe something like
> > "Erasing data on ${DE
17 matches
Mail list logo
