Bug#746413: live-build: DEBOOTSTRAP_OPTIONS not actually passed to debootstrap
close 746413 4.0.0-1 thanks there wasn't enough time to finish the python transition, hence, i've reverted the python stubs to their previous shell script. we'll do the move to python for jessie+1. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746413: live-build: DEBOOTSTRAP_OPTIONS not actually passed to debootstrap
On 30/04/14 00:17, Daniel Baumann wrote: general disclaimer: you're using 4.x, which has many rough edges and such, so.. i'm aware that there are lots of things to finish before its properly usuable, and any help getting it done faster is more than welcome. OK, noted. I'm mainly using 4.x because it seems I need the new --hdd-size feature; the existing size estimation code doesn't seem to allocate enough space, perhaps because my working area filesystem (initially btrfs, now tmpfs) has lower overhead than the one I'm using for the binary image (ext4). the general plan is this: * lb init would do more-or-less what lb config did wrt/ initialize a config tree in a previously empty directory. * lb config would be a set/get program only Thanks, that's useful information. [cdebootstrap] options = --exclude=package1,package2 into config/options/cdebootstrap I can't devote enough time to this to implement the whole of your plan, but now that I know where the goal is, I could make bootstrap-(c)debootstrap read a file with that syntax if one is supplied - that's a step forward at least. S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746413: live-build: DEBOOTSTRAP_OPTIONS not actually passed to debootstrap
On 04/30/2014 11:44 AM, Simon McVittie wrote: I can't devote enough time to this to implement the whole of your plan, sure; I could make bootstrap-(c)debootstrap read a file with that syntax if one is supplied - that's a step forward at least. any part/help to reach the goal is more than welcome ;) -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746413: live-build: DEBOOTSTRAP_OPTIONS not actually passed to debootstrap
On 04/29/2014 09:38 PM, Simon McVittie wrote: I see there's a TODO in bootstrap-debootstrap for reading options from config/options/cdebootstrap. Is that the new UI for a user to do what used to be done via --debootstrap-options, or is the idea that lb config should create that file? general disclaimer: you're using 4.x, which has many rough edges and such, so.. i'm aware that there are lots of things to finish before its properly usuable, and any help getting it done faster is more than welcome. the general plan is this: * lb init would do more-or-less what lb config did wrt/ initialize a config tree in a previously empty directory. * lb config would be a set/get program only this means: * if the user would do lb init, it would probably touch an empty config/options/cdebootstrap * if the user then wants to set cdebootstrap options, he could use e.g. lb config --set options.cdebootstrap --exclude=package1,package2 which would then write: [cdebootstrap] options = --exclude=package1,package2 into config/options/cdebootstrap * lb bootstrap-cdebootstrap would then read (if existing) options/config/cdebootstrap and use the options specified there when invoking cdebootstrap. hope that helps, Daniel -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org