public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
To: git-commits@fedoraproject.org
Subject: [rpms/putty] epel8: Merge remote-tracking branch 'origin/rawhide' into epel8
Date: Mon, 01 Jun 2026 13:45:35 GMT [thread overview]
Message-ID: <178032153591.1.7925150025608809693.rpms-putty-67e4812bd52b@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/putty
Branch : epel8
Commit : 67e4812bd52b773be7c7083e6737fb296aa47092
Author : Jaroslav Škarvada <jskarvad@redhat.com>
Date : 2026-06-01T15:31:13+02:00
Stats : +33/-4 in 2 file(s)
URL : https://src.fedoraproject.org/rpms/putty/c/67e4812bd52b773be7c7083e6737fb296aa47092?branch=epel8
Log:
Merge remote-tracking branch 'origin/rawhide' into epel8
---
diff --git a/putty.spec b/putty.spec
index 228496e..6027b80 100644
--- a/putty.spec
+++ b/putty.spec
@@ -1,5 +1,5 @@
Name: putty
-Version: 0.81
+Version: 0.84
Release: 1%{?dist}
Summary: SSH, Telnet and Rlogin client
License: MIT
@@ -22,6 +22,8 @@ BuildRequires: gcc
BuildRequires: make
BuildRequires: cmake
Requires: hicolor-icon-theme
+# https://bugzilla.redhat.com/show_bug.cgi?id=2442271
+Requires: gdk-pixbuf2-modules-extra
%description
Putty is a SSH, Telnet & Rlogin client - this time for Linux.
@@ -37,8 +39,7 @@ export CFLAGS="%{build_cflags} -DNOT_X_WINDOWS -Wno-error=unused-function"
%cmake
%cmake_build
make -C icons putty-48.png
-cd %{__cmake_builddir}
-make -C doc
+%cmake_build -t doc
%install
%cmake_install
@@ -65,6 +66,34 @@ install -m644 -D -p %{SOURCE3} %{buildroot}%{_metainfodir}/uk.org.greenend.chiar
%{_metainfodir}/uk.org.greenend.chiark.sgtatham.putty.metainfo.xml
%changelog
+* Mon May 25 2026 Jaroslav Škarvada <jskarvad@redhat.com> - 0.84-1
+- New version
+ Resolves: rhbz#2480724
+
+* Mon Mar 02 2026 Jaroslav Škarvada <jskarvad@redhat.com> - 0.83-4
+- Fixed invisible login prompt
+ Resolves: rhbz#2442271
+
+* Sat Jan 17 2026 Fedora Release Engineering <releng@fedoraproject.org> - 0.83-3
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_44_Mass_Rebuild
+
+* Fri Jul 25 2025 Fedora Release Engineering <releng@fedoraproject.org> - 0.83-2
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_43_Mass_Rebuild
+
+* Mon Mar 10 2025 Jaroslav Škarvada <jskarvad@redhat.com> - 0.83-1
+- New version
+ Resolves: rhbz#2344452
+
+* Sat Jan 18 2025 Fedora Release Engineering <releng@fedoraproject.org> - 0.82-2
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_42_Mass_Rebuild
+
+* Thu Nov 28 2024 Jaroslav Škarvada <jskarvad@redhat.com> - 0.82-1
+- New version
+ Resolves: rhbz#2329243
+
+* Fri Jul 19 2024 Fedora Release Engineering <releng@fedoraproject.org> - 0.81-2
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_41_Mass_Rebuild
+
* Wed Apr 17 2024 Jaroslav Škarvada <jskarvad@redhat.com> - 0.81-1
- New version
Resolves: rhbz#2275179
diff --git a/sources b/sources
index 8b42dd2..131d2ee 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (putty-0.81.tar.gz) = d86f2fd0e126b18275d58cf64334b3b27c450899a1c2be2502de9faa2ef58f7fc8efc5d45f25c8395623f1e21917aa02407343bb2fee44c4c00b9f81267d5ecd
+SHA512 (putty-0.84.tar.gz) = 647c84490c01f8c0f9cf02f565081d80ea2ea4fb90207cfb2fbe13ba5e8c3cea7c4807504363d3d3a851df5edb6087c3b39084820bf20e818dd551db54af0765
reply other threads:[~2026-06-01 13:45 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=178032153591.1.7925150025608809693.rpms-putty-67e4812bd52b@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