Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 524332

Summary: net-p2p/bitcoin-qt-0.9.3 with /bin/sh -> dash - ?
Product: Gentoo Linux Reporter: Mikael Magnusson <mikachu>
Component: Current packagesAssignee: Anthony Basile <blueness>
Status: RESOLVED FIXED    
Severity: normal CC: alexander, luke-jr+gentoobugs, proxy-maint
Priority: Normal Keywords: PATCH
Version: unspecified   
Hardware: All   
OS: All   
Whiteboard:
Package list:
Runtime testing required: ---
Bug Depends on:    
Bug Blocks: 526268    
Attachments: use posix test syntax and no brace expansions

Description Mikael Magnusson 2014-10-03 03:13:08 UTC
Created attachment 385972 [details]
use posix test syntax and no brace expansions

test foo == bar syntax is used in configure.ac and src/m4/bitcoin-qt.m4, $@{.n,} is used in some Makefile templates. I've attached a patch that fixes this, generated by these two gnu sed commands in zsh (maybe bash supports **/ too?)

sed -i s/' == / = /'g configure.ac src/m4/bitcoin_qt.m4
sed -i s/'\$@{\.n,}/\$@.n \$@'/g **/Makefile*
Comment 1 Luke-Jr 2014-10-03 19:01:37 UTC
Can someone with a non-BASH system please confirm the fixes in https://github.com/bitcoin/bitcoin/pull/5038 ?
Comment 2 Anthony Basile gentoo-dev 2014-10-07 11:29:44 UTC
@reporter, can you test Luke-Jr's fixes.  I don't have a dash only system.
Comment 3 Mikael Magnusson 2014-10-07 16:40:10 UTC
(In reply to Anthony Basile from comment #2)
> @reporter, can you test Luke-Jr's fixes.  I don't have a dash only system.

Not really, the patches in that pull are to tests and something called gitian, i don't even know what that is, and I also don't have a git checkout of bitcoin-qt. All you have to do to test it is emerge dash and run eselect sh set dash, you can then change it back to bash if you want. The parts I could test are the parts that were included in my patch and I already tested those :).
Comment 4 Luke-Jr 2016-07-01 16:25:27 UTC
The PR (which addressed more than just gitian) was merged a while ago and was released in 0.10 and newer. Can you confirm if this is still a problem with the latest versions (0.12.x) or not?
Comment 5 Mikael Magnusson 2016-07-01 17:02:27 UTC
I upgraded to 0.12 some time ago without noticing any problems, had no memory of this bug report at the time, but I suppose it must have been fixed then :).
Comment 6 Anthony Basile gentoo-dev 2016-07-01 17:17:08 UTC
(In reply to Mikael Magnusson from comment #5)
> I upgraded to 0.12 some time ago without noticing any problems, had no
> memory of this bug report at the time, but I suppose it must have been fixed
> then :).

@luke-jr is this then fixed upstream?  if so, let's close.
Comment 7 Luke-Jr 2016-07-01 17:23:58 UTC
(In reply to Anthony Basile from comment #6)
> (In reply to Mikael Magnusson from comment #5)
> > I upgraded to 0.12 some time ago without noticing any problems, had no
> > memory of this bug report at the time, but I suppose it must have been fixed
> > then :).
> 
> @luke-jr is this then fixed upstream?  if so, let's close.

Yep, sounds close-worthy to me. I cannot change the status myself, however.