okay...
the first time I tried that url, my browser download tool cried 'network
error'
retrying the download pulled the complete/correct file.
running ./sage -i bleach seemed to work as well.
Now, happily, I get the familiar...
[bleach-3.0.2]
That file is the wrong size. Here is what I see:
$ ls -l upstream/bleach-3.0.2.tar.gz
-rw-r--r-- 1 palmieri staff 165682 Jan 26 20:52
upstream/bleach-3.0.2.tar.gz
So try downloading a new version, say from
http://files.sagemath.org/spkg/upstream/bleach/index.html. I would suggest
not
$ ls -l upstream/bleach-3.0.2.tar.gz
-rw-r--r-- 1 lauve admin 24576 Feb 4 12:39 upstream/bleach-3.0.2.tar.gz
Is this what you wanted to see?
(Also, would it not say 'invalid checksum' because I hit ctrl+c to abort
whatever download it was doing?)
On Monday, February 4, 2019 at
Actually, don't do that yet. What do you get with
$ ls -l upstream/bleach-3.0.2.tar.gz
It shouldn't say "Invalid checksum": that is a standard package and a valid
tarball should be included with the Sage distribution.
On Monday, February 4, 2019 at 10:36:57 AM UTC-8, John H Palmieri wrote:
>
Try downloading bleach-3.0.2.tar.gz separately and put it in the "upstream"
directory in Sage. Then run "./sage -i bleach".
(If I try the link
http://mirrors.mit.edu/sage/spkg/upstream/bleach/bleach-3.0.2.tar.gz
It really seems like nothing is going on.
running
./sage -i bleach
I open my activity monitor and look under network heading. I see that
python has:
bytes sent: 118
bytes received: 30
packages sent: 1
packages received: 21
And it's been that way for ten minutes now. I broke the code
Sage downloads packages during a build. Thus, if you have an unstable
internet connection, things
like this might happen.
Could you try running
./sage -i bleach
and if this succeeds, run make
On Mon, Feb 4, 2019 at 5:06 PM wrote:
>
> Hi there,
>
> I recently ran a 'make distclean' plus
