Skip to content
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 upload a PKGBUILD #98

Open
pirate486743186 opened this issue Aug 5, 2022 · 4 comments
Open

Can't upload a PKGBUILD #98

pirate486743186 opened this issue Aug 5, 2022 · 4 comments

Comments

@pirate486743186
Copy link

Issue

I'm trying to reupload a AUR package.
https://aur.archlinux.org/perl-lwp-useragent-cached.git

I kept the git history and it fails with this error.

remote: error: The following error occurred when parsing commit
remote: error: 1acd520f98c9e187a5a31eecd7c7698b3d7c237c:
remote: error: Line 0: Couldn't find ' = ' delimiter.
remote: error: hook declined to update refs/heads/master
To ssh://mpr.makedeb.org/perl-lwp-useragent-cached.git
 ! [remote rejected] master -> master (hook declined)
error: failed to push some refs to 'ssh://mpr.makedeb.org/perl-lwp-useragent-cached.git'
@hwittenborn
Copy link
Member

Looking at the commit in that error, it looks like the line in question is a comment in the SRCINFO file, and the MPR's SRCINFO parser doesn't know how to handle such comments. You'll probably need to ditch the Git history and regenerate the SRCINFO file with makedeb, then it should upload fine.

Support for those comments could also be added to the parser, but since this is only an issue with AUR SRCINFO files I'm not quite sure if I want to support it yet.

@hwittenborn
Copy link
Member

I needed to rewrite the SRCINFO parsing library for some stuff I was needing the library for, so this comment issue should be fixed in the library itself at least. I'm not sure when I'll get to fixing it in the deployed instance, though I'll try to get that done in the next few days if time allows for it.

@pirate486743186
Copy link
Author

Is it really necessary to check for compliance inside of git history? In this case, i was hopping to preserve the history from AUR. A lot of packages will be ported from AUR.

@hwittenborn
Copy link
Member

Is it really necessary to check for compliance inside of git history?

Probably not, but that'd need to be thought about for a bit before I decided if I wanted to not check for such. It's something inherited from aurweb, so I'm sure there's some kind of logic behind it.

Regardless of if it gets changed it definitely won't be immediate since I'm busy with other makedeb stuff, an immediate solution would definitely just be to ditch the commit history, otherwise you'll probably be stuck waiting for a bit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants