Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: psmisc: update checksum
Date: Sun, 09 Feb 2020 15:35:08 +0100	[thread overview]
Message-ID: <20200209143508.n-CDhNTzx8UCBTNB1UqD09mJRnhliDB1KkuKgLmXn7I@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18823@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 555 bytes --]

New comment by ailiop-git on void-packages repository

https://github.com/void-linux/void-packages/pull/18823#issuecomment-583852130

Comment:
> @ailiop-git this is not simple as it sounds. If a checksum changed could mean malware, be careful

Totally agree (plus sourceforge has a history with malware..), which is why I'm trying to get rid of the pkg altogether. Unfortunately I haven't kept the previous two tarballs from the same release that changed cksums, in order to run a diff. I'll try to ping the upstream author anyway to see if he's aware.

      parent reply	other threads:[~2020-02-09 14:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18823@inbox.vuxu.org>
2020-02-07 18:31 ` voidlinux-github
2020-02-07 18:46 ` voidlinux-github
2020-02-07 19:21 ` voidlinux-github
2020-02-07 20:04 ` voidlinux-github
2020-02-07 20:11 ` voidlinux-github
2020-02-07 20:44 ` voidlinux-github
2020-02-07 20:54 ` voidlinux-github
2020-02-07 20:54 ` voidlinux-github
2020-02-07 20:55 ` voidlinux-github
2020-02-08 14:28 ` voidlinux-github
2020-02-08 14:29 ` voidlinux-github
2020-02-09 13:57 ` voidlinux-github
2020-02-09 14:01 ` voidlinux-github
2020-02-09 14:03 ` voidlinux-github
2020-02-09 14:35 ` voidlinux-github [this message]

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=20200209143508.n-CDhNTzx8UCBTNB1UqD09mJRnhliDB1KkuKgLmXn7I@z \
    --to=voidlinux-github@inbox.vuxu.org \
    --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).