Github messages for voidlinux
 help / color / mirror / Atom feed
From: Vaelatern <Vaelatern@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] PrusaSlicer: update to 2.6.1.
Date: Fri, 20 Oct 2023 19:35:22 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46799@inbox.vuxu.org> (raw)

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

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

https://github.com/Vaelatern/void-packages prusa-slicer-2.6.1
https://github.com/void-linux/void-packages/pull/46799

PrusaSlicer: update to 2.6.1.
draft, for CI

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

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-prusa-slicer-2.6.1-46799.patch --]
[-- Type: text/x-diff, Size: 1144 bytes --]

From c433eaf58d47746c79c66c1af0686fa520c64b10 Mon Sep 17 00:00:00 2001
From: Toyam Cox <Vaelatern@voidlinux.org>
Date: Fri, 20 Oct 2023 13:28:01 -0400
Subject: [PATCH] PrusaSlicer: update to 2.6.1.

---
 srcpkgs/PrusaSlicer/template | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/PrusaSlicer/template b/srcpkgs/PrusaSlicer/template
index c28c2d707c229..34fb50cfe3b8e 100644
--- a/srcpkgs/PrusaSlicer/template
+++ b/srcpkgs/PrusaSlicer/template
@@ -1,7 +1,7 @@
 # Template file for 'PrusaSlicer'
 pkgname=PrusaSlicer
-version=2.5.2
-revision=3
+version=2.6.1
+revision=1
 build_style=cmake
 build_helper="qemu cmake-wxWidgets-gtk3"
 # Pre-Compiled Headers seems to be slower
@@ -17,7 +17,7 @@ maintainer="Orphaned <orphan@voidlinux.org>"
 license="GPL-3.0-or-later"
 homepage="https://www.prusa3d.com/prusaslicer/"
 distfiles="https://github.com/prusa3d/Prusaslicer/archive/version_${version}.tar.gz"
-checksum=e58278067b9d49a42dc9bb02b74307b3cb365bb737f28e246ca8c6f466095d6b
+checksum=516eb34835cd8f301e639fa77f9f12297300ce012ebc3b7b6a73275c6245011d
 
 CXXFLAGS="-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64"
 

             reply	other threads:[~2023-10-20 17:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-20 17:35 Vaelatern [this message]
2023-10-20 18:05 ` [PR PATCH] [Updated] " Vaelatern
2023-10-20 18:46 ` Vaelatern
2023-10-20 19:18 ` Vaelatern
2023-10-23  0:27 ` Vaelatern
2023-10-23  2:17 ` Vaelatern
2023-10-23  3:06 ` Vaelatern
2023-10-23 22:13 ` Vaelatern
2023-10-23 22:19 ` agausmann
2023-11-01  6:38 ` [PR PATCH] [Updated] " Vaelatern
2023-11-17  4:31 ` Vaelatern
2023-11-17  4:32 ` Vaelatern
2024-02-16  1:44 ` github-actions
2024-02-25 22:17 ` [PR PATCH] [Updated] " Vaelatern
2024-04-17 21:49 ` Vaelatern
2024-04-17 21:50 ` Vaelatern
2024-04-18 17:01 ` Vaelatern

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