public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
To: git-commits@fedoraproject.org
Subject: [rpms/i3] epel9: Obsolete i3-gaps (got merged into i3 with 4.22)
Date: Tue, 04 Aug 2026 13:35:41 GMT [thread overview]
Message-ID: <178585054122.1.18318149326315737790.rpms-i3-d81eb788e22d@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/i3
Branch : epel9
Commit : d81eb788e22d69ffd697f6b00a4de07a978f6722
Author : Dan Čermák <dan.cermak@cgc-instruments.com>
Date : 2023-01-03T00:38:42+01:00
Stats : +6/-2 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/i3/c/d81eb788e22d69ffd697f6b00a4de07a978f6722?branch=epel9
Log:
Obsolete i3-gaps (got merged into i3 with 4.22)
---
diff --git a/i3.spec b/i3.spec
index ce75fc1..9a2fc58 100644
--- a/i3.spec
+++ b/i3.spec
@@ -13,6 +13,10 @@ Source4: fedora-i3-config
Source5: fedora-i3-keycodes
Patch0: 0001-Correct-dex-binary-name-dex-dex-autostart.patch
+# i3-gaps was merged into i3 with 4.22
+Provides: i3-gaps = %{version}-%{release}
+Obsoletes: i3-gaps < 4.22-1
+
BuildRequires: gcc
# need at least 0.53 to build the documentation
BuildRequires: meson >= 0.53
@@ -107,7 +111,7 @@ Please be aware that i3 is primarily targeted at advanced users and developers.
%package config
Summary: Upstream configuration for %{name}
BuildArch: noarch
-Requires: (%{name} = %{version}-%{release} or %{name}-gaps)
+Requires: %{name} = %{version}-%{release}
Recommends: rxvt-unicode
Conflicts: %{name}-config-fedora
@@ -118,7 +122,7 @@ This is the upstream/vanilla configuration file of i3.
RemovePathPostfixes: .fedora
Summary: Configuration of %{name} for the Fedora i3 Spin
BuildArch: noarch
-Requires: (%{name} = %{version}-%{release} or %{name}-gaps)
+Requires: %{name} = %{version}-%{release}
Recommends: xfce4-terminal
# the Fedora branded config file uses xdg-user-dirs-update indirectly via `dex-autostart --autostart`
Recommends: xdg-user-dirs
reply other threads:[~2026-08-04 13:35 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=178585054122.1.18318149326315737790.rpms-i3-d81eb788e22d@fedoraproject.org \
--to=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