From: cinerea0 <cinerea0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: gping: update to 1.2.6
Date: Wed, 27 Oct 2021 16:41:22 +0200 [thread overview]
Message-ID: <20211027144122.NDcDVn-zRMLL-XTfXrAkyGSiZxqlgHOQ6kywkyfvPGo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33773@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 873 bytes --]
New comment by cinerea0 on void-packages repository
https://github.com/void-linux/void-packages/pull/33773#issuecomment-952999344
Comment:
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`.
next prev parent reply other threads:[~2021-10-27 14:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 23:15 [PR PATCH] " cinerea0
2021-10-27 14:41 ` cinerea0 [this message]
2021-10-28 22:26 ` paper42
2021-10-29 4:19 ` [PR PATCH] [Updated] " cinerea0
2021-10-30 1:06 ` cinerea0
2021-10-30 8:49 ` [PR PATCH] [Merged]: " paper42
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211027144122.NDcDVn-zRMLL-XTfXrAkyGSiZxqlgHOQ6kywkyfvPGo@z \
--to=cinerea0@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).