public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Kevin Kofler <Kevin@tigcc.ticalc.org>
To: git-commits@fedoraproject.org
Subject: [rpms/kig] epel10: fix pykig shebang sed invocation, again (#1840510)
Date: Tue, 04 Aug 2026 19:44:54 GMT [thread overview]
Message-ID: <178587269413.1.11696766868324379269.rpms-kig-6ea4131dbf59@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/kig
Branch : epel10
Commit : 6ea4131dbf59fdd8233b0c8db491946f0748f6cf
Author : Kevin Kofler <Kevin@tigcc.ticalc.org>
Date : 2020-05-27T12:11:12+02:00
Stats : +5/-2 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/kig/c/6ea4131dbf59fdd8233b0c8db491946f0748f6cf?branch=epel10
Log:
fix pykig shebang sed invocation, again (#1840510)
* Wed May 27 2020 Kevin Kofler <Kevin@tigcc.ticalc.org> - 20.04.1-2
- fix pykig shebang sed invocation, again (#1840510)
Changing the sed line was just wrong. The reason my sed line did not
work as is for your 19.12.x builds is because the "Port pykig to python
3" patch was NOT upstreamed into 19.12.x, only into 20.04.x, so it was
wrong to drop the patch in the 19.12.x builds.
---
diff --git a/kig.spec b/kig.spec
index e5495d2..961a293 100644
--- a/kig.spec
+++ b/kig.spec
@@ -4,7 +4,7 @@
Name: kig
Summary: Interactive Geometry
Version: 20.04.1
-Release: 1%{?dist}
+Release: 2%{?dist}
License: GPLv2+
URL: https://cgit.kde.org/%{name}.git
@@ -61,7 +61,7 @@ Conflicts: kdeedu-math < 4.7.0-10
%prep
%autosetup -p1
-sed -ie "s|^#!/usr/bin/env python|#!%{__python3}|" pykig/pykig.py
+sed -ie "s|^#!/usr/bin/env python3|#!%{__python3}|" pykig/pykig.py
%build
@@ -110,6 +110,9 @@ desktop-file-validate %{buildroot}%{_kf5_datadir}/applications/org.kde.%{name}.d
%changelog
+* Wed May 27 2020 Kevin Kofler <Kevin@tigcc.ticalc.org> - 20.04.1-2
+- fix pykig shebang sed invocation, again (#1840510)
+
* Tue May 26 2020 Rex Dieter <rdieter@fedoraproject.org> - 20.04.1-1
- 20.04.1
reply other threads:[~2026-08-04 19: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=178587269413.1.11696766868324379269.rpms-kig-6ea4131dbf59@fedoraproject.org \
--to=kevin@tigcc.ticalc.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