Mike Bird [EMAIL PROTECTED] wrote:
A lot of packages need a working Tetex/Texlive. If I decide to use
such a package a year from now, I'd rather have the possibility of using
Texlive and the hope that most of the dependencies are correct rather
than being forced to use an unsupported and
Steve Langasek [EMAIL PROTECTED] wrote:
Would it be possible to get a carte blanche for an etch-ignore tag for
any RC bug that
[...]
No, I certainly don't think such bugs would warrant an etch-ignore tag,
especially seeing how they would be new bugs *introduced* after the start of
the
On Thursday 14 December 2006 22:18, Steve Langasek wrote:
On Tue, Dec 12, 2006 at 08:38:42AM +0100, Frank Küster wrote:
Would it be possible to get a carte blanche for an etch-ignore tag for
any RC bug that
- has been introduced by adding alternative dependencies on texlive
- on a
On Tue, Dec 12, 2006 at 08:38:42AM +0100, Frank Küster wrote:
I would like to start a mass bug filing (not yet discussed on -devel,
severity non-RC) on packages that depend on teTeX without an alternative
TeXlive dependency. This is mainly targetted at lenny, but I would also
like to
Am Dienstag, 12. Dezember 2006 21:10 schrieb Frank Küster:
This would overload the buildd's and their ftp mirrors, because the
small texlive metapackage does not cover the complete teTeX, whereas
texlive-full pulls in really everything, about 2 Gigabyte of files. And
it doesn't make sense to
Hi all!
My few cents.
On Die, 12 Dez 2006, Frank Küster wrote:
[rumors that texlive does not provide identical functionality compared
to teTeX]
I've never heard someone claim that. There are some packages missing in
texlive that were already obsolete when sarge's tetex was released, but
Norbert Preining [EMAIL PROTECTED] wrote:
[ the bug reports we submitted so far do not specify exact dependencies
to use ]
Indeed, since this requires knowledge about the internals of the package
that needs more than a cursory look at the sources. The splitting of
Well. If the
Hi,
I've been asked in private mail why we want to do this mass bug filing
at all. I paste here the relevant parts of my answer:
[why not wait until after etch]
We won't push that hard before etch is released, but it doesn't hurt to
fix those bugs now if a package gets an upload for etch,
8 matches
Mail list logo
