2015-07-11 20:03 GMT+03:00 Olaf van der Spek :
> +# MySQL/MariaDB default is Latin1, but in Debian we rather default to the
> full
> +# utf8 4-bit character set. See also client.cnf
>
> 4 bits isn't much, did you mean 4 bytes?
Thank you for spotting the typo.
Feel free to open a pull request on
2015-07-06 19:14 GMT+03:00 Olaf van der Spek :
> I don't see it being stopped:
That is probably because you are running dpkg to configure two not
fully configured packages, thus dpkg does do the full restart cycle of
the service. I just tested, here is how it looks in a normal upgrade:
The follo
2015-07-06 17:33 GMT+03:00 Olaf van der Spek :
> On 3-7-2015 16:13, Otto Kekäläinen wrote:
>>
>> This should now be fixed in commit
>>
>> https://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/commit/debian/mariadb-server-10.0.postinst
Oops, here is the full link
Hello!
2015-06-30 11:35 GMT+03:00 Bob Proulx :
> I had also modified /etc/mysql/debian-start (hey it is a conffile
> after all) to avoid printing this message:
>
> echo "Checking for tables which need an upgrade, are corrupt or were "
> echo "not closed cleanly."
This and many similar things
Hello!
2015-07-03 16:52 GMT+03:00 Yurii Kolesnykov :
> I think I know the reason and a way to reproduce this.
I still don't know how to reproduce the issue. You should put a
copy-paste of your experience here.
> I have ran into same issue today when I have installed mariadb on sid, then
> I have
Hello!
mysql-5.6 is now in unstable, but it has many problems and does not
seem to arrive in testing any soon..?
https://tracker.debian.org/pkg/mysql-5.6
When mysql-5.6 is in testing it should be safe for me to remove the
temporary mv line from mariadb-10.0 in favour of only using the
mysql-commo
2015-06-27 1:35 GMT+03:00 Olaf van der Spek :
> Hi,
>
> I might've hit the same issue:
It is probably not the same issue, but the symptoms look similar.
> Setting up mariadb-server-10.0 (10.0.20-1) ...
> 150627 0:30:08 [Note] /usr/sbin/mysqld (mysqld 10.0.20-MariaDB-1) starting
> as process 1025
2015-07-03 1:14 GMT+03:00 Otto Kekäläinen :
> Basically what you Yuril did was removed all configuration and data
> files, and then installed. For some reason the mysqld daemon did not
> start on your system, and the failure became visible during an upgrade
> where the system restarts
Basically what you Yuril did was removed all configuration and data
files, and then installed. For some reason the mysqld daemon did not
start on your system, and the failure became visible during an upgrade
where the system restarts the service.
I broke one installation on purpose, and this is ho
I've tracked this change to this commit:
Author: Otto Kekäläinen 2015-02-03 22:47:54
Committer: Otto Kekäläinen 2015-02-04 00:03:55
Parent: 8c267579283fcbcfa307ef7aa062c222e9832140 (Update debconf
translations to match new passwordless scheme)
Child: 2b8806a90d791159a9aeafd282feeedbf4b
2015-06-22 14:52 GMT+03:00 Yurii Kolesnykov :
>* What was the outcome of this action?
> Stuck at "Configuring mariadb-server-10.0"
Thanks for reporting this!
Do you have any additional information what dpkg is stuck at? What
version of MariaDB did you have previously?
I can see in your repo
Please install the latest official Debian package of MariaDB and this
issue will not exist. If you want to use .deb packages from other
sources, please don't file bugs against Debian in those cases.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscr
2015-06-11 21:56 GMT+03:00 Andreas Beckmann :
>> This my.cnf modification was introduced in commit
>> https://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/commit/?id=90b6bde63c8128eb7f54f16dfeec88081e4bdb0d
>
> That is, sorry, so utterly wrong ...
> Renaming the old my.cnf must be done by mys
Hello!
2015-06-02 18:07 GMT+03:00 Andreas Beckmann :
..
> during a test with piuparts I noticed your package modifies conffiles.
> This is forbidden by the policy, see
> https://www.debian.org/doc/debian-policy/ch-files.html#s-config-files
This my.cnf modification was introduced in commit
https:/
Hello!
Thanks for reporting your request. OpenSSL is problematic because its license.
I think Debian recommends using cyassl so we'll switch from bundled
yassl to cyassl once it is confirmed to work. I don't think anybody is
actively testing or tracking that at the moment.
See discussion at http
Related to this issue:
The MariaDB 10.0 in Debian unstable uses auth_socket for root account
by default now and has already that line removed.
The MariaDB 10.0 version in Jessie is however affected.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubs
OK, I'll close this to drop if off the radar.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
All occurrences of mysql-server in depends, recommends or suggests
should be replaced with 'mysql-server | virtual-mysql-server' as
announced by James Page in Misc Developer News #37
(https://lists.debian.org/debian-devel-announce/2014/11/msg00015.html).
Alternatively, if you prefer MariaDB, then
All occurrences of mysql-server in depends, recommends or suggests
should be replaced with 'mysql-server | virtual-mysql-server' as
announced by James Page in Misc Developer News #37
(https://lists.debian.org/debian-devel-announce/2014/11/msg00015.html).
Alternatively, if you prefer MariaDB, then
All occurrences of mysql-server in depends, recommends or suggests
should be replaced with 'mysql-server | virtual-mysql-server' as
announced by James Page in Misc Developer News #37
(https://lists.debian.org/debian-devel-announce/2014/11/msg00015.html).
Alternatively, if you prefer MariaDB, then
All occurrences of mysql-server in depends, recommends or suggests
should be replaced with 'mysql-server | virtual-mysql-server' as
announced by James Page in Misc Developer News #37
(https://lists.debian.org/debian-devel-announce/2014/11/msg00015.html).
Alternatively, if you prefer MariaDB, then
All occurrences of mysql-server in depends, recommends or suggests
should be replaced with 'mysql-server | virtual-mysql-server' as
announced by James Page in Misc Developer News #37
(https://lists.debian.org/debian-devel-announce/2014/11/msg00015.html).
Alternatively, if you prefer MariaDB, then
All occurrences of mysql-server in depends, recommends or suggests
should be replaced with 'mysql-server | virtual-mysql-server' as
announced by James Page in Misc Developer News #37
(https://lists.debian.org/debian-devel-announce/2014/11/msg00015.html).
Alternatively, if you prefer MariaDB, then
All occurrences of mysql-server in depends, recommends or suggests
should be replaced with 'mysql-server | virtual-mysql-server' as
announced by James Page in Misc Developer News #37
(https://lists.debian.org/debian-devel-announce/2014/11/msg00015.html).
Alternatively, if you prefer MariaDB, then
All occurrences of mysql-server in depends, recommends or suggests
should be replaced with 'mysql-server | virtual-mysql-server' as
announced by James Page in Misc Developer News #37
(https://lists.debian.org/debian-devel-announce/2014/11/msg00015.html).
Alternatively, if you prefer MariaDB, then
All occurrences of mysql-server in depends, recommends or suggests
should be replaced with 'mysql-server | virtual-mysql-server' as
announced by James Page in Misc Developer News #37
(https://lists.debian.org/debian-devel-announce/2014/11/msg00015.html).
Alternatively, if you prefer MariaDB, then
All occurrences of mysql-server in depends, recommends or suggests
should be replaced with 'mysql-server | virtual-mysql-server' as
announced by James Page in Misc Developer News #37
(https://lists.debian.org/debian-devel-announce/2014/11/msg00015.html).
Alternatively, if you prefer MariaDB, then
All occurrences of mysql-server in depends, recommends or suggests
should be replaced with 'mysql-server | virtual-mysql-server' as
announced by James Page in Misc Developer News #37
(https://lists.debian.org/debian-devel-announce/2014/11/msg00015.html).
Alternatively, if you prefer MariaDB, then
All occurrences of mysql-server in depends, recommends or suggests
should be replaced with 'mysql-server | virtual-mysql-server'
..as announced by James Page in Misc Developer News #37
(https://lists.debian.org/debian-devel-announce/2014/11/msg00015.html).
Alternatively, if you prefer MariaDB, th
All occurrences of mysql-server in depends, recommends or suggests
should be replaced with 'mysql-server | virtual-mysql-server'
..as announced by James Page in Misc Developer News #37
(https://lists.debian.org/debian-devel-announce/2014/11/msg00015.html).
Alternatively, if you prefer MariaDB, th
All occurrences of mysql-server in depends, recommends or suggests
should be replaced with 'mysql-server | virtual-mysql-server'
..as announced by James Page in Misc Developer News #37
(https://lists.debian.org/debian-devel-announce/2014/11/msg00015.html).
Alternatively, if you prefer MariaDB, th
All occurrences of mysql-server in depends, recommends or suggests
should be replaced with 'mysql-server | virtual-mysql-server'
..as announced by James Page in Misc Developer News #37
(https://lists.debian.org/debian-devel-announce/2014/11/msg00015.html).
Alternatively, if you prefer MariaDB, th
All occurrences of mysql-server in depends, recommends or suggests
should be replaced with:
mysql-server | virtual-mysql-server
..as announced by James Page in Misc Developer News #37
(https://lists.debian.org/debian-devel-announce/2014/11/msg00015.html).
Alternatively, if you prefer MariaDB, th
All occurrences of mysql-server in depends, recommends or suggests
should be replaced with:
mysql-server | virtual-mysql-server
..as announced by James Page in Misc Developer News #37
(https://lists.debian.org/debian-devel-announce/2014/11/msg00015.html).
Alternatively, if you prefer MariaDB, th
The package currently has the following line:
Recommends: mysql-server
It should be changed to
Suggests: mysql-server | virtual-mysql-server
..as announced by James Page in Misc Developer News #37
(https://lists.debian.org/debian-devel-announce/2014/11/msg00015.html).
Alternatively, if you
nsive to I seek for a DD to sponsor me via mentors
now.
Regards,
Otto Kekäläinen
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
2015-04-21 9:25 GMT+03:00 Salvatore Bonaccorso :
> Yes, I can confirm that we most likely will need to use the same
> strategy as for the mysql-5.5 packages for mariadb-10.0 once updated
> through jessie-security.
It seems nobody will upload 10.0.17-1 to the release. Can the security
team then ple
Hello Josef!
2015-04-20 21:44 GMT+03:00 Josef Moosbauer :
> # But packages for MariaDB take priority
> Package: *
> Pin: Origin http://tweedo.com/
> Pin-Priority: 1000
Looking at your sources listing I can see that you are mixing
repositories for both wheezy and jessie, and also have ubuntu rep
Hello!
2015-04-21 0:15 GMT+03:00 Debian Bug Tracking System :
..
> I don't see anything that's appropriate for a point release either, so I'm
> going to close this bug.
>
>
> --
> Jonathan Wiltshire j...@debian.org
> Debian Developer htt
variants (LP: #1421520).
[ Jan Wagner ]
* Adding mysqld_multi.server_lsb-header.patch, provides LSB headers for
example initscript (Closes: #778762)
* Adding mysqld_multi_confd.patch, makes mysqld_multi reading conf.d
(Closes: #778761)
[ Otto Kekäläinen ]
* New upstream release
2015-04-05 13:56 GMT+03:00 Cyril B. :
> Package: mariadb-server-10.0
> Version: 10.0.16-1
> Severity: normal
>
> Installing mariadb-server-10.0 on a fresh install of Jessie shows this in the
> (syslog) logs:
>
> /etc/init.d/mysql[3893]: 150405 12:38:36 mysqld_safe Can't log to error log
> and sysl
Ok, thanks for the details. I filed an issue upstream as I think
fixing this is outside the scope of Debian packagers. See
https://mariadb.atlassian.net/browse/MDEV-7680
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listma
Thanks for reviewing man pages. Can you point out an example of a paragraph
in a man page that has wrong information as a proof of your claim? I don't
think man pages are in general outdated.
Thanks
Cool, I didn't know that piuparts also test mysql->mariadb migration
scenarios. Issue fixed in git now.
Thanks for reporting!
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
2015-03-03 14:09 GMT+02:00 Jan Wagner :
>> single "feature": being able to understand how to convert a
>> stand-alone instance into a multidb and have a script to start the
>> new config.
>
> So in the end it is something the package maintainers have to consider
> and decide.
Debian is a very incl
2015-02-26 10:36 GMT+02:00 Arnaud Fontaine :
>> I'd vote for this. Let's put at least all the big plugins in their own
>> packages. The main mariadb-server-10.0 could include only the plugins
>> that are loaded by default or that are just really small.
>
> Actually, none of these plugins are ena
2015-02-20 11:28 GMT+02:00 Jan Wagner :
> installing the actual versions of mariadb-server and mysql-server in
> sid seems only ship /etc/mysql/conf.d/. Did I miss something or is
> this split planed for post-jessie?
Yes, there is a split planned post-jessie. The MariaDB repo contains
two branches
Hello!
Would you care to provide a patch that can be applied on MariaDB 10.0.16?
source at http://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git
(and github mirror for pull requests, if you prefer them:
https://github.com/ottok/mariadb-10.0)
--
To UNSUBSCRIBE, email to debian-bugs-dist-req
2015-02-10 8:45 GMT+02:00 Arnaud Fontaine :
> 1. Create one package per plugin as you suggested, but this would
> create many (some of them really small) packages though. Or perhaps
> one package containing several plugins, because some of them, such
> as query_cache_info, ar
I will close this issue unless the original reporter adds some more
information that would enable us to reproduce the bug.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773223
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Con
All issues mentioned in this bug report seems to have been fixed.
Piuparts pass successfully e.g. here:
https://piuparts.debian.org/sid/source/m/mariadb-10.0.html
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@li
Hello!
Can you please post some details about how to reproduce this error? If
I could reproduce it I should be able to create a fix.
Maybe your /etc/mysql/my.cnf has something customized in it? Did you
have something installed before, is this a migration/upgrade or a
fresh install? If you had som
After thinking about it for a while, I am starting to think that the
best policy would be to _not_ load bundled plugins by default if they
are not compulsory for the server to run. It is better to keep the
server lean and sleek, and let the user activate extra plugins if they
need them.
We could h
Hello Arnaud!
Could you please apply your patch on the
http://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git master
branch and test it out?
I read the patch and it looks correct at least by syntax, but I don't
actually know about what is the best policy for plugin bundling and/or
activation.
Mroonga & TokuDB plugins in mariadb-server-10.0
[ Otto Kekäläinen ]
* Imported Upstream version 10.0.16. Inludes fixes for the following security
vulnerabilities:
- CVE-2015-0411
- CVE-2015-0382
- CVE-2015-0381
- CVE-2015-0432
- CVE-2014-6568
- CVE-2015-
ulien Muchembled ]
* Fix inclusion of Mroonga & TokuDB plugins in mariadb-server-10.0
[ Otto Kekäläinen ]
* Imported Upstream version 10.0.16. Inludes fixes for the following security
vulnerabilities:
- CVE-2015-0411
- CVE-2015-0382
- CVE-2015-0381
- CVE-2015-0432
- CVE-
Status:
The test suite failed. I found out that the cacert.pem that is part of
the test suite expired today at 6 am UTC. I am working with devs to
get this cert re-issued and test suite successful again.
I did upload
https://buildd.debian.org/status/package.php?p=mariadb-10.0&suite=experimental
2015-01-27 8:09 GMT+02:00 Salvatore Bonaccorso :
> Thanks for the update and checking with upstream regarding the two
> other CVEs. 10.0.16 seems now avaiable[1] (even though not yet
> announced on the webpage itself).
>
> [1] https://downloads.mariadb.com/files/MariaDB/mariadb-10.0.16/source
1
Here is the reply from a MariaDB core developer:
2015-01-26 21:39 GMT+02:00 Sergei Golubchik :
> Hi, Otto!
>
> On Jan 26, Otto Kekäläinen wrote:
>> Hello Sergei!
>>
>> The page https://mariadb.com/kb/en/mariadb/security/ does not mention
>> the ones Salvatore ask
The page https://mariadb.com/kb/en/security/ has updated and includes
info about these latest CVEs.
It seems most issues were fixed in 5.5.41/10.0.16.
One was for 5.5.39/10.0.13.
10.0.16 hasn't been yet released, but I'll expect it is released soon
and I will try to be as fast as possible in upda
I started to search information about this 2 days ago, but so far I
haven't found any indication that these would affect MariaDB, though I
haven't got the definitive final reply from mariadb devs confirming so
either.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a s
2014-12-22 19:13 GMT+02:00 Julien Muchembled :
> The attached patch fixes it. Could you please apply it?
Thanks for the patch!
I have applied it both to the jessie and master branches at
http://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/ (and kept
yo as author with --author)
FYI, there i
Hello!
Thanks for taking the time to report. I think #773631 and #773282 are
duplicates, so this issue is fixed, but not uploaded yet.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
I now had the time to reproduce this, and write and test a fix. This
is now committed in
http://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/commit/?id=3afe791ed47b897de8fa9be998a4217fc2a36bad
but I am not sure if this alone justifies an upload of 10.0.15-3 into
unstable..
Please file some m
2014-12-16 14:04 GMT+02:00 Frédéric Brière :
> The problem lies with line 122: /etc/mysql/debian-start no longer
> outputs anything (at least for me), so the expression evaluates to 1,
> hence the statement (because of &&), hence the script (because this is
> the last statement). Shell scripting i
Thank you Gilles for reporting this.
The mysqld init script should call on scripts that run mysql_upgrade,
which is suppose to handle situations like this. Have you tried
running mysql_upgrade manually?
This issue is possibly an upstream bug and I have asked upstream devs
for help regarding this.
2014-12-13 14:30 GMT+02:00 Andreas Beckmann :
> I recently added (in piuparts) preseeding to enable database cleanup for
> all the new mysql server variants ... so most of these issues should be
> fixed now ...
Thanks Andreas. I think your change was sensible - leaving behind
/var/lib/mysql with u
Hello!
2014-12-13 14:35 GMT+02:00 Andreas Beckmann :
> during a test with piuparts I noticed your package failed to install. As
> per definition of the release team this makes the package too buggy for
> a release, thus the severity.
Thanks for taking the time to review the piuparts logs. Due to
Hello!
This is potentially fixed in
http://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/commit/?id=3b66ec189bdda12c2bf899fec87fcff7ee4f2bbf
but I need to upload to experimental first to confirm it..
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "u
Thanks for reporting this!
I mysql-5.5/5.6 the mysql_plugin is part of the client package:
mysql-client-5.6.install:usr/bin/mysql_plugin
mysql-client-5.6.manpages:debian/tmp/usr/share/man/man1/mysql_plugin.1
In MariaDB it is part of server package:
mariadb-server-10.0.install:usr/bin/mysql_plugin
Thanks for reporting this!
It seems that when you have multiple /var/lib/mysql/debian-*.flag
files, the version comparison is buggy and ends up comparing new
version to the oldest flag file version.
The relevant code in mariadb-server-10.0.preinst is:
**
# Show upgrade warning if old data exists
affects + mariadb-10.0
Also MariaDB needs a systemd file, which I assume would be identical
with the one for MySQL. Actually there are multiple attempts at this,
one in every distro. See issue
https://mariadb.atlassian.net/browse/MDEV-427 and comment number 2 by
me, which lists the systemd files i
Package: libmariadb-client-lgpl-dev
I decided to forward the message from Arnaud Fontaine below as a bug
report so we can work on it using the normal Debian bug tracking
processes.
My quick opinion is that we cannot use upstream libmysqlclient as it
conflicts with Oracle libmysqlclient in Debian
indentantion to two spaces in init file for easier
+ debugging of #609537
+
+ -- Otto Kekäläinen Mon, 17 Nov 2014 11:45:11 +0200
+
mariadb-10.0 (10.0.14-3) unstable; urgency=low
* Added patch d/username-in-tests-replace.patch to fix
diff --git a/debian/patches/username-in-tests-replace.patch
b
Just for the record: I have done a test build and ran the test suites,
but it seems my pbuilder skips this test so it wasn't caught:
http://labs.seravo.fi/~otto/mariadb-repo/mariadb-10.0-sid-i386/mariadb-10.0_10.0.14-3_amd64.build-7b8f5e6-pbuilder.log
plugins.unix_socket [
> The latest upload if mariadb-10.0 failed during the testsuite on i386:
>
> https://buildd.debian.org/status/package.php?p=mariadb-10.0
> https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.0&arch=i386&ver=10.0.14-3&stamp=1416208329
>
> A number of architectures are still building at this po
Hello!
In MariaDB the script has a section that waits for a long time so that
even the biggest and busiests databases will have enough time to shut
down:
for i in `seq 1 600`; do
sleep 1
if mysqld_status check_dead nowarn; then server_down=1; break; fi
done
if te
Package: ftp.debian.org
Severity: normal
Please remove src:mariadb-5.5 and any binaries it has created from
unstable.
MariaDB 5.5 had been replaced by MariaDB 10.0. The source package
mariadb-10.0 produces less binary packages than the old mariadb-5.5 and
thus there are some binary packages (e.g.
I've analyzed the log and found the issue (test comparison failed due
to capitalization issues in the word USER vs user). With the help of
upstream a patch has been produced and I've tested it and pushed it in
commit
http://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/commit/?id=8f5470f7d7d6
More information:
In the files (mariadb/mysql)-server.X.X.postrm there is a section that
does the removal and it looks like this:
#
# - Do NOT purge logs or data if another mysql-sever* package is
installed (#307473)
# - Remove the mysql user only after all his owned files are purged.
#
if [ "$1"
Thanks for taking time to file a bug about this. Here is some
additional details i investigated:
- mariadb-server-10.0 (in sid) has piuparts issues in sid:
https://piuparts.debian.org/sid/source/m/mariadb-10.0.html. The file
/etc/mysql/debian.cnf and files in /var/lib/mysql/* are not owned.
- mari
2014-10-21 23:53 GMT+03:00 Salvatore Bonaccorso :
> Take this as personal point of view so far: So the idea is to get
> MariaDB 10 into Jessie? Note that the freeze is coming soon and any
> new ustream version need to be in testing on 5th of november. AFAIR
> from the last discussion in the "MySQL
MariaDB has now pubished this page that tracks CVE (Oracle issued and
others) to MariaDB releases, also post-release:
https://mariadb.com/kb/en/mariadb/development/security/
We are in the process of uploading MariaDB 10.0 to unstable very soon,
and that will depricate MariaDB 5.5 so I do not plan
A systemd file for MariaDB would be good too. Upstream does not
provide one and the different downstream versions are wildly different
so this requires more work than just to pick one, see
https://mariadb.atlassian.net/browse/MDEV-427?focusedCommentId=59306&page=com.atlassian.jira.plugin.system.iss
I've read up on pages like
https://people.gnome.org/~markmc/openssl-and-the-gpl.html and
https://www.openssl.org/support/faq.html#LEGAL2. Getting a permission
statement for a GPL-OpenSSL exception (which basically is only needed
for Debian as others don't interpret GPL in such a strict way) from
al
2014-09-18 1:11 GMT+03:00 Clint Byrum :
> The above mentioned stuff was about the client libraries, and not about
> the server daemon.
OK.
>> Should I add to line 134 the parapraph below?
>> **
>> On Debian based systems the full text of the GNU General Public License
>> version
>> 2 can be fo
Now also added the extra patch from Holger Wansing:
http://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/commit/?id=4e21d8fbb4fd8f8432ef2a8fbaaad4fdfc72b367
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lis
I don't know why somebody wants to reassign this report to a package
that does not exists, but anyway I already committed the translation a
few days ago and this bug is essentially fixed:
http://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/commit/?id=d94bb2f9b3147239ca1a2c3f8051440e96b6a677
Package: debian-maintainers
Severity: normal
Dear Maintainers,
Please add Otto Kekäläinen to the Debian Maintainers
keyring. I have attached the jetstring changeset.
Kind regards,
Otto Kekäläinen
add-BED8449FCEE8DA88
Description: Binary data
Thank you for the translation! Unfortunaly it seems debconf-updatepo
chocked on the special character in the word "geïnstalleerd" so I
replaced it with simple "i".
File committed in
http://anonscm.debian.org/cgit/pkg-mysql/mariadb-5.5.git/commit/?id=b72553133b8086b270e4e9d0cd825d33ec07d58c
--
To
2014-09-30 9:07 GMT+03:00 Tobias Frost :
> Regarding the upload: I think d/copyright should be improved first, (at
> least the parts where license-reconsile claims that the wrong license is
> applied needs to be clearified) But as this is a huge package and it is
> already through NEW I would be al
2014-09-28 16:33 GMT+03:00 Tobias Frost :
> That gives a hint; I think I now know whats wrong:
> My username id tobi; coldtobi-guest was my pre-DD account...
Ok, I added coldtobi-guest as it was the only username under "Frost" I
found in the alioth user directory. I've now removed it and added
'to
> Nope, does not work... (However, pulling works via ssh)
>
> tobi@edoras:~/workspace/deb/mentors/mariadb/mariadb-10.0$ git push
> Counting objects: 4, done.
> Delta compression using up to 4 threads.
> Compressing objects: 100% (4/4), done.
> Writing objects: 100% (4/4), 487 bytes | 0 bytes/s, don
Hello!
2014-09-27 14:04 GMT+03:00 Tobias Frost :
> Hi Otto,
>
> (I wrote most of this before your response at 9:26)
> I tested commit rights: No I do not have them. (Feel free to add me, if
> you like; but then you need to answer this: Is it okay for you to also
Sorry, I remembered incorrectly. Y
2014-09-23 10:28 GMT+03:00 Guido van Steen :
> Yesterday Arnoud Fontaine expressed his willingness to sponsor
> (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745135#69). He asks
> "What's blocking the upload to unstable?". Other sponsors may have the
> same question.
Thanks Guido for pointing
2014-09-23 10:28 GMT+03:00 Guido van Steen :
> I would like Mariadb to be accepted before the freeze as well. However
> I am not a DD, so I cannot sponsor it myself.
Thanks for your feedback!
> In order to get Mariadb sponsored you might handle at least the
> Lintian error
> (https://lintian.deb
Top 10 reasons you should sponsor MariaDB 10.0 into Debian this weekend:
1) Help Debian stay modern! Debian hasn't had any MariaDB in any
official release yet, while for example Fedora and OpenSUSE have not
only had MariaDB for a years, they now even default to it over MySQL.
2) MariaDB 10.0 has
Hello!
The copyright file at
http://anonscm.debian.org/cgit/pkg-mysql/mariadb-5.5.git/tree/debian/copyright
already includes in the comment a paragraph about "FOSS License
Exception" and on line 111 OpenSSL is specifically mentioned.
This is perhaps the wrong format?
Is this bug report a reminde
Package: mariadb-server-5.5
Thanks Jonathan for reporting this.
In your particular case you can recover from your situation by running as root:
$ echo "fset mariadb-server/oneway_migration seen false" |
debconf-communicate mariadb-server-5.5
After that you can run the installation and choose Yes
Package: sponsorship-requests
Dear mentors,
I am looking for a new sponsor for my package "mariadb-10.0".
The package was already once uploaded to experimental, but the sponsor
I had 5 months ago when the package entered the NEW queue has been
unable to continue (too busy with other things) with
1301 - 1400 of 1495 matches
Mail list logo
