-
Notifications
You must be signed in to change notification settings - Fork 18
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
Segfault on publish #17
Comments
I don't get this problem, but I do get a different one:
Looks like the chomsky-font 2.1-1 update got successfully pushed to the AUR, then later amended locally. |
That's possible, but how do I fix it? Usually when that happens I can |
Nuke and pave, see eli-schwartz/aurpublish#17
I've been using
aurpublish
for some time to manage this repository of AUR packages that I (co-)maintain. I've gotten into a few messes (usually because I work on packages from more than one machine and then have to cobble the history together without breakinggit subtree
) but am usually able to get out of them. All packages do publish...except one.For some reason my chomsky-font base package has gone wonky. My usual bump routine ended with a segfault. Because I was on hardware with a serious south bridge issue I kind of just ignored it and figured it had memory problems. I pushed the commit to my repo without getting the subtree pushed to the AUR.
Now I'm trying from another machine with stable hardware and realize there is still a problem:
I've tried a few things such as checking out the repository before the last commit on that package, running
aurpublish -p chomsky-font
, and redoing the bump. Nothing flies, for some reason any attempt I make to publish that package to the AUR now results in a segfault no matter what machine I try from.The text was updated successfully, but these errors were encountered: