Bash fails to patch due to the SHA256 of bash43-042. Reproducible: Always Steps to Reproduce: 1. use paludis (haven't checked with emerge) 2. cave resolve -1 app-shells/bash 3. receive error Actual Results: Checking 'bash43-042'... failed SHA256 See attached build log for full output. Expected Results: Successful build.
Created attachment 422310 [details] build output
> wget -q ftp://ftp.cwru.edu/pub/bash/bash-4.3-patches/bash43-042 && sha256sum bash43-042 ac219322db2791da87a496ee6e8e5544846494bdaaea2626270c2f73c1044919 bash43-042 > grep bash43-042 $(portageq get_repo_path / gentoo)/app-shells/bash/Manifest | awk '{print $5}' ac219322db2791da87a496ee6e8e5544846494bdaaea2626270c2f73c1044919 It's the mirrors that don't update the patch file...
*** This bug has been marked as a duplicate of bug 570820 ***
infra: Can you look into why bash43-042 has not been updated on mirrors for 4 days now?
(In reply to Mike Gilbert from comment #4) > infra: Can you look into why bash43-042 has not been updated on mirrors for > 4 days now? I had a similar problem with a mips-sources patchball a few weeks ago, where I forgot to upload one when committing the ebuild, but despite copying the patchball to /space/distfiles-local later on, it refused to populate to the mirrors. I had to bump the patchball rev up once before it'd populate. See Bug #562994. Figured it was something I was doing wrong (and maybe I was), but figured I'd chime in since this issue looks similar.
*** Bug 571826 has been marked as a duplicate of this bug. ***
*** Bug 571994 has been marked as a duplicate of this bug. ***
Use SRC_URI arrows to rename the file and be done with it. And learn not to reuse the same name for another contents. We can't make remote mirrors magically start syncing something if rsync doesn't trigger it.
(and it probably doesn't trigger update because the size didn't change)
(In reply to Michał Górny from comment #8) It seemed like a bug in the mirroring process. Certainly not looking for a "magical" solution, just an explanation.
SRC_URI is kind of a mess in the bash ebuild. I'm going to try adding the file to distfiles-local with a recent timestamp. If that doesn't work, I guess we could do some string manipulation in the ebuild.
Should no longer be an issue.
