public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Gwyn Ciesla <limburgher@gmail.com>
To: git-commits@fedoraproject.org
Subject: [rpms/transmission] epel10: 2.94
Date: Mon, 20 Jul 2026 20:37:34 GMT	[thread overview]
Message-ID: <178457985418.1.1470017051664501541.rpms-transmission-8c55005ddcc1@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/transmission
Branch : epel10
Commit : 8c55005ddcc10f233e429f6e0fbe24cf98745ec8
Author : Gwyn Ciesla <limburgher@gmail.com>
Date   : 2018-05-01T19:46:36-05:00
Stats  : +5/-7 in 3 file(s)
URL    : https://src.fedoraproject.org/rpms/transmission/c/8c55005ddcc10f233e429f6e0fbe24cf98745ec8?branch=epel10

Log:
2.94

---
diff --git a/.gitignore b/.gitignore
index c2b0678..f79b335 100644
--- a/.gitignore
+++ b/.gitignore
@@ -24,3 +24,4 @@ transmission-2.04.tar.xz
 /transmission-2.90.tar.xz
 /transmission-2.92.tar.xz
 /transmission-2.93.tar.xz
+/transmission-2.94.tar.xz

diff --git a/sources b/sources
index c1f59ce..802a15c 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (transmission-2.93.tar.xz) = 7565893f67fc10f1b683814fa4d365d841ec833bc8dfdab731432fe68f1a38daeb4c9100653763f16bfb4336fba11c9b0b9730a9817e17a140704a7c4aa5c087
+SHA512 (transmission-2.94.tar.xz) = ee411743940f2897aa0bbc351ce79f11d860075d2e9e399d60301eae8cfc453e20426ef553fc62ee43019a07c052d512f5d7972cc4411fb57b1312c2c1558da7

diff --git a/transmission.spec b/transmission.spec
index 03540f1..eed3a33 100644
--- a/transmission.spec
+++ b/transmission.spec
@@ -1,7 +1,7 @@
 %global _hardened_build 1
 
 Name:           transmission
-Version:        2.93
+Version:        2.94
 Release:        2%{?dist}
 Summary:        A lightweight GTK+ BitTorrent client
 # See COPYING. This licensing situation is... special.
@@ -39,7 +39,6 @@ back-end.
 
 %package common
 Summary:       Transmission common files
-Group:         Applications/Internet
 Conflicts:     transmission < 1.80-0.3.b4
 %description common
 Common files for Transmission BitTorrent client sub-packages. It includes
@@ -48,14 +47,12 @@ transmission-edit, transmission-show utilities.
 
 %package cli
 Summary:       Transmission command line implementation
-Group:         Applications/Internet
 Requires:      transmission-common%{?_isa}
 %description cli
 Command line version of Transmission BitTorrent client.
 
 %package daemon
 Summary:       Transmission daemon
-Group:         Applications/Internet
 Requires:      transmission-common%{?_isa}
 Requires(pre): shadow-utils
 Requires(post): systemd
@@ -67,7 +64,6 @@ Transmission BitTorrent client daemon.
 
 %package gtk
 Summary:       Transmission GTK interface
-Group:         Applications/Internet
 Requires:      transmission-common%{?_isa}
 
 %description gtk
@@ -75,7 +71,6 @@ GTK graphical interface of Transmission BitTorrent client.
 
 %package qt
 Summary:       Transmission Qt interface
-Group:         Applications/Internet
 Requires:      transmission-common%{?_isa}
 
 %description qt
@@ -228,6 +223,8 @@ EOF
 %doc %{_mandir}/man1/transmission-qt.*
 
 %changelog
+* Tue May 01 2018 Gwyn Ciesla <limburgher@gmail.com> - 2.94-1
+
 * Thu Feb 15 2018 Björn Esser <besser82@fedoraproject.org> - 2.93-2
 - Rebuilt for libevent-2.1.so.6
 

                 reply	other threads:[~2026-07-20 20:37 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=178457985418.1.1470017051664501541.rpms-transmission-8c55005ddcc1@fedoraproject.org \
    --to=limburgher@gmail.com \
    --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