Script 'mail_helper' called by obssrc
Hello community,

here is the log from the commit of package mariadb-image for openSUSE:Factory 
checked in at 2025-12-17 17:35:51
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/mariadb-image (Old)
 and      /work/SRC/openSUSE:Factory/.mariadb-image.new.1939 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "mariadb-image"

Wed Dec 17 17:35:51 2025 rev:61 rq:1323203 version:unknown

Changes:
--------
--- /work/SRC/openSUSE:Factory/mariadb-image/mariadb-image.changes      
2025-10-21 11:19:01.457360170 +0200
+++ /work/SRC/openSUSE:Factory/.mariadb-image.new.1939/mariadb-image.changes    
2025-12-17 17:40:23.393790664 +0100
@@ -1,0 +2,5 @@
+Tue Dec 16 15:28:01 UTC 2025 - SUSE Update Bot <[email protected]>
+
+- README.md language cleanups
+
+-------------------------------------------------------------------

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

Other differences:
------------------
++++++ README.md ++++++
--- /var/tmp/diff_new_pack.kwbJnK/_old  2025-12-17 17:40:23.981815389 +0100
+++ /var/tmp/diff_new_pack.kwbJnK/_new  2025-12-17 17:40:23.989815726 +0100
@@ -3,7 +3,7 @@
 ![Redistributable](https://img.shields.io/badge/Redistributable-Yes-green)
 
 ## Description
-MariaDB is an open-source, multi-threaded, relational database management 
system. It's a backward-compatible branch of the MySQL Community Server that 
provides a drop-in replacement for MySQL.
+MariaDB is an open source, multi-threaded, relational database management 
system. It's a backward-compatible branch of the MySQL Community Server that 
provides a drop-in replacement for MySQL.
 
 
 ## Usage
@@ -27,7 +27,7 @@
 
 When using the MariaDB image, we recommend one of the following options:
 
-* Use a named volume to manage the storage of your database data. This is the 
default option and it is easy to use. The downside is that the files may be 
hard to locate for tools and applications that run directly on the host system, 
i.e. outside containers.
+* Use a named volume to manage the storage of your database data. This is the 
default option and it is easy to use. The downside is that the files may be 
hard to locate for tools and applications that run directly on the host system.
 * Create a data directory on the host system (outside the container) and mount 
the created directory to a directory accessible from inside the container. This 
stores the database files in a known location on the host system and makes it 
easy for tools and applications on the host system to access the files. If you 
choose this approach, make sure that the specified directory exists, and its 
permissions along with other security mechanisms on the host system are set up 
correctly.
 
 To mount a host directory as a volume for your data run the following command:

Reply via email to