Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 919865 - dev-db/mariadb: rekeywording for dev-perl/DBD-MariaDB
Summary: dev-db/mariadb: rekeywording for dev-perl/DBD-MariaDB
Status: IN_PROGRESS
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Keywording (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Linux MySQL bugs team
URL:
Whiteboard:
Keywords: CC-ARCHES, SECURITY
: 913026 (view as bug list)
Depends on:
Blocks: 915511 917515
  Show dependency tree
 
Reported: 2023-12-14 06:44 UTC by Sam James
Modified: 2024-04-05 05:18 UTC (History)
10 users (show)

See Also:
Package list:
>=dev-db/mariadb-10.11.5-r1:10.11 >=dev-db/mariadb-10.6.15-r1:10.6 dev-perl/DBD-MariaDB dev-perl/Proc-ProcessTable <dev-libs/libfmt-10 s390
Runtime testing required: ---
nattka: sanity-check+


Attachments
test summary (file_919865.txt,3.48 KB, text/plain)
2024-02-27 16:23 UTC, matoro
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sam James archtester Gentoo Infrastructure gentoo-dev Security 2023-12-14 06:44:31 UTC
Thanks!
Comment 1 NATTkA bot gentoo-dev 2023-12-14 06:48:17 UTC Comment hidden (obsolete)
Comment 2 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2023-12-14 06:50:18 UTC
*** Bug 913026 has been marked as a duplicate of this bug. ***
Comment 3 NATTkA bot gentoo-dev 2023-12-14 06:52:16 UTC Comment hidden (obsolete)
Comment 4 Tomáš Mózes 2024-02-03 10:35:16 UTC
Hello Sam, would be good to proceed as we need to stabilize a newer version of MariaDB due to security issues, thanks!
Comment 5 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2024-02-03 10:37:57 UTC
sec
Comment 6 Larry the Git Cow gentoo-dev 2024-02-03 10:39:13 UTC
The bug has been referenced in the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=31a91f41b46cbdac7e714fa86126ba3c9e4406d2

commit 31a91f41b46cbdac7e714fa86126ba3c9e4406d2
Author:     Sam James <sam@gentoo.org>
AuthorDate: 2024-02-03 10:38:45 +0000
Commit:     Sam James <sam@gentoo.org>
CommitDate: 2024-02-03 10:39:07 +0000

    profiles/arch/loong: force dev-perl/DBD-MariaDB[mariadb]
    
    No MySQL here.
    
    Bug: https://bugs.gentoo.org/919865
    Signed-off-by: Sam James <sam@gentoo.org>

 profiles/arch/loong/package.use.force | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)
Comment 7 Larry the Git Cow gentoo-dev 2024-02-03 10:40:45 UTC
The bug has been referenced in the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4a645015b14793aab35252a2916c43ad4244c151

commit 4a645015b14793aab35252a2916c43ad4244c151
Author:     Sam James <sam@gentoo.org>
AuthorDate: 2024-02-03 10:40:20 +0000
Commit:     Sam James <sam@gentoo.org>
CommitDate: 2024-02-03 10:40:20 +0000

    profiles/arch/loong: mask dev-perl/DBD-MariaDB[mysql]
    
    No MySQL here. Note that not use.mask-ing USE=mysql as it has a generic
    meaning too.
    
    Bug: https://bugs.gentoo.org/919865
    Signed-off-by: Sam James <sam@gentoo.org>

 profiles/arch/loong/package.use.mask | 4 ++++
 1 file changed, 4 insertions(+)
Comment 8 Jakov Smolić archtester gentoo-dev 2024-02-03 23:23:09 UTC
riscv done
Comment 9 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2024-02-21 01:20:23 UTC
matoro, I don't understand why you've changed it from depends on <-> blocks.

The point of this bug is to let people get rid of DBD-MySQL. What's dragging it in for you when doing this package list?
Comment 10 matoro archtester 2024-02-21 01:24:47 UTC
(In reply to Sam James from comment #9)
> matoro, I don't understand why you've changed it from depends on <-> blocks.
> 
> The point of this bug is to let people get rid of DBD-MySQL. What's dragging
> it in for you when doing this package list?

When I try to emerge dev-db/mariadb:10.11 it pulls in dev-perl/DBD-mysql which then fails to build.  See:  https://paste.matoro.tk/b1z1sxr
Comment 11 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2024-02-21 01:56:03 UTC
(In reply to matoro from comment #10)
> (In reply to Sam James from comment #9)
> > matoro, I don't understand why you've changed it from depends on <-> blocks.
> > 
> > The point of this bug is to let people get rid of DBD-MySQL. What's dragging
> > it in for you when doing this package list?
> 
> When I try to emerge dev-db/mariadb:10.11 it pulls in dev-perl/DBD-mysql
> which then fails to build.  See:  https://paste.matoro.tk/b1z1sxr

You need to do mariadb-10.11-r1 which changes the dep, that's why this is a rekeywording bug.
Comment 12 matoro archtester 2024-02-21 01:59:00 UTC
(In reply to Sam James from comment #11)
> (In reply to matoro from comment #10)
> > (In reply to Sam James from comment #9)
> > > matoro, I don't understand why you've changed it from depends on <-> blocks.
> > > 
> > > The point of this bug is to let people get rid of DBD-MySQL. What's dragging
> > > it in for you when doing this package list?
> > 
> > When I try to emerge dev-db/mariadb:10.11 it pulls in dev-perl/DBD-mysql
> > which then fails to build.  See:  https://paste.matoro.tk/b1z1sxr
> 
> You need to do mariadb-10.11-r1 which changes the dep, that's why this is a
> rekeywording bug.

You mean 10.11.5-r1?  So should package list say >=dev-db/mariadb-10.11.5-r1:10.11 ?
Comment 13 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2024-02-21 02:04:28 UTC
Yes -- although it's very weird it has to, given the package list normally handles this fine...?
Comment 14 matoro archtester 2024-02-27 16:23:33 UTC
Created attachment 886132 [details]
test summary

Here's my summary of the test suite status on all of the requested architectures (see attachment).  How do we want to approach the ones with more drastic failures?

Passes:  arm64, ia64, ppc64le
One failure:  ppc64, loong64
mips64 has a handful of failures.  One due to big-endian.
arm has 2 failures on 10.6, but regresses severely to 10.11.
Many failures:  alpha, hppa, ppc

I can open individual bugs for these, but would like to understand if that would be helpful first.
Comment 15 Tomáš Mózes 2024-03-05 12:55:20 UTC
(In reply to matoro from comment #14)
> Created attachment 886132 [details]
> test summary
> 
> Here's my summary of the test suite status on all of the requested
> architectures (see attachment).  How do we want to approach the ones with
> more drastic failures?
> 
> Passes:  arm64, ia64, ppc64le
> One failure:  ppc64, loong64
> mips64 has a handful of failures.  One due to big-endian.
> arm has 2 failures on 10.6, but regresses severely to 10.11.
> Many failures:  alpha, hppa, ppc
> 
> I can open individual bugs for these, but would like to understand if that
> would be helpful first.

Thank you matoro for testing, actually I only use MariaDB on amd64 where the tests pass, no idea about the others arches, I don't use any of others. However this is KW request, so probably we should proceed if it can be compiled and started, the tests itself may be flaky.

A failing test doesn't really mean it won't work, however I do understand it would be great to 100% of success rate. On the other side, it's blocking a security stabilization where users are now stuck with old and vulnerable version.
Comment 16 matoro archtester 2024-03-05 14:42:06 UTC
(In reply to Tomáš Mózes from comment #15)
> (In reply to matoro from comment #14)
> > Created attachment 886132 [details]
> > test summary
> > 
> > Here's my summary of the test suite status on all of the requested
> > architectures (see attachment).  How do we want to approach the ones with
> > more drastic failures?
> > 
> > Passes:  arm64, ia64, ppc64le
> > One failure:  ppc64, loong64
> > mips64 has a handful of failures.  One due to big-endian.
> > arm has 2 failures on 10.6, but regresses severely to 10.11.
> > Many failures:  alpha, hppa, ppc
> > 
> > I can open individual bugs for these, but would like to understand if that
> > would be helpful first.
> 
> Thank you matoro for testing, actually I only use MariaDB on amd64 where the
> tests pass, no idea about the others arches, I don't use any of others.
> However this is KW request, so probably we should proceed if it can be
> compiled and started, the tests itself may be flaky.
> 
> A failing test doesn't really mean it won't work, however I do understand it
> would be great to 100% of success rate. On the other side, it's blocking a
> security stabilization where users are now stuck with old and vulnerable
> version.

If this is blocking a kwreq, then let's split it up into two bugs - one for arches blocking the stablereq, one for new arches.

Regardless, my vote on this would be to investigate the small failures - ppc64, loong64 - and drop keywords elsewhere.  I think it's unlikely to be running a mariadb server on the remaining arches - alpha, arm, hppa, mips, ppc.
Comment 17 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2024-03-05 15:06:16 UTC
agreed^2, can you do the split + file bugs for those arches and then a mega bug is ok for the other random failures all in one (hppa etc)

(sorry for brevity, on mobile)
Comment 18 Arthur Zamarin archtester Gentoo Infrastructure gentoo-dev Security 2024-04-05 05:16:52 UTC
ia64 done
Comment 19 Arthur Zamarin archtester Gentoo Infrastructure gentoo-dev Security 2024-04-05 05:17:45 UTC
arm done
Comment 20 Arthur Zamarin archtester Gentoo Infrastructure gentoo-dev Security 2024-04-05 05:17:46 UTC
arm64 done
Comment 21 Arthur Zamarin archtester Gentoo Infrastructure gentoo-dev Security 2024-04-05 05:18:25 UTC
ppc done
Comment 22 Arthur Zamarin archtester Gentoo Infrastructure gentoo-dev Security 2024-04-05 05:18:27 UTC
ppc64 done