Re: Bug#238193: use debconf to manage permissions of ls-r not high-priority question
Colin Watson <email@example.com> wrote:
> There will hopefully be another release update soon; we're holding
> reasonably to the last schedule posted on -devel-announce,
Which was, IIRC, basically: Work hard on d-i, report on March 15, and
then we'll see. At least I don't remember any dates or even approximate
> there are still a number of serious bugs in the base system that need to
> be ironed out and a few more architectures that need to be hammered into
> shape for d-i.
So what does this mean? To me, it is still not clear whether this means
weeks or many months. Perhaps I could know better if I followed the
development of d-i closer. But in fact I'd rather spend my time fixing
bugs in my packages.
> In the meantime, it does make our lives harder in release
> planning when people drop in major new versions of major packages, and
> it makes it harder to get a freeze working.
Note that 80% of the work we've done on tetex-3.0 is related to
packaging bugs that also exist in our current packages, and can easily
be backported once it is clear that sarge will release soon.
Currently I don't dare install sarge on my working box because I cannot
be sure that there won't be a broken glibc, XFree86 or perl one
day. Under these circumstances I don't feel much inclined to refrain
generally from including any other upstream version of a very-much-less
In fact we haven't discussed this on the teTeX maintainers list yet,
because the new packages simply are not in any shape, they don't even
install. But once they do, once we have categorized and verified our big
bunch of bugs (which would also be good for sarge, contain it 2.0.2 or
3.0), I would suggest to upload the new packages to experimental, and to
encourage packages maintainers of depending packages to work with
them. After that, we can discuss how far sarge is, and what to do next.
So don't panic. We won't throw in tetex-3.0 packages simply because
dpkg-buildpackage; echo $? says "0". But on the other hand, we do our
best to prevent sarge users from having a totally rotten TeX
I don't prepare those packages because I want them to be integrated into
sarge, I make them because I want good tetex-3.0 packages for Debian
users. I will make them also if I know that sarge users will have to use
Frank Küster, Biozentrum der Univ. Basel
Abt. Biophysikalische Chemie