Github messages for voidlinux
 help / color / mirror / Atom feed
From: yoshiyoshyosh <yoshiyoshyosh@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] disklow: workaround distfiles cert error.
Date: Fri, 28 Apr 2023 20:38:44 +0200	[thread overview]
Message-ID: <20230428183844.-RerEn-71XTSeUADeW9sF3VE8BNDEmQxBB5vFHZpnN4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43648@inbox.vuxu.org>

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

There is an updated pull request by yoshiyoshyosh against master on the void-packages repository

https://github.com/yoshiyoshyosh/void-packages disklow-distfiles
https://github.com/void-linux/void-packages/pull/43648

disklow: workaround distfiles cert error.
#### Testing the changes
- I tested the changes in this PR: **YES**

#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)

Addresses #42403.
I tried finding any precedence for an alive distfile but with broken certs and could only find #7512. Don't know if this is still the right way to workaround this 4 years later.

A patch file from https://github.com/void-linux/void-packages/pull/43648.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-disklow-distfiles-43648.patch --]
[-- Type: text/x-diff, Size: 1118 bytes --]

From 1d59ea429079ef578efdf713d3f4b711d6169024 Mon Sep 17 00:00:00 2001
From: yosh <yosh-git@riseup.net>
Date: Thu, 27 Apr 2023 11:09:03 -0400
Subject: [PATCH] disklow: workaround distfiles cert error.

---
 srcpkgs/disklow/template | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/srcpkgs/disklow/template b/srcpkgs/disklow/template
index 1e0ccd108ffc..b5e9aae8efb2 100644
--- a/srcpkgs/disklow/template
+++ b/srcpkgs/disklow/template
@@ -1,7 +1,7 @@
 # Template file for 'disklow'
 pkgname=disklow
 version=1.2
-revision=1
+revision=2
 depends="perl-Filesys-Df perl-Config-General perl-Mail-Sendmail
  perl-Net-SMTP-SSL perl-Authen-SASL"
 short_desc="Fine grained disk space reporting with emphasis on mail functionality"
@@ -11,6 +11,9 @@ homepage="https://loomsday.co.nz/development?id=linuxutils"
 distfiles="https://loomsday.co.nz/sources/disklow-${version}.tar.gz"
 checksum=05b9f510278147f24b0556eb745ff2b71c98c00fedf33434744fbe76ec884c26
 
+# xbps-fetch cannot verify this cert
+fetch_cmd="env SSL_NO_VERIFY_PEER=1 $XBPS_FETCH_CMD"
+
 do_install() {
 	vbin  disklow
 	vconf disklow.conf

  parent reply	other threads:[~2023-04-28 18:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-27 15:19 [PR PATCH] " yoshiyoshyosh
2023-04-27 19:07 ` Duncaen
2023-04-27 19:07 ` Duncaen
2023-04-27 19:08 ` Duncaen
2023-04-27 19:32 ` yoshiyoshyosh
2023-04-27 19:32 ` yoshiyoshyosh
2023-04-27 19:54 ` yoshiyoshyosh
2023-04-28 17:39 ` classabbyamp
2023-04-28 17:39 ` classabbyamp
2023-04-28 17:40 ` classabbyamp
2023-04-28 18:38 ` yoshiyoshyosh [this message]
2023-04-30  0:34 ` [PR PATCH] [Merged]: " classabbyamp

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=20230428183844.-RerEn-71XTSeUADeW9sF3VE8BNDEmQxBB5vFHZpnN4@z \
    --to=yoshiyoshyosh@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).