Make PADD compatible with non-master branches #232
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR allows to run
PADDif non-master branches are used.The issue so far was that PADD used fixed arguments when obtaining the version information via
pihole -v. If one was using custom branches, the version information do not appear (nor not at the spot) where they are expected. Therefore./piholeVersioncould contained special characters (e.g.() which were parsed by PADD and made the script fail.This PR does
xx_version_latestis always the last column inpihole -v(therefore using awk '{print $(NF)}`)xx_versionstring matches[0-9]or[0-9].[0-9]+via the RegEX2.1) if not, set the version to
N/Avin the output but the version string before printing (avoidsvN/Abeing printed`P.S. as we are try to be POSIX compliant, we can't use
=~for RegEx matching but usegrep -EinsteadMaster:

Dev:

By submitting this pull request, I confirm the following:
git rebase)