Conversation
d28c951 to
cb0ae7e
Compare
|
@cthoyt, I have some problems with the internal logic. The dependencies do not seem to be downloaded properly. Do you have any clue what is going on? |
|
So this is probably an upstream issue with scijava |
b03505b to
280fc3d
Compare
|
Maybe I'm making progress on other fronts... now running into this issue: sphinx-doc/sphinx#10491 |
e987135 to
3e8a3d7
Compare
Yes, indeed, thanks for finding that fix. Unfortunately the implicit default for english was removed and every repository needs this update :/ |
|
As far as the maven resolution, it seems that something is relying on a version of This page says that only version 1.1.1 and 1.1.2 exist - https://search.maven.org/artifact/org.osgi/org.osgi.service.prefs |
yes, but far as I know both fall in the range But I am considering this lead and in the progress of releasing Bacting 0.0.40 which depends on the new Eclipse core libraries that came up. Another lead I have been trying is a comment somewhere that JGO has a hashing issue and mixing up versions in the local cache... that's why I tried deleting |
0448251 to
d921dd6
Compare
|
Okay, we're not the only ones having the issue :( And the root cause if identified here: eclipse-equinox/equinox.bundles#54 They also mention the removal of bundles from Maven Central here. |
|
So, Bacting 0.0.40 should fix it. It depends on the fixed libraries, but JGO/ScyJava is not picking up the libraries correctly. Here's the dependencies: But note that ScyJava is still looking for the old (wrong: Well, obvious because it's depending on the wrong |
a74e510 to
d921dd6
Compare
|
On the upside, at least I can reproduce it locally now. Maybe a confounding ScyJava bug after all? |
|
I filed an issue to indicate pybacting is currently uninstallable: #11 |
|
Okay, the workaround for the Eclipse problem worked. But now I got other problems (that should not even exist). |
|
Replacing this with a clean new PR. |
|
I do squash and merge exclusively on my projects so it’s not strictly necessary to open a new PR, just for future reference |
|
Yeah, I know. It was more for myself, so that I can see better what is happening. |


This brings in @bioregistry support: