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: 0x860CDC13fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Bug#673991: hypertex: too much vspace before theorem if previous line full
On Wed, May 23, 2012 at 07:57:44AM +0900, Norbert Preining wrote: > On Di, 22 Mai 2012, Hilmar Preuße wrote: >> You love to open bugs for Debian stable, right? Please note that we >> don't deal with bug severity < RC in Debian stable, i.e. if that >> problem would have been solved in Debian sid we'd have closed that >> bug immediately. > And, in addition, did you read the reportbug message: > *We*are*not*a*TeX*Help*Desk* > Bugs should be concerning the packaging, not concerning bugs within > packages (like interoperabillity etc). Yes, I did. The reportbug message I got (with texlive version 2009-11) was very exactly: begin quote If you report an error when running one of the TeX-related binaries (latex, pdftex, metafont,...), or if the bug is related to bad or wrong output, please include a MINIMAL example input file that produces the error in your report. Please run your example with (pdf)latex -recorder ... (or any other program that supports -recorder) and send us the generated file with the extension .fls, it lists all the files loaded during the run and can easily explain problems induced by outdated files in your home directory. Don't forget to also include minimal examples of other files that are needed, e.g. bibtex databases. Often it also helps to include the logfile. Please, never send included pictures! If your example file isn't short or produces more than one page of output (except when multiple pages are needed to show the problem), you can probably minimize it further. Instructions on how to do that can be found at http://www.latex-einfuehrung.de/mini-en.html (english) or http://www.latex-einfuehrung.de/mini.html (german) --- end quote --- I see that in a *later* version this text was added, but _it was not in the message I got_: --- begin quote --- 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. *** The Debian TeX Team is *not* a LaTeX Help Desk *** --- end quote --- I understand that either your policy changed, or you documented it more clearly, between these two points in time. But I _did_ read the reportbug message in its entirety! 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 upstream, the user not being expected to by able to do that; on the contrary we kinda protected upstream from users (which were not in a very good position to know if the problem was upstream or Debian-specific). It has become popular for maintainers of "big" packages to have another policy, that they won't do that and ask users to speak to upstream directly. I respect that (and I understand the "lack of resources" reasons), but when that policy is not clearly documented (as it was in the version of the TeX Live packages I had at that time) and I'm not knowledgeable enough about the program to make a good bug report upstream, yes, I do fall back on what I understand to be the default policy. In the specific case of (La)TeX I (at the time) found it sometimes highly not obvious how to find the upstream of this or that LaTeX package... If I remember well, maintainership changed hands by announcement on some Usenet newsgroup, so you kinda had to search the archives, ... Maybe hypertex was more clearly maintained, but I must admit that I felt quite overwhelmed by all this (La)TeX galaxy, and that in 2012 I was emptying the "found during my thesis writing" pipeline and was not as available as before to launch into investigations. Also, IMHO it is to be expected to have bug reports about the version in stable, since that's what users not interested in the risk of "how broken is my system today" supposedly run... If the user gets as an answer "bug fixed in unstable", that's rather good news! But IMHO expecting every single user to balance several different VMs or jails or ... is not that user-friendly. While I sympathise with the lack of manpower, in the abstract I wish Debian would be more user-friendly in that way. No, I don't have a solution to give package maintainers the resources to fulfil my wish. Thank you very much Hilmar that you exceptionally took the time to handle my bug report anyway. -- Lionel
Bug#673991: hypertex: too much vspace before theorem if previous line full
forwarded 673991 https://github.com/ho-tex/hyperref/issues/11 tags 673991 fixed-upstream # in version 2016-05-21 6.83p David Carlisle stop On 22.05.12 Hilmar Preuße (hill...@web.de) wrote: Hi all, > Thanks for explanation, forwarded to upstream. > Upstream tracking system has changed, forward address fixed. According to David Carlislie the bug has been fixed in 6.83p (no, I did not check this). A work around has been posted in the upstream tracker. Hilmar -- sigmentation fault signature.asc Description: PGP signature
Bug#673991: hypertex: too much vspace before theorem if previous line full
Just to let you know we have moved the hyperref issues to github I just committed a fix for this to the upstream github sources https://github.com/ho-tex/hyperref/issues/11 will move it to ctan and from there it will get to texlive and you as soon as texlive 2016 updates start again. David The Numerical Algorithms Group Ltd is a company registered in England and Wales with company number 1249803. The registered office is: Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom. This e-mail has been scanned for all viruses by Microsoft Office 365.
Bug#673991: hypertex: too much vspace before theorem if previous line full
retitle 673991 hypertex: too much vspace before theorem if previous line full
thanks
On Tue, May 22, 2012 at 07:15:35PM +0200, Hilmar PreuÃe wrote:
On 22.05.12 Lionel Elie Mamane (lio...@mamane.lu) wrote:
Package: texlive-latex-base
Version: 2009-11
Severity: normal
You love to open bugs for Debian stable, right?
I open bugs for the version where I find the bug.
Please note that (...) if that problem would have been solved in
Debian sid we'd have closed that bug immediately.
Yes, and I'd have been happy of that outcome.
For lighter programs, I can test the sid version, but (La)TeX is so
big with so many interdependencies that I can't switch from stable to
sid and back reasonably easily.
These URLs are 404s, so I minimised as well as I could on my own.
I tried to minimise further and I think I found a more minimalistic
example:
Ah yes, indeed ntheorem is not necessary. Thanks for that.
Either commenting out \usepackage{fullpage} or
\usepackage[dvips]{hyperref} solves the problem.
So it might be in fullpage or hyperref.
No, removing fullpage does not show the problem anymore because the
previous line is not exactly full anymore; the one line becomes two
lines (because of bigger margins) and thus the last line of the
paragraph before the definition is not full. If one also removes/adds
text so that the line is again exactly full, the problem shows up
again. I attach a version without \usepackage{fullpage}.
It seems to be purely a hyperref problem.
--
Lionel
\documentclass[a4paper,12pt]{report}
\usepackage[dvips]{hyperref}
\newtheorem{definition}{Definition}[section]
\begin{document}
\chapter{Too much vspace}
The user interacts with a proof assistant via a proof script
in the folllowing.
\begin{definition}[proof script]
A \emph{proof script} is the sequence of instructions
a user gives a proof assistant to prove a statement.
\end{definition}
The user interacts with a proof assistant via a proof script
in the folllowing
\begin{definition}[proof script]
A \emph{proof script} is the sequence of instructions
a user gives a proof assistant to prove a statement.
\end{definition}
The user interacts with a proof assistant via a proof script
in the folllowing.
\begin{definition}[proof script]
A \emph{proof script} is the sequence of instructions
a user gives a proof assistant to prove a statement.
\end{definition}
The user interacts with a proof assistant via a proof script
in the folllowing
\begin{definition}[proof script]
A \emph{proof script} is the sequence of instructions
a user gives a proof assistant to prove a statement.
\end{definition}
\end{document}
bug.dvi
Description: TeX dvi file
Bug#673991: hypertex: too much vspace before theorem if previous line full
forwarded 673991 https://puszcza.gnu.org.ua/bugs/index.php?165
retitle 673991 hypertex: too much vspace before theorem if previous line full
stop
On 22.05.12 Lionel Elie Mamane (lio...@mamane.lu) wrote:
On Tue, May 22, 2012 at 07:15:35PM +0200, Hilmar PreuÃe wrote:
On 22.05.12 Lionel Elie Mamane (lio...@mamane.lu) wrote:
Hi,
You love to open bugs for Debian stable, right?
I open bugs for the version where I find the bug.
...and we close these busg in case they are solved in sid.
For lighter programs, I can test the sid version, but (La)TeX is so
big with so many interdependencies that I can't switch from stable to
sid and back reasonably easily.
Yes I know. There are VMs, changeroots and other methods to run
unstable systems. No, I won't go into detail.
Either commenting out \usepackage{fullpage} or
\usepackage[dvips]{hyperref} solves the problem.
So it might be in fullpage or hyperref.
No, removing fullpage does not show the problem anymore because the
previous line is not exactly full anymore; the one line becomes two
lines (because of bigger margins) and thus the last line of the
paragraph before the definition is not full. If one also removes/adds
text so that the line is again exactly full, the problem shows up
again. I attach a version without \usepackage{fullpage}.
Thanks for explanation, forwarded to upstream.
H.
--
sigmentation fault
signature.asc
Description: Digital signature
