Thanks for the clear suggestion
On Sunday, 15 May 2016 10:37:17 UTC+2, Tony Kelman wrote:
>
> Renaming an existing package can cause problems if anyone else has started
> using or depending on it. You can deprecate the existing name of the
> package by adding an upper Julia version number bound
Renaming an existing package can cause problems if anyone else has started
using or depending on it. You can deprecate the existing name of the
package by adding an upper Julia version number bound on all existing tags
of the package in METADATA, so it will no longer be installable once newer
hub might also be to blame here? Though I'm pretty sure we have other hub
users around who might've noticed this earlier
On Wednesday, April 27, 2016 at 6:39:53 AM UTC-7, Chang Kwon wrote:
>
> That’s pretty interesting. I’m actually surprised to find out what LFS is…
> No, I didn’t enable
You can try moving the .git/hooks directory aside to disable all git hooks,
including the LFS ones.
On Wed, Apr 27, 2016 at 9:39 AM, Changhyun Kwon wrote:
> That’s pretty interesting. I’m actually surprised to find out what LFS is…
> No, I didn’t enable anything… I believe…
>
That’s pretty interesting. I’m actually surprised to find out what LFS is… No,
I didn’t enable anything… I believe…
My github account is “Micro”, individual. I have once installed `hub` from
github, but nothing else. I want to blame homebrew-cask’s Julia, but not even
sure with that…
>
Git LFS is https://git-lfs.github.com/ - you didn't enable anything? What
kind of github account do you have? I wonder if you may have installed some
git extension, or if homebrew-cask's version of Julia is using its own
customized git rather than the bundled one?
On Tuesday, April 26, 2016
"VariationalInequality.jl" is a new name.
When I did Pkg.publish(), I obtained this error:
This repository is configured for Git LFS but 'git-lfs' was not found on
your path. If you no longer wish to use Git LFS, remove this hook by
deleting .git/hooks/pre-push.
error: failed to push some
You could first uninstall the package, then rename on Github and then clone
from the new address.
Cheers,
Bart
On Tuesday, April 26, 2016 at 6:17:10 PM UTC+2, Chang Kwon wrote:
>
> I was wondering what is the proper way to change the package name under
> development. This is often the case