public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Filipe Rosset <filiperosset@fedoraproject.org>
To: git-commits@fedoraproject.org
Subject: [rpms/xschem] rawhide: update to 3.4.7 rhbz#2435198 and rhbz#2385746
Date: Mon, 29 Jun 2026 23:44:56 GMT [thread overview]
Message-ID: <178277669677.1.12440344993062078842.rpms-xschem-3f24bebb133c@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/xschem
Branch : rawhide
Commit : 3f24bebb133c2d619d178dd2a980927cd1519204
Author : Filipe Rosset <filiperosset@fedoraproject.org>
Date : 2026-06-29T20:43:56-03:00
Stats : +25/-20 in 2 file(s)
URL : https://src.fedoraproject.org/rpms/xschem/c/3f24bebb133c2d619d178dd2a980927cd1519204?branch=rawhide
Log:
update to 3.4.7 rhbz#2435198 and rhbz#2385746
Signed-off-by: Filipe Rosset <filiperosset@fedoraproject.org>
---
diff --git a/sources b/sources
index 35d0f9e..5946973 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (xschem-3.1.0.tar.gz) = 8f0fbc6844d8a3c4e4708b174998207b0b75395b09ab6f98e532dadf4d3bd7db96fe83f7e68e3d87601f10a4ff824c5b7aec642c403107379cd280081be6d155
+SHA512 (xschem-3.4.7.tar.gz) = 1f2cbc0b703c0101f2db62ad1bae32623699e3ae0c48f619b1c91ecae84161fabf28a0b1d744368e4b705bbde71933653e2ddb3cf378c2224aa00a1dc4f0ee84
diff --git a/xschem.spec b/xschem.spec
index c4d7f3c..ed0d487 100644
--- a/xschem.spec
+++ b/xschem.spec
@@ -1,9 +1,5 @@
-# xschem Package description for Fedora/Free Electronic Lab
-#
-%global rpm_has_recommends %(rpm --version | awk -e '{print ($3 > 4.12)}')
-#
Name: xschem
-Version: 3.1.0
+Version: 3.4.7
Release: %autorelease
Summary: Schematic capture and Netlisting EDA tool
@@ -11,24 +7,19 @@ License: GPL-2.0-or-later
URL: http://repo.hu/projects/xschem
Source0: http://repo.hu/projects/xschem/releases/xschem-%{version}.tar.gz
-BuildRequires: make
-BuildRequires: gcc
+BuildRequires: bison
+BuildRequires: flex
BuildRequires: gawk
-BuildRequires: flex, bison
-#BuildRequires: flex-devel
+BuildRequires: gcc
+BuildRequires: libjpeg-turbo-devel
+BuildRequires: make
+BuildRequires: pkgconfig(cairo-xcb)
+BuildRequires: pkgconfig(xpm)
BuildRequires: tcl-devel
BuildRequires: tk-devel
-BuildRequires: pkgconfig(xpm)
-BuildRequires: pkgconfig(cairo-xcb)
-#BuildRequires: cairo-devel
-#BuildRequires: xcb-util-devel
-
-%if %rpm_has_recommends
Recommends: %{name}-doc = %{version}-%{release}
-%endif
-
-#Requires: tcl, tk
-
+Requires: tcl
+Requires: tk
%description
%{name} is a schematic capture program, it allows creation of hierarchical
@@ -52,6 +43,16 @@ Documentation for %{name}.
%prep
%autosetup
+# Fix wrong line encoding (CRLF to LF)
+sed -i 's/\r$//' src/make_sym_lcc.awk
+
+# Remove shebang from non-executable script
+sed -i '1{\@^#!/@d}' src/make_sym_lcc.awk
+
+# Ensure LDFLAGS are passed when building rawtovcd to enable PIE/hardening
+sed -i 's/rawtovcd rawtovcd.o/rawtovcd rawtovcd.o $(LDFLAGS)/' src/Makefile.in
+
+
%build
./"configure" --CFLAGS="%{build_cflags}" --LDFLAGS="%{build_ldflags}" \
@@ -74,6 +75,10 @@ Documentation for %{name}.
%files doc
%{_docdir}/%{name}
+%exclude %{_docdir}/%{name}/AUTHORS
+%exclude %{_docdir}/%{name}/Changelog
+%exclude %{_docdir}/%{name}/README
+
%changelog
reply other threads:[~2026-06-29 23:44 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=178277669677.1.12440344993062078842.rpms-xschem-3f24bebb133c@fedoraproject.org \
--to=filiperosset@fedoraproject.org \
--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