Re: task-* problem
Philip Charles <philipc@copyleft.co.nz> writes:
> I built disc trees with the latest debian-cd with FORCENONUSONCD1 and
> export NONUS switched on. FORCENONUSONCD1 did not work by itself. Two
> sets of disc trees were produced, non-US and the other, so far so good.
>
> However, when I checked the task-* packages they were scattered through
> the three CDs of both sets, mainly on CD 3.
>
> Is this the case with the TC3 images?
open:/debian2/staging-area$ grep task */*.list | grep '[23].list'
alpha/potato-alpha-2.list:/dists/potato/main/binary-all/devel/task-parallel-computing-dev_1.0.2.deb
alpha/potato-alpha-2.list:/dists/potato/main/binary-all/misc/task-chinese-t_0.6.deb
alpha/potato-alpha-2.list:/dists/potato/main/binary-all/misc/task-chinese-s_0.6.deb
alpha/potato-alpha-2.list:/dists/potato/main/binary-all/misc/task-german_0.5.debalpha/potato-alpha-2.list:/dists/potato/main/binary-all/misc/task-japanese_0.7.deb
alpha/potato-alpha-2.list:/dists/potato/main/binary-all/misc/task-polish_0.1.debalpha/potato-alpha-2.list:/dists/potato/main/binary-all/misc/task-spanish_0.2.deb
i386/potato-i386-2.list:/dists/potato/main/binary-all/misc/task-japanese_0.7.debi386/potato-i386-2.list:/dists/potato/main/binary-all/misc/task-polish_0.1.deb
src/potato-src-2.list:/dists/potato/main/source/misc/task-japanese_0.7.dsc
src/potato-src-2.list:/dists/potato/main/source/misc/task-japanese_0.7.tar.gz
src/potato-src-2.list:/dists/potato/main/source/misc/task-polish_0.1.dsc
src/potato-src-2.list:/dists/potato/main/source/misc/task-polish_0.1.tar.gz
open:/debian2/staging-area$
Seems to have put task-japanese and task-polish onto i386#2
On alpha it's done those as well as task-german, task-chinese-[ts] &
task-parallel-computing
Presumably, all that packages that make up those tasks failed to fit
on CD#1, so there's not much point putting the task on #1 and taunting
the people that have got single CDs.
> When I rebuilt the trees with only export NONUS switched on
> everything went well.
That's because you've freed up some room on #1 by not including
non-US.
The only worrying thing is that you say they ended up on CD#3 --- how
non-deterministic is this? Are we likely to see a mass migration of
task packages from CD#1 just because some package that's on there
grows by a few KB as the result of a last minute fix?
Cheers, Phil.
Reply to: