Bug#863675: [debian-mysql] Bug#863675: libmariadbd-dev: fails to upgrade from 'sid' - trying to overwrite /usr/bin/mysql_config

[Otto Kekäläinen]

su 20. tammik. 2019 klo 14.42 Andreas Beckmann (a...@debian.org) kirjoitti:
...
> -rwxr-xr-x 1 root root 14840 Jan  8 21:52 /usr/bin/mariadb_config
> lrwxrwxrwx 1 root root14 Jan  8 21:52 /usr/bin/mysql_config -> 
> mariadb_config
> lrwxrwxrwx 1 root root17 Jan  8 21:52 
> /usr/share/man/man1/mariadb_config.1.gz -> mysql_config.1.gz
> -rw-r--r-- 1 root root  2045 Jan  8 21:52 
> /usr/share/man/man1/mysql_config.1.gz
>
> Could we please have the symlinks in one direction only?

This is because upstream ships mariadb_config, but no manpage for it.
The manpage is named mysql_config.1...
Therefore the links go in opposite directions for the manpage. I am
hoping for a rename upstream so we don't have to introduce a rename
downstream and maintain more delta to upstream..

- Otto

Bug#863675: [debian-mysql] Bug#863675: libmariadbd-dev: fails to upgrade from 'sid' - trying to overwrite /usr/bin/mysql_config

[Otto Kekäläinen]

su 20. tammik. 2019 klo 16.21 Andreas Beckmann (a...@debian.org) kirjoitti:
>
> On 2019-01-20 13:39, Andreas Beckmann wrote:
> > Could we please have the symlinks in one direction only?
>
> There is also this Lintian warning:
> W: mariadb-10.3 source: binaries-have-file-conflict libmariadb-dev
> libmariadb-dev-compat usr/include/mysql
>
> Both libmariadb-dev and libmariadb-dev-compat are shipping the
> /usr/include/mysql -> mariadb symlink - shouldn't that be only in the
> -compat package?

This was introduced by patch in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917266
Reverted now in
https://salsa.debian.org/mariadb-team/mariadb-10.3/commit/71cada820618e00f88325c6e575ed5149eaa9455

Bug#863675: [debian-mysql] Bug#863675: libmariadbd-dev: fails to upgrade from 'sid' - trying to overwrite /usr/bin/mysql_config

[Otto Kekäläinen]

su 20. tammik. 2019 klo 14.21 Andreas Beckmann (a...@debian.org) kirjoitti:

> Followup-For: Bug #863675
> Control: reopen -1
> Control: found -1 1:10.3.12-1
>
> So, which package is shipping /usr/bin/mysql_config ?
> libmariadb-dev (which got the B+R added) or libmariadb-dev-compat ?
>
>   Unpacking libmariadb-dev-compat:amd64 (1:10.3.12-1) ...
>   dpkg: error processing archive
> /var/cache/apt/archives/libmariadb-dev-compat_1%3a10.3.12-1_amd64.deb
> (--unpack):
>trying to overwrite '/usr/bin/mysql_config', which is also in package
> libmariadbclient-dev 10.1.26-0+deb9u1
>   Errors were encountered while processing:
>/var/cache/apt/archives/libmariadb-dev-compat_1%3a10.3.12-1_amd64.deb
>
> libmariadb-dev-compat probably needs the same
>   B+R: libmariadbclient-dev (<< 1:10.3)
> as libmariadb-dev.
>
>
Problem reproduced in
https://salsa.debian.org/mariadb-team/mariadb-10.3/pipelines/33421
[image: image.png]

Fixed in
https://salsa.debian.org/mariadb-team/mariadb-10.3/commit/50c097665cb0e7c39b6697ca5ed3ac3c7f1c2569

Bug#863675: libmariadbd-dev: fails to upgrade from 'sid' - trying to overwrite /usr/bin/mysql_config

[Andreas Beckmann]

On 2019-01-20 13:39, Andreas Beckmann wrote:
> Could we please have the symlinks in one direction only?

There is also this Lintian warning:
W: mariadb-10.3 source: binaries-have-file-conflict libmariadb-dev
libmariadb-dev-compat usr/include/mysql

Both libmariadb-dev and libmariadb-dev-compat are shipping the
/usr/include/mysql -> mariadb symlink - shouldn't that be only in the
-compat package?


Andreas

Bug#863675: libmariadbd-dev: fails to upgrade from 'sid' - trying to overwrite /usr/bin/mysql_config

[Andreas Beckmann]

On 2019-01-20 13:17, Andreas Beckmann wrote:
> So, which package is shipping /usr/bin/mysql_config ?

How weird is that?

-rwxr-xr-x 1 root root 14840 Jan  8 21:52 /usr/bin/mariadb_config
lrwxrwxrwx 1 root root14 Jan  8 21:52 /usr/bin/mysql_config -> 
mariadb_config
lrwxrwxrwx 1 root root17 Jan  8 21:52 
/usr/share/man/man1/mariadb_config.1.gz -> mysql_config.1.gz
-rw-r--r-- 1 root root  2045 Jan  8 21:52 /usr/share/man/man1/mysql_config.1.gz

Could we please have the symlinks in one direction only?


Andreas

Bug#863675: libmariadbd-dev: fails to upgrade from 'sid' - trying to overwrite /usr/bin/mysql_config

[Andreas Beckmann]

Followup-For: Bug #863675
Control: reopen -1
Control: found -1 1:10.3.12-1

So, which package is shipping /usr/bin/mysql_config ?
libmariadb-dev (which got the B+R added) or libmariadb-dev-compat ?

  Unpacking libmariadb-dev-compat:amd64 (1:10.3.12-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libmariadb-dev-compat_1%3a10.3.12-1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/bin/mysql_config', which is also in package 
libmariadbclient-dev 10.1.26-0+deb9u1
  Errors were encountered while processing:
   /var/cache/apt/archives/libmariadb-dev-compat_1%3a10.3.12-1_amd64.deb

libmariadb-dev-compat probably needs the same
  B+R: libmariadbclient-dev (<< 1:10.3)
as libmariadb-dev.


Andreas


default-libmysqlclient-dev_1.0.5.log.gz
Description: application/gzip

Bug#863675: [debian-mysql] Bug#863675: libmariadbd-dev: fails to upgrade from 'sid' - trying to overwrite /usr/bin/mysql_config

[Otto Kekäläinen]

I made this extension to the gitlab-ci.yml file to be able to
automatically test for issues like this in the future:
https://salsa.debian.org/mariadb-team/mariadb-10.3/commit/0ec004b4e4fc7c98a7b16cbe1a821be12ace1110

Ideally it would actually also attempt to build something first with
MySQL and then with MariaDB and verify it actually works, but I don't
know any good example to do it with.

Bug#863675: [debian-mysql] Bug#863675: libmariadbd-dev: fails to upgrade from 'sid' - trying to overwrite /usr/bin/mysql_config

[Otto Kekäläinen]

The packages libmaraidbclient-dev and libmysqlclient-dev were in
Conflicts with each other and not co-installable. We should probably
have the same libmariadb-dev vs libmysqlclient-dev as well.

Feel free to open a merge request on Salsa for whatever change to want
to have in the packaging. I wrote instructions with screenshots at
https://wiki.debian.org/Teams/MySQL/patches so it would be as easy as
possible to contribute.

I am also grateful for meta-contributions to the contribution process
itself: the wiki texts, READMEs inside the packaging, gitlab-ci.yml
tweaks to make the testing more extensive and reliable etc.

I made a mysql-5.7 upgrade test in the gitlab-ci.yml file
(https://salsa.debian.org/mariadb-team/mariadb-10.3/blob/master/debian/gitlab-ci.yml#L138-152)
but it is not enabled due to differences in auth_socket name and
Password column in mysql.users table, and would for now just always
fail, thus disabled. It would be very cool if you extended this file
to install the libmysqlclient-dev package (and maybe some others) and
then upgraded / co-installed selected MariaDB packages to verify that
all d/control stanzas about conflicts/breaks/replaces are correctly
working.

The more bugs we can stump right at the commit they were made, the
better quality we have and the better for users.

Bug#863675: [debian-mysql] Bug#863675: libmariadbd-dev: fails to upgrade from 'sid' - trying to overwrite /usr/bin/mysql_config

[Otto Kekäläinen]

Alternatively, the mentioned files could be moved to
libmariadb-dev-compat but that would require some tweaking to the
manpage names etc as currently the mariadb-config.1 does not have it's
own file but is a symlink to mysql-config.1 (unlike how the
libmariadb-dev-compat version 3.0.7 in unstable works). This might
need coordination with upstream e.g. issue filed on jira.mariadb.org.

Bug#863675: libmariadbd-dev: fails to upgrade from 'sid' - trying to overwrite /usr/bin/mysql_config

[Andreas Beckmann]

Followup-For: Bug #863675

And another conflict:

  Preparing to unpack .../libmariadb-dev_1%3a10.3.11-1~exp2_amd64.deb ...
  Unpacking libmariadb-dev:amd64 (1:10.3.11-1~exp2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libmariadb-dev_1%3a10.3.11-1~exp2_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libmysqlservices.a', which is 
also in package libmysqld-dev 5.7.24-2
  Errors were encountered while processing:
   /var/cache/apt/archives/libmariadb-dev_1%3a10.3.11-1~exp2_amd64.deb


Andreas

Bug#863675: libmariadbd-dev: fails to upgrade from 'sid' - trying to overwrite /usr/bin/mysql_config

[Andreas Beckmann]

Followup-For: Bug #863675
Control: found -1 1:10.3.11-1~exp2

  Preparing to unpack .../libmariadb-dev_1%3a10.3.11-1~exp2_amd64.deb ...
  Unpacking libmariadb-dev:amd64 (1:10.3.11-1~exp2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libmariadb-dev_1%3a10.3.11-1~exp2_amd64.deb (--unpack):
   trying to overwrite '/usr/share/aclocal/mysql.m4', which is also in package 
libmysqlclient-dev 5.7.24-2
  Errors were encountered while processing:
   /var/cache/apt/archives/libmariadb-dev_1%3a10.3.11-1~exp2_amd64.deb

The following files are in both libmysqlclient-dev/sid and 
libmariadb-dev/experimental:

usr/share/aclocal/mysql.m4
usr/share/man/man1/mysql_config.1.gz


Andreas

Bug#863675: [debian-mysql] Bug#863675: Bug#863675: libmariadbd-dev: fails to upgrade from 'sid' - trying to overwrite /usr/bin/mysql_config

[Ondřej Surý]

Yeah, there's no harm in keeping experimental stuff in the "experimental"...


On 31 May 2017 13:15:09 Robie Basak  wrote:


Hi Otto,

On Wed, May 31, 2017 at 01:49:28PM +0300, Otto Kekäläinen wrote:

MariaDB 10.3 test packages should be removed from experimental. I
think it was just a temporary test by Ondrej. There is no point in
having a unreleased upstream version in Debian permantently.


Entirely up to you, but along similar lines it has been suggested that
we put in and maintain MySQL 5.8 in experimental. Then when 5.8 is
released as stable upstream, we would have it tested and ready to go
into sid immediately.

Robie

Bug#863675: [debian-mysql] Bug#863675: Bug#863675: libmariadbd-dev: fails to upgrade from 'sid' - trying to overwrite /usr/bin/mysql_config

[Robie Basak]

Hi Otto,

On Wed, May 31, 2017 at 01:49:28PM +0300, Otto Kekäläinen wrote:
> MariaDB 10.3 test packages should be removed from experimental. I
> think it was just a temporary test by Ondrej. There is no point in
> having a unreleased upstream version in Debian permantently.

Entirely up to you, but along similar lines it has been suggested that
we put in and maintain MySQL 5.8 in experimental. Then when 5.8 is
released as stable upstream, we would have it tested and ready to go
into sid immediately.

Robie


signature.asc
Description: PGP signature

Bug#863675: [debian-mysql] Bug#863675: libmariadbd-dev: fails to upgrade from 'sid' - trying to overwrite /usr/bin/mysql_config

[Otto Kekäläinen]

MariaDB 10.3 test packages should be removed from experimental. I
think it was just a temporary test by Ondrej. There is no point in
having a unreleased upstream version in Debian permantently.

Bug#863675: libmariadbd-dev: fails to upgrade from 'sid' - trying to overwrite /usr/bin/mysql_config

[Andreas Beckmann]

Package: libmariadbd-dev
Version: 10.3.0-0+exp2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package libmariadb-dev:amd64.
  Preparing to unpack .../10-libmariadb-dev_10.3.0-0+exp2_amd64.deb ...
  Unpacking libmariadb-dev:amd64 (10.3.0-0+exp2) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-vvkKED/10-libmariadb-dev_10.3.0-0+exp2_amd64.deb 
(--unpack):
   trying to overwrite '/usr/bin/mysql_config', which is also in package 
libmariadbclient-dev 10.1.23-8


cheers,

Andreas


libmariadbd-dev_10.3.0-0+exp2.log.gz
Description: application/gzip