Hi!
Resurrecting this again and filed as
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/16
with plan to merge it on 10.6 and upload to Debian soon.
Hello Dick!
On Thu, Feb 24, 2022 at 2:54 PM Otto Kekäläinen wrote:
>
> Thanks Dick for reporting #1006388!
>
> We need to fix multi-arch support on MariaDB 10.6 in unstable before
> we can consider backporting anything to Bullseye/10.5. Right now we
> don't have anybody
On Fri, May 20, 2022 at 10:19 PM Cameron Davidson wrote:
>
> On 20-Feb-22 10:42, Otto Kekäläinen wrote:
> > Hello!
> >
> > Thanks for using MariaDB. In the scope of Debian packaging we do not
> > fix upstream bugs. If you have a reproducible test case you coul
Control: tags -1 moreinfo
Hello Akira!
Was https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001843 already
solved for you?
Thanks John for researching this!
Since you are close to solving it, would you like to finalize it by
submitting a MR at
https://salsa.debian.org/mariadb-team/mariadb-server?
https://salsa.debian.org/mariadb-team/mariadb-server/-/wikis/Contributing-to-MariaDB-packaging-in-Debian
Thanks for reporting.
Upstream is scheduled to release new versions in about a month or so,
and the next Debian stable update date will show up at
https://release.debian.org/ when it is planned. There will be no extra
releases of MariaDB 1:10.3.3x in Debian 10 "Bullseye" than the next
stable updat
On Tue, Mar 29, 2022 at 9:33 PM Johnny A. Solbu wrote:
>
> On Sunday 20 February 2022 02:23, Otto Kekäläinen wrote:
> > Is the issue https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996028
> > still affecting people?
>
> We just hit it again on our server aftre4r upgradin
Hi!
Thanks for looking into this. Can you elaborate why you filed this on
26.4.8 and not latest 26.4.10?
Builds are passing. Thus tests indicate that there is no issue. What is the
broken thing exactly and since tests are passing, how will we verify that
the broken thing is fixed or still broken?
Hi Adam!
Could you please also approve upload of galera-4 and galera-3 to
Bullseye stable updates?
Thanks
Control: Severity -1 wishlist
Based on replies from Daniel and Marko this code section is indeed
correct. Also, based on git blame the section you suggest to be
removed was not added in a MariaDB version. However, instead of
closing this bug report as invalid, I leave it open as a wishlist item
in
Source: mariadb-10.6
Version: 1:10.6.7-3
Tags: upstream, confirmed, ftbfs
User: debian-sp...@lists.debian.org
Usertags: sparc64
Forwarded: https://jira.mariadb.org/browse/MDEV-28052
X-Debbugs-CC: debian-sp...@lists.debian.org
After upload of mariadb-10.6 1:10.6.7-3 I noticed that sparc64 builds
a
Source: mariadb-10.6
Version: 1:10.6.7-3
Tags: upstream, confirmed, ftbfs
User: debian-powe...@lists.debian.org
Usertags: powerpc
Forwarded: https://jira.mariadb.org/browse/MDEV-23915
X-Debbugs-CC: debian-powe...@lists.debian.org
Filing this bug for tracking purposes. No help needed from Debian
po
Source: mariadb-10.6
Version: 1:10.6.7-1
Tags: upstream, confirmed, help, ftbfs
User: debian-powe...@lists.debian.org
Usertags: ppc64
X-Debbugs-CC: debian-powe...@lists.debian.org
Builds on ppc64 failed with:
[ 48%] Building CXX object
extra/mariabackup/CMakeFiles/mbstream.dir/xbstream.cc.o
cd /<
/codership/documentation/blob/master/release-notes/release-notes-galera-25.3.35.txt
-- Otto Kekäläinen Wed, 02 Mar 2022 21:39:54 -0800
Debdiff attached. Created with commands:
git diff --stat debian/25.3.34-0+deb11u1..bullseye | xz >
25.3.36-0+deb11u1.debdiff.stat.xz
git diff debian/25.3.3
/codership/documentation/blob/master/release-notes/release-notes-galera-26.4.10.txt
-- Otto Kekäläinen Wed, 02 Mar 2022 21:26:00 -0800
Debdiff attached. Created with commands:
git diff --stat debian/26.4.9-0+deb11u1..bullseye | xz >
26.4.11-0+deb11u1.debdiff.stat.xz
git diff debian/26.4.
> > According to https://release.debian.org/ the next stable update is
> > due
> > in February. Please include this update to MariaDB.
> >
>
> That was the plan, yes. As you probably noticed, we're a little behind
> schedule
That's fine as long as it is just about a couple of weeks, and not
long e
Control: forwarded -1 https://jira.mariadb.org/browse/MDEV-27936
This was actually already in progress upstream. Sorry for escalating
to list before noticing this.
Hello!
A recent build regression on ppc64el is preventing a new MariaDB version
from migrating from unstable to testing.
Could any experts on this list help out?
Please use reply-to-all, I don't subscribe to the list.
Builds on both ppc64 and ppc64el fail due to misc errors related to
htmxlintr
Control: retitle -1 mariadb-10.6: FTBFS on sh4: test suite fails to start
Control: reopen -1
Control: reassign -1 mariadb-10.6
Control: found -1 1:10.6.7-1
This bug still exists for MariaDB 10.6.
In
https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.6&arch=sh4&ver=1%3A10.6.7-1&stamp=16453
Control: retitle -1 mariadb-10.6: FTBFS on m68k: test suite fails to start
Control: reopen -1
Control: reassign -1 mariadb-10.6
Control: found -1 1:10.6.7-1
This bug still exists for MariaDB 10.6.
In
https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.6&arch=m68k&ver=1%3A10.6.7-2%7Eexp1&st
Source: mariadb-10.6
Version: 1:10.6.7-1
Tags: confirmed, help, ftbfs
User: debian-h...@lists.debian.org
Usertags: hurd
Builds on hurd-i386 currently fail due to unknown reasons. See log at
https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.6&arch=hurd-i386&ver=1%3A10.6.7-2%7Eexp1&stamp=164
Source: mariadb-10.6
Version: 1:10.6.7-1
Tags: confirmed, help, ftbfs
User: debian-...@lists.debian.org
Usertags: x32
Builds on x32 currently fail due to unknown reasons. See log at
https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.6&arch=x32&ver=1%3A10.6.7-2%7Eexp1&stamp=1645782519&raw=0
Source: mariadb-10.6
Version: 1:10.6.7-1
Tags: upstream, confirmed, help, ftbfs
User: debian-h...@lists.debian.org
Usertags: hppa
Builds on hppa succeed, but as the mariadbd binary crashes immediately on start:
mysql-test-run: *** ERROR: Error executing mariadbd --bootstrap
Could not install syst
Source: mariadb-10.6
Version: 1:10.6.7-1
Tags: confirmed, help, ftbfs
User: debian-...@lists.debian.org
Usertags: sh4
Builds on sh4 currently fail due to unknown reasons. See log at
https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.6&arch=sh4&ver=1%3A10.6.7-2%7Eexp1&stamp=1645784432&raw=0
Source: mariadb-10.6
Version: 1:10.6.7-1
Tags: upstream, confirmed, help, ftbfs
User: debian-powe...@lists.debian.org
Usertags: ppc64el, ppc64
Builds on both ppc64 and ppc64el fail due to misc errors related to htmxlintrin:
htmxlintrin.h:25:3: error: #error "HTM instruction set not enabled"
htmxl
Thanks Dick for reporting #1006388!
We need to fix multi-arch support on MariaDB 10.6 in unstable before
we can consider backporting anything to Bullseye/10.5. Right now we
don't have anybody on the maintainer team who fully understands the
Debian multi-arch stuff.
If you have suggestions on how
Hello Sebastian!
I have now MariaDB 10.6 working with OpenSSL 3.0.0. Yihuu!
However I have problems making the correct debian/control changes. If
I use just 'libssl-dev' as the dependency then the build will pick up
old OpenSSL 1.1.1. If I use 'libssl-dev (>= 3.0.0)' then only
experimental builds
I've now successfully built MariaDB 10.6 with OpenSSL 3.0 using the
patches CentOS folks had written:
https://salsa.debian.org/mariadb-team/mariadb-server/-/jobs/2498671
Hello!
As part of our CI we run a Bullseye MariaDB 10.5 to Debian Sid MariaDB
10.6 upgrade on every commit. If passes correctly with:
The following packages will be REMOVED:
mariadb-client-10.5 mariadb-client-core-10.5 mariadb-server-10.5
mariadb-server-core-10.5
The following NEW packages wi
Hi!
Personally I don't use trailing dots in d/changelog unless there are
actual full sentences that need them. I do however wish gbp-dch had
this feature, as currently when it does not have it, Lintian-brush
adds trailing dot to git commit message titles.
I find that ugly and I believe most git u
Control: reassign -1 mariadb-server-10.3
Control: tags moreinfo
Hello!
Is the issue https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996028
still affecting people? Did anybody figure out the root cause or what
upstream issue it was, or what version it was fixed in?
Hello!
If somebody wants to continue to work on this issue[1], please submit
your packaging improvement suggestion as a Merge Request on Salsa[2].
I promise to review them promptly.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975911
[2]
https://salsa.debian.org/mariadb-team/mariadb-ser
Package: mariadb-plugin-mroonga
Version: 10.6.5-1
Severity: normal
Tags: newcomer
Hello!
If somebody wants to continue working on this[1] newcomer friendly tagged
bug report, please submit Merge Requests[2].
I promise to review them quickly.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug
Hello!
Thanks for using MariaDB. In the scope of Debian packaging we do not
fix upstream bugs. If you have a reproducible test case you could file
bug report upstream.
We are in the process of uploading 10.3.34, 10.5.15 and 10.6.7 to
Debian. If these versions fix the issue then we can mark the is
Seems upstream added OpenSSL 3.0 support in
https://jira.mariadb.org/browse/MDEV-25785. It has 4 git commits
linked, from which I learned that:
* OpenSSL 3.0 is disabled on all old MariaDB majors
(https://github.com/MariaDB/server/commit/c9beef43154a199bfcd9f71049c011a2ed77ca74)
and enabled only o
Is https://github.com/MariaDB/server/pull/2010 a fix for this perhaps?
Do we have any takers for making 10.6 build with OpenSSL 3.0?
On Thu, Feb 17, 2022 at 2:27 PM Sebastian Andrzej Siewior
wrote:
>
> Source: mariadb-10.6
> Version: 1:10.6.5-2
> Severity: important
> Tags: bookworm sid
> User:
Package: ftp.debian.org
Severity: normal
Hi,
Please remove src:mariadb-10.5 from unstable.
MariaDB 10.5 has been replaced by MariaDB 10.6, which is now available
in unstable and testing.
Ref:
https://tracker.debian.org/pkg/mariadb-10.5
https://tracker.debian.org/pkg/mariadb-10.6
bian/salsa-ci.yml
Latest run shows no upgrade regressions:
https://salsa.debian.org/mariadb-team/mariadb-server/-/pipelines/335209
On Thu, Jan 27, 2022 at 10:05 AM Otto Kekäläinen wrote:
>
> Note that apt-get and apt use different resolvers. Did you
> specifically run 'apt' or 'apt-get'?
Note that apt-get and apt use different resolvers. Did you
specifically run 'apt' or 'apt-get'?
> With mariadb-10.6 migrated to testing, I was expecting to see it
> installed on my bookworm system today. However, it turns out that the
> version of mariadb on my system is determined by
> default-mysql-server-core. I think both packages should agree on what
> the default mariadb version is.
Th
Thanks for the bug report.
Highlighting lines:
>The following packages will be REMOVED:
> mariadb-client-10.5 mariadb-client-core-10.5 mariadb-server
>mariadb-server-10.5 python-pip-whl
The package 'mariadb-server' should not be here but instead
'mariadb-server-core-10.5'.
> On 21-01-2022 21:11, Otto Kekäläinen wrote:
> > Currently mariadb-10.6 is blocked from migrating to testing due to
> > test failure in ruby-mysql2/0.5.3-3
>
> I just uploaded a fix. The bug report already had the solution since
> January 5.
Thanks!
Please submit to
FYI: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004151
Filed skip-test request to release team to get mariadb-10.6 migrate
from unstable to testing.
Package: release.debian.org
Currently mariadb-10.6 is blocked from migrating to testing due to
test failure in ruby-mysql2/0.5.3-3
Please consider adding a migration hint[1, 2] like:
force-skiptest ruby-mysql2/0.5.3-3
We are currently waiting for upstream ruby-mysql2 to make a new
release 0.5.4
Hi!
> Yes, please fix the situation in unstable/testing. It looks like 10.6
> isn't migrating because your reverse depends need fixing first (did you
> report that to the maintainers?); having 10.6 migrate would ease the
> situation a bit because then we can just remove 10.5. I think it would
Wai
uery> with backtrace:
> >
> > Our error message changed.
> >
> > ruby-mysql2 already fixed the test upstream -
> > https://github.com/brianmario/mysql2/commit/cca57b97ad6d1b1b985376be110b89d2b487dea6
> >
> >
> > On Thu, Dec 23, 2021 at 4:47 AM Ot
Hey,
Next MariaDB for Bullseye release tracked in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000342
Status: the stable release team decided not to release the latest
MariaDB 10.5.13 even though it was prepared and uploaded for Bullseye.
Apparently on the grounds that Debian testing does n
Hello!
Yes, you are referring to
https://salsa.debian.org/mariadb-team/mariadb-server/-/blob/debian/latest/debian/control#L12
Indeed, libaio-dev only exists on Linux:
https://packages.debian.org/sid/libaio-dev
This change is related to using uring-io on Linux. The correct
solution here I guess w
On Mon, Dec 13, 2021 at 2:59 AM Anthony Bourguignon
wrote:
>
> Le dimanche 12 décembre 2021 à 20:54 -0800, Otto Kekäläinen a écrit :
> > Hello!
> >
> > > On Thu, Dec 9, 2021 at 5:00 AM Anthony Bourguignon
> > > wrote:
> > > ...
> > > > I
Yes it is in both:
https://salsa.debian.org/mariadb-team/mariadb-10.5/-/commit/2313ef33b1a1adb8299faa3827bd4c519362a641
https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/5dcd5f1abd7502b55701aa1afda154060752a8f8
Hello!
> On Thu, Dec 9, 2021 at 5:00 AM Anthony Bourguignon
> wrote:
> ...
> > I’m having an issue with the mariadb-client in bullseye. I can’t connect
> > to a local server using the mariadb client.
> >
> > To reproduce the bug :
> > - Install bullseye
> > - Install mariadb-server and mariad
Control: severity -1 wishlist
On Thu, Dec 9, 2021 at 5:00 AM Anthony Bourguignon
wrote:
...
> I’m having an issue with the mariadb-client in bullseye. I can’t connect
> to a local server using the mariadb client.
>
> To reproduce the bug :
> - Install bullseye
> - Install mariadb-server and m
> When we were faced with a similar situation for 10.3 last year, we
> decided to proceed anyway as 10.5 was about to become the default
> version and 10.3 was then removed from unstable shortly afterwards.
True
> Looking at the current status of the 10.6 packages in unstable, it
> doesn't seem l
MariaDB 10.6.5 has been uploaded to Sid and will replace 10.5 as soon as it
has the initial bugs weeded out and is same or better overall quality as
10.5.
> On Fri, 2021-11-26 at 22:32 -0800, Otto Kekäläinen wrote:
> > Thanks Paul for the schedule update. Maybe link those emails from
> > release.debian.org so that they are easy to find in the future..?
> >
The current text on https://release.debian.org/ is good, helps a lot
in
> > Before I submit the final debdiff and changelog I will wait for the
> > release date to show up at https://release.debian.org/
>
> Why? The longer you wait, the fewer changes you have to actually get the
> update
> into the next point release. It'd be better to send those debdiffs early and
>
> Could we please change the default keybindings in Debian libedit2 itself,
> instead of having to do same as having to create following ~/.editrc
> for all users on all systems in order for seamless transition?
Modifying .editrc seems like a change that could have a lot of side
effects. Maybe "ba
> > mariadb-10.5 (1:10.5.13-0+deb11u1) bullseye; urgency=medium
> >
> >* New upstream version 10.5.13. Includes security fixes for:
> > - CVE-2021-35604
> >* Drop MIPS and libatomic patches applied now upstream
> >
> > -- Otto Kekäläinen
-35604
* Drop MIPS and libatomic patches applied now upstream
-- Otto Kekäläinen Sat, 20 Nov 2021 12:53:28 -0800
* Drop MIPS and libatomic patches applied now upstream
* Upstream issue MDEV-25114 about Galera WSREP invalid state
fixed (Closes: #989898)
-- Otto Kekäläinen Thu, 18 Nov 2021 20:26:21 -0800
Hello Etes!
Please follow up on this bug report or we can't do anything than close
the issue as invalid.
On Sun, Aug 8, 2021 at 7:15 PM Daniel Black wrote:
>
> Hi,
>
> MDEV-25394 is dissimilar. It is in InnoDB while this appears to be in
> the optimizer code.
>
> A new 10.3.31 is coming soon
> h
Control: tags -1 moreinfo
Jeremy, please follow up on your bug report or we won't be able to help you.
On Tue, Aug 3, 2021 at 1:39 PM Daniel Black wrote:
>
> Jeremy,
>
> You are correct in that this is due to one of the hardening directives
> in the service file Protect{Home,System} or PrivateDe
Oct 11, 2021 at 12:58 AM Otto Kekäläinen wrote:
>
> > The problem is in the ibdata1 file (about 450MB). Deleted other database
> > directories and it still crashes, deleted ibdata1 and it runs.
> >
> > How to bisect mariadb from git? Tried:
> > $ git bisect good
Control: severity -1 normal
On Thu, Oct 21, 2021 at 9:24 PM Marc Gallet wrote:
> I've been brought to this bug by apt-listbugs while doing upgrades
> on my buster install, warning me of a grave bug.
We have two users who have experienced a potentially corrupted
database (out of hundreds of thous
> So maybe I do have a corrupted database or something but I'm unsure what to do
> next (I don't think I have an older backups of the database). Also it still
> works just fine with 10.3.25.
Run it with the old database, make a logical dump (with mysqldump) and
import that logical dump into a fres
Right. Here is for Buster:
https://salsa.debian.org/mariadb-team/mariadb-10.3/-/commit/8ccf2240960cbb609cedfeb269df22d43ccbba21
https://salsa.debian.org/mariadb-team/mariadb-10.3/-/pipelines/302376
Hello!
On Tue, Oct 12, 2021 at 4:51 AM Yves-Alexis Perez wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Mon, 2021-10-11 at 11:27 +0200, Jan Korbel wrote:
> > Maybe this: https://bugs.freebsd.org/bugzilla//show_bug.cgi?id=257728
>
> If I read the bug correctly, it points to
>
Hello!
This is not a duplicate of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995066, right?
Does the same fix
(https://salsa.debian.org/mariadb-team/mariadb-10.5/-/merge_requests/11)
however apply to this too?
> > Latest reference to DEP-14 is in 2016. Following DEP-14 would be
> > easiest if git-buildpackage simply did so by default.
> >
> > Also, it would be nice to see a couple of links to repositories that
> > have DEP-14. Even better would be some stats on the different
> > suggested conventions to
> The problem is in the ibdata1 file (about 450MB). Deleted other database
> directories and it still crashes, deleted ibdata1 and it runs.
>
> How to bisect mariadb from git? Tried:
> $ git bisect good mariadb-10.3.29
> $ git bisect bad mariadb-10.3.31
> the build process showed version 10.2 so I
Hello!
Thanks for reporting. Could you please check if this has been reported
upstream at jira.mariadb.org?
There isn't much we can do about InnoDB internals in Debian packaging.
On Sun, Sep 26, 2021 at 9:27 PM Marco d'Itri wrote:
>
> On Sep 27, Otto Kekäläinen wrote:
>
> > Seems this libcrypt1 change not only affects upgrades from Stretch,
> > but in some cases even upgrades from Buster:
> Buster to Bookworm still means skipping a release.
On Sat, May 8, 2021 at 8:27 PM Otto Kekäläinen wrote:
> Upstream closed the issue
> https://github.com/mroonga/mroonga/issues/353 by removing the file.
>
> Will close the issue once MariaDB imports latest Mroonga and the this
> file is no longer part of MariaDB sources either:
>
This was submitted as
https://salsa.debian.org/mariadb-team/mariadb-10.5/-/merge_requests/7
but not approved yet due to lacking quality assurance. Will most
likely be done in the 10.6 cycle.
Hello Jan!
Readline was changed to libedit in
https://salsa.debian.org/mariadb-team/mariadb-10.5/-/commit/d8796a0e3b5fc4450f4dc80fd159599a7f03997a
because of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940879
when readline5 was orphaned. I don't know if anybody has researched
readline8 (http
Hello!
The output of `mysql_upgrade
--socket=/run/user/1000/akonadi/mysql.socket` in your log from a
Fedora machine is not relevant. The output is exactly the same as any
normal mysql_upgrade run in Debian or elsewhere.
Your Fedora example would only be relevant if you copy the crashed
database f
Hello!
Seems this libcrypt1 change not only affects upgrades from Stretch,
but in some cases even upgrades from Buster:
- https://salsa.debian.org/mariadb-team/galera-4/-/jobs/2008098
- https://salsa.debian.org/mariadb-team/galera-4/-/jobs/2008103
I wonder if there is some workaround? Could we so
Hello!
I tested this today, but unfortunately the yaml.nanorc seems to have
syntax errors:
```
Error in /usr/share/nano/yaml.nanorc on line 6: A syntax name must be quoted
Error in /usr/share/nano/yaml.nanorc on line 7: A 'header' command
requires a preceding 'syntax' command
Error in /usr/share/
Thanks for the report and patch!
Would you want to submit it as a MR at
https://salsa.debian.org/mariadb-team/mariadb-10.5 ?
Hello!
Thanks for looking into the issue and for submitting a fix suggestion
in the form of a patch!
It would be easier to process the patch if it was an actual git commit
with explanation of why you think this is the correct solution, how it
has been tested to verify that it does indeed fix kFre
Hello!
Thanks for the report and the fix suggestion. Would you like to send
it as a Merge Request at
https://salsa.debian.org/mariadb-team/mariadb-10.5 ?
Even though this is just an onliner, please write a good git commit
message and reference the upstream bug report or commit that fixed it.
If i
Thanks for reporting!
Do you want to submit your patch as a Merge Request at
https://salsa.debian.org/mariadb-team/mariadb-10.5 ?
Unfortunately the upstream PR
https://github.com/MariaDB/server/pull/1556 is still pending.
Out of curiosity, why do you use the file at all? Why did you remove
the Ma
This issue is a bit nasty though, as if a user encounters it,
recovering with apt is impossible as dpkg depends on perl and will not
run if libcrypt1 got broken:
$ apt -y install libcrypt1
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to ru
Hello!
Any updates on the Debian package git branch layout?
I am about to start working on mariadb-10.6 and will create a new repo
for it, and would be open to adopting DEP-14 if it is finalized.
If gbp-buildpackage adopts the current DEP-14, please mention it in
the changelog:
https://tracker.
Thanks for a quick reply. I understand why libc6 maintainers prefer
not to touch the dependencies they have unless the issue is severe.
I guess the workaround for this is to manually start the upgrade by
installing perl-base before upgrading the rest of the system.
Package: manpages-dev
Version: 5.10-1
Hello!
I spotted on Salsa-CI runs that when a Stretch system with manpages
4.10 tries to upgrade to Sid, it fails due to conflict with
manpages-dev 5.10. There should probably be some conflicts/breaks
defined in manpages-dev on manpages.
This is visible on a
Package: libcrypt1
The file /lib/x86_64-linux-gnu/libcrypt.so.1 used to be in package
libc6 on Stretch and Buster until it was split off into a separate
libcrypt in Bullseye (and in Sid).
Something in the upgrade logic to adopt the new pacakge is lacking
when upgrading libc6 as the system ends in
Thanks Tobias for looking into it.
When you do testing, please don't do any pinning or other stuff that
interferes with apt. There is no need to recompile anything either.
The versions of MariaDB and Galera in Debian Sid, Testing and Bullseye
are all compiled with the exact same toolchain and are
> Btw. a successful migration should also take care of the redo logs. The user
> normally does not know, whether the database was shut down correctly or not.
Maybe they should, or at least take a backup before a big upgrade so
they can go back to the old version when they see an error message
lik
Please test with the version in Debian testing.
An identical version is about to enter Bullseye in next stable update.
Hello!
I uploaded this now: mariadb-10.3_10.3.31-0+deb10u1_source.changes
ACCEPTED into oldstable-proposed-updates->oldstable-new
Uploading without prior permissions is allowed according to
https://lists.debian.org/debian-devel-announce/2018/04/msg7.html
I will do the same for MariaDB 10.5 a
latest version to Bullseye is important as the upstream
bugs might cause data loss or data to drift in the Galera cluster.
Changelog:
galera-4 (26.4.9-0+deb11u1) bullseye; urgency=medium
[ Otto Kekäläinen ]
* New upstream release 26.4.9. Includes multiple bug fixes, see
https://github.com
Control: tags -1 moreinfo
Hello!
This is not a bug in the Debian packaging and not really an upstream bug either.
The error message seems pretty clear:
> [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was
> created with MariaDB 10.3.27.
Before you upgrade, you need to ens
Control: retitle -1 buster-pu: package mariadb-10.3 10.3.31-0+deb10u1
New MariaDB 10.3.31 is out and it is also a security update. I'll take
this with the sec team since stable updates are not on the horizon
according to release.debian.org.
Hello!
Would you like to submit a Merge Request about this on
Salsa.Debian.org and become a MariaDB contributor?
On Mon, Jul 26, 2021 at 2:23 AM Laurent Bigonville wrote:
>
> reopen 861553
> thanks
>
> Le 26/07/21 à 01:10, Otto Kekäläinen a écrit :
>
> Version: 1:10.5.5-1
Thanks for the report!
Could you do a favour and test and identical scenario with Debian
Bullseye and the MariaDB 10.5 in it?
Both MariaDB 10.3 and 10.5 inherit the upstream systemd service file as-is.
Sources:
10.3:
https://salsa.debian.org/mariadb-team/mariadb-10.3/-/blob/buster/support-files
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package mariadb-10.5 to allow new upstream maintenance
release into Bullseye.
[ Motivation ]
The new upstream version 10.5.11 is a maintenance release that only
fixes bugs.
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package galera-3 to allow new upstream maintenance
release into Bullseye.
unblock: galera-3/25.3.33-1
[ Motivation ]
The new upstream version 25.3.33 is a maintenance relea
Hello!
I've experimented with trying to filter out extra upstream source
directories we don't like automatically in the git-buildpackage step
with filters in
https://salsa.debian.org/mariadb-team/mariadb-10.5/-/commit/f4214a4bee3f4f35ae31746c542cf54bfc9536f7
This would help fix both
https://bugs.
Thanks to Vagrant and Lamby for looking into this.
See results of research at:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985821
https://github.com/mroonga/mroonga/issues/298
I am leaving the issue open as it is not yet fully resolved, but the
affecting part is only in Debian unstable buil
401 - 500 of 1491 matches
Mail list logo
