From: mhmdanas <mhmdanas@users.noreply.github.com> To: ml@inbox.vuxu.org Subject: [PR PATCH] freetds: update to 1.3.11. Date: Thu, 02 Jun 2022 14:30:39 +0200 [thread overview] Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37386@inbox.vuxu.org> (raw) [-- Attachment #1: Type: text/plain, Size: 1217 bytes --] There is a new pull request by mhmdanas against master on the void-packages repository https://github.com/mhmdanas/void-packages freetds-1.3.11 https://github.com/void-linux/void-packages/pull/37386 freetds: update to 1.3.11. <!-- Uncomment relevant sections and delete options which are not applicable --> #### Testing the changes - I tested the changes in this PR: **NO** <!-- #### New package - This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO** --> <!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration and test at least one native build and, if supported, at least one cross build. Ignore this section if this PR is not skipping CI. --> <!-- #### Local build testing - I built this PR locally for my native architecture, (ARCH-LIBC) - I built this PR locally for these architectures (if supported. mark crossbuilds): - aarch64-musl - armv7l - armv6l-musl --> A patch file from https://github.com/void-linux/void-packages/pull/37386.patch is attached [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #2: github-pr-freetds-1.3.11-37386.patch --] [-- Type: text/x-diff, Size: 1117 bytes --] From 4aece35b9ebc4103827f725958a20c769686dc69 Mon Sep 17 00:00:00 2001 From: mhmdanas <triallax@tutanota.com> Date: Thu, 2 Jun 2022 15:32:51 +0300 Subject: [PATCH] freetds: update to 1.3.11. --- srcpkgs/freetds/template | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/srcpkgs/freetds/template b/srcpkgs/freetds/template index 027a4b539d81..9adee3a5053b 100644 --- a/srcpkgs/freetds/template +++ b/srcpkgs/freetds/template @@ -1,6 +1,6 @@ # Template file for 'freetds' pkgname=freetds -version=1.3.10 +version=1.3.11 revision=1 build_style=gnu-configure configure_args="--sysconfdir=/etc/freetds --with-unixodbc=${XBPS_CROSS_BASE}/usr" @@ -13,7 +13,7 @@ license="LGPL-2.0-or-later" homepage="https://www.freetds.org/" changelog="https://raw.githubusercontent.com/FreeTDS/freetds/master/NEWS.md" distfiles="https://www.freetds.org/files/stable/freetds-${version}.tar.bz2" -checksum=819aeaf7feaa1bfdbc2213f81ad067061dd4c56245996a4e2b529d87296a5d63 +checksum=31ab43617cb096788975eb2b5503b32893f1faca2dabe31543b8c09a8d9d1b8a # Some tests require connection to a server. make_check=no
next reply other threads:[~2022-06-02 12:30 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-02 12:30 mhmdanas [this message] 2022-06-23 13:12 ` [PR PATCH] [Updated] " mhmdanas 2022-06-23 14:46 ` [PR PATCH] [Updated] freetds: update to 1.3.12 mhmdanas
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-37386@inbox.vuxu.org \ --to=mhmdanas@users.noreply.github.com \ --cc=ml@inbox.vuxu.org \ --subject='Re: [PR PATCH] freetds: update to 1.3.11.' \ /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
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).