public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Andrew Bauer <zonexpertconsulting@outlook.com>
To: git-commits@fedoraproject.org
Subject: [rpms/nextcloud] epel10: 34.0.4 Release
Date: Sat, 19 Sep 2026 19:53:58 GMT	[thread overview]
Message-ID: <178984763890.1.17251326738078388919.rpms-nextcloud-9a75f858cde4@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/nextcloud
Branch : epel10
Commit : 9a75f858cde4230392fb134bb4f78d3ddfebb71b
Author : Andrew Bauer <zonexpertconsulting@outlook.com>
Date   : 2026-09-19T14:50:34-05:00
Stats  : +46/-2 in 3 file(s)
URL    : https://src.fedoraproject.org/rpms/nextcloud/c/9a75f858cde4230392fb134bb4f78d3ddfebb71b?branch=epel10

Log:
34.0.4 Release

---
diff --git a/bodhi.template.last b/bodhi.template.last
new file mode 100644
index 0000000..91fdf63
--- /dev/null
+++ b/bodhi.template.last
@@ -0,0 +1,44 @@
+[ nextcloud-33.0.3-1.el10_1 ]
+
+# bugfix, security, enhancement, newpackage, unspecified (required)
+type=security
+
+# testing, stable
+request=testing
+
+# Bug numbers: 1234,9876
+bugs=2454311,2452582,2452622,2452631,2452635,2452645,2452647,2454038,2456575,2457502,2457810,2457875,2463443,2452588,2452590,2452593,2452596,2452597,2453984,2456569,2457496,2457809,2457869,2463440
+
+# Severity: low, medium, high, urgent
+# This is required for security updates.
+severity=high
+
+display_name=
+
+
+# Here is where you give an explanation of your update.
+# Content can span multiple lines, as long as they are indented deeper than
+# the first line. For example,
+# notes=first line
+#     second line
+#     and so on
+notes=33.0.3 Release
+
+# Enable request automation based on the stable/unstable karma thresholds
+autokarma=True
+stable_karma=3
+unstable_karma=-3
+
+# Automatically close bugs when this marked as stable
+close_bugs=True
+
+# Suggest that users performs one of the following actions after the update:
+# unspecified, restart, logout
+# The default value is unspecified
+suggest=unspecified
+
+# A boolean to require that all of the bugs in your update have been confirmed by testers.
+require_bugs=True
+
+# A boolean to require that this update passes all test cases before reaching stable.
+require_testcases=True

diff --git a/nextcloud.spec b/nextcloud.spec
index 2b4260b..1a67c5d 100644
--- a/nextcloud.spec
+++ b/nextcloud.spec
@@ -5,7 +5,7 @@
 %endif
 
 Name:           nextcloud
-Version:        34.0.3
+Version:        34.0.4
 Release:        %autorelease
 Summary:        Private file sync and share server
 # Automatically converted from old format: AGPLv3+ and MIT and BSD and ASL 2.0 and WTFPL and CC-BY-SA and GPLv3+ and Adobe - review is highly recommended.

diff --git a/sources b/sources
index 95997de..fc45096 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (nextcloud-34.0.3.tar.bz2) = 3463dbbdeae5275a0791b115cf86aed41c5a138fdd19bb32ec12837a6698106b6f172e24fb1264a2d4e20b2b805bcf7841b2338e4e02f1fd5394fbed830cc695
+SHA512 (nextcloud-34.0.4.tar.bz2) = 83ac93832da26ea0f03c03a2860a8769faee4d20582993d22badb5bf3889c5e16f4167d50a09936f9bcf95a3be68eafeee8e4cf3341f23593354fc5049b10f84

                 reply	other threads:[~2026-09-19 19:53 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=178984763890.1.17251326738078388919.rpms-nextcloud-9a75f858cde4@fedoraproject.org \
    --to=zonexpertconsulting@outlook.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