Gentoo Archives: gentoo-commits

From: Kent Fredric <kentnl@g.o>
To: gentoo-commits@l.g.o
Subject: [gentoo-commits] repo/gentoo:master commit in: profiles/base/
Date: Sat, 03 Mar 2018 01:58:58
Message-Id: 1520042253.1e3aadf18792bd10d5577b971994641467258458.kentnl@gentoo
1 commit: 1e3aadf18792bd10d5577b971994641467258458
2 Author: Kent Fredric <kentnl <AT> gentoo <DOT> org>
3 AuthorDate: Sat Mar 3 01:53:25 2018 +0000
4 Commit: Kent Fredric <kentnl <AT> gentoo <DOT> org>
5 CommitDate: Sat Mar 3 01:57:33 2018 +0000
6 URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1e3aadf1
7
8 profiles: package.use.stable.mask dev-perl/DBD-SQLite[system-sqlite]
9
10 - Using versions of system sqlite other than the one DBD-SQLite ships
11 with causes regular issues that challenge the ability for tis package
12 to have a meaning stability status
13 - Restricting system sqlite versions to solve the above problem causes
14 significant impediments to stabilizing sqlite. ( DBD-SQLites release
15 cycle is somewhat behind that of SQLites )
16
17 Bug: https://bugs.gentoo.org/641108
18 Bug: https://bugs.gentoo.org/649408
19 Bug: https://bugs.gentoo.org/640724
20
21 profiles/base/package.use.stable.mask | 6 ++++++
22 1 file changed, 6 insertions(+)
23
24 diff --git a/profiles/base/package.use.stable.mask b/profiles/base/package.use.stable.mask
25 index 5fd8228658f..25385e4e025 100644
26 --- a/profiles/base/package.use.stable.mask
27 +++ b/profiles/base/package.use.stable.mask
28 @@ -4,6 +4,12 @@
29 # This file requires eapi 5 or later. New entries go on top.
30 # Please use the same syntax as in package.use.mask
31
32 +# Kent Fredric <kentnl@g.o> (3 Mar 2018)
33 +# Not an officially supported configuration, as it causes unpredictable
34 +# fragility and/or dependency headaches due to the very narrow interop window
35 +# Bugs #649408, #641108, #640724
36 +dev-perl/DBD-SQLite system-sqlite
37 +
38 # Ilya Tumaykin <itumaykin+gentoo@×××××.com> (13 Feb 2018)
39 # Requires >=dev-lang/mujs-1.0.0 stabilized. mpv-0.27.2 is stabilized
40 # due to a security bug, so we won't bother with javascript this time.