public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Troy Dawson <tdawson@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/kpublictransport] epel10: Merge branch f44 into epel10
Date: Fri, 11 Sep 2026 17:11:43 GMT [thread overview]
Message-ID: <178914670302.1.3352967654154275184.rpms-kpublictransport-f714967b6ffa@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/kpublictransport
Branch : epel10
Commit : f714967b6ffa717526d87cbabef8269a185d53b6
Author : Troy Dawson <tdawson@redhat.com>
Date : 2026-09-11T10:11:18-07:00
Stats : +21/-3 in 3 file(s)
URL : https://src.fedoraproject.org/rpms/kpublictransport/c/f714967b6ffa717526d87cbabef8269a185d53b6?branch=epel10
Log:
Merge branch f44 into epel10
---
diff --git a/.gitignore b/.gitignore
index 8f2305a..835f2cc 100644
--- a/.gitignore
+++ b/.gitignore
@@ -58,3 +58,6 @@
/kpublictransport-26.04.1.tar.xz
/kpublictransport-26.04.2.tar.xz
/kpublictransport-26.04.3.tar.xz
+/kpublictransport-26.07.90.tar.xz
+/kpublictransport-26.08.0.tar.xz
+/kpublictransport-26.08.1.tar.xz
diff --git a/kpublictransport.spec b/kpublictransport.spec
index 84f7752..0e44c63 100644
--- a/kpublictransport.spec
+++ b/kpublictransport.spec
@@ -1,5 +1,5 @@
Name: kpublictransport
-Version: 26.04.3
+Version: 26.08.1
Release: 1%{?dist}
License: CC0-1.0 AND ODbL-1.0 AND LGPL-2.1-or-later AND BSD-2-Clause AND MIT AND LGPL-2.0-or-later AND BSD-3-Clause
Summary: Library to assist with accessing public transport timetables and other data
@@ -62,7 +62,7 @@ Developer Documentation files for %{name} for use with KDevelop or QtCreator.
%{_kf6_libdir}/libKPublicTransportOnboard.so.%{version}
%{_kf6_qmldir}/org/kde/kpublictransport/*
%{_kf6_datadir}/qlogging-categories6/org_kde_kpublictransport_onboard.categories
-
+%{_kf6_libdir}/qt6/metatypes/qt6kpublictransport*.json
%files devel
%{_includedir}/*
@@ -74,6 +74,21 @@ Developer Documentation files for %{name} for use with KDevelop or QtCreator.
%{_qt6_docdir}/*.qch
%changelog
+* Wed Sep 09 2026 Steve Cossette <farchord@gmail.com> - 26.08.1-1
+- 26.08.1
+
+* Fri Aug 14 2026 Steve Cossette <farchord@gmail.com> - 26.08.0-1
+- 26.08.0
+
+* Fri Jul 31 2026 Steve Cossette <farchord@gmail.com> - 26.07.90-1
+- 26.07.90
+
+* Wed Jul 29 2026 Steve Cossette <farchord@gmail.com> - 26.07.80-1
+- 26.07.80
+
+* Thu Jul 16 2026 Fedora Release Engineering <releng@fedoraproject.org> - 26.04.3-2
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_45_Mass_Rebuild
+
* Tue Jun 30 2026 Steve Cossette <farchord@gmail.com> - 26.04.3-1
- 26.04.3
diff --git a/sources b/sources
index d51c301..23c5df5 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (kpublictransport-26.04.3.tar.xz) = 59dcb14bb7c3deffc20c4e79f4a6b28c6782a5ab0143b6dd8a344228deef974af2501e1ae4a3fb553050f7b699be76ce0352eb4aec5da0c0262bef783b06b85e
+SHA512 (kpublictransport-26.08.1.tar.xz) = ca191ea3841b3b0689e2c588dcce4f0f756537d99120b66765efb5c29e54f95baf6097479d66ebde3ae27feb42b892420e3700f93858aea15f162a28fde594e1
next reply other threads:[~2026-09-11 17:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 17:11 Troy Dawson [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-07-30 15:59 [rpms/kpublictransport] epel10: Merge branch f44 into epel10 Troy Dawson
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=178914670302.1.3352967654154275184.rpms-kpublictransport-f714967b6ffa@fedoraproject.org \
--to=tdawson@redhat.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