{"diffoscope-json-version": 1, "source1": "/srv/reproducible-results/rbuild-debian/r-b-build.oI6lveVJ/b1/tcode_0.1.20080918-3_armhf.changes", "source2": "/srv/reproducible-results/rbuild-debian/r-b-build.oI6lveVJ/b2/tcode_0.1.20080918-3_armhf.changes", "unified_diff": null, "details": [{"source1": "Files", "source2": "Files", "unified_diff": "@@ -1,2 +1,2 @@\n \n- df3bc3b9b5bd05b46eb6f89790787103 220196 java optional tcode_0.1.20080918-3_all.deb\n+ e427e49292782901e7987cc491f78d84 220208 java optional tcode_0.1.20080918-3_all.deb\n"}, {"source1": "tcode_0.1.20080918-3_all.deb", "source2": "tcode_0.1.20080918-3_all.deb", "unified_diff": null, "details": [{"source1": "file list", "source2": "file list", "unified_diff": "@@ -1,3 +1,3 @@\n -rw-r--r-- 0 0 0 4 2018-05-03 07:15:38.000000 debian-binary\n -rw-r--r-- 0 0 0 1108 2018-05-03 07:15:38.000000 control.tar.xz\n--rw-r--r-- 0 0 0 218896 2018-05-03 07:15:38.000000 data.tar.xz\n+-rw-r--r-- 0 0 0 218908 2018-05-03 07:15:38.000000 data.tar.xz\n"}, {"source1": "control.tar.xz", "source2": "control.tar.xz", "unified_diff": null, "details": [{"source1": "control.tar", "source2": "control.tar", "unified_diff": null, "details": [{"source1": "./md5sums", "source2": "./md5sums", "unified_diff": null, "details": [{"source1": "./md5sums", "source2": "./md5sums", "comments": ["Files differ"], "unified_diff": null}]}]}]}, {"source1": "data.tar.xz", "source2": "data.tar.xz", "unified_diff": null, "details": [{"source1": "data.tar", "source2": "data.tar", "unified_diff": null, "details": [{"source1": "file list", "source2": "file list", "unified_diff": "@@ -4,15 +4,15 @@\n -rwxr-xr-x 0 root (0) root (0) 250 2018-05-03 07:15:38.000000 ./usr/bin/texjava\n drwxr-xr-x 0 root (0) root (0) 0 2018-05-03 07:15:38.000000 ./usr/share/\n drwxr-xr-x 0 root (0) root (0) 0 2018-05-03 07:15:38.000000 ./usr/share/doc/\n drwxr-xr-x 0 root (0) root (0) 0 2018-05-03 07:15:38.000000 ./usr/share/doc/tcode/\n -rw-r--r-- 0 root (0) root (0) 3514 2008-09-16 16:18:54.000000 ./usr/share/doc/tcode/README\n -rw-r--r-- 0 root (0) root (0) 508 2018-05-03 07:15:38.000000 ./usr/share/doc/tcode/changelog.Debian.gz\n -rw-r--r-- 0 root (0) root (0) 1353 2018-05-03 07:15:38.000000 ./usr/share/doc/tcode/copyright\n--rw-r--r-- 0 root (0) root (0) 190224 2018-05-03 07:15:38.000000 ./usr/share/doc/tcode/tcode.pdf.gz\n+-rw-r--r-- 0 root (0) root (0) 190247 2018-05-03 07:15:38.000000 ./usr/share/doc/tcode/tcode.pdf.gz\n drwxr-xr-x 0 root (0) root (0) 0 2018-05-03 07:15:38.000000 ./usr/share/doc-base/\n -rw-r--r-- 0 root (0) root (0) 575 2018-05-03 07:15:38.000000 ./usr/share/doc-base/tcode\n drwxr-xr-x 0 root (0) root (0) 0 2018-05-03 07:15:38.000000 ./usr/share/man/\n drwxr-xr-x 0 root (0) root (0) 0 2018-05-03 07:15:38.000000 ./usr/share/man/man1/\n -rw-r--r-- 0 root (0) root (0) 462 2018-05-03 07:15:38.000000 ./usr/share/man/man1/texjava.1.gz\n drwxr-xr-x 0 root (0) root (0) 0 2018-05-03 07:15:38.000000 ./usr/share/tcode/\n -rw-r--r-- 0 root (0) root (0) 8185 2008-09-16 15:38:04.000000 ./usr/share/tcode/lmac.sty\n"}, {"source1": "./usr/share/doc/tcode/tcode.pdf.gz", "source2": "./usr/share/doc/tcode/tcode.pdf.gz", "unified_diff": null, "details": [{"source1": "tcode.pdf", "source2": "tcode.pdf", "unified_diff": null, "details": [{"source1": "pdftotext {} -", "source2": "pdftotext {} -", "unified_diff": "@@ -1,26 +1,26 @@\n TCode\n User Guide\n Tools for documenting Java programs in LATEX\n-Version: January 6, 2024\n+Version: January 7, 2024\n \n This document describes facilities that help writing Java classes, together with detailed\n documentation of their application programming interface (API), in a single LATEX file. The\n LATEX package tcode offers special commands and environments for typesetting API documentation and user guides. It permits one to display certain parts of the code (e.g., method\n headers), hide others (e.g., method bodies and private variables), and explain the methods,\n variables, etc., in a uniform format. Although it is targeted to that language, it works not\n only for Java, but also for other programming languages such as C, C++, etc. LATEX will\n produce the documentation as a .dvi, .ps, or .pdf file.\n A Perl script called texjava produces a .java file by extracting the code form the .tex\n file. With the help of LATEX2HTML, texjava also transforms some of the documentation into\n Javadoc format, so that the javadoc program can later produce HTML documentation from\n the .java file. Another Perl script called javatex does the reverse transformation, recovering\n the .tex file from the .java file.\n \n-\fJanuary 6, 2024\n+\fJanuary 7, 2024\n \n 1\n \n 1 INTRODUCTION 1\n \n Introduction\n \n@@ -64,15 +64,15 @@\n script can process only one .tex file at a time, one may create a Makefile to automate the\n generation process when dealing with many files.\n The tcode package. To use the commands of the tcode LATEX package, this one must be\n imported via the command\n \\usepackage{tcode}\n This command will locate and load tcode.sty, so this file must be accessible in a directory\n \n-\fJanuary 6, 2024\n+\fJanuary 7, 2024\n \n 2 LAYOUT OF THE LATEX FILES 2\n \n pointed to by the TEXINPUTS environment variable. The tcode package requires the html\n and alltt packages which should also be locatable through the TEXINPUTS environment\n variable.\n The code environment. The basic construct for identifying programming code in the\n@@ -107,15 +107,15 @@\n them from the documentation, while part of the code of each method may already be in a\n hide environment (inside the code environment). In this case, the outer hide environment\n must begin and end outside any code environment.\n The hide environment has no effect on the code extracted by texjava in the sense that\n all hidden code goes to the .java file anyway. However, the hidden documentation will not\n appear in the HTML conversion produced by Javadoc.\n \n-\fJanuary 6, 2024\n+\fJanuary 7, 2024\n \n 2 LAYOUT OF THE LATEX FILES 3\n \n No hiding. In case one wishes a documentation that contains all the code, including the\n method implementations and other private material, one can simply turn OFF the hiding\n mechanism of the hide environment with the command \\hidefalse. It can be turned ON\n again with the command \\hidetrue. However, turning the hide mechanism OFF will get\n@@ -153,15 +153,15 @@\n documentation block, i.e., should not contain a code environment. Departure from that\n rule could prevent LATEX2HTML from writing the markers separating the blocks (i.e., the\n fields and methods), and empty documentation blocks could then appear for subsequent\n fields and methods. The script calls LATEX2HTML only once for the LATEX file given to it, so\n any modification of the LATEX parameters in one text block could have an impact on the\n subsequent blocks.\n \n-\fJanuary 6, 2024\n+\fJanuary 7, 2024\n \n 2 LAYOUT OF THE LATEX FILES 4\n \n LATEX-only and HTML-only parts. Certain parts of the .tex files can be intended only\n for LATEX, others only for the HTML file. This can be specified by the usual commands and\n environments available in the html package (e.g., the latexonly, htmlonly, and rawhtml\n environments).\n@@ -200,15 +200,15 @@\n Indenting documentation. The environments tab, tabb, and tabbb have been defined\n to indent the documentation and put it in a smaller font. These environments are normally\n used to describe fields and methods, they are ignored by LATEX2HTML, and produce the\n following results:\n This is a text indented with tab.\n This text is more indented because it is in a tabb environment.\n \n-\fJanuary 6, 2024\n+\fJanuary 7, 2024\n \n 2 LAYOUT OF THE LATEX FILES 5\n \n This text is still more indented because it is in a tabbb environment.\n \n Doc-comment tags for javadoc. The following LATEX commands are mapped by texjava\n to the corresponding javadoc doc-comment tags which are used to encode specific information\n@@ -256,15 +256,15 @@\n case, the signature argument will be empty.\n Examples: \\method{density}{} and \\method{density}{double} will generate the density\n label whereas \\method{density(double)}{} will generate density(double).\n \n \\externalmethod{package}{class-name}{method-name}{signature}\n Indicates the name of a method in another class. This is formatted in typed text in the LATEX\n \n-\fJanuary 6, 2024\n+\fJanuary 7, 2024\n \n 2 LAYOUT OF THE LATEX FILES 6\n \n document, and converted to an hyperlink in HTML. The package name, class name and the\n signature will not appear in the label name.\n Example: \\externalmethod{umontreal.iro.lecuyer.gof}{GofStat}{andersonDarling}{}\n will typeset andersonDarling\n@@ -301,15 +301,15 @@\n \\begin{code}\n public Complex add (Complex c)\\begin{hide} {\n realPart += c.realPart;\n imagPart += c.realPart;\n return this;\n }\\end{hide}\n \n-\fJanuary 6, 2024\n+\fJanuary 7, 2024\n \n 3 RUNNING TEXJAVA 7\n \n \\end{code}\n \\begin{tabb} Adds two complex numbers.\n \\param{c}{The complex number to add to this one.}\n \\return{This object, allowing to perform more than one operation\n@@ -351,15 +351,15 @@\n Here, texjava.pl has to be replaced by a path to the script if it is not executed in the\n tcode directory. Its arguments and options are as follows:\n infile\n The name of the input file, which should have the .tex extension. If the extension is not given\n and no file with such a name exists, .tex is appended to the file name. The input file is parsed\n but not modified.\n \n-\fJanuary 6, 2024\n+\fJanuary 7, 2024\n \n 3 RUNNING TEXJAVA 8\n \n outfile\n The name of the output file. Normally, it should be a program file, e.g., with the .java\n extension. If no extension is specified, .java is assumed. When using the HTML option, .html\n is used. If no output file is given, the name of the input file is taken, with a .java or .html\n@@ -410,15 +410,15 @@\n \n -htmlonly\n Indicates that the script only has to convert a LATEX document to HTML, not processing Java\n code blocks. This option is useful to convert overviews into package.html files. It is simpler\n and better than calling LATEX2HTML directly because texjava.pl passes a bunch of options\n to LATEX2HTML and transforms the .tex and .html contents to avoid some images from math\n \n-\fJanuary 6, 2024\n+\fJanuary 7, 2024\n \n 3 RUNNING TEXJAVA 9\n \n formulas.\n \n -htmltitle title\n When using HTML-only mode, allows to give a title to the generated HTML file. This title will\n@@ -454,15 +454,15 @@\n \n \\begin{hide}{\n LATEX will treat the rest of the file as an argument to the hide environment and an\n error will occur.\n \u0088 The method bodies should always be hidden, otherwise, the insertion point of the\n documentation may be incorrectly computed.\n \n-\fJanuary 6, 2024\n+\fJanuary 7, 2024\n \n 4 THE JAVATEX SCRIPT 10\n \n \u0088 The first sentence of a doc comment is used by javadoc as a brief (a one-sentence\n summary) of the corresponding class, interface, field, or method. The first sentence\n of a LATEX documentation block which is to be converted to a doc comment should\n therefore be short and simple. It should not contain special commands, mathematical\n@@ -502,15 +502,15 @@\n source files may have been produced by texjava, but not necessarily. For example, one may\n want to use a special editor for Java programs to edit the Java file and encode the LATEX\n documentation in it by hand, in the same format as it would have been saved by texjava.\n The Java source file intended for conversion should normally contain Java doc comments,\n of the form /** comments */, where comments can be any (multi-line) text. The contents of\n these comments is converted into LATEX documentation blocks for classes, interfaces, fields,\n \n-\fJanuary 6, 2024\n+\fJanuary 7, 2024\n \n 5 RUNNING JAVATEX 11\n \n and methods. Other types of comments in the code are simply ignored and preserved intact\n into code blocks.\n The contents of HTML commented blocks of the form will be inserted directly into the LATEX document. This construct allows hiding LATEX code inside Java\n doc comments. Note that a doc comment should never begin with such an HTML comment,\n@@ -551,15 +551,15 @@\n not modified.\n \n outfile\n The name of the output file, which should have the .tex extension. If outfile already exists, it\n will be replaced without notice, otherwise the file will be created in the working directory. If\n infile and outfile are the same, an error will occur.\n \n-\fJanuary 6, 2024\n+\fJanuary 7, 2024\n \n 6 ANT TASKS 12\n \n -tabsize i\n By using the -tabsize i option, where i is a non-negative integer, one can specify the number\n of spaces that corresponds to a tab character. The default value is 8.\n \n@@ -584,15 +584,15 @@\n one must include tcode.jar in the CLASSPATH environment variable and declare the use\n tasks in the build.xml file, using the taskdef task. For example, to use texjava task, one\n must write, in the project section of build.xml,\n \n \n \f13\n \n-January 6, 2024\n+January 7, 2024\n \n Texjava\n This Ant task invokes texjava.pl to extract Java code from LATEX files. Given a list of\n files, it can invoke texjava.pl once for each, creating Java file that can be processed with\n Ant. The Texjava task checks for depencies, avoiding to run texjava.pl for .tex files\n with a more recent .java file. It acts like a proxy to texjava.pl so all of its options are\n supported by the task through attributes. It is possible to set default values for most of\n@@ -627,15 +627,15 @@\n \n overviewtopackage\n Normally, any .tex file is mapped to a corresponding .java for dependency checking and\n conversion. If htmlonly is true, .tex files will be mapped to .html files. This attribute, if\n set to true, will define a mapping from overview.tex to package.html. This allows one to\n generate package overviews without converting them every time.\n \n-\fJanuary 6, 2024\n+\fJanuary 7, 2024\n \n Texjava 14\n \n Nested elements Two nested elements are supported: file sets and file lists. These elements allows one to construct the list of .tex files to be converted to .java files.\n texfileset\n Corresponds to an Ant FileSet element which should only contain .tex files. A set can include\n files matching patterns.\n@@ -675,15 +675,15 @@\n \n public void setImages (boolean images)\n If set to true, LATEX2HTML will generate images when converting the documentation.\n \n public boolean getSavelatex()\n Returns true if the LATEX contents is saved to allow reverting to LATEX using javatex.\n \n-\fJanuary 6, 2024\n+\fJanuary 7, 2024\n \n Texjava 15\n \n public void setSavelatex (boolean savelatex)\n If set to true the LATEX contents will be saved in the produced Java file.\n \n public boolean getHtmlonly()\n@@ -731,15 +731,15 @@\n \n public void execute() throws BuildException\n Executes the conversion task, using the Ant exec task to invoke texjava.pl on each .tex\n file.\n \n \f16\n \n-January 6, 2024\n+January 7, 2024\n \n PdfLatex\n This task allows one to automate the PDF documentation generation. It uses pdfLATEX to\n convert the LATEX documentation into PDF. To avoid errors when using the LATEX hyperref\n package, all .aux files are first deleted. The pdfLATEX program is then called one time to\n make an initial run. BIBTEX is called to generate to bibliography file, then pdfLATEX is\n called two more times to fix references and table of contents. It always runs pdfLATEX in\n@@ -762,15 +762,15 @@\n \n public void setLatexfile (File latexFile)\n Sets the name of the LATEX file to be processed.\n \n public void execute() throws BuildException\n Executes the task.\n \n-\fJanuary 6, 2024\n+\fJanuary 7, 2024\n \n REFERENCES 17\n \n References\n [1] ActiveState. ASPN: Reference\u2014ActivePerl Docs, 2003. Available online at http://\n aspn.activestate.com/ASPN/Reference/Products/ASPNTOC-ACTIVEPERL.\n [2] D. Flanagan. Java in a Nutshell. O\u2019Reilly, Sebastopol, CA, third edition, 1999.\n"}]}]}]}]}]}]}