Cap older versions breaking everything? about general HOT 15 CLOSED

I can verify that there was a problem but that 1a5454c seems to have resolved the test I was about to report.

from general.

If I checkout the last commit before 0c75a4d, then I can use the package manager again.

from general.

What are you trying to install? Without that information, we can't fix it.

from general.

Mamba and Missings are broken for me (installing for 0.7).

from general.

Here are the packages that didn't work before I gave up: Decimals, ShowItLikeYouBuildIt, Destruct, Seaborn, TOML, PkgDev, but it felt like the tip of the iceberg. If I somehow got around one unsatisfiable requirement, it would just reveal another.

from general.

Do these work on 0.7?

from general.

I'm able to dev Decimals and then test Decimals but it does print a lot of deprecation warnings.

from general.

I'm not sure if PkgDev did (I don't think it did), but Destruct and Seaborn certainly did. Looking at the released versions for the others, Decimals seems to have a release explicitly for 1.0 support, TOML seems like a maybe, ShowItLikeYouBuildIt seems doesn't have a version about compatibility.

I don't know, I've been using 0.7 for a month or more now without any problems, but now I can't. The only thing I tried to add this morning when I discovered the problem was JLD2, which I think is 1.0 compatible.

from general.

• ShowItLikeYouBuildIt fails tests on 0.7 and 1.0 so that's a legitimate cap.
• Seaborn is broken and needs to use Test instead of Base.Test.
• Destruct also has deprecations in its tests.
• etc.

In short, I think the answer to this is mostly that people need to fix their shit. I'm still perplexed that people are so unwilling to just fix a few deprecations, but now is the time to do so. If you want to work around this while people get their acts together and fix things and make releases of packages that aren't broken, you can go into ~/.julia/registries/General and do

git checkout -b dontcapmebro e5748a7e36745cf42952c5451586a79911a524b4

from general.

It might be true that people need to fix their packages, but as a user yesterday Julia worked, and today it doesn't.

I thought the point of 0.7 was that it was 1.0 with deprecation warnings instead of failure. Maybe you could change the enforced cap to include 0.7?

from general.

Maybe you could change the enforced cap to include 0.7?

I've had the same thought.

from general.

Sure, we could potentially do that. I don't really care about 0.7, so 🤷‍♂️

from general.

Dunno, I'll gladly switch to 1.0 once the packages I need to graduate stop throwing deprecation warnings. Until then, 0.7 it is.

Not that I get a vote, but if I did I would vote for relaxing the cap to allow minimally maintained, but still useful, packages to work and be installable on 0.7.

from general.

Thanks for relaxing the cap, it makes life much easier!

from general.

Sure, happy to make life easier while still having correct caps for 1.0 at least.

from general.