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
Size mismatch in 1.3.4 #906
Comments
Workaround: |
I think I've fixed this problem in the |
Looks solid. I wanted to make a regression test for this bug but I see that the testing framework has been not working for some time. With all the regressions, some of which caught minutes after release, it's perhaps an idea to reinstate it or go with a new framework? |
All help in that area to get regression working is really welcomed :) 2014-08-05 4:04 GMT+02:00 Melvyn Sopacua notifications@github.com:
|
Ok, can you elaborate what's broken now? I see several things in there (bsd.tests.mk and configure.ac hooks) and without some architectural overview it's quite the puzzle to even figure out how to trigger the broken implementation. |
This is not fixed. I ran pkg: cached package git-2.0.2: size mismatch, fetching from remote Fetching git-2.0.2.txz: 100% of 3 MB pkg: cached package git-2.0.2: size mismatch, cannot continue |
This was the whole purpose of the cached filenames. What happened?? |
checksum filenames* |
Using:
The output is:
pkg: cached package vim-7.4.364: size mismatch (4901580 != 4904224), fetching from remote
4904224 is the correct pkgsize. I have no idea where the 4901580 comes from. The packagesite.txz in the repo also has the correct 4904224 as pkgsize. No 4901580 in packagesite.yaml anywhere.
The text was updated successfully, but these errors were encountered: