-
-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reposilite 2.9.23 build fails due to net.dzikoysk:cdn:1.8.0 missing #780
Labels
bug
Bugs & errors found in Reposilite
Comments
Right, we need to update repository for 2.x, because Reposilite 3.x does not support this method. |
dzikoysk
added a commit
that referenced
this issue
Oct 7, 2021
dzikoysk
added a commit
that referenced
this issue
Oct 7, 2021
dzikoysk
added a commit
that referenced
this issue
Oct 7, 2021
dzikoysk
added a commit
that referenced
this issue
Oct 7, 2021
Should be fine with 2.9.25 |
benalexau
added a commit
to benalexau/aur-repo
that referenced
this issue
Oct 7, 2021
Thanks @dzikoysk. I confirm 2.9.25 builds without issue. |
benalexau
added a commit
to benalexau/aur-repo
that referenced
this issue
Oct 8, 2021
This package was temporarily removed due to the build issue reported in dzikoysk/reposilite#780 This reverts commit 8f6b7a8.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
The aforementioned artifact is not published on Maven Central. It is only published in
panda-repository
. As this version used to build without any issue (I run an automatic weekly binary packaging action for Arch Linux) I suspect a configuration change to the Reposilite instance hosting the latter repository is no longer accepting requests if they omit/releases
.Verification:
The issue is the
pom.xml
doesn't includereleases
:Would you please either release a 2.9.x that includes
releases
or modify the configuration of thehttps://repo.panda-lang.org
to allow omitting the path?Reposilite version
2.x
Relevant log output
No response
The text was updated successfully, but these errors were encountered: