Closed staticfloat closed 4 years ago
I've updated this PR to include an upgrade of the testing scripts to better reflect the current best accepted practices. I've also upgraded the package to declare compatibility with Julia 1.0+, hopefully nobody is still using 0.7. :)
Any idea what this is about in the appveyor build?:
C:\julia\bin\julia -e 'using Libdl; Libdl.dlopen("Libz")'
ERROR: syntax: incomplete: invalid character literal
Maybe worth switching over to travis for windows too, see here.
I think it would also be good to allow failures on nightly.
Alright, the debugging showed me what I thought; the failure here is because Julia 1.3-rc3 doesn't include libz, but 1.3-rc4 should (and does, as shown in the nightly, although libz.dll
is broken due to https://github.com/JuliaLang/julia/pull/33535). Let's merge this once that PR is merged and we get a new nightly that passes these tests; then when 1.3-rc4 is released next week, this should go all-green.
@staticfloat 33535 is merged, is this ready to merge now too?
Let's re-trigger CI and see what happens on the nightly
versions. If it passes, then yes, this is good to merge and you can tag a new release.
Let's try again now that RC-4 is on travis?
Yep, the last result is exactly what we expected (nightly passes, 1.3 fails) and if we do it one more time, we should get a full green flush!
Bump :slightly_smiling_face:
bump!!! it's green!!!
is this going to be released as a new version? I still pick up the one without this fix
Is it possible for a release to be tagged please?
Anything depending on WinRPM (which is a lot of packages) would really benefit from a new release!
@staticfloat are you able to tag a release here or ping someone that can please?
I cannot; I think we need @BenJWard to do it.
Let's try pinging @bicycle1885 as well. Would you be able to make a new release?
Ok I've just set the version in the project for 1.0.1 since this is a non-breaking change, and deleted the manifest file as it didn't look like it should be there.
I'll see if I can migrate it over to using the artifacts system and then make a release.
Does it not make sense to just tag a release right now with this and then an artifact release could come whenever that is finished?
@JuliaRegistrator register branch=master
Pull request comments will not trigger Registrator as it is disabled. Please trying using a commit or issue comment.
Ok, there's a pending release here: https://github.com/JuliaRegistries/General/pull/6530
Does anyone have any insight as to why the AutoMerge checking over there is telling me the number of supported julia versions is being reduced? As far as I can tell, the julia compatibility specified is correct, according to how semver is described in Pkg docs.
Add compatibility for changes in Julia 1.3
Types of changes
This PR implements the following changes:
:clipboard: Additional detail
Previously, Julia bundled a
zlib1.dll
file on windows, necessitating platform-specificccall()
handles. In Julia 1.3, we are unifying the library name, so you will no longer need to do this. The addedVERSION
check here should make this package work on both 1.2- and 1.3+ versions of Julia, however if you want to simplify, you could change future versions of this package to be compatible with Julia 1.3+ and only use thelibz
name.Note that we probably won't be shipping libz with Julia forever; eventually we may remove it entirely, so I would encourage you to switch over to providing your
libz
through the new Pkg Artifacts/JLL package system. (To emphasize how easy that would be, you would just need to switch this package over to usingProject.toml
, define it as compatible with Julia 1.3+, then addZlib_jll
as a dependency, sayusing Zlib_jll
in your package, and you're done. Importing thatZlib_jll
package will definelibz
for you, and will download/install it atPkg.add()
time so that you never need to worry about Julia shipping or not shipping libz in the future.