Bug#761627: libtomcrypt-dev: arch-dependent file in "Multi-Arch: same" package

[François Poirotte]

Hi Michael,

I just noticed that this issue is not present anymore in Debian Buster 
(libtomcrypt-dev 1.18.1-1).
Judging from the git history upstream, it seems to have been fixed by 
your patch:

https://github.com/libtom/libtomcrypt/commit/4ab63ccd3a6ed5e11fa616fafc9915ef694e8775#diff-cd5dbf3629c558b0104ba8f0937d6816

So I think this bug can now be closed.

Best regards,
François

On Sat, 22 Jul 2017 22:40:26 +0200 Michael Stapelberg 
 wrote:

> Thanks for the ping.
>
> I applied your patch and tried to build the package, but it fails to 
build

> (build log attached).
>
> I’m not sure if that is because of your patch or an unrelated issue, 
but I

> don’t have the time to debug LaTeX issues right now. Any help welcome.
>
> On Wed, Jul 19, 2017 at 11:46 AM, François Poirotte 
> wrote:
>

Bug#761627: libtomcrypt-dev: arch-dependent file in "Multi-Arch: same" package

[Michael Stapelberg]

Thanks for the ping.

I applied your patch and tried to build the package, but it fails to build
(build log attached).

I’m not sure if that is because of your patch or an unrelated issue, but I
don’t have the time to debug LaTeX issues right now. Any help welcome.

On Wed, Jul 19, 2017 at 11:46 AM, François Poirotte 
wrote:

> Hi Michael,
>
> I believe the freeze has been lifted following the release of Debian
> Stretch a few weeks ago.
> Could you take another look at the proposed patch?
>
> Best regards,
> François
>
> On 05/14/2017 11:02 PM, Michael Stapelberg wrote:
>
> Thanks for investigating this issue and providing the updated patch. As
> Debian is currently in a freeze, I can’t upload the patch right now. Could
> you ping this email thread/bug report once Debian left the freeze please?
> Thank you.
>
> On Sun, May 14, 2017 at 5:49 PM, François Poirotte 
> wrote:
>
>> Hi,
>>
>> It seems the patch "deterministic-latex.patch" is not working as it
>> should.
>> I guess it may have to do with the way it uses escape sequences (in my
>> case, "\\fixedpdfdate" is actually replaced by a form feed character
>> followed by "ixedpdfdate" in the final .tex file).
>>
>> Attached is an updated version of the patch that fixes the issue for me.
>> It uses "printf" instead of "echo" to avoid possible issues with the
>> interpretation of escape sequences.
>> It blanks the "ModDate" & "CreationDate" fields instead of trying to be
>> smart about them.
>> It also removes pdfLaTeX's banner & trailer ID from the final output
>> (which may also fix the issue you reported about different versions of the
>> build-dependencies resulting in different output files).
>>
>> Best regards,
>> François
>>
>
> --
> Best regards,
> Michael
>
>
>


-- 
Best regards,
Michael


libtomcrypt_1.17-10_amd64-2017-07-22T20:37:35Z.build
Description: Binary data

Bug#761627: libtomcrypt-dev: arch-dependent file in "Multi-Arch: same" package

[François Poirotte]

Hi Michael,

I believe the freeze has been lifted following the release of Debian 
Stretch a few weeks ago.

Could you take another look at the proposed patch?

Best regards,
François


On 05/14/2017 11:02 PM, Michael Stapelberg wrote:
Thanks for investigating this issue and providing the updated patch. 
As Debian is currently in a freeze, I can’t upload the patch right 
now. Could you ping this email thread/bug report once Debian left the 
freeze please? Thank you.


On Sun, May 14, 2017 at 5:49 PM, François Poirotte 
> wrote:


Hi,

It seems the patch "deterministic-latex.patch" is not working as
it should.
I guess it may have to do with the way it uses escape sequences
(in my case, "\\fixedpdfdate" is actually replaced by a form feed
character followed by "ixedpdfdate" in the final .tex file).

Attached is an updated version of the patch that fixes the issue
for me.
It uses "printf" instead of "echo" to avoid possible issues with
the interpretation of escape sequences.
It blanks the "ModDate" & "CreationDate" fields instead of trying
to be smart about them.
It also removes pdfLaTeX's banner & trailer ID from the final
output (which may also fix the issue you reported about different
versions of the build-dependencies resulting in different output
files).

Best regards,
François


--
Best regards,
Michael

Bug#761627: libtomcrypt-dev: arch-dependent file in "Multi-Arch: same" package

[Michael Stapelberg]

Thanks for investigating this issue and providing the updated patch. As
Debian is currently in a freeze, I can’t upload the patch right now. Could
you ping this email thread/bug report once Debian left the freeze please?
Thank you.

On Sun, May 14, 2017 at 5:49 PM, François Poirotte 
wrote:

> Hi,
>
> It seems the patch "deterministic-latex.patch" is not working as it should.
> I guess it may have to do with the way it uses escape sequences (in my
> case, "\\fixedpdfdate" is actually replaced by a form feed character
> followed by "ixedpdfdate" in the final .tex file).
>
> Attached is an updated version of the patch that fixes the issue for me.
> It uses "printf" instead of "echo" to avoid possible issues with the
> interpretation of escape sequences.
> It blanks the "ModDate" & "CreationDate" fields instead of trying to be
> smart about them.
> It also removes pdfLaTeX's banner & trailer ID from the final output
> (which may also fix the issue you reported about different versions of the
> build-dependencies resulting in different output files).
>
> Best regards,
> François
>



-- 
Best regards,
Michael

Bug#761627: libtomcrypt-dev: arch-dependent file in "Multi-Arch: same" package

[François Poirotte]

Hi,

It seems the patch "deterministic-latex.patch" is not working as it should.
I guess it may have to do with the way it uses escape sequences (in my 
case, "\\fixedpdfdate" is actually replaced by a form feed character 
followed by "ixedpdfdate" in the final .tex file).


Attached is an updated version of the patch that fixes the issue for me.
It uses "printf" instead of "echo" to avoid possible issues with the 
interpretation of escape sequences.
It blanks the "ModDate" & "CreationDate" fields instead of trying to be 
smart about them.
It also removes pdfLaTeX's banner & trailer ID from the final output 
(which may also fix the issue you reported about different versions of 
the build-dependencies resulting in different output files).


Best regards,
François
Description: Deterministically build crypt.pdf for multi-arch
Author: Michael Stapelberg 
Forwarded: https://github.com/libtom/libtomcrypt/pull/33
Bug-Debian: http://bugs.debian.org/734109
Last-Updated: 2014-01-04

---

Index: libtomcrypt/makefile
===
--- libtomcrypt.orig/makefile	2014-01-04 16:26:09.001353782 +0100
+++ libtomcrypt/makefile	2014-01-04 16:26:57.328828492 +0100
@@ -355,14 +355,23 @@
 #delete it if we are rebuilding it.
 docs: crypt.tex
 	rm -f doc/crypt.pdf $(LEFTOVERS)
+	cp crypt.tex crypt.bak
+	touch --reference=crypt.tex crypt.bak
+	printf "pdfinfo{ /ModDate () /CreationDate () }\\n" >> crypt-deterministic.tex
+	printf "pdftrailerid{}\\n" >> crypt-deterministic.tex
+	printf "pdfsuppressptexinfo15\\n" >> crypt-deterministic.tex
+	cat crypt.tex >> crypt-deterministic.tex
+	mv crypt-deterministic.tex crypt.tex
+	touch --reference=crypt.bak crypt.tex
 	echo "hello" > crypt.ind
 	latex crypt
 	latex crypt
 	makeindex crypt.idx
 	perl fixupind.pl
-	latex crypt
-	dvipdf crypt
+	pdflatex crypt
+	sed -i 's,^/ID \[.*\]$$,/ID [<0> <0>],g' crypt.pdf
 	mv -ivf crypt.pdf doc/crypt.pdf
+	mv crypt.bak crypt.tex
 	rm -f $(LEFTOVERS)
 
 docdvi: crypt.tex

Bug#761627: libtomcrypt-dev: arch-dependent file in Multi-Arch: same package

[Jakub Wilk]

* Michael Stapelberg stapelb...@debian.org, 2014-09-29, 19:49:
libtomcrypt-dev is marked as Multi-Arch: same, but the following 
file is architecture-dependent:


/usr/share/doc/libtomcrypt-dev/crypt.pdf.gz

MD5 sums of the file are:

6499c811b72bd3e21dcbd5bcd7f7c934 on arm64 and ppc64el;
150c0017b77e05d325dda105716569ad elsewhere.
The difference is not caused by the architecture, but by the version of 
Build-Dependencies with which the file was compiled — on arm64 and 
ppc64el it was built last month, presumably because those are new 
architectures, and it was built using TeXLive 2014. On the other 
(older) architectures, the package was built 270 days ago, with TeXLive 
2013.


I don’t think Debian offers a way to have reproducible builds under 
these circumstances, i.e. I cannot expect all builds of my package to 
have _exactly_ the same Build-Dependencies available.


Hence, I’m inclined to close this bug report without actually doing 
anything. Do you agree or is there something that we can do to avoid 
getting into this situation in the future?


What you could do is to move the PDF to separate -doc package. That 
would reduce size of the -dev package from 1M to 340K. (Admittedly 1M is 
not THAT big, so maybe it'd be overkill.)


For now, I’ll upload 1.17-6 soon, and then the file will be the same on 
all architectures again.


Unfortunately, this upload didn't fix the problem for some reason. Now 
the MD5 sums are:


6499c811b72bd3e21dcbd5bcd7f7c934 on arm64, mips;
10e5c01c6c99ea4e45f7b480b232727d elsewhere.

--
Jakub Wilk


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#761627: libtomcrypt-dev: arch-dependent file in Multi-Arch: same package

[Michael Stapelberg]

Hey Jakub,

On Mon, Sep 15, 2014 at 9:54 AM, Jakub Wilk jw...@debian.org wrote:
 Package: libtomcrypt-dev
 Version: 1.17-5
 User: multiarch-de...@lists.alioth.debian.org
 Usertags: multiarch

 libtomcrypt-dev is marked as Multi-Arch: same, but the following file is
 architecture-dependent:

 /usr/share/doc/libtomcrypt-dev/crypt.pdf.gz

 MD5 sums of the file are:

 6499c811b72bd3e21dcbd5bcd7f7c934 on arm64 and ppc64el;
 150c0017b77e05d325dda105716569ad elsewhere.
The difference is not caused by the architecture, but by the version
of Build-Dependencies with which the file was compiled — on arm64 and
ppc64el it was built last month, presumably because those are new
architectures, and it was built using TeXLive 2014. On the other
(older) architectures, the package was built 270 days ago, with
TeXLive 2013.

I don’t think Debian offers a way to have reproducible builds under
these circumstances, i.e. I cannot expect all builds of my package to
have _exactly_ the same Build-Dependencies available.

Hence, I’m inclined to close this bug report without actually doing
anything. Do you agree or is there something that we can do to avoid
getting into this situation in the future? For now, I’ll upload 1.17-6
soon, and then the file will be the same on all architectures again.

-- 
Best regards,
Michael


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#761627: libtomcrypt-dev: arch-dependent file in Multi-Arch: same package

[Jakub Wilk]

Package: libtomcrypt-dev
Version: 1.17-5
User: multiarch-de...@lists.alioth.debian.org
Usertags: multiarch

libtomcrypt-dev is marked as Multi-Arch: same, but the following file 
is architecture-dependent:


/usr/share/doc/libtomcrypt-dev/crypt.pdf.gz

MD5 sums of the file are:

6499c811b72bd3e21dcbd5bcd7f7c934 on arm64 and ppc64el;
150c0017b77e05d325dda105716569ad elsewhere.

--
Jakub Wilk


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org