Are you using encryption or compression in MariaDB which
percona-xtrabackup does not support? In that case you need
mariabackup: https://mariadb.com/kb/en/library/mariadb-backup-overview/
Otherwise I am not aware of any reasons percona-xtrabackup would not
work, it should.
Control: tags -1 +moreinfo
Hello!
> mariadb moved my_print_defaults from mysql-server-core to mariadb-server.
> So akonadi-backend-mysql do now need to depend at mariadb-server. As
> "my_print_defaults" is only needed at first start of akonadi it is a pity if
> we
> would that for now rely on a
Control: tag -1 pending
Hello,
Bug #921488 in mariadb-10.3 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/mariadb-team/mariadb-10.3/commit/21008f9fdfe0f13a360c
Potentially related:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916375 apache2:
Segmentation fault when mod_perl.so is enabled
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918988
libmysqlclient symbol conflict segfaulted Apache
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920
Control: tag -1 pending
Hello,
Bug #921488 in mariadb-10.3 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/mariadb-team/mariadb-10.3/commit/21008f9fdfe0f13a360c
Looks like this has never been in the core package:
https://packages.debian.org/search?searchon=contents&keywords=resolveip&mode=path&suite=unstable&arch=any
/usr/bin/resolveipmariadb-server-10.0 [arm64], mariadb-server-10.1
[powerpc], mariadb-server-10.3 [ei ia64, powerpc, s390, sparc],
mariadb-s
Hello!
2017-02-23 16:27 GMT+02:00 Robie Basak :
> The rule would be: any package that arranges a /etc/mysql/my.cnf
> symlink, usually via /usr/share/mysql-common/configure-symlinks, MUST
> Provide and Conflict mysql-my-cnf, with the exception of mysql-common.
Sorry for the late reply. I think tha
Hello Michael!
I am not sure what the actual problem here is. What are you trying to
achieve which does not work? What is the name of the software that
fails to compile with MariaDB, either using libmariadbclient-dev,
libmariadbclient-dev-compat, libmariadb-dev or libmariadb-dev-compat?
To my kn
For the record:
2017-01-05 8:07 GMT+02:00 Salvatore Bonaccorso :
> Hi
>
> When installing myssql-server-5.6 in stretch and sid, then mysqld is
> started and listend not binding on localhost only, but listen on *.
>
> tcpLISTEN 0 80 :::mysql:::*
>
Hello!
>> One way to make this an easier transition would be to have a
>> mysql-server package in stretch that's a dummy package that depends
>> on
>> default-mysql-server, and that has an upgrade notice about the
>> transition to mariadb that is happening.
The transition is supposed to be automa
2017-03-15 10:14 GMT+02:00 Lars Tangvald :
> When I did a quick test, I just replaced jessie with stretch in
> /etc/apt/sources.list, ran apt-get update and apt-get dist-upgrade
I've done this upgrade test many times over and it works well. We need
more details about scenarios where the upgrade d
Hello!
la 30. kesäk. 2018 klo 1.15 James Clarke (jrt...@debian.org) kirjoitti:
>
> Package: libmariadb3
> Version: 1:3.0.3-2
> Severity: serious
>
> Hi,
> Trying to install libmariadb3 on a system which already has libmariadb2
> installed fails with:
>
> > Unpacking libmariadb3:amd64 (1:3.0.3-2)
This has been fixed in upstream master branch with the introduction of
CMAKE variable INSTALL_LIBDIR_DEB in commit
https://github.com/MariaDB/mariadb-connector-c/commit/eb64582b68eb627d70dffad8808c7b6d4cf11b27
I have tested it and works well. Will upload to Debian as part of
3.0.6 when it is relea
Control: tag -1 pending
Hello,
Bug #902729 in mariadb-connector-c reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:
https://salsa.debian.org/mariadb-team/mariadb-connector-c/commit/f7845
Control: tag -1 pending
Hello,
Bug #886756 in mariadb-10.1 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:
https://salsa.debian.org/mariadb-team/mariadb-10.1/commit/89ae638d1d3b5a7157d
Hello!
I plan to have this commit included in the next upload of MariaDB
10.1.x into Debian:
https://salsa.debian.org/mariadb-team/mariadb-10.1/commit/89ae638d1d3b5a7157d086a9be2468cae764aae7
ti 9. tammik. 2018 klo 17.45 Jonas Meurer (jo...@freesources.org) kirjoitti:
>
> Package: mariadb-server
Hello!
ti 7. elok. 2018 klo 11.58 Jonas Meurer (jo...@freesources.org) kirjoitti:
>
> Am 07.08.2018 um 10:51 schrieb Jonas Meurer:
> > Hey Otto,
> >
> > Am 06.08.2018 um 23:09 schrieb Otto Kekäläinen:
> >> I plan to have this commit included in the next upload o
onnect bug:
>
> Latest code is setting the reconnect flag correctly via mysql_options
> (instead of accessing internal member), so I need to debug why it's failing.
>
> /Georg
>
> On Fri, Dec 28, 2018 at 1:31 PM gregor herrmann wrote:
>>
>> On Fri, 28 De
ti 25. jouluk. 2018 klo 21.31 Sebastiaan Couwenberg
(sebas...@xs4all.nl) kirjoitti:
...
> > I cannot reproduce this inside a Docker image (e.g. via Salsa
> > gitlab-ci.yml) because the operation is too heavy, but basically this
> > bug report is about how aptitude resolves build dependencies and th
pe 4. tammik. 2019 klo 18.31 gregor herrmann (gre...@debian.org) kirjoitti:
>
> On Fri, 04 Jan 2019 00:22:54 +0100, gregor herrmann wrote:
>
> > I've now pinged the upstream issue at:
> > https://github.com/perl5-dbi/DBD-mysql/issues/275
>
> And they plan to try and fix the issue:
> https://github.
Hello!
gregor herrmann kirjoitti pe 4. tammikuuta 2019 klo
1.23:
> On Thu, 03 Jan 2019 22:04:48 +0200, Otto Kekäläinen wrote:
>
> > Just checking: are you Georg or Gregor currently working on this
> > issue, and do you have any estimate when we could expect either a
&g
For the records of this bug report and people following it, there are a lot
of discussions going on in both
https://github.com/perl5-dbi/DBD-mysql/issues/275 and
https://github.com/MariaDB/mariadb-connector-c/pull/95
I will now import MariaDB 10.3.12 into
https://salsa.debian.org/mariadb-team/mari
Now with the mysql version fixed the mariadb version regressed. Does any of
you spot what is the failure cause in
https://ci.debian.net/data/autopkgtest/testing/amd64/libd/libdbd-mariadb-perl/1690599/log.gz
?
MariaDB 10.3 overview at https://tracker.debian.org/pkg/mariadb-10.3
Otto Kekäläinen
Hello!
ke 23. tammik. 2019 klo 16.45 Giovanni Mascellani (g...@debian.org) kirjoitti:
>
> Hi,
>
> the failure is apparently due to insufficient timeout time for some
> tests. Some mipsel builders are more powerful, therefore manage to go
> through all the tests without problems, but other are weak
> Can't you just use dh_link to add a symlink?
I am re-evaluating this fix and considering to revert it. The problem
with Postfix was that it did not find /usr/include/mysql/mysql.h and
we added a symlink in libmariadb-dev to fix it.
However, this symlink already existed in libmariadb-dev-compat,
Hello!
ke 23. tammik. 2019 klo 19.49 Scott Kitterman (deb...@kitterman.com) kirjoitti:
>
> On Wednesday, January 23, 2019 05:32:49 PM Otto Kekäläinen wrote:
> > > Can't you just use dh_link to add a symlink?
> >
> > I am re-evaluating this fix and considering to
FYI: I decided to revert this commit in
https://salsa.debian.org/mariadb-team/mariadb-10.3/commit/71cada820618e00f88325c6e575ed5149eaa9455
We have quite extensive CI that has not spotted any regressions, but indeed
the CI would be even more perfect if it included a 3rd party build test,
e.g. Postf
su 20. tammik. 2019 klo 14.21 Andreas Beckmann (a...@debian.org) kirjoitti:
> Followup-For: Bug #863675
> Control: reopen -1
> Control: found -1 1:10.3.12-1
>
> So, which package is shipping /usr/bin/mysql_config ?
> libmariadb-dev (which got the B+R added) or libmariadb-dev-compat ?
>
> Unpacki
su 20. tammik. 2019 klo 16.21 Andreas Beckmann (a...@debian.org) kirjoitti:
>
> On 2019-01-20 13:39, Andreas Beckmann wrote:
> > Could we please have the symlinks in one direction only?
>
> There is also this Lintian warning:
> W: mariadb-10.3 source: binaries-have-file-conflict libmariadb-dev
> li
su 20. tammik. 2019 klo 14.42 Andreas Beckmann (a...@debian.org) kirjoitti:
...
> -rwxr-xr-x 1 root root 14840 Jan 8 21:52 /usr/bin/mariadb_config
> lrwxrwxrwx 1 root root14 Jan 8 21:52 /usr/bin/mysql_config ->
> mariadb_config
> lrwxrwxrwx 1 root root17 Jan 8 21:52
> /usr/share/man/ma
Control: tag -1 pending
Hello,
Bug #920209 in galera-3 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/mariadb-team/galera-3/commit/43d6848d75f50d7f19ac762fe260
Hello!
The OpenSSL licence will change from 3.0.0 onwards
(https://www.openssl.org/source/license.html) but you are right that
for version 1.1.1 the SSLeay clause applies. MySQL and MariaDB has the
OpenSSL exception, and YaSSL has been used due to earlier
interpretation by non-maintainers that it
2015-07-19 23:16 GMT+02:00 Otto Kekäläinen :
> I cannot however upload it until a fixed version of mysql-5.6 is
> uploaded and has entered 'testing', as the dependency on mysql-common
> 5.6.25 would make all mariadb-10.0 installations in Debian testing to
> fail.
For the rec
This issue was already fixed in commit
http://anonscm.debian.org/cgit/pkg-mysql/galera-3.git/commit/?id=3ccca8f62609bd310d670de0fc96065466eaa2e8
I see your patch also contains diagnostic lines. If you want those
included in the package, please rebase your patch on the current git
master at http://
2016-12-19 1:19 GMT+02:00 Dirk Eddelbuettel :
>
> On 19 December 2016 at 00:05, Andreas Beckmann wrote:
> | I just tried rmysql on the porterbox eller. B-D cannot be installed in
> | sid due to a dpkg-maintscript-helper bug, but stretch works fine.
> | I could build the package in stretch without i
Fix committed in
https://anonscm.debian.org/cgit/pkg-mysql/mysql.git/commit/?id=9ead71eaee19f5c701f7e6c7a9919b2c7de6418b
2017-01-13 0:42 GMT+02:00 Andreas Beckmann :
> Looks good. Cloning/reassigning/retitling the bug accordingly, to keep
> an RC bug against mariadb-10.0 open.
Ok, so we need to have one RC against 10.0 open all the time to
prevent it from migrating from unstable to testing until it has been
cleaned
Thanks Robie for the analysis.
Fixed as suggested in
https://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.1.git/commit/?id=75fa84af6bdf84ff95bd0cabb2a8966330d77154
uld
be placed in /etc/mysql/mariadb.cnf.d/, and for them to be read,
mariadb-common must control the configure-symlinks.
Maybe we should mark both the client and server packages to conflict
each other, and for mariadb-common to conflict on mysql-client and
mysql-server?
--
Otto Kekäläinen
I filed this regression upstream earlier today:
https://jira.mariadb.org/browse/CONC-226
It seems this is still not fixed, so I filed it upstream:
https://jira.mariadb.org/browse/MDEV-11877
Thanks for reporting!
Is this sporadic or does it reproduce every time?
We have this upgrade scenario in CI without issues, thus asking about
reproducibility.
Hi!
I was able to reproduce this with:
apt install mariadb-plugin-gssapi-server mariadb-plugin-gssapi-client
sed s/bullseye/bookworm/g -i /etc/apt/sources.list
apt update
apt-get upgrade
Upgrade only updates mysql-common and mariadb-common:
$ dpkg -l | grep -e mysql -e maria
ii libdbd-mariadb-
After some experimentation I found out that updating libkrb5-3 so that
/usr/lib/x86_64-linux-gnu/libkrb5.so.3 upgrades will stop MariaDB from
crashing.
$ apt install libk5crypto3 libkrb5-3
...
libssl3 amd64 3.0.8-1
libgssapi-krb5-2 amd64 1.20.1-1+b1
libkrb5support0 amd64 1.20.1-1+b1
libkrb5-3 amd6
Hi Andreas!
Thanks for reporting and looking into this.
> Here apt choses a suboptimal removal order: mariadb-server-10.5 gets
> removed (and therefore stopped, but that fails) only after
> mariadb-client-10.5 and mariadb-client-core-10.5 are already gone.
You are right. The /usr/bin/mysqladmin
Control: retitle -1 mariadb-plugin-gssapi-server: crash on partial
upgrade of libk5crypto3
Filed now https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036055
for krb5 maintainers to advise on.
This is not a fix, but could help make the situation easier to
detect/debug for users:
* https://salsa.debian.org/mariadb-team/mariadb-10.5/-/merge_requests/14
* https://salsa.debian.org/mariadb-team/mariadb-10.3/-/merge_requests/37
I did some more testing in throwaway containers.
In each test starting point was same:
apt-get install default-mysql-server zoph
sed s/bullseye/bookworm/g -i /etc/apt/sources.list
apt update
All cases ran apt 2.6.0.
I only varied the command that followed:
1) apt-get install default-mysql-serv
Here is the apt resolver output for debugging:
# apt install default-mysql-server -o Debug::pkgDepCache::Marker=1 -o
Debug::pkgDepCache::AutoInstall=1 -o Debug::pkgProblemResolver=1
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
MarkInstall defau
I am experimenting the suggestion in
https://salsa.debian.org/otto/mariadb-server/-/commits/bugfix/1035949-upgrade-removes-client
Hello!
This is not fixed.
I sampled failing autopkgtests for MariaDB at
https://ci.debian.net/packages/m/mariadb/testing/ppc64el/ between May
7th and 22nd. They still have crashes that include error message
'Database page corruption on disk'. Both failing and passing ones were
running kernel: Lin
I filed now
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/47
as an exploration to fix this issue.
If we don't fix this in 10.11 the alternative would be to patch 10.5
and 10.3 to simply never fail on missing mariadb-client-10.3/5
package. I already did
https://salsa.debian
I adjusted your patch a bit as it didn't apply cleanly and pushed it
to https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/47
to replace the transitional mariadb-client-10.5 I had earlier.
Thanks for diving deep in piuparts testing for MariaDB 10.11 and for the patch!
Ideally t
Indeed the transitional mariadb-server-10.5 fixes the issue.
What do you Andreas suggest we do now?
It is already past freeze for Bookworm, and this is not just a small
fix but also introduces a new package (albeit transitional). Let me
know how you want to proceed and I can immediately tomorrow
Package: release.debian.org
Severity: serious
Tags. bookworm
User: release.debian@packages.debian.org
Usertags: unblock
Control: affects -1 src:mariadb
This pre-unblock request is to get a decision from the Bookworm
release team if you prefer to have this Bug#1035949 fix:
a) in Bookworm in a
Forwarded: https://jira.mariadb.org/browse/MDEV-28640
For reference:
* The upgrade scenario this MR fixed:
https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/15cbf6e691827608636e6ff7f0a50432f50d0c4f
* Release notes mention:
https://salsa.debian.org/ddp-team/release-notes/-/merge_reques
Hi!
Note that upstream released 10.11.4 today. Import preparation in
progress at
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/50.
I plan to upload this to experimental tomorrow and eventually into
bookworm-pu if the release team approves.
- Otto
Thanks Frederick for the report!
Do you still have the output of apt? Can you copy-paste here or attach log
to show exactly what happened?
It is likely that you hit this bug, but exact details would help confirm,
and also help build CI test/scenario to ensure we have realistic upgrade
testing.
Can you attach the full log as an attachment?
The current short log does not show what apt told you in the beginning
about what it plans to do, nor can I see if mariadb-client-10.5 was
uninstalled or what happened.
But it did at least hit a bug where the uninstall fails on
`invoke-rd.c stop maria
Hi!
I did a bunch of reproducible experiments using Salsa-CI in
https://salsa.debian.org/mariadb-team/mariadb-server/-/pipelines/536587
testing:
## upgrade to Bookworm
* cacti and Bullseye upgrade
- apt install -qq --yes cacti
-> - apt full-upgrade -qq --yes
* default-mysql-server and Bu
This is now solved on
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/31
> > This is now solved on
> > https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/31
>
> Mangling the maintainers scripts of another package is a delicate issue
> as it's often fragile and can cause hard to debug failures in corner cases.
>
> Personally, I would have turned the ve
After restarting the build there is no longer a timeout, but a crash:
main.plugin_auth 'innodb'w1 [ fail ] Found
warnings/errors in server log file!
Test ended at 2023-02-05 09:41:56
line
Attempting backtrace. You can use the following information to find out
^ Found warni
Hi!
The error message "Variable 'innodb_compression_algorithm' can't be
set to the value of 'lz4'" is from the first test, and it fails.
Actually all tests fail because in MariaDB 10.11 the compression
methods are packaged in separate packages.
The root cause here is that the test in 10.6 depends
Control: retitle -1 mariadb: FTBFS on s390x: crash on munmap(),
free(), aligned_free()
For the record, the latest build
https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=s390x&ver=1%3A10.11.1-3&stamp=1675662468&raw=0
shows other test failures again, but the stack trace seem to have
munma
And again same phenomenon in
https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=s390x&ver=1%3A10.11.1-3&stamp=1675697634&raw=0.
Copy-pasting more context to track if the main.xml is the preceding
test other times as well:
main.group_by_innodb 'innodb'w2 [ pass ] 11
main.g
Control: severity -1 normal
Control: tags -1 help
The s390x build is still failing after 5 retries at
https://buildd.debian.org/status/package.php?p=mariadb. The issue
seems to be with Debian buildd, as the Launchpad s390x build passed
just fine without the need to retry anything:
https://launchpa
Control: tag -1 pending
Hello,
Bug #1030604 in mariadb reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/5545bb341808cef8a422
For the record, the failing Debian machines run:
Linux ci-worker-s390x-01 5.10.0-21-s390x #1 SMP Debian 5.10.162-1
(2023-01-21) s390x GNU/Linux
The passing Launchpad builders run:
Linux bos02-s390x-013 5.4.0-137-generic #154-Ubuntu SMP Thu Jan 5
17:03:11 UTC 2023 s390x
Control: found -1 1:10.11.2-1
Control: retitle -1 mariadb breaks mariadb-10.6 autopkgtest: provider
plugins not installed
Control: severity -1 normal
Since https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/36
was merged it fixed Bug#1031116 (apt ordering broke Cacti
autopkgtest
> On Tue, 17 Jan 2023 08:00:00 -0800 =?UTF-8?B?T3R0byBLZWvDpGzDpGluZW4=?=
> wrote:
> > This severity 'serious' bug should prevent the migration
> > automatically. Close this bug when migration is free to proceed.
>
> I believe this has happened now. Do you think it should solve that issue
> I was
Forwarded: https://lists.launchpad.net/maria-discuss/msg06508.html
This is most likely a duplicate of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031863
Any updates on this one?
I am still seeing the main.index_merge_innodb failure in
https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=ppc64el&ver=1%3A10.11.2-2%7Eexp1&stamp=1678728871&raw=0
and rebuild
https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=ppc64el&ver=1%3A10.11.2-2%7
> > On Sat, Mar 18, 2023 at 11:19:29PM -0700, Otto Kekäläinen wrote:
> > > Any updates on this one?
> > >
> > > I am still seeing the main.index_merge_innodb failure in
> > > https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=ppc64el&a
> > > Paul Gevers asked if the issues are gone as well with 6.1.12-1
> > > (or later 6.1.y series versions, which will land in bookworm). That
> > > would be valuable information to know as well to exclude we do not
> > > have the issue as well in bookworm.
> >
> > Were you able to verify this?
Ye
Hi!
Thanks for reporting the issue. I saw this earlier and fixed it via
https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/dd3a058ebec877da50aadc9f8909d61ac634430a
- but cleary the fix does not fully work as you ran into this again.
I will dive deeper.
- Otto
Hi!
I have been frantically trying to reproduce the issue you reported.
Would you be able to describe more in detail what was the situation
before and after you upgraded and what commands exactly did you do to
execute the upgrade (apt upgrade, apt full-upgrade, apt-get,
aptitude)?
We might very w
Hi!
I managed now to reproduce this. The purge step is not relevant, but
simply the upgrade itself.
In clean Docker container with Debian unstable:
$ apt install -y mariadb-server-10.6
-> install successful
$ apt full-upgrade -y
-> does nothing
$ service mariadb restart
Stopping MariaDB datab
Hi!
Here is the situation after 'apt full-upgrade -y':
$ dpkg -l | grep -iE 'maria|mysql|galera' || true # List installed
ii default-mysql-client 1.1.0
all MySQL database client binaries (metapackage)
ii default-mysql-client-core 1.1.0
all
Package: mysql-defaults
Version: 1.1.0
Severity: serious
Owner: Otto Kekäläinen
Don't allow mysql-defaults into testing/Bookworm before MariaDB
1:10.11.1-1 has entered it first. There is no package
'mariadb-server-core' in MariaDB 1:10.6.11-2 and thus the defaults
pointer wo
Control: tag -1 pending
Hello,
Bug #928885 in rdiff-backup reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/python-team/applications/rdiff-backup/commit/2c06400c
For some strange reason page https://tracker.debian.org/pkg/mariadb-10.3
still says "Updating mariadb-10.3 introduces new bugs: #910902".
Do you Sandro have any ideas why that is?
For the record, I already did the packaging last weekend and
salsa.debian.org has updates for both 10.3 and 10.5 ready. Now just waiting
for people to respond to various bug reports and follow-ups.
Hello!
Status summary:
* MariaDB 10.5 for Debian is pending at
https://salsa.debian.org/mariadb-team/mariadb-10.5/ since last weekend
but still waiting for contributions on
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988089, #976147 and
#977137.
* MariaDB 10.3 for Debian is pending at
http
Status: Vicențiu is debugging this but has challenges replicating armhf
build
ke 19. toukok. 2021 klo 12.39 Sebastian Ramacher
kirjoitti:
> Control: severity -1 serious
>
> On 2021-05-16 21:26:48 -0700, Otto Kekäläinen wrote:
> > Source: mariadb-10.5
> > Version:
Hello!
Potential armhf FTBFS fix pending at
https://salsa.debian.org/mariadb-team/mariadb-10.5/-/compare/master...bugfix%2F988629-armhf-build-regression
Would somebody have time to help and test build this on armhf? I am
short on time, don't have time to refresh my porter box usage skills.
If no
Control: tag -1 pending
Hello,
Bug #988089 in galera-4 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/mariadb-team/galera-4/-/commit/f1143fadffdbf6a5d0bcd6d4a1
Control: tag -1 pending
Hello,
Bug #988089 in galera-4 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/mariadb-team/galera-4/-/commit/360310c7959ef0b8765f9f6b85
Control: tag -1 pending
Hello,
Bug #988089 in galera-4 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/mariadb-team/galera-4/-/commit/4b794f6573f3ebd4df345d2a5b
Control: tag -1 pending
Hello,
Bug #988089 in galera-4 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/mariadb-team/galera-4/-/commit/042cdaa9b0ea5e66ca7c0ae691
Control: tag -1 pending
Hello,
Bug #988089 in galera-4 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/mariadb-team/galera-4/-/commit/dc908944f0684478f863fb2391
Control: tag -1 pending
Hello,
Bug #988089 in galera-4 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/mariadb-team/galera-4/-/commit/996c84387498e9a5ace52863b5
Control: tag -1 pending
Hello,
Bug #988089 in galera-4 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/mariadb-team/galera-4/-/commit/05fad203bd9fdb2239a55f4d1d
Control: tag -1 pending
Hello,
Bug #988089 in galera-4 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/mariadb-team/galera-4/-/commit/2fc32e6a1aee2c0dc624e93c65
Control: tag -1 pending
Hello,
Bug #988089 in galera-4 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/mariadb-team/galera-4/-/commit/9f425977a2c29f8d8571f04a35
Hello!
On Sun, May 16, 2021 at 4:18 PM Otto Kekäläinen wrote:
>
>
>> > But as said, the bug #988089 can only be fixed by a change in galera-4
>> > debian/control. Changing the mariadb-10.5 debian/control to
>> > recommends:galera-4 is a separate change.
>>
Control: tag -1 pending
Hello,
Bug #988629 in mariadb-10.5 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/mariadb-team/mariadb-10.5/-/commit/011ffd142e7c7c40b8
Hello!
There is an updated Galera-4 in Debian unstable now. If you want to
contribute to the effort, you could now do testing and verify that the
fix delivered works.
On Sun, May 9, 2021 at 8:41 PM Otto Kekäläinen wrote:
>
> Thanks for running the debug commands. Would you like to also re
> Hello!
>
> There is an updated Galera-4 in Debian unstable now. If you want to
> contribute to the effort, you could now do testing and verify that the
> fix delivered works.
I filed now http://bugs.debian.org/989513 but would still welcome
help. There needs to be more testing that the current u
Hello!
Thanks!
Bullseye is meant to ship with 10.5 and 10.3 should be removed once
10.5 has been in Debian testing for a while (currently still in Debian
unstable due to debci false positive).
1 - 100 of 414 matches
Mail list logo
