The reason: [LWN.net]

The reason:

Posted Jun 14, 2012 9:44 UTC (Thu) by NAR (subscriber, #1313)
In reply to: Quotes of the week by drago01
Parent article: Quotes of the week

I've recently installed 64 bit Debian. Then I had to reinstall the 32 bit version, because it turned out that the lgrind package is only packaged for i386: http://packages.debian.org/testing/tex/lgrind

to post comments

The reason:

Posted Jun 14, 2012 10:18 UTC (Thu) by przemoc (guest, #67594) [Link] (3 responses)

This is strange. Quick check (possibly inaccurate) shows that it's not a x86-specific package.

$ cat /etc/debian_version
wheezy/sid
$ uname -m
x86_64
$ apt-get source lgrind
...
$ ( cd lgrind-3.67/ && dpkg-buildpackage -b -us -uc )
...
$ dpkg -I lgrind_3.67-3_amd64.deb
...
Package: lgrind
Version: 3.67-3
Architecture: amd64
...
$ sudo dpkg -i lgrind_3.67-3_amd64.deb
...
$ lgrind
lgrind -- general purpose "pretty printer" for use with LaTeX.
usage: lgrind [options] <name> ...
...

BTW what was the tag for using fixed-size font in HTML comments at LWN.net? <code>, <samp> and <tt> seem unsupported...

The reason:

Posted Jun 14, 2012 12:19 UTC (Thu) by nix (subscriber, #2304) [Link] (1 responses)

You want <pre>, I think.

The reason:

Posted Jun 14, 2012 12:45 UTC (Thu) by przemoc (guest, #67594) [Link]

You're right. I tried <pre> at the beginning, but there is this ridiculous requirement of dealing by hand with & and other stuff in HTML that I went with other tags before carefully reading the note. There is also an old <xmp> tag, treating everything in it as-is, but it's not universally supported.

Having Markdown as a third option for format would be really nice in such cases. The only problem is indentation that is tiring unless you have a vi/xclip+sed/etc. close. The solution is a fenced code blocks (~~~) extension, available in many implementations.

But it's OT here, sorry.

The reason:

Posted Jun 14, 2012 12:25 UTC (Thu) by cortana (subscriber, #24596) [Link]

AFAIK packages in non-free are not auto-built by default. So a lack of an officially-build amd64 instance of this package probably just means that the maintainer didn't go through the steps to request that it by autobuilt.

On the other hand, now that multiarch is present in testing/unstable:

$ dpkg-architecture -qDEB_HOST_ARCH
amd64

# apt-get install lgrind
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Recommended packages:
  tetex-bin:i386
The following NEW packages will be installed:
  lgrind:i386
0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
Need to get 81.8 kB of archives.
After this operation, 250 kB of additional disk space will be used.
Get:1 http://ftp.uk.debian.org/debian/ wheezy/non-free lgrind i386 3.67-3 [81.8 kB]
Fetched 81.8 kB in 0s (303 kB/s)
Selecting previously unselected package lgrind.
(Reading database ... 447986 files and directories currently installed.)
Unpacking lgrind (from .../lgrind_3.67-3_i386.deb) ...
Processing triggers for man-db ...
Processing triggers for doc-base ...
Processing 1 added doc-base file...
Registering documents with scrollkeeper...
Setting up lgrind (3.67-3) ...
texhash: Updating /usr/local/share/texmf/ls-R... 
texhash: Updating /var/lib/texmf/ls-R-TEXLIVEMAIN... 
texhash: Updating /var/lib/texmf/ls-R-TEXLIVEDIST... 
texhash: Updating /var/lib/texmf/ls-R-TEXMFMAIN... 
texhash: Updating /var/lib/texmf/ls-R... 
texhash: Done.
W: Operation was interrupted before it could finish

$ ldd /usr/bin/lgrind
	linux-gate.so.1 =>  (0xf77d4000)
	libc.so.6 => /lib/i386-linux-gnu/i686/cmov/libc.so.6 (0xf764d000)
	/lib/ld-linux.so.2 (0xf77d5000)

Not too impressive since I already had libc6:i386 installed, and lgrind has no other dependencies, but you can see how multiarch nicely makes obsolete the old biarch problems that jschrod lists in a post above.