Github messages for voidlinux
 help / color / mirror / Atom feed
From: meator <meator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] libisofs: update to 1.5.4 + fix links.
Date: Wed, 08 Sep 2021 21:05:59 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32878@inbox.vuxu.org> (raw)

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

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

https://github.com/meator/void-packages libisofs
https://github.com/void-linux/void-packages/pull/32878

libisofs: update to 1.5.4 + fix links.
<!-- Mark items with [x] where applicable -->

#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [x] I generally don't use the affected packages but briefly tested this PR

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!-- 
#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] 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/32878.patch is attached

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

From 722a439f147a27f39e8a0f5a571c64d7bcc8a4c9 Mon Sep 17 00:00:00 2001
From: meator <meator.dev@gmail.com>
Date: Wed, 8 Sep 2021 21:02:09 +0200
Subject: [PATCH] libisofs: update to 1.5.4 + fix links.

---
 srcpkgs/libisofs/template | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/srcpkgs/libisofs/template b/srcpkgs/libisofs/template
index 70c52d45afad..38a8d76d8108 100644
--- a/srcpkgs/libisofs/template
+++ b/srcpkgs/libisofs/template
@@ -1,6 +1,6 @@
 # Template file for 'libisofs'
 pkgname=libisofs
-version=1.5.2
+version=1.5.4
 revision=1
 build_style=gnu-configure
 configure_args="--enable-libacl --enable-xattr"
@@ -8,9 +8,9 @@ makedepends="acl-devel zlib-devel"
 short_desc="Library to create ISO9660 images"
 maintainer="Orphaned <orphan@voidlinux.org>"
 license="GPL-2.0-or-later"
-homepage="http://www.libburnia-project.org"
-distfiles="http://files.libburnia-project.org/releases/${pkgname}-${version}.tar.gz"
-checksum=ef5a139600b3e688357450e52381e40ec26a447d35eb8d21524598c7b1675500
+homepage="https://dev.lovelyhq.com/libburnia/web/wiki/Libisofs"
+distfiles="https://files.libburnia-project.org/releases/${pkgname}-${version}.tar.gz"
+checksum=aaa0ed80a7501979316f505b0b017f29cba0ea5463b751143bad2c360215a88e
 
 libisofs-devel_package() {
 	depends="${makedepends} libisofs>=${version}_${revision}"

             reply	other threads:[~2021-09-08 19:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-08 19:05 meator [this message]
2021-09-09 19:17 ` ericonr
2021-09-10 17:19 ` [PR PATCH] [Updated] " meator
2021-09-10 17:22 ` meator
2021-09-10 18:00 ` ericonr
2021-09-10 18:00 ` [PR PATCH] [Merged]: " ericonr

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-32878@inbox.vuxu.org \
    --to=meator@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).