I'm chasing my tail I think.
I'm trying to automate in a bash shell the process of incrementing a version # by one digit. 2.23 to 2.24

I've got the following script. It may be the long way around but I've been piecing this step by step trying to get the
syntax right on each line. So it's broken down that way. It's the last line that is giving me the issue.

OLDver=$(expr $(grep '"version"' manifest.json | awk -F\" '{ print $4 }')) # grab the version with dot
leftOLD=${OLDver:0:1}
rightOLD=${OLDver:2:4} #split the digits out for sed command
INCR=0.01
NEWver=$(echo $OLDver + $INCR | bc) # Increment the version number number to 2.24
leftNEW=${NEWver:0:1}
rightNEW=${NEWver:2:4} #split the digits again
# all this because sed will not substitute with periods unless escaped.
# so I've split the digits out
# but this last line does not work.
sed -i 's/$leftOLD\.$rightOLD/$leftNEW\.$rightNEW/' manifest.json

I've run this by clicking the shell script. I've run the shell script from a terminal. No errors anywhere.
I can paste these lines into terminal and run them, it doesn't work, but I can echo the last line:
echo "sed -i 's/$leftOLD\.$rightOLD/$leftNEW\.$rightNEW/' manifest.json"
and I get: sed -i 's/2\.23/2\.24/' manifest.json
which is what I want.
If I write out the sed
sed -i 's/2\.23/2\.24/' manifest.json
it works. Just not in the bash script.

Anyone got an idea? Some idiosyncrasy of Bash?

--
Linux Mint 21.1 Cinnamon 5.6.8
Al

On 8/17/23 12:51, this is what Big Al wrote:
> I'm chasing my tail I think.
> I'm trying to automate in a bash shell the process of incrementing a version # by one digit. 2.23 to 2.24
>
> I've got the following script.   It may be the long way around but I've been piecing this step by step trying to get the
> syntax right on each line.  So it's broken down that way.   It's the last line that is giving me the issue.
>
> OLDver=$(expr $(grep '"version"' manifest.json | awk -F\" '{ print $4 }'))  # grab the version with dot
> leftOLD=${OLDver:0:1}
> rightOLD=${OLDver:2:4}  #split the digits out for sed command
> INCR=0.01
> NEWver=$(echo $OLDver + $INCR | bc) # Increment the version number number to 2.24
> leftNEW=${NEWver:0:1}
> rightNEW=${NEWver:2:4}  #split the digits again
>     # all this because sed will not substitute with periods unless escaped.
>     # so I've split the digits out
>     # but this last line does not work.
> sed -i 's/$leftOLD\.$rightOLD/$leftNEW\.$rightNEW/' manifest.json
>
>
> I've run this by clicking the shell script.  I've run the shell script from a terminal.  No errors anywhere.
> I can paste these lines into terminal and run them, it doesn't work, but I can echo the last line:
>     echo "sed -i 's/$leftOLD\.$rightOLD/$leftNEW\.$rightNEW/' manifest.json"
> and I get:     sed -i 's/2\.23/2\.24/' manifest.json
> which is what I want.
> If I write out the sed
>     sed -i 's/2\.23/2\.24/' manifest.json
> it works.  Just not in the bash script.
>
> Anyone got an idea?  Some idiosyncrasy of Bash?
>
Not part of the problem, but the first line has an excess 'expr' command that does nothing but complicate the code.
OLDver=$(grep '"version"' manifest.json | awk -F\" '{ print $4 }')
--
Linux Mint 21.1 Cinnamon 5.6.8
Al

On 8/17/23 11:55 AM, Big Al wrote:
> I've run this by clicking the shell script.  I've run the shell script
> from a terminal.  No errors anywhere.

Assuming you're doing this within the file manager (FM) it's probably
the FM settings; if you right-click on the script and select 'Properties
>> Permissions' you can check what the permissions are. I think you
need to have

'Execute: [x] Allow executing file as program'

enabled for launching scripts from the FM. Once enabled when you
double-click on the script you should get prompted for what to do; click
'Run in terminal' or 'Run'. Note that if you choose the former and your
script doesn't have a "pause" built into it the terminal will
immediately close once the program completes. You can add a pause using
the built-in function 'read':

$ cat foo.sh
#!/bin/bash
oldVER='2.23'
newVER="$(echo $oldVER |sed 's/2\.23/2\.24/')"
echo "oldVER = $oldVER"
echo "newVER = $newVER"
read -n1 -r -p'press any key to continue..'

$ . ./foo.sh
oldVER = 2.23
newVER = 2.24
press any key to continue..

This seems to work both in the terminal and launched from the Nemo FM.
If you're writing the results to some file then you don't need a pause
and can just choose 'Run'.

On 17/08/2023 17:51, Big Al wrote:
> I'm chasing my tail I think.
> I'm trying to automate in a bash shell the process of incrementing a
> version # by one digit. 2.23 to 2.24
>
> I've got the following script. It may be the long way around but I've
> been piecing this step by step trying to get the syntax right on each
> line. So it's broken down that way. It's the last line that is giving
> me the issue.
>
> OLDver=$(expr $(grep '"version"' manifest.json | awk -F\" '{ print $4
> }')) # grab the version with dot
> leftOLD=${OLDver:0:1}
> rightOLD=${OLDver:2:4} #split the digits out for sed command
> INCR=0.01
> NEWver=$(echo $OLDver + $INCR | bc) # Increment the version number
> number to 2.24
> leftNEW=${NEWver:0:1}
> rightNEW=${NEWver:2:4} #split the digits again
> # all this because sed will not substitute with periods unless
> escaped.
> # so I've split the digits out
> # but this last line does not work.
> sed -i 's/$leftOLD\.$rightOLD/$leftNEW\.$rightNEW/' manifest.json
>

change the 's in the above line to "s
single quotes stop the expansion of variables

>
> I've run this by clicking the shell script. I've run the shell script
> from a terminal. No errors anywhere.
> I can paste these lines into terminal and run them, it doesn't work, but
> I can echo the last line:
> echo "sed -i 's/$leftOLD\.$rightOLD/$leftNEW\.$rightNEW/'
> manifest.json"
> and I get: sed -i 's/2\.23/2\.24/' manifest.json
> which is what I want.
> If I write out the sed
> sed -i 's/2\.23/2\.24/' manifest.json
> it works. Just not in the bash script.
>
> Anyone got an idea? Some idiosyncrasy of Bash?
>

--

Chris Elvidge, England
COFFEE IS NOT FOR KIDS

On 8/17/2023 12:51 PM, Big Al wrote:
> I'm chasing my tail I think.
> I'm trying to automate in a bash shell the process of incrementing a version # by one digit. 2.23 to 2.24
>
> I've got the following script.   It may be the long way around but I've been piecing this step by step trying to get the syntax right on each line.  So it's broken down that way.   It's the last line that is giving me the issue.
>
> OLDver=$(expr $(grep '"version"' manifest.json | awk -F\" '{ print $4 }'))  # grab the version with dot
> leftOLD=${OLDver:0:1}
> rightOLD=${OLDver:2:4}  #split the digits out for sed command
> INCR=0.01
> NEWver=$(echo $OLDver + $INCR | bc) # Increment the version number number to 2.24
> leftNEW=${NEWver:0:1}
> rightNEW=${NEWver:2:4}  #split the digits again
>     # all this because sed will not substitute with periods unless escaped.
>     # so I've split the digits out
>     # but this last line does not work.
> sed -i 's/$leftOLD\.$rightOLD/$leftNEW\.$rightNEW/' manifest.json
>
>
> I've run this by clicking the shell script.  I've run the shell script from a terminal.  No errors anywhere.
> I can paste these lines into terminal and run them, it doesn't work, but I can echo the last line:
>     echo "sed -i 's/$leftOLD\.$rightOLD/$leftNEW\.$rightNEW/' manifest.json"
> and I get:     sed -i 's/2\.23/2\.24/' manifest.json
> which is what I want.
> If I write out the sed
>     sed -i 's/2\.23/2\.24/' manifest.json
> it works.  Just not in the bash script.
>
> Anyone got an idea?  Some idiosyncrasy of Bash?
>

All I could find, is this for inspiration. I don't
know how complex your problem really is (what cruft is in
the file to prevent a solution from working).

https://stackoverflow.com/questions/36402167/update-version-number-stored-in-json-file

Paul

On 8/17/23 15:26, this is what Chris Elvidge wrote:
> On 17/08/2023 17:51, Big Al wrote:
>> I'm chasing my tail I think.
>> I'm trying to automate in a bash shell the process of incrementing a version # by one digit. 2.23 to 2.24
>>
>> I've got the following script.   It may be the long way around but I've been piecing this step by step trying to get
>> the syntax right on each line.  So it's broken down that way.   It's the last line that is giving me the issue.
>>
>> OLDver=$(expr $(grep '"version"' manifest.json | awk -F\" '{ print $4 }'))  # grab the version with dot
>> leftOLD=${OLDver:0:1}
>> rightOLD=${OLDver:2:4}  #split the digits out for sed command
>> INCR=0.01
>> NEWver=$(echo $OLDver + $INCR | bc) # Increment the version number number to 2.24
>> leftNEW=${NEWver:0:1}
>> rightNEW=${NEWver:2:4}  #split the digits again
>>      # all this because sed will not substitute with periods unless escaped.
>>      # so I've split the digits out
>>      # but this last line does not work.
>> sed -i 's/$leftOLD\.$rightOLD/$leftNEW\.$rightNEW/' manifest.json
>>
>
> change the 's in the above line to "s
> single quotes stop the expansion of variables
>
>>
>> I've run this by clicking the shell script.  I've run the shell script from a terminal.  No errors anywhere.
>> I can paste these lines into terminal and run them, it doesn't work, but I can echo the last line:
>>      echo "sed -i 's/$leftOLD\.$rightOLD/$leftNEW\.$rightNEW/' manifest.json"
>> and I get:     sed -i 's/2\.23/2\.24/' manifest.json
>> which is what I want.
>> If I write out the sed
>>      sed -i 's/2\.23/2\.24/' manifest.json
>> it works.  Just not in the bash script.
>>
>> Anyone got an idea?  Some idiosyncrasy of Bash?
>>
>
>
You are the man!!! I knew there was some little item I was overlooking!
I knew it was possible, hell there isn't much linux can't do even in the lowly bash!
Thanks much.
--
Linux Mint 21.1 Cinnamon 5.6.8
Al

On 8/17/23 15:34, this is what Paul wrote:
> On 8/17/2023 12:51 PM, Big Al wrote:
>> I'm chasing my tail I think.
>> I'm trying to automate in a bash shell the process of incrementing a version # by one digit. 2.23 to 2.24
>>
>> I've got the following script.   It may be the long way around but I've been piecing this step by step trying to get the syntax right on each line.  So it's broken down that way.   It's the last line that is giving me the issue.
>>
>> OLDver=$(expr $(grep '"version"' manifest.json | awk -F\" '{ print $4 }'))  # grab the version with dot
>> leftOLD=${OLDver:0:1}
>> rightOLD=${OLDver:2:4}  #split the digits out for sed command
>> INCR=0.01
>> NEWver=$(echo $OLDver + $INCR | bc) # Increment the version number number to 2.24
>> leftNEW=${NEWver:0:1}
>> rightNEW=${NEWver:2:4}  #split the digits again
>>     # all this because sed will not substitute with periods unless escaped.
>>     # so I've split the digits out
>>     # but this last line does not work.
>> sed -i 's/$leftOLD\.$rightOLD/$leftNEW\.$rightNEW/' manifest.json
>>
>>
>> I've run this by clicking the shell script.  I've run the shell script from a terminal.  No errors anywhere.
>> I can paste these lines into terminal and run them, it doesn't work, but I can echo the last line:
>>     echo "sed -i 's/$leftOLD\.$rightOLD/$leftNEW\.$rightNEW/' manifest.json"
>> and I get:     sed -i 's/2\.23/2\.24/' manifest.json
>> which is what I want.
>> If I write out the sed
>>     sed -i 's/2\.23/2\.24/' manifest.json
>> it works.  Just not in the bash script.
>>
>> Anyone got an idea?  Some idiosyncrasy of Bash?
>>
>
> All I could find, is this for inspiration. I don't
> know how complex your problem really is (what cruft is in
> the file to prevent a solution from working).
>
> https://stackoverflow.com/questions/36402167/update-version-number-stored-in-json-file
>
> Paul
>
It was help by a mile!
That long verbose script of mine is a one liner. A suggestion in the link, modified for my needs.

awk -F'["]' -v OFS='"' '/"version":/{split($4,a,".");$4=a[1]"."a[2]+1};1' manifest.json > manifest2.json

and then a simple mv manifest.json2 manifest.json
--
Linux Mint 21.1 Cinnamon 5.6.8
Al