Github messages for voidlinux
 help / color / mirror / Atom feed
From: realcharmer <realcharmer@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] qflipper: update to 1.2.2
Date: Sun, 05 Mar 2023 21:09:20 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42613@inbox.vuxu.org> (raw)

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

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

https://github.com/realcharmer/void-packages qflipper
https://github.com/void-linux/void-packages/pull/42613

qflipper: update to 1.2.2
32bit has been fixed upstream, so the patch is no longer needed.

Tagging the maintainer @Vaelatern

#### Testing the changes
- I tested the changes in this PR: **briefly**

#### Local build testing
- I built this PR locally for my native architecture, (x86_64)
- I built this PR locally for these architectures:
  - i686
  - i686-musl


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

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

From 400f2a383d4fc8a71674e9809cd398292e17b8d1 Mon Sep 17 00:00:00 2001
From: Emil Miler <em@0x45.cz>
Date: Sun, 5 Mar 2023 21:05:43 +0100
Subject: [PATCH] qflipper: update to 1.2.2

32bit has been fixed upstream, so the patch is no longer needed.
---
 srcpkgs/qflipper/patches/fix-build-32-bit.patch | 10 ----------
 srcpkgs/qflipper/template                       |  4 ++--
 2 files changed, 2 insertions(+), 12 deletions(-)
 delete mode 100644 srcpkgs/qflipper/patches/fix-build-32-bit.patch

diff --git a/srcpkgs/qflipper/patches/fix-build-32-bit.patch b/srcpkgs/qflipper/patches/fix-build-32-bit.patch
deleted file mode 100644
index cd93b8440b40..000000000000
--- a/srcpkgs/qflipper/patches/fix-build-32-bit.patch
+++ /dev/null
@@ -1,10 +0,0 @@
---- a/dfu/device/stm32wb55/infotable.h
-+++ b/dfu/device/stm32wb55/infotable.h
-@@ -52,6 +52,7 @@ struct FUSDeviceInfoTable
-     uint32_t  reserved2;
-     uint64_t  UID64;
-     uint16_t  deviceID;
-+    uint32_t  padding_ /* padding for 32 bits build */;
- };
- 
- struct DeviceInfoTable {
diff --git a/srcpkgs/qflipper/template b/srcpkgs/qflipper/template
index 8970f5f665ef..7e0dfda62c37 100644
--- a/srcpkgs/qflipper/template
+++ b/srcpkgs/qflipper/template
@@ -1,6 +1,6 @@
 # Template file for 'qflipper'
 pkgname=qflipper
-version=1.2.0
+version=1.2.2
 revision=1
 _nanopb_version=0.4.6
 create_wrksrc=yes
@@ -15,7 +15,7 @@ license="GPL-3.0-only"
 homepage="https://flipperzero.one"
 distfiles="https://github.com/flipperdevices/qFlipper/archive/refs/tags/${version}.tar.gz
  https://github.com/nanopb/nanopb/archive/refs/tags/${_nanopb_version}.tar.gz"
-checksum="d830c9f442e833957431bdd42f5711cb24d64e0d83976e35987cccbe046a3c8c
+checksum="486543a66fcf899073972d4f081f89a709a66628d71e9412c74be0a7a1fb79a7
  caa97d55fb9c98b4cfa0b069acd9657f706e9629af0baeaefcae0a0e8c4a64d2"
 
 post_extract() {

             reply	other threads:[~2023-03-05 20:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-05 20:09 realcharmer [this message]
2023-03-05 21:27 ` Vaelatern
2023-03-05 21:27 ` [PR PATCH] [Merged]: " 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-42613@inbox.vuxu.org \
    --to=realcharmer@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).