Re: texlive-bin upload
Norbert Preining <preining@logic.at> wrote:
> - Frank's patch to Bug#454324: texlive-base-bin -- Doesn't purge all
> files after piuparts Install+Upgrade+Purge test
> that would need some testing
Yes and no.
No, because I made the changes in the package which takes over the
configuration, texlive-base. So this does *not* affect the upload of
texlive-bin.
Yes, it needs testing. What I want to do (but anyone else can):
- build packages with the patch
- in an etch chroot, install texlive. In 10texlive-base-bin.cnf, copy
one line, call it "mytex" or "mymf" or whatever, and edit the
remaining line (I usually didn't care whether this would give a
functional format definition)
- dist-upgrade to sid, and check
* whether the postinst output is sensible (i.e. no additional info. Or
should we indicate we take over settings?)
* whether the changed/added lines show up in 10texlive-base.cnf
Plus a standard install/remove/install/purge/install test in sid.
I won't have time for this soon (today I go to bed, tomorrow I go to a
barbecue, and on Friday I'll take part in a community run and I fear I
won't be able to touch a computer afterwards...).
> - #458059 texlive-base-bin: max grouping levels exceeded
> from Taco's last email:
> > time (probably a lot of time) finding out the absolute truth, but I
> > agree that a nest_size of 600 appears to make the error unreachable.
>
> In (pdf)tex, that is. Not in Aleph|Omega|Luatex, and I am not sure
> about XeTeX.
> I am not sure what this means, so is it enough to increase this in the
> source code? This is completely untested.
Didn't Taco state that it's a macro error, and all the discussion was
just which of both (max grouping level or max nesting depth) should be
displayed?
> Last question? Do we want triggers/tex-common in lenny?
Hadn't we agreed (I myself by not saying anything, IIRC) to upload the
version with triggers to experimental, announce it, and see later
whether it should be included in lenny?
Regards, Frank
--
Frank Küster
Debian Developer (teTeX/TeXLive)
Reply to: