Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [PR PATCH] tectonic: remove hardcoded versions
Date: Sun, 15 Sep 2019 01:46:05 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14463@inbox.vuxu.org> (raw)

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

There is a new pull request by concatime against master on the void-packages repository

https://github.com/concatime/void-packages tectonic-openssl-fix
https://github.com/void-linux/void-packages/pull/14463

tectonic: remove hardcoded versions
This way, we don’t need to change theses numbers at each breaking change from libressl,
because cargo will pick the latest openssl and openssl-sys.

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

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-tectonic-openssl-fix-14463.patch --]
[-- Type: text/x-diff, Size: 1500 bytes --]

From 0686bf9d2052da292d37afa479e19dd12de64967 Mon Sep 17 00:00:00 2001
From: Issam Maghni <me@concati.me>
Date: Sat, 14 Sep 2019 19:45:47 -0400
Subject: [PATCH] tectonic: remove hardcoded versions

---
 srcpkgs/tectonic/template | 13 +++++++++++--
 1 file changed, 11 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/tectonic/template b/srcpkgs/tectonic/template
index 19954ca6d7a..effe33ce097 100644
--- a/srcpkgs/tectonic/template
+++ b/srcpkgs/tectonic/template
@@ -13,9 +13,18 @@ changelog="https://raw.githubusercontent.com/tectonic-typesetting/tectonic/maste
 distfiles="https://github.com/tectonic-typesetting/${pkgname}/archive/v${version}.tar.gz"
 checksum=e700dc691dfd092adfe098b716992136343ddfac5eaabb1e8cfae4e63f8454c7
 
+# REMOVE THIS SECTION ON NEXT VERSION
 pre_build() {
-	cargo update --package openssl-sys --precise 0.9.46
-	cargo update --package openssl --precise 0.10.22
+	# openssl-sys v0.9.39
+	# This crate is only compatible with OpenSSL 1.0.1 through 1.1.1, or LibreSSL 2.5
+	# through 2.8.1, but a different version of OpenSSL was found. The build is now aborting
+	# due to this version mismatch.
+	# openssl 0.10.15
+	# error[E0432]: unresolved imports `ffi::SSLv23_method`, `ffi::DTLSv1_method`
+	# error[E0432]: unresolved imports `ffi::SSLEAY_VERSION`, `ffi::SSLEAY_CFLAGS`,
+	# `ffi::SSLEAY_BUILT_ON`, `ffi::SSLEAY_PLATFORM`, `ffi::SSLEAY_DIR`, `ffi::SSLeay`,
+	# `ffi::SSLeay_version`
+	cargo update --package openssl --package openssl-sys
 }
 
 post_install() {

             reply	other threads:[~2019-09-14 23:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-14 23:46 voidlinux-github [this message]
2019-09-15 12:00 ` voidlinux-github
2019-09-15 15:31 ` voidlinux-github
2019-09-15 15:45 ` [PR PATCH] [Updated] " voidlinux-github
2019-09-15 15:45 ` voidlinux-github
2019-09-15 16:07 ` voidlinux-github
2019-09-15 16:10 ` voidlinux-github
2019-09-15 16:11 ` voidlinux-github
2019-09-15 20:18 ` [PR PATCH] [Closed]: " voidlinux-github
2019-09-15 20:18 ` voidlinux-github

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14463@inbox.vuxu.org \
    --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).