[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#673991: hypertex: too much vspace before theorem if previous line full



Hi Lionel,

just one short message from the one (me) who rewrote the policy
(i.e. reportbug message):

***** reportbug message
> IMPORTANT INFORMATION: We will only consider bug reports concerning
> the packaging of TeX Live as relevant. If you have problems with
> combination of packages in a LaTeX document, please consult your
> local TeX User Group, the comp.text.tex user group, the author of
> the original .sty file, or any other help resource.
> 
> In particular, bugs that are related to up-upstream, i.e., neither
> Debian nor TeX Live (upstream), but the original package authors,
> will be closed immediately.
*********************

> When I entered Debian, it was very much the general policy that users
> should report the bug to the Debian BTS, and the maintainer would
> separate upstream issues from Debian-specific issues and interact with

That is fine, and the above does not exclude this.
What it *DOES* exclude are bugs in *packages*. The reason is that,
if I as Debian packager report this to TeX Live, I will get the answer
	We just take what is on CTAN, please contact the author
	of the package.
Now, with about several thousands of upstream authors, I honestly
assume that this is the only package in Debian with a similar setup,
and I consider it impossible for me to look up the upstream author,
track down wrong emails, and contact him for every bug reported in
Debian.

Now for the reason why I *close* these bugs:
I simply want to keep the BTS *usable*. If there are hundreds and
hundreds of bugs I will *never* treat and will never look into,
unless Debian or someone pays me a full salary for that, I prefer
to have them closed and away so that I can concentrate on those
which are actually packaging bugs.

Concerning stable vs unstable: Of course one is free to report
bugs against stable, but you should be aware that:
* someone has to do the work and check whether this is still the
  case in unstable
* and if that is a package bug (not packag*ing* bug), my motivation 
  to trace these things down is minimal


Hope that helps to understand the situation

Norbert

--
PREINING Norbert + TeX Live & Debian Developer + http://www.preining.info
GPG: 0x860CDC13    fp: F7D8 A928 26E3 16A1 9FA0  ACF0 6CAC A448 860C DC13


Reply to: