Script 'mail_helper' called by obssrc
Hello community,

here is the log from the commit of package purple-rocketchat for 
openSUSE:Factory checked in at 2025-01-24 13:40:11
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/purple-rocketchat (Old)
 and      /work/SRC/openSUSE:Factory/.purple-rocketchat.new.2316 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "purple-rocketchat"

Fri Jan 24 13:40:11 2025 rev:11 rq:1239975 version:0.0+git20220925

Changes:
--------
--- /work/SRC/openSUSE:Factory/purple-rocketchat/purple-rocketchat.changes      
2024-03-22 15:34:27.863478185 +0100
+++ 
/work/SRC/openSUSE:Factory/.purple-rocketchat.new.2316/purple-rocketchat.changes
    2025-01-24 13:40:21.934561146 +0100
@@ -1,0 +2,8 @@
+Thu Jan 23 15:05:59 UTC 2025 - Dominique Leuenberger <[email protected]>
+
+- Drop requires_ge pidgin: as pidgin has not been in the buildroot,
+  that line silently was a no-op. requires_ge now returns errors in
+  those situations. As it as a ho-op so far, we seem to be fine
+  without it.
+
+-------------------------------------------------------------------

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ purple-rocketchat.spec ++++++
--- /var/tmp/diff_new_pack.ItwsFy/_old  2025-01-24 13:40:22.590588241 +0100
+++ /var/tmp/diff_new_pack.ItwsFy/_new  2025-01-24 13:40:22.594588405 +0100
@@ -1,7 +1,7 @@
 #
 # spec file for package purple-rocketchat
 #
-# Copyright (c) 2024 SUSE LLC
+# Copyright (c) 2025 SUSE LLC
 #
 # All modifications and additions to the file contributed by third parties
 # remain the property of their copyright owners, unless otherwise agreed
@@ -47,7 +47,6 @@
 %package -n pidgin-plugin-%{_name}
 Summary:        RocketChat protocol plugin for Pidgin
 Requires:       libpurple-plugin-%{_name} = %{version}
-%requires_ge    pidgin
 Supplements:    (libpurple-plugin-%{_name} and pidgin)
 BuildArch:      noarch
 

Reply via email to