gping: update to 1.2.6

[cinerea0]

General

• This is a new package and it conforms to the quality requirements

Have the results of the proposed changes been tested?

• I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
• I generally don't use the affected packages but briefly tested this PR

[paper42]

I didn't see this update because our update check is broken, would you mind looking into this? Otherwise lgtm, thanks!

[cinerea0]

Upstream started naming their releases "gping-${version}" instead of just "${version}" two releases after the last time you updated the package. Since xbps-src update-check is specific when it comes to the URL needed to check for updates, it didn't show anything other than the update to 1.2.1. The distfile now uses upstream's new naming convention, so this problem shouldn't arise again for this package. However, I think there are potentially many more packages with this same problem since the list of available updates at https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt doesn't include the "NO VERSION found" errors that tipped me off to the exact same name change situation having happened to watchexec.

[paper42]

The distfile now uses upstream's new naming convention, so this problem shouldn't arise again for this package.

It is not, you can see the whole list of versions detected by update-check when XBPS_UPDATE_CHECK_VERBOSE=y is set.

Putting pattern="gping-v\K[0-9.]+(?=.tar.gz)" to the update file seems to help.

However, I think there are potentially many more packages with this same problem since the list of available updates at alpha.de.repo.voidlinux.org/void-updates/void-updates.txt doesn't include the "NO VERSION found" errors that tipped me off to the exact same name change situation having happened to watchexec.

That's probably correct and we should fix them when we find them. In this case, versions were detected, but only until 1.2.1.

[cinerea0]

@paper42 The update file has been added!