Skip to content

Conversation

@JuliaRegistrator
Copy link
Contributor

@JuliaRegistrator JuliaRegistrator commented Feb 7, 2022

@github-actions
Copy link
Contributor

github-actions bot commented Feb 7, 2022

Your new version pull request met all of the guidelines for auto-merging and is scheduled to be merged in the next round.


If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.

@JuliaRegistrator JuliaRegistrator force-pushed the registrator/quantumcontrol/8a270532/v0.0.4 branch from 37b9316 to 6f0871e Compare February 7, 2022 05:03
@JuliaRegistrator JuliaRegistrator temporarily deployed to stopwatch February 7, 2022 05:03 Inactive
@goerz
Copy link
Member

goerz commented Feb 7, 2022

[noblock]

Ok, I'm going to need some help here. This package (QuantumControl) is supposed to pull together all the packages in the JuliaQuantumControl org.

I recently released QuantumPropagators 0.1.0 and QuantumControlBase 0.1.0.

This broke my local development of QuantumControl.jl, Krotov.jl, and GRAPE.jl. I think this is because testing those packages depends on all the other packages. However, the current QuantumControl.jl in the registry is still depending on the old releases for QuantumPropagators and QuantumControlBase, and thus it's not possible to fulfill the dependencies for creating a test environment.

So, I figured I have to make an "emergency" release of QuantumControl.jl that is less strict about the versions of all the component packages, see the diff in https://github.com/JuliaQuantumControl/QuantumControl.jl/pull/5/files

Yet, I'm getting unsatisfiable requirements for this release, too! https://github.com/JuliaRegistries/General/runs/5088442799?check_suite_focus=true

I'm having difficulty comprehending what the problem is from the log. It looks like it thinks QuantumPropagators is restricting GRAPE, but GRAPE isn't a dependency of QuantumPropagators! It is a dependency for running the QuantumPropagator tests (it's in tests/Project.toml, but not in the main Project.toml).

What is going on here?

It's possible that the problem can be solved by just merging this QuantumControl v0.0.4 release... so maybe someone can do that?

@goerz
Copy link
Member

goerz commented Feb 7, 2022

[noblock]

I've asked for help on Discourse as well: https://discourse.julialang.org/t/unsatisfiable-requirements-when-trying-to-release-new-version-of-quantumcontrol-package/75965

This couldn't be an issue of the recent 0.1.0 releases of QuantumPropagators and QuantumControlBase having propagated through the General registry, right?

UUID: 8a270532-f23f-47a8-83a9-b33d10cad486
Repo: https://github.com/JuliaQuantumControl/QuantumControl.jl.git
Tree: 5fc887fc70e95c36c45a2cecab67c0384a25b6d2

Registrator tree SHA: 8e1a5ac2695627143951512d700c7e3c445102ec
@JuliaRegistrator JuliaRegistrator force-pushed the registrator/quantumcontrol/8a270532/v0.0.4 branch from 6f0871e to eb57dee Compare February 8, 2022 02:36
@JuliaRegistrator JuliaRegistrator temporarily deployed to stopwatch February 8, 2022 02:36 Inactive
@JuliaTagBot JuliaTagBot merged commit edede00 into master Feb 8, 2022
@JuliaTagBot JuliaTagBot deleted the registrator/quantumcontrol/8a270532/v0.0.4 branch February 8, 2022 02:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants