-
Notifications
You must be signed in to change notification settings - Fork 2
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
Can't build today - clsql-sys symbol missing? #5
Comments
Ahh... yes, I see I should have delayed releasing this till the clsql version it requires was made. Apologies, I will roll master back and leave this work in a branch till clsql lands. Thanks |
It should be back in a state where master and clsql are at compatible versions. |
Thanks! And if you're into RSS, try
http://report.quicklisp.org/feeds/author/AccelerationNet.rss for fun
automatic reports!
…On Fri, Feb 9, 2018 at 10:30 AM, Russ Tyndall ***@***.***> wrote:
It should be back in a state where master and clsql are at compatible
versions.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#5 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAT2rQGWzaHT4_Kw04aFoDryj7vhUI8Vks5tTGSUgaJpZM4SAEl1>
.
|
Did you fix this by force-pushing an old git head?
…On Fri, Feb 9, 2018 at 10:34 AM, Zach Beane ***@***.***> wrote:
Thanks! And if you're into RSS, try http://report.quicklisp.org/
feeds/author/AccelerationNet.rss for fun automatic reports!
On Fri, Feb 9, 2018 at 10:30 AM, Russ Tyndall ***@***.***>
wrote:
> It should be back in a state where master and clsql are at compatible
> versions.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#5 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AAT2rQGWzaHT4_Kw04aFoDryj7vhUI8Vks5tTGSUgaJpZM4SAEl1>
> .
>
|
Yeah, I reset the head to the previous stable state. Does that mess up the quicklisp workflow? If so, apologies, I will try to remember to revert rather than force pushing. What's the best way to rectify this? Should I put back the patches, then revert them? |
I usually update already-fetched git projects with "git pull", and a force push can make that error out. But I cleared the git cache and rebuilt. There are still a number of failing minor AccelerationNet systems - the above RSS feed shows more details. |
This happened again - same issue with the same symbol. |
http://report.quicklisp.org/2018-02-26/failure-report/clsql-helper.html#clsql-helper has the current failure log. |
Sorry about that, I applied a rollback commit this time instead of resetting, so hopefully it works with no more personal intervention. |
http://report.quicklisp.org/2018-02-09/failure-report/clsql-helper.html#clsql-helper has a log. I get this:
The text was updated successfully, but these errors were encountered: