-
Notifications
You must be signed in to change notification settings - Fork 1
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
Build is failing #2
Comments
|
I did neither, but I might have used "reset build files" when it stopped building. After that the pkgver seemed to be stuck to 372 and it would not build, either. So I deleted everything related to luxcore, the version still was at 372 but this time it built successfully. Now it shows the correct version number again. |
Sorry to bother you again, but I can't get it working permanently. Perhaps I am doing something stupid, but I have other AUR git packages that do work without problems. For example, I successfully built luxcorerender-git 2:2.3.r410.gf026a8d18-1 only after removing it on 21.Jan. 2020: Click to expand
But since I did not remove the package, I was unable to upgrade the package to r414 on 22.Jan 2020: Click to expand
Github won't let me include the complete logs, so I had to delete some hopefully irrelevant stuff in the middle. |
I've tested this package with
miscellaneous
|
You are right, although it clearly states |
If I may suggest something, try poking pamac devs about the issue. |
Please have a look at https://gitlab.manjaro.org/applications/pamac/-/issues/730#note_15698 |
Indeed, upgrading it 2 times in a row today with yay, the first time (after clean install with yay) worked, the second one didn't so like suggested in the pamac thread it seems more likely now that the problem is in luxcorerender-git package instead of pamac With yay:
Now waiting for the next update so I can check if upgrading works multiple times. And there it is.
|
Built successful for 3 updates in a row, so I guess it's fixed. |
Hi,
building has been unsuccessful for the last three days. Is this something you can fix or is there an error in the sourcecode?
The text was updated successfully, but these errors were encountered: