Re: Sources vs udeb mismatch in sarge
(I'm still not subscribed)
On Sun, May 01, 2005 at 10:53:37AM -0400, Joey Hess wrote:
> Jeroen van Wolffelaar wrote:
> > cdebconf: udeb's are from 0.72, but in sarge is 0.74.
> > Suggested resolution: accept the udeb's from sid into sarge
>
> I've been sorta planning to accept 0.74, since it's had a lot of testing
> time. It does actually have some UI behavior change, so who knows if
> this will end up confusing people.
Right, most of the other change have been committed as of today's
dinstall, with a little delay, obviously. Currently, a (mostly) new set
of 10 d-i source packages are out-of-sync. They are:
sarge's udeb's built from | sarge's source is at
- cdebconf: 0.72 | 0.74
- dhcp3: 3.0.1-1 | 3.0.1-2
- e2fsprogs: 1.35-8 | 1.37-2
- expat: 1.95.8-1 | 1.95.8-3
- glibc: 2.3.2.ds1-20 | 2.3.2.ds1-21
- hdparm: 5.9-4 | 6.1-1
- lvm2: 2.01.04-3 | 2.01.04-5
- ppp: 2.4.3-20050321+1 | 2.4.3-20050321+2
- util-linux: 2.12-10 | 2.12p-4
Basicly, unless (what's a really bad idea) one wants to have the source
versions go *downwards*, udeb's need to be upgraded w.r.t. what sarge's
sources are.
Unfortunately, it seems a number of those source packages got unstable
uploads already, causing the not yet synced over udeb's to go missing.
This is a direct result from unstable uploads not intended for sarge
while sarge's d-i wasn't yet in shape in the archive. The following
packages can therefore not be straightforwardly fixed by allowing
the right udeb's in: cdebconf (sid has 0.77), e2fsprogs (sid has
1.37+1.38-WIP-0509-1) and glibc* (sid has 2.3.2.ds1-22).
* but glibc's -22 probably needs to make testing anyway, so isn't too
bad
For e2fsprogs and cdebconf, unless somehow the sid versions are
suiteable for sarge, there will need to come a testing-proposed-updates
rebuild-only upload to get the udeb's back, so that this time they *can*
be put in sarge.
Are there otherwise issues with any of those 9 source packages w.r.t.
udeb's getting synced to what already happened due to the source
packages being let into sarge? If so, those will need to be fixed.
The only out-of-sync-the-other-way package is vmelilo-installer, on next
run I will (have) put the 1.8 source in sarge to go with the 1.8 udeb
that's already in.
Thanks,
--Jeroen
--
Jeroen van Wolffelaar
Jeroen@wolffelaar.nl (also for Jabber & MSN; ICQ: 33944357)
http://Jeroen.A-Eskwadraat.nl
Reply to: