From: Federico Beffa <beffa@ieee.org>
To: Andreas Enge <andreas@enge.fr>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: failing packages
Date: Sat, 17 Oct 2015 18:18:36 +0200 [thread overview]
Message-ID: <CAKrPhPN86zsa_mOtJKRsjyCrGspsNY892Af=3DiqxixY44LbHg@mail.gmail.com> (raw)
In-Reply-To: <CAKrPhPMhEJ3d-vc1ygJOZZibnCOZfVmaUDh4G5jPQCia8Dsorw@mail.gmail.com>
Looking further: A macro was removed from TeXLive 2015 because of a
license problem.
I've pushed a fix to generate the fastcap documentation using a different macro.
Regards,
Fede
On Sat, Oct 17, 2015 at 5:20 PM, Federico Beffa <beffa@ieee.org> 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
>
> Could you please look into this?
>
> Thanks,
> Fede
>
> On Sat, Oct 17, 2015 at 1:14 PM, Federico Beffa <beffa@ieee.org> wrote:
>> Andreas Enge <andreas@enge.fr> writes:
>>
>>> On Tue, Oct 06, 2015 at 12:48:12PM +0300, Efraim Flashner wrote:
>>>> chicken:
>>>> guix refresh -l chicken: no dependant packages.
>>>> Has not built successfully since early May.
>>>> x86_64: http://hydra.gnu.org/build/701776/nixlog/1 (~1900 lines) runtime tests
>>>> timed out
>>>> armhf: http://hydra.gnu.org/build/701673/nixlog/1 (~4300 lines) tests pass
>>>> (including runtime tests) until ports test
>>>> Error: (line 294) invalid escape-sequence '\x o' => Embedded NUL bytes in
>>>> filenames are rejected.
>>>> mips64el: http://hydra.gnu.org/build/699177/nixlog/1 same as arm
>>>> i686: http://hydra.gnu.org/build/698575/nixlog/1 same as x86_64
>>>
>>> Should we simply drop this? Or would someone like to try an update to the
>>> most recent version 4.10.0?
>>>
>>>> fastcap:
>>>> fails on all hardware targets.
>>>> has not built successfully since August 1st.
>>>
>>> Does the software really date from 1992 as the filename suggests?!
>>> Here only the documentation does not build; maybe the fix-doc phase should
>>> be modified? Is anybody interested in the package, or should we drop it?
>>
>> Yes, the software dates 1992 and works great. Electromagnetism has not
>> changed since then.
>>
>> Why would you want to drop it? The documentation was broken by the
>> last texlive update, it didn't break by itself. It's just a matter to
>> fix some LaTeX macro.
>>
>> Dropping the documentation is a bad idea, because without it, you will
>> not know how to use this complex piece of software.
>>
>> I will look into fixing the documentation of this package.
>>
>> Regards,
>> Fede
next prev parent reply other threads:[~2015-10-17 16:18 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 [this message]
2015-10-17 16:21 ` Andreas Enge
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='CAKrPhPN86zsa_mOtJKRsjyCrGspsNY892Af=3DiqxixY44LbHg@mail.gmail.com' \
--to=beffa@ieee.org \
--cc=andreas@enge.fr \
--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).