Hi all,
I just added the stinkbug.png file to the sample_data repo so the
Image tutorial and other examples using this image could be run by
users making cbook.get_sample_data calls. But while it works fine
with a reasonably recent MPL, I tested with the system one in Ubuntu
11.10, and it does not find the file. The reason is simply that this
version of mpl still had the old SVN sample_data repo URL:
baseurl = ‘http://matplotlib.svn.sourceforge.net/svnroot/matplotlib/trunk/sample_data/’
So the problem is that any users of 11.10 are now stuck with a 'frozen
in time' sample_data repo.
We can fix this easily by simply pushing over to sample_data an update
with any new files in the github one. Since that repo changes fairly
slowly and the changes typically involve just putting new files in and
no actual code, it should be fairly easy to do manually.
What do folks think? If you agree, I'm happy to push an update now
(I'm assuming the SVN repo is still writable, which might not be the
case...).
Cheers,
f
Hi all,
I just added the stinkbug.png file to the sample_data repo so the
Image tutorial and other examples using this image could be run by
users making cbook.get_sample_data calls. But while it works fine
with a reasonably recent MPL, I tested with the system one in Ubuntu
11.10, and it does not find the file. The reason is simply that this
version of mpl still had the old SVN sample_data repo URL:
baseurl = 'matplotlib download | SourceForge.net’
So the problem is that any users of 11.10 are now stuck with a 'frozen
in time' sample_data repo.
We can fix this easily by simply pushing over to sample_data an update
with any new files in the github one. Since that repo changes fairly
slowly and the changes typically involve just putting new files in and
no actual code, it should be fairly easy to do manually.
What do folks think? If you agree, I'm happy to push an update now
(I'm assuming the SVN repo is still writable, which might not be the
case...).
Fernando,
If you are willing and able to do it, please go ahead. I can't think of any problem it would create. (But I don't know whether the repo is writable.)
Eric
···
On 12/16/2011 10:20 AM, Fernando Perez wrote:
Cheers,
f
Great, thanks. I'll see if I can push and will report back. If it
doesn't work, we'll see if John can later restore write access to it.
Cheers,
f
···
On Fri, Dec 16, 2011 at 3:34 PM, Eric Firing <efiring@...229...> wrote:
If you are willing and able to do it, please go ahead. I can't think of
any problem it would create. (But I don't know whether the repo is
writable.)
Well, I can't seem to push. I don't know if it's my sourceforge
credentials, or if the repos are read-only, or what. In case anyone
else wants to give it a try, I tarred the svn directory and put it up
here:
http://fperez.org/tmp/sample_data_svn.tgz
I've already done the add steps, so all you should need to do is:
wget Conference - FP Conference
tar xzf sample_data_svn.tgz
cd sample_data_svn
svn commit -m"Sync SVN repo with contents in current git repo"
If one of you wants to try pasting the above four lines into a
terminal, let me know if it works for you.
Cheers,
f
···
On Fri, Dec 16, 2011 at 3:39 PM, Fernando Perez <fperez.net@...149...> wrote:
Great, thanks. I'll see if I can push and will report back. If it
doesn't work, we'll see if John can later restore write access to it.
Nope:
efiring@...340...:~/temp/sample_data_svn$ svn commit -m"Sync SVN repo with contents in current git repo"
svn: Commit failed (details follow):
svn: Server sent unexpected return value (403 Forbidden) in response to MKACTIVITY request for '/svnroot/matplotlib/!svn/act/9b074418-cd32-4039-88d8-06b46c4c8764'
I think the repo was frozen when we moved to github.
Eric
···
On 12/16/2011 02:12 PM, Fernando Perez wrote:
wgethttp://fperez.org/tmp/sample_data_svn.tgz
tar xzf sample_data_svn.tgz
cd sample_data_svn
svn commit -m"Sync SVN repo with contents in current git repo"
OK, thanks for trying. Next week we can see if John can reopen it for
this. I think there's no danger of anyone mistakenly committing any
real work there anymore.
Cheers,
f
···
On Fri, Dec 16, 2011 at 5:11 PM, Eric Firing <efiring@...229...> wrote:
Nope:
efiring@...340...:~/temp/sample_data_svn$ svn commit -m"Sync SVN repo with
contents in current git repo"
svn: Commit failed (details follow):
svn: Server sent unexpected return value (403 Forbidden) in response to
MKACTIVITY request for
'/svnroot/matplotlib/!svn/act/9b074418-cd32-4039-88d8-06b46c4c8764'
I think the repo was frozen when we moved to github.
I've selectively enabled your (fperez) write access to the repo. Give
it a try and let me know if you have any problems.
Thanks,
JDH
···
On Fri, Dec 16, 2011 at 7:17 PM, Fernando Perez <fperez.net@...149...> wrote:
OK, thanks for trying. Next week we can see if John can reopen it for
this. I think there's no danger of anyone mistakenly committing any
real work there anymore.
my SF username is fer_perez, by the time I joined fperez was taken on
SF. If you have a chance of fixing this, I'll try to push again.
Did you test? I did enable the same old fer_perez sf account you've always had. I was just referring to you by your email moniker in the post above. If it's still not working, I'll see if there is some other setting that needs tweaking.
···
OK, it worked now. I was using before an auto-generated password that
was OK for web login but had funny quote characters that were
confusing the svn login (probably being escaped by the shell). I
changed that to a more normal password, and now I was able to push.
Sorry for the confusion, and thanks!
Doing these updates should be easy and infrequent enough that I'm
happy to push them by hand when needed, just ping me.
Checked and the system mpl on ubuntu 11.10 can now fetch stinkbug correctly:
In [3]: matplotlib.__version__
Out[3]: '1.0.1'
In [4]: cbook.get_sample_data('stinkbug.png')
Out[4]: <open file
'/home/fperez/.matplotlib/sample_data/stinkbug.png', mode 'rb' at
0x2860b70>
Cheers,
f
···
On Sat, Dec 17, 2011 at 11:56 AM, John Hunter <jdh2358@...149...> wrote:
Did you test? I did enable the same old fer_perez sf account you've always had. I was just referring to you by your email moniker in the post above. If it's still not working, I'll see if there is some other setting that needs tweaking.