Bug#315914: priority issue

2005-06-26 Thread Joey Hess
 aj: hmm, debootstrap sid fails now because whiptail depends on 
libslang2. Wasn't dependency resolution supposed to avoid this kind of problem?
 joeyh: only if you use it?
 sid script uses it, doesn't it?
 no
 --resolve-deps
 for sid, the non dep-resolving fix is to get the overrides changed so 
libslang2 is the same priority as whatever it depends on
 hmm, I see. So should d-i start using --resolve-deps to get the added 
robustness?
 (libslang2 is already standard, but whiptail is prio important)
 d-i betas, yeah; pretty much until the point of release candidates
 until base is frozen, but not after, because of .. overhead?
 the dependency resolver isn't particularly precise or particularly fast

So we need an override to either make whiptail be standard priority, or
libslang2 important priority.

-- 
see shy jo


signature.asc
Description: Digital signature


Bug#315914: priority issue

2005-06-26 Thread Alastair McKinstry
On Luan, 2005-06-27 at 01:42 -0400, Joey Hess wrote:
>  aj: hmm, debootstrap sid fails now because whiptail depends on 
> libslang2. Wasn't dependency resolution supposed to avoid this kind of 
> problem?
>  joeyh: only if you use it?
>  sid script uses it, doesn't it?
>  no
>  --resolve-deps
>  for sid, the non dep-resolving fix is to get the overrides changed so 
> libslang2 is the same priority as whatever it depends on
>  hmm, I see. So should d-i start using --resolve-deps to get the added 
> robustness?
>  (libslang2 is already standard, but whiptail is prio important)
>  d-i betas, yeah; pretty much until the point of release candidates
>  until base is frozen, but not after, because of .. overhead?
>  the dependency resolver isn't particularly precise or particularly fast

Yes. My upload of libslang2 2.0.4, which was supposed to go into the
archive at the same time as libnewt, didn't; it had the changeover to
Priority: required.

> So we need an override to either make whiptail be standard priority, or
> libslang2 important priority.
> 

Uploading now



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]