[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#649319: debootstrap: cannot handle perl-modules 5.12.4-6 and 5.14.2-5 both being in sid



Colin Watson wrote:
> I agree that debootstrap ought to solve this problem.  (In fact, it's in
> the pkgdetails API, so we need to solve this in both debootstrap and
> bootstrap-base; cloning this bug for that.)
> 
> The bit that makes it difficult is that we need to do this work before
> we necessarily have dpkg available, so we can't compare version numbers
> in any remotely reliable way.  What we can do, however, is notice when
> there are multiple stanzas with the same package name, and pick the last
> one rather than the first.  dak seems to reliably sort in ascending
> version order; Launchpad also does, although from code inspection I
> think this is a result of sorting by ascending order of publication IDs,
> but it seems to amount to the same thing in practice.  (Even if this
> weren't 100% reliable, always picking the last stanza for a given
> package name is no worse than always picking the first one.)
> 
> I'm working on this now.

Note that debootstrap should not need to install perl at all, and I made
a NMU yesterday that should remove the dependency that was pulling it
in.

This is an unusual situation; I think DAK included both perl-modules
because it's arch all and different versions are needed on different
architectures. It follows that there's no single right version -- a
dependency resolver is needed to pick the right one. It does not make
sense to put a dependency resolver in debootstrap, so the place to fix
this kind of breakage seems to be in the archive, and not in
debootstrap.

Preferring the later version might be a better heuristic on average.

-- 
see shy jo

Attachment: signature.asc
Description: Digital signature


Reply to: