<div dir="ltr">thanks for the hard work !<div>does it include ARM support, especially rasperrypi 2/3 armhf processor (at least required libraries packages to link device server code) ?</div><div><br></div><div>regards</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Sep 3, 2016 at 9:36 AM, PICCA Frederic-Emmanuel <span dir="ltr"><<a href="mailto:frederic-emmanuel.picca@synchrotron-soleil.fr" target="_blank">frederic-emmanuel.picca@synchrotron-soleil.fr</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello Tangoers,<br>
<br>
Here an email received from the pkg-mysql-maint Team from Debian.<br>
<br>
It explains that mariadb will be the default instead of mysql for<br>
Debian Stretch (aka Debian 9)<br>
<br>
for now only tango8 is part of debian/ubuntu, tango9 is available in<br>
the experimental release.<br>
<br>
My questions are.<br>
<br>
1) is tango-db (8 and 9) compatible with mariadb ?<br>
<br>
by compatible I mean the setup scripts of tango8 and tango9 work<br>
out of the box with mariadb. all the upgrade scripts available in<br>
the package (debian/mysql/*) are working out of the box in order<br>
to have a smooth upgrade for our users.<br>
<br>
2) should we switch to the default-* mecanism<br>
<br>
It seems that there is a problem with these scripts on mysql-5.7,<br>
so maybe also with mariadb.<br>
<br>
I do not have the time myself to take care of this, BUT I can sponsor<br>
your work.<br>
<br>
3) which version of tango do you want in debian/ubuntu ?<br>
<br>
Work required in order to have:<br>
* tango8<br>
<br>
- adapt all the sql scripts to the new mysql/mariadb version<br>
<br>
- support tango8 for the next release ;) (do not forget the<br>
Long time support LTS effort)<br>
<br>
* tango9<br>
<br>
- adapt all the sql scripts to the new mysql/mariadb version<br>
<br>
- upload pytango9<br>
<br>
- upload itango<br>
<br>
thank to the work done by Bodó-Merle Sándor from ELI-APLS these two<br>
last packages are almost ready. (Big thanks) I will upload pytango9<br>
into experimental this week-end, and itango in the near future.<br>
<br>
Indeed all this should be tested.<br>
<br>
Just for information, the dead line for this to happend for Debian<br>
Stretch is close. In november no more transition will be allow by<br>
the Release Team. So to my opinion, all this should be finished<br>
before the end of September.<br>
<br>
Thanks for your attention.<br>
<br>
Frederic on the behalf of the Debian-Pan team.<br>
<br>
PS: Crossposting to debian-pan-maintainers<br>
<br>
______________________________<wbr>__________<br>
De : pkg-mysql-maint [pkg-mysql-maint-bounces+<wbr>picca=<a href="mailto:synchrotron-soleil.fr@lists.alioth.debian.org">synchrotron-soleil.fr@<wbr>lists.alioth.debian.org</a>] de la part de Otto Kekäläinen [<a href="mailto:otto@debian.org">otto@debian.org</a>]<br>
Envoyé : samedi 3 septembre 2016 08:41<br>
À : <a href="mailto:debian-devel-announce@lists.debian.org">debian-devel-announce@lists.<wbr>debian.org</a><br>
Cc : <a href="mailto:ntyni@debian.org">ntyni@debian.org</a>; Paul Gevers; pkg-mysql-maint<br>
Objet : [debian-mysql] Introducing default-mysql-* metapackages<br>
<br>
Hello maintainers of packages that depend in MySQL/MariaDB!<br>
<br>
TL;DR;<br>
<br>
Please update packages that depend on MySQL or MariaDB as follows:<br>
<br>
BEFORE: Build-Depends: libmysqlclient-dev<br>
AFTER: Build-Depends: default-libmysqlclient-dev<br>
<br>
BEFORE: Depends: mysql-server | virtual-mysql-server<br>
OR Depends: mariadb-server | virtual-mysql-server<br>
AFTER: Depends: default-mysql-server | virtual-mysql-server<br>
<br>
BEFORE: Depends: mysql-client | virtual-mysql-client<br>
OR Depends: mariadb-client | virtual-mariadb-client<br>
AFTER: Depends: default-mysql-client | virtual-mysql-client<br>
<br>
<br>
Details follow:<br>
<br>
The release team decided earlier in the spring that MariaDB should be<br>
made the default MySQL variant in Debian. The release team also wished<br>
to have a facility that allows easy switching of the default.<br>
<br>
Therefore we have introduced the following metapackages<br>
from the mysql-defaults source package:<br>
- default-mysql-server<br>
- default-mysql-server-core<br>
- default-mysql-client<br>
- default-mysql-client-core<br>
- default-libmysqlclient-dev<br>
<br>
All maintainers of packages that currently depend directly on<br>
mysql-server, mariadb-server, or any of the other packages in these<br>
series, shall update the dependencies in their packages to point to<br>
default-mysql-* instead.<br>
<br>
Installing the metapackage default-mysql-server will pull in<br>
mariadb-server-10.0. Users who had mysql-server-5.6 will have it<br>
removed and replaced by the MariaDB equivalent on upgrade. Note that<br>
once you have switched to MariaDB, it might not possible to convert<br>
your in-place database files back to MySQL automatically, since Oracle<br>
does not maintain tools to convert possible MariaDB features present<br>
in the binary format. Please back up your data first if you wish to<br>
switch or experiment. Manual dump/import is the most reliable way to<br>
import data from one installation to another.<br>
<br>
A virtual package scheme virtual-mysql-* already exists since 2013,<br>
and will continue to exist. All MySQL variants in Debian (and outside<br>
in 3rd party repositories too) have Provides for these virtual-mysql-*<br>
packages. Maintainers can must use "Depends: default-mysql-server |<br>
virtual-mysql-server" if their package can be satisfied by any MySQL<br>
variant (Oracle, MariaDB, Percona, mysql-wsrep).<br>
<br>
The first dependency should be default-mysql-*, which is a<br>
metapackage, that in turn depends on exactly one option, which for now<br>
is MariaDB.<br>
<br>
If a maintainer knows that his/her package only works with one<br>
variant, then the package can depend directly on that package and not<br>
use the default-mysql-* (matches one) or virtual-mysql-* (matches any)<br>
schemes. Please get in touch if this applies to you. At the moment<br>
there should be no such packages, but in the future cases like this<br>
can arise when MySQL and MariaDB develop diverging feature sets.<br>
<br>
Packages built against default-mysqlclient-dev and link using<br>
"-lmysqlclient" will end up with a shared library dependency on either<br>
libmysqlclient.so.X or libmariadbclient.so.X depending on the default<br>
defined by the release team at build time. These will be provided by<br>
the libmysqlclient18 (soon to be libmysqlclient20) and<br>
libmariadbclient18 packages, which will be co-installable. Packages<br>
which require particular functionality available from only one of the<br>
forks may Build-Depend directly on libmysqlclient-dev or<br>
libmariadbclient-dev and then link using "-lmysqlclient" or<br>
"-lmariadbclient" respectively. Again, please get in touch if this<br>
applies to you.<br>
<br>
Users that want to rebuild packages against a different variant of<br>
lib*client-dev for experimenting and testing locally should prefer<br>
using a locally modified default-libmysqlclient-dev over modifying<br>
each client application source package individually.<br>
<br>
The default-mysql-* metapackages have been available in experimental<br>
since July, and since also in unstable and testing, and we are<br>
confident there are no regressions. If you however do encounter<br>
problems, please report to pkg-mysql-maint@.<br>
<br>
<br>
On behalf ot the pkg-mysql team,<br>
<br>
- Otto<br>
<br>
______________________________<wbr>_________________<br>
pkg-mysql-maint mailing list<br>
<a href="mailto:pkg-mysql-maint@lists.alioth.debian.org">pkg-mysql-maint@lists.alioth.<wbr>debian.org</a><br>
<a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint" rel="noreferrer" target="_blank">http://lists.alioth.debian.<wbr>org/cgi-bin/mailman/listinfo/<wbr>pkg-mysql-maint</a><br>
<br>
<br>To stop receiving message from <a href="mailto:tango@esrf.fr">tango@esrf.fr</a>, please send an e-mail to<br>
<a href="mailto:tango-unsubscribe@esrf.fr">tango-unsubscribe@esrf.fr</a> (subject/content don't matter).<br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">a+<br>raph</div>
</div>