public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Artur Frenszek-Iwicki <fedora@svgames.pl>
To: git-commits@fedoraproject.org
Subject: [rpms/lhasa] f44: Update to v0.6.0
Date: Thu, 18 Jun 2026 12:29:01 GMT [thread overview]
Message-ID: <178178574179.1.2102216619483446901.rpms-lhasa-5413adcda5f1@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/lhasa
Branch : f44
Commit : 5413adcda5f1b9833129f13ecbd1c9fc08323f43
Author : Artur Frenszek-Iwicki <fedora@svgames.pl>
Date : 2026-06-18T13:37:00+02:00
Stats : +33/-5 in 4 file(s)
URL : https://src.fedoraproject.org/rpms/lhasa/c/5413adcda5f1b9833129f13ecbd1c9fc08323f43?branch=f44
Log:
Update to v0.6.0
---
diff --git a/.gitignore b/.gitignore
index 0cadf39..5bdd03f 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,2 +1,3 @@
/lhasa-v0.4.0.tar.gz
/lhasa-v0.5.0.tar.gz
+/lhasa-v0.6.0.tar.gz
diff --git a/0000-no-O0-for-tests.patch b/0000-no-O0-for-tests.patch
new file mode 100644
index 0000000..316f23c
--- /dev/null
+++ b/0000-no-O0-for-tests.patch
@@ -0,0 +1,19 @@
+--- lhasa-0.6.0--orig/configure.ac 2026-06-18 00:19:23.000000000 +0200
++++ lhasa-0.6.0/configure.ac 2026-06-18 00:43:12.478120357 +0200
+@@ -28,14 +28,14 @@
+ fi
+
+ TEST_CFLAGS="-DTEST_BUILD"
+
+-# Turn on all warnings for gcc. Turn off optimisation for the test build.
++# Turn on all warnings for gcc.
+
+ if $is_gcc; then
+ WARNINGS="-Wall -Wsign-compare"
+ CFLAGS="$CFLAGS $WARNINGS"
+- TEST_CFLAGS="$TEST_CFLAGS $WARNINGS -O0"
++ TEST_CFLAGS="$CFLAGS $TEST_CFLAGS $WARNINGS"
+ fi
+
+ # Support for coverage analysis via gcov:
+
diff --git a/lhasa.spec b/lhasa.spec
index 530927a..30812e1 100644
--- a/lhasa.spec
+++ b/lhasa.spec
@@ -2,12 +2,19 @@ Name: lhasa
Summary: Free Software LHA implementation
License: ISC
-Version: 0.5.0
+Version: 0.6.0
Release: 1%{?dist}
URL: https://fragglet.github.io/lhasa/
Source0: https://github.com/fragglet/lhasa/archive/v%{version}/%{name}-v%{version}.tar.gz
+# Upstream builds tests with a minimal set of compiler flags, ignoring CFLAGS.
+# It also uses -O0 for the tests, which conflicts with Fedora's code hardening:
+# #warning _FORTIFY_SOURCE requires compiling with optimization (-O) [-Wcpp]
+#
+# Use normal CFLAGS for tests and remove the -O0 switch.
+Patch0: 0000-no-O0-for-tests.patch
+
BuildRequires: autoconf
BuildRequires: automake
BuildRequires: doxygen
@@ -66,9 +73,7 @@ for Lhasa, the free software LHA implementation library.
%prep
-%autosetup
-sed -i configure.ac \
- -e 's|TEST_CFLAGS="-DTEST_BUILD"|TEST_CFLAGS="$CFLAGS -DTEST_BUILD"|g'
+%autosetup -p1
%build
@@ -112,6 +117,9 @@ cp -a doc/html %{buildroot}%{_pkgdocdir}
%changelog
+* Thu Jun 18 2026 Artur Frenszek-Iwicki <fedora@svgames.pl> - 0.6.0-1
+- Update to v0.6.0
+
* Tue Jan 20 2026 Artur Frenszek-Iwicki <fedora@svgames.pl> - 0.5.0-1
- Update to v0.5.0
diff --git a/sources b/sources
index f7f338e..a4c0ad4 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (lhasa-v0.5.0.tar.gz) = 021de4f341c211548e6ae0ec9e69c5423bae8ef368eb28490ff0de6a5be8d77979e8b4808626e8212928a55fa67bf296df7cf0b9832387dc45155fe173cdece9
+SHA512 (lhasa-v0.6.0.tar.gz) = 1803770700be800b3743504395183d3788d92e15f1d970419545001d7a1614fd9bd1df59fc62391cf1e3738fe7e1a52f728d22fea39ca79dbc1215bd7a706aed
reply other threads:[~2026-06-18 12:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=178178574179.1.2102216619483446901.rpms-lhasa-5413adcda5f1@fedoraproject.org \
--to=fedora@svgames.pl \
--cc=git-commits@fedoraproject.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