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
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
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
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
> 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
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
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=sparc64=26.4.18-1%7Eexp1=1713134650=0:
Running tests...
/usr/bin/ctest --force-new-ctest-process --output-on-failure
Test project /<>/obj-sparc64-linux-gnu
Start 1: gu_tests
1/7
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=ia64=26.4.18-1%7Eexp1=1713220669=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
>
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
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
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=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
] This 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 perhaps
> > 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
>
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
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
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
Hi Graham!
I have your change pending at
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/68.
Do you want me to put it into unstable now?
Thanks Daniel!
Pushed to
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/70
for additional testing/review
Hi!
I did additional testing and converted the attached patch into a MR
ready to be merged on the debian/latest branch and uploaded to
unstable:
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/68
Seems the experimental builds for MariaDB went OK. Let me know when is
the
Thanks for maintaining this package in Debian, it is very useful!
Could you please update it to latest version 7.2 so both Trixie and
also Ubuntu 24.04 will ship with a fresh version?
Thanks
Hi!
Please do not do non-maintainer-uploads. This package is actively
maintained, we can just include your patch in the next upload in a
couple of days.
On Sat, 3 Feb 2024 at 11:57, Graham Inggs wrote:
>
> Source: mariadb
> Version: 1:10.11.6-2
> Severity: serious
> Tags: patch pending sid
Thanks!
This is pending now at
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/66
I opened an MR about this one at
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/65
to get CI validation.
I will do some more testing over the weekend and then merge both.
Thanks for your contribution!
Thanks, I wil check all occurrences of /lib after
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/29
has been approved and merged.
Your review on that one would be appreciated.
Hi Peter and Toby!
The issues about systemd are potentially fixed in
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/29
Please test it (you can download the .deb packages from the pipeline
build artifacts
(https://salsa.debian.org/otto/mariadb-server/-/pipelines/628913) and
Control: forwarded -1 https://github.com/MariaDB/server/pull/2995
This will be fixed in Debian next month when MariaDB 10.11.7 releases
Hi oldstable release managers,
I got email after my upload 11 days ago that 10.5.23 was accepted in
oldstable-proposed-updates but I don't see any updates under 'News' at
https://tracker.debian.org/pkg/mariadb-10.5 yet.
Is the update progressing automatically somewhere?
Control: outlook -1 Superseded by Pulsar ITP #1060778
Seems there was a lot of interest in this Atom ITP. I just wanted to
let you know that I filed an ITP[1] for packaging Pulsar, which
superseded Atom[2].
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060778
[2]
Hi!
On a quick review of the deb packages offered at
https://www.id.ee/en/article/install-id-software/ and the related
source code https://github.com/open-eid and documentation
https://open-eid.github.io/ I did not spot any reason why it could not
be properly packaged for Debian officially.
If
Hi!
I am a big fan of Pulsar[1] so I filed the ITP[2] for it which led me
to dive into the status of Electron[3] and NodeJS and JavaScript in
Debian in general.
Electron seems already to be shipped[4] among others in FreeBSD ports,
Arch, Manjaro, Nix and OpenSUSE, but not in Fedora or Debian.
FYI: Discussion about this continued in
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/61
Package: wnpp
Severity: wishlist
Owner: Otto Kekäläinen
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: pulsar-edit
Version : 1.112.1
Upstream Contact: ad...@pulsar-edit.dev
* URL : https://pulsar-edit.dev/
* License : MIT
Programming Lang
On Sat, 20 May 2023 at 12:24, Henrik Riomar wrote:
>
> Reproduction of the bug is simple with safekeep from a system running Debian
> 11 trying to backup a system running Debian 12.
>
> The backup can not even start, just get "Exception ''restrict_path'' raised
> of class ''" from rdiff-backup
Control: tag -1 help moreinfo
Hi!
I don't think the Python packagers in Debian have capacity to debug
this issue in upstream code.
Could you as the original reporter check if this has already been
reported upstream at
https://github.com/rdiff-backup/rdiff-backup/issues?
Control: tag -1 help moreinfo
Hi!
I don't think the Python packagers in Debian have capacity to debug
this issue in upstream code.
Could you as the original reporter check if this has already been
reported upstream at
https://github.com/rdiff-backup/rdiff-backup/issues?
Control: merge 974526 1024096
This is a confirmed need, but pending for contributors to submit
something at
https://salsa.debian.org/python-team/packages/rdiff-backup/-/merge_requests
03 février 2023 à 15:11 -0800, Otto Kekäläinen a écrit :
> > Thanks for using rdiff-backup in Debian. The latest version
> > (https://tracker.debian.org/pkg/rdiff-backup) has recently been
> > uploaded to Debian. I would appreciate it if you can help testing it,
> > and perh
...
> …skipping binNMUs ?
The "spec" I drafted probably forgot some more cases as well, hence
good to have a issue open for a while to collect feedback/ideas to
further refine the logic and capture corner cases :)
..
> Somewhat related is /usr/share/doc/git-buildpackage/examples/gbp-upload
>
Package: git-buildpackage
Severity: wishlist
Hi!
I frequently find myself doing manual work comparing if my local git
repository contents and tags are correct and in sync with the git
remotes and the Debian and Ubuntu archives.
I am worried about mistakes such as:
- A maintainer tagged and
Package: lintian
Version: 2.116.3
Severity: normal
While preparing entr 5.5 I imported upstream sources directly based on
upstream git tag using command:
gbp import-ref --verbose --upstream-version=5.5
Eventually after building the resulting .changes file being uploaded
did not contain the
New 1:10.116-2 uploaded, looking good so far at
https://tracker.debian.org/pkg/mariadb:
autopkgtest for mariadb/1:10.11.6-2: amd64: Pass, arm64: Pass, armel:
Pass, armhf: Pass, i386: Pass, ppc64el: Test in progress, s390x: Pass
> > The ci.debian.net results for mariadb seem to be very flaky lately (on
> > amd64 they fail roughly 9/10) since version 1:10.11.6-1. Might be
> > related (although the failure is different). i386 and arm64 seem to be
> > exceptions.
>
> No - the current CI failures for MariaDB are unrelated and
> Thanks Daniel Lewart!
>
> I filed your submission at
> https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/61
> for review/testing/feedback.
The Salsa-CI autopkgtests shows that this change affects the default
mariadbd server command-line parameters:
Thanks Guido of for the inside about backwards compatibility issues. I did
not realize that git-buildpackage doesn't have way did is distinguish when
it is running on an existing repository and when on a 'fresh' repository.
Maybe we can engineer something to give it that capability automatically,
Hei Paul!
Thanks for taking the time to report these upstream along with patches!
I don't see the upstream MDEVs having a status 'fixed' nor any
confirmation/review about the patches yet. Let's wait a bit for a
feedback round.
## arm64
All green at https://ci.debian.net/packages/m/mariadb/testing/arm64/
Latest log has "Completed: All 1049 tests were successful."
## i386
Likewise, all green at https://ci.debian.net/packages/m/mariadb/testing/i386/
Latest log has "Completed: All 1047 tests were successful.".
## armel
Summary of current status of https://ci.debian.net/packages/m/mariadb/
## ppc64el
Last passed in
https://ci.debian.net/packages/m/mariadb/testing/ppc64el/40870773/
where 1048 tests were successful:
MariaDB: 1:10.6.11-1
kernel: Linux 6.5.0-0.deb12.4-powerpc64le
The log above includes 4 variants
Hi and Happy New Year!
Using 'debian/latest' instead of 'master' by default in
git-buildpackage would still make sense.
I started drafting a PR at
https://github.com/agx/git-buildpackage/pull/93 to implement this, but
it takes a while to read through and understand all the 500+ mentions
of
Hi!
I have been running riscv64 builds and test suite at
https://launchpad.net/~mysql-ubuntu/+archive/ubuntu/mariadb-10.11/+builds?build_text=_state=all
for several months and all known riscv64 issues have been fixed. This
is a new one - I will take a look and probably apply the patch from
I am working on a 1:10.11.6-2 upload to fix these. If I can make them
reliable, I will temporarily disable the test suite.
Package: release.debian.org
Followup-For: Bug #1057180
Control: retitle -1 bullseye-pu: package mariadb-10.5/1:10.5.23-0+deb11u1
Control: tags -1 -moreinfo
The MR at
https://salsa.debian.org/mariadb-team/mariadb-10.5/-/merge_requests/16
has been merged and is ready to proceed to upload.
##
As it is very unlikely to get changes anymore after 4+ weeks of
pending review, I uploaded it in the delayed 7 days queue.
Package: lintian
Severity: minor
Currently on my fairly performant Intel i7 / Dell XPS 13 laptop the
Lintian run for the mariadb source package takes 6-7 minutes. I spent
some time analyzing what is going running Lintian with --debug and
--jobs and I noticed that running Lintian with --jobs=8 is
Thanks for the clarifications!
I updated the man page in
https://salsa.debian.org/debian/devscripts/-/merge_requests/378 so
that the next DD trying to figure out what dget is for will have an
easier time.
Thanks for the example.
Apt can be used to download a specific source version of something
with the = parameter, which you probably know. In this case your
example showed that one can't use apt to download versions from
another (historic) Debian release.
apt-get source glibc=2.19-13
Reading
Hi!
> Subject: Re: Bug#1059551: Remove obsolete command 'dget'
> Ummm, no. dget is a very useful tool with very different use cases
> from apt-get - particularly when grabbing source packages.
What if we then at least update the man page to mention `apt-get
download` and `apt-get source
Hi!
I just wanted to +1 on this idea.
I am exploring this in order to get my text editor to nag about findings
immediately without separate build steps. To implement something similar to
e.g. linter-shellcheck[1] in my favorite editor it would help immensely if
Lintian would accept simply the
Package: devscripts
Version: 2.23.7
Currently devscripts contains package 'dget' [1] for downloading
Debian binary/source packages.
Everything it does can be done using apt-get. The man page itself
explicitly says 'dget package should be implemented in apt-get install
-d.', which it kind of
Hi!
> The ci.debian.net results for mariadb seem to be very flaky lately (on
> amd64 they fail roughly 9/10) since version 1:10.11.6-1. Might be
> related (although the failure is different). i386 and arm64 seem to be
> exceptions.
No - the current CI failures for MariaDB are unrelated and not
Package: nuspell
Version: 5.1.4-1
Severity: normal
Tags: upstream
While trying to learn how to use Nuspell I noticed that it has no man page in
Debian (https://dyn.manpages.debian.org/jump?q=nuspell yields 'page not
found'). The README about the tool usage at
Sure, this will be fixed (automatically) with uploading latest upstream
minor release as stable update, and I intend to do it in coming 1-2 weeks.
Hi!
Currently in
https://salsa.debian.org/mariadb-team/mariadb-server/-/blob/debian/latest/debian/control?ref_type=heads
we have
Package: mariadb-server
Architecture: any
Suggests: mailx,
mariadb-test,
netcat-openbsd
Recommends: libhtml-template-perl,
Thanks Daniel Lewart!
I filed your submission at
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/61
for review/testing/feedback.
Hi Scott and Kr!
Did you note this line?
2023-12-14 14:51:33 0 [Note] InnoDB: Header page consists of zero bytes in
datafile: ./ibdata1, Space ID:0, Flags: 0
Can you include the output of `find /var/lib/mysql -ls` so we can see what
files your system has?
What is the hardware you have? The
Hi Debian security team!
MariaDB 1:10.11.6-1 entered Trixie only today after being stuck in
pending migration since Nov 28th from unstable. This
1:10.11.6-0+deb12u1 missed the point update window.
Are you OK if we proceed with this as a security upload?
Changes visible at
Uploading 10.11.6 to Bookworm should be done today but since autopkgtests
(mostly misc unrelated fails in LibreOffice) have been blocking the
migration from unstable to testing for past 10 days, uploading latest to
Bookworm would lead to a situation where Trixie has and older version
(10.11.5)
From: https://jira.mariadb.org/browse/MDEV-30046
The commit
https://github.com/MariaDB/server/commit/703e73e221a42638f2f05379124b35c57482da93
was never in a pull request nor included on any branch, and `git log
-S MDEV-30046` does not yield any results from 10.5 branch, so I
assume this issue is
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
I propose that the latest version of MariaDB 10.5.23 be included in
the oldstable release update of Debian.
According to https://release.debian.org/ there is no planned point
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
I propose that the latest version of MariaDB 10.11.6 be included in
the stable release update of Debian.
I am filing this bug report for tracking purposes. The final version
and
> > > > Thus a third thing the README could advise on is how Debian Developers
> > > > and
> > > > Debian sysadmins are advised to build CI systems and test upgrade paths
> > > > for
> > > > the next 10 years as what worked in the past 10 years does not apply
> > > > as-is
> > > > anymore.
> >
The fix for this issue is still only in git at
https://salsa.debian.org/lintian/lintian/-/commit/ebb739d102d55797516c0f10452e4e4c2502644d
and there has not been any new Lintian uploads since Lintian 2.116.3
in February 2023.
Anybody maintaining packages in Bookworm and using Salsa-CI is bound
to
> > Just create the chroot for the CI with --merged-usr and all will be
> > fine. Debootstrap in Buster is not going to be updated to do it
> > automatically, only in Bookworm/Bullseye.
>
> Thanks Luca for clarification. So seems we need to get bookworm
> removed from
>
Thanks Guillem!
Patch is now as one of the commits
athttps://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/59/commits
Severity: wishlist
Version 1:10.11.5-3
You are correct in that there are still calls to
'--defaults-file=/etc/mysql/debian.cnf' in the package scripts and
that they have been deprecated.
They are obsolete on new installs. However on old installs that
upgraded from MariaDB 10.x they are still
> > One more clarifying question:
> >
> > > > Thus a third thing the README could advise on is how Debian Developers
> > > > and
> > > > Debian sysadmins are advised to build CI systems and test upgrade paths
> > > > for
> > > > the next 10 years as what worked in the past 10 years does not
Hi!
One more clarifying question:
> > Thus a third thing the README could advise on is how Debian Developers and
> > Debian sysadmins are advised to build CI systems and test upgrade paths for
> > the next 10 years as what worked in the past 10 years does not apply as-is
> > anymore.
> People
If you read my previous message with some thought, you can see it has
exact steps on how to start a fresh Docker container running Debian
Sid and install MariaDB and test it.
If you can reproduce the issue you reported in a fresh environment in
a similar way it would prove the experience you had
On Wed, 22 Nov 2023 at 11:10, rpnpif wrote:
> I download https://packages.debian.org/sid/mariadb-server from SID. I
> see in that /etc/mysql/mariadb.conf.d/50-server.cnf has
> basedir = /usr
>
> Have you the same files ?
If you read my previous message with some thought, you can see it has
Hi!
I get 'latin1' when running the MariaDB client in a clean install:
```
± docker run -it -v ${PWD}:/build -w /build debian:sid bash
root@eb0c4013a610:/build# apt update
root@eb0c4013a610:/build# apt install -y mariadb-server
...
Processing triggers for mariadb-server (1:10.11.5-3) ...
> The automatically generated /etc/mysql/debian.cnf includes:
> [mysql_upgrade]
> ...
> basedir = /usr
>
> However, mysql_upgrade(1) says:
> --basedir=path
> Old option accepted for backward compatibility but ignored.
>
> This issue is still present in
1 - 100 of 1427 matches
Mail list logo
