-
Notifications
You must be signed in to change notification settings - Fork 16
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
pacsync: Floating point exception #13
Comments
Are you running a recent build of pacman-git? There was a change to the download callback arguments that may be causing this: andrewgregory/pacman@58140db |
The error was with pacman v5.0.1 / libalpm v10.0.1, but it's the same with pacman-git from HEAD |
I can't reproduce the error, but the only possible issue that I can see is in the download callback if curl is reporting a total download size of 0 for the file for some reason. Try building pacutils from the dload_fpe branch (with pacman v5.0.1) and let me know if that fixes it. |
The |
If |
Yeah, pacman output looks normal:
Without --debug it now seems the output is there, albeit partially (see last line):
|
The xfer size looks fine, so I'm not sure why |
Sorry, forgot to include the actual syncing of core e.a: |
I am out of ideas that make any kind of sense. Can you install pacman-git from my dlcb_debug branch (https://github.com/andrewgregory/pacman/tree/dlcb_debug) and give me the full output of |
Ok, (Note that before compiling, I removed -Werror due to a -Wformat error in dload.c) |
The curl callback is clearly getting the correct values, and, even though I messed up the printf (hence the -Wformat error), it looks like should be passing the correct values to the front-end callback. The message that |
Okay, I think I got it. If you rebuild the dload_fpe branch of pacutils, I think you should get the correct download progress with percentages. |
That indeed fixes it, thanks! One more thing, I had to disable make check, since it fails on
https://gist.github.com/anonymous/9c95af5c8612e291cd1a208d688bfad5/raw |
A few of the tests use an ugly late binding hack to open in-memory files. I'm not sure why it's not working correctly for you, but I'm not terribly surprised that it's broken either. I've pushed some updated commits to dload_fpe; if you can verify that they build cleanly and work correctly I'll push them to master and take a look at the broken tests later. |
It builds correctly, but it seems that newlines are not printed and there are some duplicate entries:
|
Try it now. |
Yep, it works:
Thanks for taking the time to figure out this issue! |
Merged. Thanks for reporting. |
On i686, trying to sync a local repository with pacsync fails:
This happens regardless of the database present in
/var/lib/pacman/sync
, or what packages either database contains. i.e. I can reproduce it with an empty database:strace output: https://gist.githubusercontent.com/anonymous/328229526a58ca2c9fcf23ad737c377d/raw
pacconf output: https://gist.githubusercontent.com/anonymous/c17f4309d15fced13ab44c2ca267be76/raw
The text was updated successfully, but these errors were encountered: