/edit
I propose that the latest minor maintenance version of MariaDB be included in
the stable release update of Debian. This bug report is to make it visible and
trackable to the release team that this update is available and work is in
progress.
The update is currently being worked on and revie
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: mari...@packages.debian.org
Control: affects -1 + src:mariadb
I propose that the latest minor maintenance version of Galera be included in the
stable release update o
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: mari...@packages.debian.org
Control: affects -1 + src:galera-4
I propose that the latest minor maintenance version of Galera be included in the
stable release update
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: mari...@packages.debian.org
Control: affects -1 + src:galera-4
I propose that the latest minor maintenance version of Galera be included in the
stable release update
Thanks for expressing that you are inclined and not objecting such a
change. I will put time in making an MR and technical proposal with details.
Package:dbconfig-mysql
Severity: wishlist
Hi!
The package in Debian has been using exclusively MariaDB in all
official Debian releases since Debian 9 "stretch" from 2017. Debian 8
"jessie" was the last official Debian release to ship with MySQL.
Should we consider renaming the package to dbconfi
Hi!
I saw this again today in a container but when I tried to reproduce it
didn't happen again..
Yes to finalizing DEP-14 soon, but first I think we need to complete the
technical work to have git-buildpackage use DEP-14 branch names by default.
I tried implementing it but turned out a bit too involved..
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829444
Use DEP14 branch layout by defa
Hi!
Note that MySQL 8.0 will be end-of-life in 2026, so not only will it
be FTBFS during trixie, it will also be out of support. However,
Debian only releases with MariaDB - the package mysql-8.0 is only in
unstable and will never be promoted to testing/trixie.
As long as MariaDB is 2038 compatib
Package: bash
Version: 5.2.21-2.1
Hi!
I noticed CI failing on:
Preparing to unpack .../bash_5.2.21-2.1_amd64.deb ...
Unpacking bash (5.2.21-2.1) over (5.0-4) ...
Setting up bash (5.2.21-2.1) ...
dpkg (subprocess): unable to execute installed bash package
post-installation script (/var/lib/dpkg/i
Fix pending review at
https://salsa.debian.org/debian/debcraft/-/merge_requests/13
Hi!
Indeed I forgot to update the version string inside the shell script. I
will try to come up with some scheme that is he script automatically reuses
the debian/changelog entry, as this is a native Debian package after all.
Hi!
> > Thanks for the tips. Unfortunately running just the single test
> > without any other load on the system still crashes it and system load
> > was otherwise zero, so it is not due to slowness.
>
> Single-core performance on SPARC is rather poor, especially on older
> SPARC systems like this
Hi!
Thanks for reporting. The failures are highlighted below. These issues
seem like a duplicate of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052838 "mariadb:
FTBFS multiple archs: Post-build tests randomly fail on reserved port
due to lacking builder isolation" and are sporadic by nature
Fix pending review at
https://salsa.debian.org/debian/debcraft/-/merge_requests/12
Hi!
Thanks for reporting. The filelist is actually completely wrong (
https://packages.debian.org/sid/all/debcraft/filelist). I will add a basic
autopkgtest to the package to detect things like this automatically in CI,
and add all needed files in package.
In the meantime you can install from sou
Source: mariadb
Version: 1:11.4.2-4
Tags: help
X-Debbugs-CC: debian-loonga...@lists.debian.org
User: debian-loonga...@lists.debian.org
Usertags: loong64
The CI run at
https://ci.debian.net/packages/m/mariadb/unstable/loong64/49111734/
starts, but the mariadbd program immediately crashes on start.
Hi!
Instead of VSCode/Codium I would recommend Pulsar. See
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060778 (ITP:
pulsar-edit -- A Community-led Hyper-Hackable Text Editor (formerly
Atom)).
However, to get any Electron app in Debian somebody would need to
package Electron first, see
http
Thanks for checking. The arch i386 is going away, so it can be
ignored/disabled. Issues with BLHC and reprotest should be fixed if they
are easy. Having them both pass is not a hard requirement.
Most important here is that you checked all failures and there was nothing
else.
I don't have any sugg
Hi!
If you are not using Salsa CI simply because you didn't know about it, then
check out https://salsa.debian.org/salsa-ci-team/pipeline
I will check the Mentor website and look for opportunities to document
Salsa CI better.
I didn't claim that you must use Salsa or CI.
I was just curious to learn is there a particular reason this package is
not using Salsa-CI to validate that all easily testable things are correct?
Cool, latest version indeed is on Salsa
https://salsa.debian.org/zig-team/zig/-/blob/main/debian/control
Vcs-Browser: https://salsa.debian.org/zig-team/zig
Vcs-Git: https://salsa.debian.org/zig-team/zig.git
Homepage: https://github.com/ziglang/zig
The CI at
https://salsa.debian.org/zig-team/zi
Yes, using Salsa or CI is not required, but I was curious is there
particular reason this package is not using Salsa-CI to validate
that all easily testable things are correct?
Hi!
There are no CI runs visible at https://salsa.debian.org/monty/mangl/-/pipelines
Any particular reason this package is not using Salsa-CI to validate
that all easily testable things are correct?
- Otto
Hi!
> Vcs : http://cgit.refcnt.org/colorize.git/
Any particular reason this is not hosted on Salsa and using Salsa-CI
to validate that all easily testable things are correct?
- Otto
Hi!
I noticed the CI at
https://salsa.debian.org/mdosch/bash-unit/-/pipelines/665767 is
failing on reprotest. If you are unable to fix it, you could mark the
test as 'allow failure' so it won't make the whole pipeline report
failure.
- Otto
Hi!
> * Vcs : https://github.com/NickHastings/zig-debian
Any particular reason this is not hosted on Salsa and using Salsa-CI
to validate that all easily testable things are correct?
- Otto
The symptoms here sound very much like
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1854588 which has
now been fixed in Ubuntu, but not submitted to Debian
There was also a fix drafted in
https://salsa.debian.org/atzlinux-guest/gdebi/-/commit/1de6b00bef539de4458021dc02ed2110f76ab630
but no
Hi!
> Well dpkg already has multiple repos, and they are being kept in sync,
> by having a main instance and then replicas! I think doing this
> automatically without a merge-based workflow, for multiple pushers,
> would either be racy, or not possible at all w/o making a mess of it.
Git fully su
Hi!
Thanks for a quick reply!
> > Please allow Merge Requests at https://salsa.debian.org/dpkg-team/dpkg
> > so that it is easier for others to contribute to the package.
>
> These repos are just mirrors (I've updated the repo descriptions there
> now), like the ones on Codeberg, where stuff gets
> >
> > /tmp/autopkgtest-lxc.pxhhitlw/downtmp/build.JDD/src/debian/tests/smoke-mysql:
> > line 7: /usr/bin/mysqld_safe: No such file or directory
>
> Well I imagine you (or upstream) renamed some binaries, but the
> package name stayed the same?
Thanks, somehow I wasn't able to spot that earli
Hi Christian!
Can you help read the PowerDNS autopkgtest logs to understand why they are
failing now?
ke 3. heinäk. 2024 klo 23.24 Otto Kekäläinen kirjoitti:
> Hi Marc and Christian!
>
> Just checking if you can help with debugging the pdns autopkgtest issues?
>
> https://bugs
Hi!
Could you please consider this request?
Thanks
Package: dpkg
Severity: wishlist
Hi!
Please allow Merge Requests at https://salsa.debian.org/dpkg-team/dpkg
so that it is easier for others to contribute to the package.
Thanks!
Thanks for the tips. Unfortunately running just the single test
without any other load on the system still crashes it and system load
was otherwise zero, so it is not due to slowness.
I also tested explicit debug run and various ways to invoke gdb, but
--debug didn't yield any new info and all gdb
I built the binary in debug mode and that yielded a stacktrace:
***
main.partition w38 [ retry-fail ]
Test ended at 2024-07-06 01:14:43
CURRENT_TEST: main.partition
mysqltest: At line 3010: query 'select id from t1 where data = 'a
Notes on how I setup the schroot on stadler:
source porterbox.sh
psetup sparc64
pinstall git-buildpackage gdb debian-goodies mariadb-server-core
perl-modules-ipc-system-simple
pinstall build-essential bison cmake cracklib-runtime debhelper-compat
default-jdk dh-exec libboost-dev libbz2-dev libc
Hi!
On Tue, 2 Jul 2024 at 23:24, John Paul Adrian Glaubitz
wrote:
>
> Hello Otto,
>
> On Tue, 2024-07-02 at 21:10 -0700, Otto Kekäläinen wrote:
> > I recently uploaded MariaDB 11.4 to Debian, and it seems it regressed
> > on sparc64.
> >
> > Are there any sp
Hi Christian!
Could you help with https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074782?
It might be the same root cause as for pdns in 1074780.
Hi Marc and Christian!
Just checking if you can help with debugging the pdns autopkgtest issues?
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074780
Hi!
I recently uploaded MariaDB 11.4 to Debian, and it seems it regressed
on sparc64.
Are there any sparc64 hackers interested in taking a look?
The build itself passed and most of the post-build passes, but some
tests cause the database to crash. Stack traces are visible in the
logs:
https://b
Hi!
This https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074670 is a
result of the MariaDB build with the embedded server using excessive
disk space.
I have filed reverting MR at
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/89
and asked upstream for advice in
https://l
Thanks for reporting this!
There were Breaks/Replaces in place but they had a typo in version string.
Fixed now, and also ran the check_for_missing_breaks.py script to with all
previous versions ever released of MariaDB to ensure all scenarios are
covered:
https://salsa.debian.org/mariadb-team/mar
Hi!
> > Are you OK if I push this to https://salsa.debian.org/debian/rocksdb ?
> Please do. I will try to answer other parts of your email today.
I have now created and configured the RocksDB repository under the
salsa.debian.org/debian project.
As a token of acceptance that you are OK to use t
Source: command-not-found
Version: 23.04.0-1
Severity: severe
Running /usr/lib/cnf-update-db failed on:
Traceback (most recent call last):
File "/usr/lib/cnf-update-db", line 32, in
col.create(db)
File "/usr/share/command-not-found/CommandNotFound/db/creator.py",
line 96, in create
s
Control: retitle -1 mariadb: FTBFS on sparc64: Multiple tests crash / time out
Ignore the previous list of issues, it a mistake from wrong architecture.
The actual sparc64 build at
https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=sparc64&ver=1%3A11.4.2-1&stamp=1719764783&raw=0
failed o
The upload of 1:11.4.2-1 still shows essentially the same error:
[ 67%] Building C object
tests/CMakeFiles/mariadb-client-test.dir/mysql_client_test.c.o
cd /<>/builddir/tests && /usr/bin/cc -DHAVE_CONFIG_H
-DMYSQL_CLIENT -D_FILE_OFFSET_BITS=64
-I/<>/libmariadb/include
-I/<>/builddir/libmariadb/in
With the upload of MariaDB 1:11.4.2-1, the hppa build is failing on
openjdk-5-jre-headless dependency.
The last 10.11 series build was successful up until the test suite
fails on some tests having extra optimized debug info.
Hi!
Check out https://salsa.debian.org/otto/rocksdb/
It has the import you did plus some tweaks:
- branches follow DEP-14 and instead of 'master' and 'upstream' there
is 'debian/latest' and 'upstream/latest'
- the same repo is a fork of the upstream repo so that it is easy to
cherry-pick/backport
Package: ftp.debian.org
Severity: normal
Hi,
Please remove src:galeara-3 from unstable.
Galera 3 has been replaced by Galera 4, which has been available in
unstable and testing for years.
Ref:
https://tracker.debian.org/pkg/galera-3
https://tracker.debian.org/pkg/galera-4
Good, looks like you got the hang of it.
I will post my suggestion that involves having a config similar to
https://salsa.debian.org/debian/entr/-/blob/debian/latest/debian/gbp.conf
but upstream as 'main' and some other tweaks for easier long-term
maintainability, along with explanation why my sug
Hi!
I am travelling and on slow internet. I will review and hopefully help
you with feedback this weekend.
Hi!
I can do the import on your behalf to spare you the effort of readig
git-buildpackage docs. Thanks for confirming you are open to have package
in git!
Thanks Frank and others!
I appreciate your assistance in testing the build. I will proceed to
merge this before the next upload then.
I just wanted to add here the regular Debian Developer's point of
view: after every upload of every package I maintain, I always check
the buildd status, investig
I uploaded now with 'dput --delayed=7 ftp-master *.changes' as it is
unlikely this will get any further review, nor need it as it is just a
regular new minor upstream release.
There is no tentative date at https://release.debian.org/ yet but at
least this will be in -proposed after this.
I uploaded now with 'dput --delayed=7 ftp-master *.changes' as it is
unlikely this will get any further review, nor need it as it is just a
regular new minor upstream release.
Hi!
I have a patch to tentatively fix Debian package galera-4 builds on
ia64 at https://salsa.debian.org/mariadb-team/galera-4/-/merge_requests/19
Would anybody be interested in helping out and testing if the build
fully passes now?
Details in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=97
Thanks for reporting!
The lifecycle of /run should always be longer than the process existing. I
think /run is cleared only on reboot.
Contributions are welcome from you or anybody reading this bug report. If
you have a patch (or not ideally Merge Request on Salsa) I am happy to
review.
Package: screenkey
Severity: normal
Tags: patch
X-Debbugs-CC: wav...@thregr.org
This bug report is filed to notify that
https://salsa.debian.org/georgesk/screenkey/-/merge_requests/2.patch is
available.
Personally I would prefer all feedback to be posted at
https://salsa.debian.org/georgesk/scree
For the record,
https://salsa.debian.org/debbugs-team/debbugs/-/merge_requests/19 was
not merged fully and the Salsa-CI is not yet passing, so I filed
https://salsa.debian.org/debbugs-team/debbugs/-/merge_requests/20
which you can see in the MR status as CI passing.
Package: debbugs
Severity: important
With https://salsa.debian.org/debbugs-team/debbugs/-/merge_requests/19
the build is again passing and Lintian errors fixed, and Salsa-CI
would be passing if it had been merged.
The master branch has still build failures though and they are not
evident to maint
Package: apt
Severity: important
Tags: patch
Please include
https://salsa.debian.org/debbugs-team/debbugs/-/merge_requests/20.patch
in debbugs.
If you have feedback about the submission, please post it at
https://salsa.debian.org/debbugs-team/debbugs/-/merge_requests/20 and
allow me a couple of
Package: apt
Severity: normal
Tags: patch
Please include
https://salsa.debian.org/debbugs-team/debbugs/-/merge_requests/6.patch
in debbugs.
If you have feedback about the submission, please post it at
https://salsa.debian.org/debbugs-team/debbugs/-/merge_requests/6 and
allow me a couple of days
Package: apt
Severity: normal
Tags: patch
This bug report is filed to notify that
https://salsa.debian.org/apt-team/apt/-/merge_requests/348.patch is
available.
Personally I would prefer all feedback to be posted at
https://salsa.debian.org/apt-team/apt/-/merge_requests/348 as
bugs.debian.org is
Source: mariadb
Version: 1:10.11.8-1
Forwarded: https://jira.mariadb.org/browse/MDEV-34195
Tags: confirmed, help, ftbfs
User: debian-...@lists.debian.org
Usertags: x32
X-Debbugs-CC: debian-am...@lists.debian.org
After importing 10.11.8 in Debian, dropped the temporary patch and
uploaded with the r
Package:gnupg2
Version: 2.2.43-5
Severity: important
(Sharing on debian-devel as gnupg2 is a core package and this breaks
hundreds of reverse dependencies)
Latest gnupg2 in Debian Sid cannot be installed. This also prevents
all packages that depend on gpg to be installed as well. Personally I
no
Status: The MR
https://salsa.debian.org/java-team/mariadb-connector-java/-/merge_requests/1
was merged 4 years ago but the project
https://salsa.debian.org/java-team/mariadb-connector-java does not
have pipelines enabled, and thus the Salsa-CI hasn't been running.
I did confirm by running the CI
control: forward -1 https://github.com/codership/galera/issues/659
control: forwarded -1 https://github.com/codership/galera/issues/659
Forwarded: https://github.com/codership/galera/issues/659
Package: libfmt
Severity: wishlist
Hi!
Please allow CI and Merge Requests at
https://salsa.debian.org/zhsj/fmtlib so that it is easier for others
to contribute to the package.
I would for example like to submit a Merge Request to include
https://salsa.debian.org/otto/fmtlib/-/commit/07463212495
Control: retitle -1 libmariadb-java: Request to upgrade to MariaDB
Connector Java 3.x series
Hi!
Latest upstream version of MariaDB Connector Java is 3.3.3.
Current version in Debian is 2.7.6-1.
Do you have any plans to import the latest version to Debian?
- Otto
We can put 10.11.7 in Stable until it yas been accepted in Testing first.
It is on the way though.
Hi!
Can you share more details what you mean? Perhaps steps to reproduce?
Bullseye oldstable update request filed in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069802
You can +1 it if you want to show support.
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: mari...@packages.debian.org
Control: affects -1 + src:galera-4
I propose that the latest minor maintenance version of Galera be included in the
oldstable release upda
> What about bullseye, which is also a supported distribution?
>
> I have not reached the point where I want to do NMUs for these kind
> of bugs, but if this were my package, I would certainly do an upload
> for bullseye as well. If I can be of any help, please say so.
This bug report was about Bo
I was able to reproduce this for Bookworm both locally and in CI at
https://salsa.debian.org/mariadb-team/galera-4/-/jobs/5620032
After importing latest upstream build/test passes:
https://salsa.debian.org/otto/galera/-/jobs/5624466
Stable upload request filed at
https://bugs.debian.org/cgi-bin/b
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: mari...@packages.debian.org
Control: affects -1 + src:galera-4
I propose that the latest minor maintenance version of Galera be included in the
stable release update
I converted this to MR at
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/77
Waiting for CI to pass and for a second person to approve. Perhaps Daniel Black?
Svante: Would you like to submit the two patches upstream as well?
Galera 25.3.37 was last release from upstream in 3.x series. I suspect
the best resolution here is to wait a bit and then just file removal
request for galera-3 in sid/trixie when we are confident there is no
MariaDB 10.1/2/3 users out there anymore.
This seems to be passing now with latest version:
>From
>https://buildd.debian.org/status/fetch.php?pkg=galera-4&arch=sparc64&ver=26.4.18-1%7Eexp1&stamp=1713134650&raw=0:
Running tests...
/usr/bin/ctest --force-new-ctest-process --output-on-failure
Test project /<>/obj-sparc64-linux-gnu
Sta
Status update: This exact same issue is still affecting ia64 builds
for latest Galera 26.4.18 in Debian:
https://buildd.debian.org/status/fetch.php?pkg=galera-4&arch=ia64&ver=26.4.18-1%7Eexp1&stamp=1713220669&raw=0
Thanks Svante for the patches!
I will test these next weekend.
Hi Daniel!
Do you think this change is still needed?
Do you want to participate in some open source development/testing to
make it work?
On Sun, 14 Jan 2024 at 16:03, Otto Kekäläinen wrote:
>
> FYI: Discussion about this continued in
> https://salsa.debian.org/mariadb-team/maria
Galera patch releases have been accepted as stable updates before. That is
also what users expect.
Thanks for reminding about this though, I yad forgotten about it. Will do
it next weekend.
Hi!
> > The research done in
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895570#50 looks good.
> >
> > Do we have now agreement to default to -ast or -astb for packages that have
> > Debhelper 14+?
>
> I don't think making w-a-s defaults depend on the debhelper compat level was
> conside
Today I filed https://salsa.debian.org/salsa-ci-team/pipeline/-/issues/342
("Detect missing tags: force maintainer to continue tagging upload
commits if it was done before") which would be easy to implement if
something like `gbp sync` already existed.
The research done in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895570#50 looks good.
Do we have now agreement to default to -ast or -astb for packages that have
Debhelper 14+?
Thanks Wouter for reporting this and Michael for submitting a merge
request for a potential fix!
The libcrypto.so.3 is from the OpenSSL package. In your upgrade case
it seems to be switching from
libssl3 [i386] to libssl3t64 [i386]. Your MariaDB packages are amd64.
This makes me wonder what is act
Hi!
Is anyone perhaps planning to fix cargo?
For example curl isn't building on armel/armhf now and numerous packages
that depend of curl are not building on armel/armhf.
Thanks in advance to the person who steps up.
Source: mariadb
Version: 1:10.11.7-2
Tags: confirmed, help, ftbfs
User: debian-h...@lists.debian.org
Usertags: hurd
X-Debbugs-CC: debian-h...@lists.debian.org
After fixing https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063739
the builds of MariaDB currently fail with:
[ 86%] Building CXX obje
Package: cargo
Version: 0.70.1+ds1-2+b1
I noticed that the latest build (probably for 64-bit time_t) at
https://buildd.debian.org/status/package.php?p=cargo&suite=sid fails
to build for armhf and armel.
The armhf build complains about Extra-Depends: dpkg-dev (>= 1.22.5),
gcc-13 (>= 13.2.0-16.1),
Hi Philip!
Thanks for reporting
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037124 in Debian.
The bug you describe is not due to anything in the Debian packaging,
but most likely a common bug for upstream
https://github.com/aristocratos/btop.
Do you have experience in C++ development? Do
Hi Marco!
Thanks for reporting
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012611 in Debian.
The bug you describe is not due to anything in the Debian packaging,
but most likely a common bug for upstream
https://github.com/aristocratos/btop.
Do you have experience in C++ development? Do y
server doesn't support dates later than 2038
Seems to stem from This is due to
https://github.com/MariaDB/server/blob/11.5/sql/mysqld.cc#L3903-L3908
I am looking into this now as well..
On Sat, 2 Mar 2024 at 16:41, Otto Kekäläinen wrote:
>
> > > Could you Sebastian per
> > Could you Sebastian perhaps quickly skim through the commit that
> > implemented this
> > https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/8194544349982990fb2585c2a8c15c4db3904735
> > and say if there might be something else missing as well?
>
> Did you mean
> https://salsa.debian.
Currently MariaDB is not building[1] at all due to:
**
mariadb build-depends on:
- libcurl4-openssl-dev:amd64
libcurl4-openssl-dev depends on:
- libcurl4t64:amd64 (= 8.6.0-3.1)
mariadb build-depends on:
- cmake:amd64
cmake depends on:
- libcurl4:amd64 (>= 7.16.2)
libcurl4t64 conflicts with:
-
Hi Sabastian!
> * The package is built with the wrong ABI.
> * The package migrates to testing before the change is enabled in
> testing and builds there would be produced against the wrong ABI.
>
> Please add dpkg-dev (>= 1.22.5) to Build-Depends and upload the new
> version ASAP.
Thanks for f
Ok, thanks for the clarification.
I will merge
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/68
then and upload to unstable within a couple of days.
The MariaDB armhf and armel builds are broken due to regression in
upstream anyway, so no transitions for this package will
About this suggested change (penging at
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/68):
>From the announcement message
https://lists.debian.org/debian-devel-announce/2024/02/msg0.html
lists we can find in
https://people.canonical.com/~vorlon/armhf-time_t/source-packa
1 - 100 of 1001 matches
Mail list logo
