Control: severity -1 normal
Severity: normal
Downgrading severity since ia64 is an esoteric platform and not worth
preventing the whole mariadb-10.3 from migrating from unstable to
testing for everybody.
> Hi, Otto,
>
> I did submit my patch to upstream and it was
> accepted into 3.1:
>
> https://github.com/mariadb-corporation/mariadb-connector-c/pull/144
>
> It would be great if you could apply this patch to your next
> minor update rather than waiting for 3.1, however, because it
> does fix a
Control: tags -1 moreinfo
Control: severity -1 normal
Severity: normal
Blocking the package from entering testing due to Python team address
issues is not fair, so decreasing severity. Also adding the tag
'moreinfo' since the request for more info is still open.
Hello!
If you want to get progress on this one, please champion it upstream
at https://jira.mariadb.org/browse/MDEV-17662 in a well argumented and
detailed way.
In Debian we don't want to diverge from upstream on this one, since it
would add the maintenance burden. Better get if fixed globally
Hello!
I have now submitted mariadb-10.5 release 1:10.5.5-1~exp1 to the NEW queue:
https://ftp-master.debian.org/new/mariadb-10.5_1:10.5.5-1~exp1.html
It is based on the latest mariadb-10.4 packaging with upstream
watchfile, sources and contents updated for the 10.5 series. This is
the first
Hello!
If this issue is still relevant, and you have a suggestion how to fix
it, please file a Merge Request on Salsa as a proposal. Thanks!
https://wiki.debian.org/Teams/MySQL/patches
Hello!
Please participate in the discussion upstream at
https://jira.mariadb.org/projects/CONC/issues/CONC-211 if you want to
champion this forward.
Thanks!
Hello!
If this issue is still relevant, and you have a suggestion how to fix
it, please file a Merge Request on Salsa as a proposal. Thanks!
https://wiki.debian.org/Teams/MySQL/patches
Hello!
If this issue is still relevant, and you have a suggestion how to fix
it, please file a Merge Request on Salsa as a proposal. Thanks!
https://wiki.debian.org/Teams/MySQL/patches
Source: mariadb-10.3
Version: 1:10.3.24-1
Severity: serious
Justification: fails to build from source
User: debian-i...@lists.debian.org
Usertags: ia64
The MariaDB Server package was building fine on ia64 in version
1:10.3.23. However the most recent upload regressed it.
Before:
Source: mariadb-10.4
Version: 1:10.4.13-1~exp1
Severity: important
Tags: upstream
Justification: fails to build from source (but built successfully in the past)
User: debian-h...@lists.debian.org
Usertags: hppa
The MariaDB Server package was building fine on hppa in version
1:10.4.12-1~exp3.
Package: mariadb-10.4
Severity: wishlist
MariaDB 10.5.4 was announced for general availability (GA) on June 24th, 2020.
https://mariadb.com/kb/en/mariadb-1054-release-notes/
The first fix release after GA was announced on August 10th, 2020.
https://mariadb.com/kb/en/mariadb-1055-release-notes/
Source: mariadb-10.3
Version: 1:10.3.13-1
Severity: serious
Justification: fails to build from source
User: debian-al...@lists.debian.org
Usertags: alpha ftbfs
The MariaDB Server package was building fine on alpha in version
1:10.3.12-2. However the next upload of 1:10.3.13-1 regressed it, and
Source: mariadb-10.4
Version: 1:10.4.13-1~exp1
Severity: important
Tags: upstream
Justification: fails to build from source (but built successfully in the past)
User: debian-sup...@lists.debian.org
Usertags: sh4
The MariaDB Server package was building fine on sh4 in version
1:10.4.12-1~exp3.
Hello!
Following up on the MariaDB riscv64 build issue.
In MariaDB 10.3.24 the libatomic on RocksDB patch at
https://github.com/mariadb/server/commit/715beee46abb4c29bffd6f9c5fd5ee95da55bf4f
was applied and thus MariaDB issue
https://jira.mariadb.org/browse/MDEV-23051 was closed.
Conversation
Package: libmysqld-dev
Severity: critical
Steps to reproduce and result:
apt-get install -y libmysqld-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation
Hello!
If this issue is still relevant, and you have a suggestion how to fix
it, please file a Merge Request on Salsa as a proposal. Thanks!
https://wiki.debian.org/Teams/MySQL/patches
Tags: -1 moreinfo
Hello!
If this issue is still relevant, and you have a suggestion how to fix
it, please file a Merge Request on Salsa as a proposal. Thanks!
https://wiki.debian.org/Teams/MySQL/patches
Tags: -1 moreinfo
Hello!
Seems the upstream PR was closed at https://github.com/lxc/lxc/pull/2758
Can you please confirm if this still affects MariaDB in Debian?
If you have suggestions of changed needed on the MariaDB packaging,
please file a Merge Request on Salsa as a proposal. Thanks!
Hello!
If this issue is still relevant, and you have a suggestion how to fix
it, please file a Merge Request on Salsa as a proposal. Thanks!
https://wiki.debian.org/Teams/MySQL/patches
Hello!
If this issue is still relevant, and you have a suggestion how to fix
it, please file a Merge Request on Salsa as a proposal. Thanks!
https://wiki.debian.org/Teams/MySQL/patches
Hello!
If this issue is still relevant, and you have a suggestion how to fix
it, please file a Merge Request on Salsa as a proposal. Thanks!
https://wiki.debian.org/Teams/MySQL/patches
If this issue is still relevant, and you have a suggestion how to fix
it, please file a Merge Request on Salsa as a proposal. Thanks!
https://wiki.debian.org/Teams/MySQL/patches
Tags: -1 moreinfo
Hello!
Sorry for late reply.
The MariaDB packages in Debian does not ship any
/etc/logrotate.d/mysql-server file.
Where did you get it from?
Fixing that nothing installs /etc/logrotate.d/mysql-server should be
the solution, but first we need to figure out what installed it.
Hello!
Seems this was a duplicate of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960285 and was
closed in the 1:10.4.13-1~exp1 release.
Hello!
Seems this was fixed in MariaDB 10.3.17:
https://github.com/mariadb/server/commit/620f4f8af98666e2efb7e14fb2663ab85b52bc12
Could you please help Debian package maintainers and check if the
issue is fixed, and update the bug report as "Closed" if so?
Hello!
If this issue is still relevant, and you have a suggestion how to fix
it, please file a Merge Request on Salsa as a proposal. Thanks!
https://wiki.debian.org/Teams/MySQL/patches
Hello!
If this issue is still relevant, and you have a suggestion how to fix
it, please file a Merge Request on Salsa as a proposal. Thanks!
https://wiki.debian.org/Teams/MySQL/patches
In MariaDB 10.4 and onwards, the server itself (but in 10.5 and
onwards not in ColumnStore) the libreadline has been replaced with
libedit, so this issue can be closed when 10.4 or 10.5 lands in Debian
unstable.
Hello!
I agree with Raphaël's comments. The wording of this error could be
improved a bit.
In
https://mariadb-team.pages.debian.net/-/mariadb-10.3/-/jobs/929803/artifacts/debian/output/lintian.html
I got
E duplicate-globbing-patterns mysql-test/mysql-stress-test.pl in lines
213 467 467
E
While researching this I only found packages that list the old group email:
Maintainer: Python Applications Packaging Team
-
https://salsa.debian.org/python-team/applications/nitrotool/-/blob/master/debian/control
-
Hello!
Thanks for reporting!
It would be best if you submitted your patch directly upstream at
https://github.com/mariadb-corporation/mariadb-connector-c/
They have the best knowledge to assess if this change is OK or if it
has potential regressions.
Package: liquidprompt
Hello!
There is a new upstream release available at
https://github.com/nojhan/liquidprompt/tags
Please import it to Debian.
Upstream is currently publishing release tags correctly
(https://github.com/nojhan/liquidprompt/issues/580) and the
debian/watch has detected the
.
-- Otto Kekäläinen Sat, 04 Jul 2020 15:31:51 +0300
Since the amendment is so small I will not attach a new debdiff.
Latest source always visible at
https://salsa.debian.org/mariadb-team/mariadb-10.3/-/tree/buster
Hi!
su 5. heinäk. 2020 klo 14.24 Adam D. Barratt
kirjoitti:
> On Sun, 2020-07-05 at 11:00 +0300, Otto Kekäläinen wrote:
> > For unstable the plan is to upload MariaDB 10.5 soon, and therefore
> > uploads of MariaDB 10.3 are already discontinued.
>
> How soon is "soon&q
For unstable the plan is to upload MariaDB 10.5 soon, and therefore
uploads of MariaDB 10.3 are already discontinued. Since we already
have MariaDB 10.4 in Debian experimental, it is not even possible to
do any uploads of MariaDB 10.3 because of triggering the NEW queue and
version
Control: tags -1 -moreinfo
> Tagging your bug "moreinfo" means that it's not ready for processing by
> SRM. Is that what you intended?
Thanks for a quick response. I just copied the previous stable update
email I've sent without realizing that it wasn't directly suited.
Sorry for the mistakes.
Forwarded: https://jira.mariadb.org/browse/MDEV-23051
Thanks Christian!
Note that riscv64 is nowadays an official platform for Debian, and
failures to build on riscv64 prevents MariaDB Server from being synced
from Debian to Ubuntu and Ubuntu will end up with outdated versions.
Build and sync
Hello!
Thanks for reporting. I am fixing this for mariadb-10.4 now. Feel free
to send a MR if you have more suggestions on how to improve the
copyright file.
https://salsa.debian.org/mariadb-team/mariadb-10.4/-/commit/23ff3734057e0f634ee1b04f6b6a7ec04db2b1ab
Hello!
I can verify that this bug was introduced today and among others my
Salsa-CI builds started failing due to this. Example log:
https://salsa.debian.org/mariadb-team/mariadb-10.4/-/jobs/827756
I've CC'd a couple more Salsa-CI devs who might want to confirm if
this affects all Salsa-CI
Thanks for reporting this.
Currently in mariadb-10.4 in Debian:
https://salsa.debian.org/mariadb-team/mariadb-10.4/-/blob/master/debian/libmariadb3.install
usr/lib/*/libmariadb.so.*
usr/lib/*/mariadb19/plugin/client_ed25519.so
usr/lib/*/mariadb19/plugin/dialog.so
Forwarded: https://github.com/nojhan/liquidprompt/issues/580
> My question is: Why does the server sometimes require this file to be
> present, and where? I mean, this software has imho no business asking
> for that file, to begin with.
I have never seen this issue anywhere and I have no clue what that
file is. If you can provide instructions how to
Thanks for reporting!
Can you provide us enough information about your environment so we
could try to reproduce this error?
Or can you reproduce it yourself in a Docker, LXC or other container
with a clean Debian environment?
Hello!
There are currently no stable point updates planned
(https://release.debian.org/) but once there is one, it will have the
latest MariaDB point release available at that time.
Thanks for reporting this issue, so we can track it.
Hello Alexandre!
> I've searched the tracker (https://tracker.debian.org/pkg/mariadb-10.3) and
> the BTS and couldn't find any trace of discussions for updating the
> mariadb-10.3 version to the upstream one.
>
>
>
> For information, 10.3.23 does fix a critical bug that prevent mariadb to
>
Hello!
Because of the vagueness of Oracle CVEs, I cannot judge if this
warrants a DSA or not.
I am happy to prepare a security update for you if you so request.
Currently https://release.debian.org/ states:
> stable (10.5) Not yet planned
> oldstable (9.13) Not yet planned
..so I will not rush
> I have not much to add to your analysis, and I agree in that we can't
> and shouldn't change the structure of the packages in existing stable
> releases. However we can take this issue as a good warning on the fact
> that compatibility between the two DBs can't be assumed, and the
> packages in
A future version of MariaDB might have the charsets in its own
directory, but we can't start changing paths of stuff in existing
stable releases, such as MariaDB 10.3 in Ubuntu 20.04 or Debian
Buster. If MySQL introduces a backwards incompatible change, the new
uploads should test for them and
Hello!
> /usr/share/mysql/charsets
..
> The location of these files causes the libmysqlclient20 client library
> to consider them charset files from mysql, and it tries to use them.
>
> I think this behavior is wrong, as the charset files do not belong to
> mysql, however it is not immediately
Thanks for the report!
There are new upstream releases of both Galera 3 and Galera 4, and I
intend to upload them and work with any remaining FTBFS issues in
coming weeks.
Yes, installing build-essential manually has been the work-around I've
been using. So that is now the permanent solution?
Hi!
I am sponsoring this effort. It has now passed my review and I've
uploaded it to NEW:
https://ftp-master.debian.org/new/mystiq_20.03.23-1.html
Source now hosted at https://salsa.debian.org/debian/mystiq
--
- Otto
Hello!
> Otto:
> > The Salsa-CI discussions still have no mailing list to go to. Could
> > you please create a mailing list for the team now?
> Alexander:
> We told you which list to use.
The debian-ci list is about autopkgtest and the autopkgtest managers
have explicitly said that it is not
Hello!
The Salsa-CI discussions still have no mailing list to go to. Could
you please create a mailing list for the team now?
ke 17. heinäk. 2019 klo 8.33 Otto Kekäläinen (o...@debian.org) kirjoitti:
>
> Hello!
>
> There are now 10 people discussing "Licensing salsa-ci pipel
Package: equivs
Version: 2.3.0
I noticed my builds started failing today with error message:
Step 4/7 : RUN DEBIAN_FRONTEND=noninteractive mk-build-deps -r -i
control -t 'apt-get -y -o Debug::pkgProblemResolver=yes
--no-install-recommends'
---> Running in 912092c7ebbd
dpkg-buildpackage:
Forwarded: https://github.com/codership/galera/issues/572
Thanks for looking at this! I filed it upstream as well.
I am happy to take MR at
https://salsa.debian.org/mariadb-team/galera-3 if you have ideas on
how to fix this.
Note that on Debian Sid tha main focus is already on galera-4.
Hello!
Thanks for submitting this!
Would you like to volunteer to write a Salsa-CI test case for this use
case? That way we can easily repeat the issue and once fixed, ensure
it never happens again.
Here is an example how we in the CI test that building an app against
libmariadb works:
Thanks for reporting and researching!
Looks like this isn't going to be fixed for 10.1, but you can use a
SSH tunnel with 10.1 or alternatively upgrade MariaDB to a newer
version.
Hello!
I am also in favor of this idea. I renewed my key a couple of weeks
before it expired, but I should have renewed it 2 months before. I did
not factor in the delay in the keyring releases (now already 6+ weeks
since last release).
Getting an automated reminder would indeed have been
Hello!
Related to this is upstream issue
https://jira.mariadb.org/browse/MDEV-21835 where Robert Bindar is
working to make MariaDB support building with system WolfSSL. Robert
might fill on this
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952538) issue if
there are needs regarding what the
> > OK, but for MariaDB the
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707750 does not
> > apply anymore thanks to
> > https://salsa.debian.org/mariadb-team/mariadb-10.4/-/commit/b50ee2eb0bdca49583cf447ded46f799198cd4bf
>
> Great news. As far a s I can see, it still applies to
Hello!
> > I am happy to do these changes for you in the Debian package, but I
> > wasn't quite able to follow what script do you mean is the
> > replacement?
>
> The bug submission has a shell script attached.
>
> $ ./mysql_config_generator.sh debian/libmariadb-dev/usr/bin/mariadb_config >
>
Thanks, perfect! I merged it now.
I am more than happy to get more contributions from you if you want to
help out with something.
Package: wolfssl
Priority: wishlist
Hello!
It would be nice if the package had tests. Currently it seems to build
on all platforms, but we cannot be sure that it actually _runs_ on all
platforms. I am currently looking into an issue where MariaDB with
WolfSSL builds on s390x but the binary
Hello!
Thanks for the patch! Now s390x fails with:
/<>/libmariadb/libmariadb/secure/openssl_crypt.c: At top level:
/<>/libmariadb/libmariadb/secure/openssl_crypt.c:21:10:
fatal error: openssl/evp.h: No such file or directory
Hello!
> I am also available to help if you provide your source package.
I was working on a variant of mariadb-10.4 that would use system
WolfSSL in
https://salsa.debian.org/mariadb-team/mariadb-10.4/-/compare/master...feature%2Fsystem-wolfssl
Are you familiar with Salsa? At least the package
Package: libwolfssl-dev
Hello!
While trying to build MariaDB 10.4 using the Debian provided WolfSSL
it fails due to missing user_settings.h. Upstream does have this file
(and many versions of it). Why is it missing from Debian?
https://packages.debian.org/sid/amd64/libwolfssl-dev/filelist
Hello!
Upstream has had a habit of changing the symbols a bit. Luckily they
are all tracked in packaging:
https://salsa.debian.org/mariadb-team/mariadb-10.3/commits/buster/debian/libmariadb3.symbols
Usually upstream has been careful and wise in what symbol changes they
make.The updated symbols
We can keep this issue open in Debian and close it in the changelog in
the next upload – that way it is easy to track in which Debian
releases the fix has been shipped.
Thanks for reporting.
At least the packaging in Debian has not changed. This is probably an
upstream bug.
Have you checked jira.mariadb.org for bugs related to "lc_messages = fr_FR" ?
What is the version you had before upgrading?
- Otto
> tail: cannot open '/home/debci/.kodi/temp/kodi.log' for reading: No such file
> or directory
> tail: no files remaining
This is the only output in the test log, otherwise it is installing
packages and everything else seemed to go fine.
Test source says it just starts the app, but now it does
Ok, I will amend the changelog and re-upload today 1:10.3.22-0... to buster
updates.
Thanks for pointing out this mistake.
Unfortunately it was already uploaded. There are frequently releases to
unstable/testing so I don't expect this to cause any bigger problems.
Past and future changelog entries will not have this mistake.
Hello!
Yes, we are working on it. I am both upstream and Debian maintainer. I
need to fix some upstream bugs first and will import to Debian a
version that makes sense to introduce in Debian unstable.
Control: tags -1 -moreinfo
Control: severity -1 normal
Based on #950309 security updates don't seem to warrant 'serious', so
dropping to 'normal'.
Also removing tag moreinfo that was inherited from a stable update bug
report template. apparently it is not part of the process.
As per info below, making MariaDB cross-buildable this bug should be
fixed first.
> On Thu, Jan 09, 2020 at 09:25:07PM +0200, Otto Kekäläinen wrote:
> > Despite previous help from Helmut and some effort into cross-building,
> > mariadb-10.3 does not currently seem to cross buil
Hello!
Personally I don't have any SELinux experience, but I would be happy to
merge a well tested and documented patch if somebody wants to work on this.
See https://wiki.debian.org/Teams/MySQL/patches on how to use automated
testing.
Updating bug status:
- This was filed as a pull request at
https://github.com/ottok/mariadb-10.0/pull/46
- I plan to finalize this for the mariadb-10.4 cycle.
I am terribly sorry I was not able to finalize this in due time.
Hello!
There has not been any progress on this one for a long time.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851195
Would you like to champion it upstream?
Currently this Debian bug report does not even have a link to MariaDB
Jira in case this is already reported there.
- Otto
Control: severity -1 normal
Control: tags -1 moreinfo
More info is needed if you want anybody to help out with this:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943974
Control: forwarded -1 https://jira.mariadb.org/browse/MDEV-21317
Thanks for reporting!
Unfortunately this project was discontinued by the original author in
2019 and no contributions upstream were accepted since 2016. So this
bug will not be fixed unless somebody completely forks the original
project at https://github.com/dagwieers/dstat
Forwarded: https://jira.mariadb.org/browse/MDEV-21317
Hello!
Thanks for reporting and the patch!
Since that patch is not about Debian packaging, I suggest you submit it
upstream at https://github.com/mariadb/server branch 10.3 (or latest 10.5).
We are waiting for Galera 4 to be officially released at
https://releases.galeracluster.com/
Thanks for reporting!
Since you seem to know the exact solution, would you like to make a
merge request at https://salsa.debian.org/mariadb-team/galera-3 or
even directly upstream at https://github.com/codership/galera (as this
file is inherited from upstream)?
- Otto
Hello!
MariaDB 10.3.20 is already out and I am in the process of preparing it..
Did you investigate anything suggested in
https://forum.manjaro.org/t/computer-does-not-shut-down-because-of-mariadb/81565
?
Did you figure it out?
Control: tags-1 moreinfo
Hello!
Thanks for reporting! Unfortunately you report does not include
anything useful for debugging. Please provide some log output from
system and mariadb logs, what files you have, maybe something how your
system is customized etc. The default MariaDB install does not
Hello!
Yes, upstream developers will value a good trace.
Debian ships debug symbols for all packages by default. You just need
to install them from the debug repository. Maybe this helps
https://wiki.debian.org/HowToGetABacktrace ?
Hello!
Did you report this bug upstream (as the output said "To report this
bug, see https://mariadb.com/kb/en/reporting-bugs;). This is unlikely
related to the packaging done in Debian.
pe 1. marrask. 2019 klo 22.57 Richard van den Berg
(rich...@vdberg.org) kirjoitti:
>
> Package:
Architecture: source
Version: 1:10.3.18-0+deb10u1
Distribution: buster
Urgency: high
Maintainer: Debian MySQL Maintainers
Changed-By: Otto Kekäläinen
Description:
libmariadb-dev - MariaDB database development files
libmariadb-dev-compat - MariaDB Connector/C, compatibility symlinks
libmaria
> IMHO, if we ship it at all, innotop should be shipped as a separate
> Debian source package with appropriate declared dependencies and
> autopkgtests. This current breakage might be an opportunity to fix that.
Makes sense.
Any volunteer takers?
Thanks for the suggestion!
Do you want to contribute and make a MR about that change?
https://wiki.debian.org/Teams/MySQL/patches
Control: tags -1 moreinfo
la 21. syysk. 2019 klo 1.57 Axel (a...@users.sourceforge.net) kirjoitti:
>
> Package: mariadb-server-10.3
> Version: 1:10.3.17-0+deb10u1
> Severity: important
>
> Dear Maintainer,
>
> the server keeps crashing every few seconds although no database structures,
>
> Some poking around on Github suggests that the fix is
> https://github.com/MariaDB/server/commit/47f8a18fec604983e47fdf7c822d94b26d85cade
>
> If this is actively breaking systems, couldn't we simply apply that
> patch to the current versions in stretch and buster, as a least-change
> option?
We
> [For reference, X-Debbugs-Cc is generally better than your mail client's
> CC when submitting bugs, as it means the recipient gets the mail from
> the BTS with the bug number included]
[rant] I'll try to remember, but this UI that is based on me
remembering all the option names and syntaxes (or
Buster PU filed as Bug#940521
la 14. syysk. 2019 klo 16.57 Adam D. Barratt
(a...@adam-barratt.org.uk) kirjoitti:
>
> On Fri, 2019-09-13 at 21:10 +0300, Otto Kekäläinen wrote:
> > To clarify, 10.3.18 has been uploaded to Debian unstable. Issue is
> > still open for Buster and Stretch.
>
> Is the
701 - 800 of 1481 matches
Mail list logo
