unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Federico Beffa <beffa@ieee.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: failing packages
Date: Sat, 17 Oct 2015 18:21:24 +0200	[thread overview]
Message-ID: <20151017162124.GA8484@debian> (raw)
In-Reply-To: <CAKrPhPNu+Q5gUr1JCwAtabF42J=jFAXW7pQ_80xy=NqfMGbFAQ@mail.gmail.com>

On Sat, Oct 17, 2015 at 01:14:22PM +0200, Federico Beffa wrote:
> Yes, the software dates 1992 and works great. Electromagnetism has not
> changed since then.

Well, maybe the physics have not, but compilers and language standards have;
it is rare to see very old code compiling without problems today.
(Pure and proper C code usually does, but this is no contradiction to my
previous sentence.)

> Why would you want to drop it?

As long as there is interest in the package, and someone with interest
volunteers to fix it, then I do not want to drop anything!

On Sat, Oct 17, 2015 at 05:20:07PM +0200, Federico Beffa wrote:
> The problem appears to be with TeXLive 2015 and its 'dvips' command
> being unable to handle some .ps files:
> https://www.tug.org/pipermail/tex-live/2015-June/037013.html

This looks really nasty - so the bitrot problem does not concern the code,
but its documentation! It appears that there is some non-free tex file
that was only discovered as such recently and consequently taken out from
texlive.

Actually, such a non-free file is distrubuted with the fastcap source:
   doc/psfig sty
has the following license:
% Permission is granted for use and non-profit distribution of psfig/tex
% providing that this notice be clearly maintained, but the right to
% distribute any portion of psfig/tex for profit or as part of any commercial
% product is specifically reserved for the author.

The offending macro "startTexFig" is used there, and it was probably defined
in some other non-free file of the psfig universe that was removed from
texlive.

So clearly we need to remove psfig.sty from the tarball, and then all
inclusions of ps figures of the form
   ug-run.tex:\psfig{figure=\figuredir/cubes.eps}
from the .tex files. Potentially replacing "\psfig" by "\includegraphics"
is enough, more likely, some other parameters will have to be adapted as well.

There is one more dubious file in the doc directory: ieee.sty, which comes
without any license. There is a latex class ieetran on CTAN:
   http://www.ctan.org/pkg/ieeetran
and another one ieeeconf.

Do you have some (la-)tex experience and could have a look?
Unfortunately the software does not seem to be in debian, from where we
might have taken a patch.

Andreas

  parent reply	other threads:[~2015-10-17 16:21 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-17 11:14 failing packages Federico Beffa
2015-10-17 15:20 ` Federico Beffa
2015-10-17 16:18   ` Federico Beffa
2015-10-17 16:21 ` Andreas Enge [this message]
2015-10-17 16:33   ` Andreas Enge
2015-10-17 16:45     ` Federico Beffa
2015-10-17 16:53       ` Andreas Enge
2015-10-17 17:55         ` Federico Beffa
  -- strict thread matches above, loose matches on Subject: below --
2015-10-06  9:48 Efraim Flashner
2015-10-06 11:38 ` Ludovic Courtès
2015-10-06 11:47   ` Pjotr Prins
2015-10-06 12:25 ` Ricardo Wurmus
2015-10-06 12:56   ` Andreas Enge
2015-10-06 15:30   ` Alex Kost
2015-10-06 16:47     ` Ludovic Courtès
     [not found] ` <5613B60C.6050901@uq.edu.au>
2015-10-14 10:41   ` Ben Woodcroft
2015-10-14 13:29     ` Andreas Enge
2015-10-14 13:37       ` Ben Woodcroft
2015-10-14 17:03         ` Efraim Flashner
2015-10-16 20:11 ` Andreas Enge
2015-10-16 21:02   ` Andreas Enge
2015-10-17  8:11     ` Ricardo Wurmus
2015-10-17 16:24       ` Andreas Enge
2015-10-17 10:52     ` Pjotr Prins
2015-10-17 19:56       ` Andreas Enge
2015-10-17 20:04         ` Ricardo Wurmus
2015-10-17 20:34           ` Andreas Enge
2015-10-18  5:32             ` Ricardo Wurmus
2015-10-17 20:37           ` Andreas Enge
2015-10-17 21:01           ` Andreas Enge
2015-10-17 20:40         ` Efraim Flashner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151017162124.GA8484@debian \
    --to=andreas@enge.fr \
    --cc=beffa@ieee.org \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).