Skip to content
GitLab
Menu
Projects
Groups
Snippets
/
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
Samuel Thibault
mariadb-10.1
Commits
5da7d276
Commit
5da7d276
authored
Dec 31, 2018
by
Otto Kekäläinen
Browse files
Update changelog for 1:10.3.11-3 release
parent
ff2a1c89
Changes
1
Show whitespace changes
Inline
Side-by-side
debian/changelog
View file @
5da7d276
mariadb
-
10.3
(
1
:
10.3.11
-
3
)
UNRELEASED
;
urgency
=
low
mariadb
-
10.3
(
1
:
10.3.11
-
3
)
unstable
;
urgency
=
low
*
Open
a
new
changelog
entry
[
Otto
Kek
ä
l
ä
inen
]
*
Use
sst_dump
from
package
rocksdb
-
tools
(
Closes
:
#
886853
)
--
Otto
Kek
ä
l
ä
inen
<
otto
@
debian
.
org
>
Tue
,
25
Dec
2018
13
:
56
:
17
+
0200
*
Remove
wsrep_sst_xtrabackup
(-
v2
)
already
deprecated
in
upstream
*
Make
gitlab
-
ci
.
yml
upgrade
test
specifically
run
mariadb
-
server
-
10.1
->
10.3
*
Fix
upstream
RocksDB
patch
to
fix
Lintian
complaints
about
source
code
*
Drop
the
MIPS
Innobase
patch
that
it
is
already
fixed
upstream
*
Extend
gitlab
-
ci
.
yml
to
test
libmysql
*
interactions
*
Ensure
libmariadbd19
does
not
breaks
/
replace
anything
*
Make
libmariadb
-
dev
-
compat
break
what
is
replaces
*
Make
libmariadb
-
dev
breaks
/
replaces
libmysqlclient
-
dev
(
Closes
:
#
863675
)
*
Update
Dutch
translation
by
Frans
Spiesschaert
(
Closes
:
#
895461
)
[
Faustin
Lammler
]
*
Fix
2
typo
error
in
README
contributor
*
Lintian
some
complaints
[
Helge
Deller
]
*
Skip
failing
test
on
HPPA
,
it
's not too important (Closes: #917395)
[ Scott Kitterman ]
* Update libmariadb-dev.links to restore /usr/include/mysql compatibility
symlinks lost when the default switched from 10.1 to 10.3 (Closes: #917266)
-- Otto Kekäläinen <otto@debian.org> Mon, 31 Dec 2018 16:39:33 +0200
mariadb-10.3 (1:10.3.11-2) unstable; urgency=low
mariadb-10.3 (1:10.3.11-2) unstable; urgency=low
...
...
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment