On Fri, Oct 28, 2005 at 02:50:43PM +1000, Anthony Towns wrote:
>On Wed, Oct 26, 2005 at 07:33:59PM +0100, Steve McIntyre wrote:
>> Package: debootstrap
>> Version: 0.3.2
>> Severity: important
>> 
>> Calling debootstrap with --print-debs includes kill_target. This seems
>> a little silly - if we're just calling debootstrap to list the debs,
>> we don't _have_ a target to kill!
>
>Yes, you do: --resolve-deps (on by default now) creates it as somewhere
>to store the Packages files it downloads in order to see the Depends:
>fields it's trying to resolve.

Ah, my bad. I hadn't noticed that bit.

>> This change has caused us to have some really strange issues when
>> producing debian testing CDs, as debootstrap was unexpectedly removing
>> parts of the setup tree. Hence the Severity: important above...
>
>You can use "--keep-debootstrap-dir" to avoid kill_target. I'm not
>actually quite sure why kill_target would be problematic behaviour for
>debian-cd though.

I've added the --keep-debootstrap-dir option already to get things
going, and that seems to have worked.

debian-cd is using debootstrap from the _udeb_ for each architecture
to verify that we will have all the packages needed installed on the
CD, hence the --print-debs. As we're not specifying a target, strange
things are happening in kill_target and the debian-cd work directory
is getting deleted. As the "--keep-debootstrap-dir" stops this
happening, I can only deduce that kill_target is to blame. I'll dig
into this a little more when I have the time.

-- 
Steve McIntyre, Cambridge, UK.                                [EMAIL PROTECTED]
"The problem with defending the purity of the English language is that
English is about as pure as a cribhouse whore. We don't just borrow words; on
occasion, English has pursued other languages down alleyways to beat them
unconscious and rifle their pockets for new vocabulary."  -- James D. Nicoll

Attachment: signature.asc
Description: Digital signature

Reply via email to