Re: [Bug 1676410] Re: Missing plugins
On Tue, 28 Mar 2017 16:54:10 - Robie Basak <1676...@bugs.launchpad.net> wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. > > Please note that we are currently not packaging new plugins classified > as "rapid" by upstream, since we cannot meet API stability guarantees > that users of a stable release expect. > > Lars or Norvald: could you please report the classification status of > these to plugins connection_control and group_replication? I can't > seem to find where these are defined upstream. group_replication is a "rapid" plugin. connection_control is not "rapid", but it's new in 5.7.17: https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-17.html It was backported to 5.6 and 5.7, see bug #1633485. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1676410 Title: connection_control and group_replication plugins are not packaged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1676410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1633485] [NEW] Backport login throttling plugin to 5.6 and 5.7
Public bug reported: In MySQL 8.0 we (Oracle) are adding a plugin to rate-limit/throttle login attempts in order to stop brute-force attacks. Since this is a security mechanism that has been requested by users, we would also like to backport this plugin to MySQL 5.6 and 5.7. After consulting with Robie Basak (racb), we understand this change to be allowed in Ubuntu under the SRU process (Sect. 2.2, https://wiki.ubuntu.com/StableReleaseUpdates), but if there are any comments or objections, we'd like to hear them now. Impact == This functionality is implemented in a plugin. The plugin is not loaded, and the functionality will not be activated unless the DBA explicitly activates it. Regression potential The potential for regression is considered low for the following reasons: - The new functionality is in a plugin that 1) is not loaded by default, and 2) can be unloaded if it causes problems. - The change does not introduce new SQL syntax, and no existing syntax is affected. - The plugin is new, so it's not used by any other packages in Ubuntu. ** Affects: mysql-5.6 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: mysql-5.7 (Ubuntu) Importance: Undecided Status: Triaged ** Affects: mysql-5.6 (Ubuntu Precise) Importance: Undecided Status: Invalid ** Affects: mysql-5.7 (Ubuntu Precise) Importance: Undecided Status: Invalid ** Affects: mysql-5.6 (Ubuntu Trusty) Importance: Undecided Status: Triaged ** Affects: mysql-5.7 (Ubuntu Trusty) Importance: Undecided Status: Invalid ** Affects: mysql-5.6 (Ubuntu Xenial) Importance: Undecided Status: Invalid ** Affects: mysql-5.7 (Ubuntu Xenial) Importance: Undecided Status: Triaged ** Affects: mysql-5.6 (Ubuntu Yakkety) Importance: Undecided Status: Invalid ** Affects: mysql-5.7 (Ubuntu Yakkety) Importance: Undecided Status: Triaged ** Also affects: mysql-5.6 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1633485 Title: Backport login throttling plugin to 5.6 and 5.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1633485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1610182] Re: 5.7.14 is not yet packaged
Unfortunately, 5.7.14 was released with a bug that causes builds to fail unless using the bundled liblz4 library. It will be fixed in 5.7.15. Please use the attached patch while waiting for 5.7.15 to be released. ** Patch added: "mysql-5.7.14-build-failure.patch" https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1610182/+attachment/4714858/+files/mysql-5.7.14-build-failure.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1610182 Title: 5.7.14 is not yet packaged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1610182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579008] Re: libmysqlclient-dev compilation error -- wrong header definition at client_plugin.h
This bug is fixed in MySQL 5.7.14. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579008 Title: libmysqlclient-dev compilation error -- wrong header definition at client_plugin.h To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1579008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579008] Re: libmysqlclient-dev compilation error -- wrong header definition at client_plugin.h
This will be fixed in a future version of MySQL. Please see the attached patch. ** Patch added: "Upstream patch" https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1579008/+attachment/4675915/+files/deinit_void.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579008 Title: libmysqlclient-dev compilation error -- wrong header definition at client_plugin.h To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1579008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1571605] Re: Backport the ->> operator to MySQL 5.7
This feature has been backported to MySQL 5.7.13. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1571605 Title: Backport the ->> operator to MySQL 5.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1571605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577858] Re: bacula mysql support requires server configuration changes
The default SQL mode in 5.7 is "ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION". These are good defaults, so I recommend not changing the default SQL mode for the installation, but rather setting a suitable SQL mode in bacula sessions, using SET SESSION sql_mode = '...'. I also recommend that as many of the modes are kept and that only those causing problems are removed. See http://dev.mysql.com/doc/refman/5.7/en/sql-mode.html for more info. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577858 Title: bacula mysql support requires server configuration changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1577858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1553563] Re: bconsole to Bacula Director fails with authorization problem message
** Changed in: bacula (Ubuntu) Assignee: Norvald H. Ryeng (nryeng) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1553563 Title: bconsole to Bacula Director fails with authorization problem message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1553563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576930] Re: Excessive consumption RAM of mysqld daemon in Kubuntu 16.04
It might be this bug: http://bugs.mysql.com/bug.php?id=80772 Can try the workaround mentioned in the bug report? ** Bug watch added: MySQL Bug System #80772 http://bugs.mysql.com/bug.php?id=80772 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576930 Title: Excessive consumption RAM of mysqld daemon in Kubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1576930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570808] Re: Security fixes from the April 2016 CPU
Vulnerabilities fixed by upgrading from 5.7.11 to 5.7.12: CVE-2016-0639 CVE-2016-0642 CVE-2016-0643 CVE-2016-0647 CVE-2016-0648 CVE-2016-0655 CVE-2016-0657 CVE-2016-0659 CVE-2016-0662 CVE-2016-0666 CVE-2016-0667 CVE-2016-0705 CVE-2016-2047 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016-0639 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016-0642 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016-0643 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016-0647 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016-0648 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016-0655 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016-0657 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016-0659 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016-0662 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016-0666 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016-0667 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016-0705 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016-2047 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570808 Title: Security fixes from the April 2016 CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1570808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1571606] [NEW] Backport change of expire_logs_days to floating point in MySQL 5.7
Public bug reported: I'm filing this request for backporting a feature from 5.8 to the 5.7 stable branch so that it can be considered by the SRU Team and returned as input to upstream. Upstream is waiting for response from distros before deciding whether to backport or not. Background == The expire_logs_days system variable is an integer number of days to retain binlog files. The coarse granularity is causing problems with servers running out of disk space (http://bugs.mysql.com/bug.php?id=71697). The proposed change is to make expire_logs_days a floating point number so that finer granularity can be used if necessary, e.g.: SET GLOBAL expire_logs_days= 0.1; It will also mean that the data type will change: SELECT @@expire_logs_days; @@expire_logs_days 1.00 instead of the current result: SELECT @@expire_logs_days; @@expire_logs_days 1 Upstream would like to backport this change to MysQL 5.7. If backported, it will be done after the release of Ubuntu 16.04, so it will affect an existing Ubuntu release. This does not fall under the existing microrelease exception for MySQL, and so must be considered separately. In consideration of the microrelease exception requirements, upstream is interested in a decision for acceptance in an Ubuntu SRU before making the change upstream, so that any change made, or not made, is consistent across upstream, Ubuntu and any other distribution that wish to follow suit. We would like a +1 or a -1 from the SRU team (or Technical Board if appropriate) on backporting it to 5.7. Impact == If backported, the expire_logs_days will change from an integer number to a double precision floating point number. It will still be possible to set it to an integer number, so no applications setting this number need to change. Applications reading the number may encounter floating point numbers where there were previously only integers. If backported, this will be a built-in, non-optional part of the server. It is not suited for implementation in an optional plugin. MySQL 5.7 is not yet in Ubuntu, but will be when the new syntax can be backported. Regression potential The potential for regression is considered low for the following reasons: - Upstream is not aware of any tools that read the variable and parse the value. - The change is very small and localized ** Affects: mysql-5.7 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1571606 Title: Backport change of expire_logs_days to floating point in MySQL 5.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1571606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1571605] [NEW] Backport the ->> operator to MySQL 5.7
Public bug reported: As agreed with Robie Basak (racb), I'm filing this request for backporting a feature from 5.8 to the 5.7 stable branch so that it can be considered by the SRU Team and returned as input to upstream. Upstream is waiting for response from distros before deciding whether to backport or not. Background == MySQL 5.7 introduced a new JSON datatype, functions and operators to inspect and modify JSON documents. The JSON support has received a lot of attention and user feedback, and after requests from users, a new operator was introduced in MySQL 5.8 that makes the syntax more readable and easy to use. The new operator is only syntactic sugar, not new functionality. The new operator "->>" is a shorthand that allows the user to write json_field->>"$.a_key" instead of JSON_UNQUOTE(JSON_EXTRACT(json_field, "$.a_key")) Because of the immediate user requests on a new feature, upstream would like to backport this syntax to MySQL 5.7. If backported, it will be done after the release of Ubuntu 16.04, so it will affect an existing Ubuntu release. This does not fall under the existing microrelease exception for MySQL, and so must be considered separately. In consideration of the microrelease exception requirements, upstream is interested in a decision for acceptance in an Ubuntu SRU before making the change upstream, so that any change made, or not made, is consistent across upstream, Ubuntu and any other distribution that wish to follow suit. We would like a +1 or a -1 from the SRU team (or Technical Board if appropriate) on backporting it to 5.7. Impact == If backported, the new syntax will be a built-in, non-optional part of the server. It is not suited for implementation in an optional plugin. MySQL 5.7 is not yet in Ubuntu, but will be when the new syntax can be backported. JSON functionality is new in 5.7, so the user base is limited. No packages in Ubuntu currently use this functionality. Regression potential The potential for regression is considered low for the following reasons: - The new operator is pure syntactic sugar, no new functionality is added - The change is very small and localized - The change allows new syntax, no existing syntax is affected - No packages in Ubuntu currently use the JSON functionality of MySQL ** Affects: mysql-5.7 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1571605 Title: Backport the ->> operator to MySQL 5.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1571605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570808] [NEW] Security fixes from the April 2016 CPU
*** This bug is a security vulnerability *** Public security bug reported: The Oracle Critical Patch Update for April 2016 will be released on Tuesday, April 19. According to the pre-release announcement [1], it will contain information about CVEs fixed in MySQL 5.7.12. The CVE numbers will be available when the CPU is released. MySQL 5.7.12 has already been released and is available for download. [1] http://www.oracle.com/technetwork/topics/security/cpuapr2016-2881694.html ** Affects: mysql-5.7 (Ubuntu) Importance: Undecided Status: New ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570808 Title: Security fixes from the April 2016 CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1570808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1481333] Re: internal compiler error: in final_scan_insn, at final.c:3020
Still a problem with g++-5 (Ubuntu 5.2.1-12ubuntu2) 5.2.1 20150729.
~$ lsb_release -rd
Description:Ubuntu Wily Werewolf (development branch)
Release:15.10
~$ apt-cache policy g++-5
g++-5:
Installed: 5.2.1-12ubuntu2
Candidate: 5.2.1-12ubuntu2
Version table:
*** 5.2.1-12ubuntu2 0
500 http://ports.ubuntu.com/ubuntu-ports/ wily-proposed/main arm64
Packages
100 /var/lib/dpkg/status
5.1.1-14ubuntu1 0
500 http://ports.ubuntu.com/ubuntu-ports/ wily/main arm64 Packages
~/mysql-5.7.8-rc/build$ make VERBOSE=1 -i
[...]
[ 38%] Building CXX object
storage/innobase/CMakeFiles/innobase.dir/btr/btr0btr.cc.o
cd /home/nryeng/mysql-5.7.8-rc/build/storage/innobase /usr/bin/g++-5
-DCOMPILER_HINTS -DHAVE_CONFIG_H -DHAVE_FALLOC_PUNCH_HOLE_AND_KEEP_SIZE=1
-DHAVE_IB_ATOMIC_PTHREAD_T_GCC=1 -DHAVE_IB_GCC_ATOMIC_THREAD_FENCE=1
-DHAVE_IB_GCC_SYNC_SYNCHRONISE=1 -DHAVE_IB_LINUX_FUTEX=1 -DHAVE_LZ4=1
-DHAVE_NANOSLEEP=1 -DHAVE_SCHED_GETCPU=1 -DLINUX_NATIVE_AIO=1 -DMUTEX_EVENT
-D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -Wall -Wextra -Wformat-security -Wvla
-Woverloaded-virtual -Wno-unused-parameter -O3 -g -fabi-version=2
-fno-omit-frame-pointer -fno-strict-aliasing -DDBUG_OFF
-I/home/nryeng/mysql-5.7.8-rc/build/include
-I/home/nryeng/mysql-5.7.8-rc/extra/rapidjson/include
-I/home/nryeng/mysql-5.7.8-rc/build/libbinlogevents/include
-I/home/nryeng/mysql-5.7.8-rc/libbinlogevents/export
-I/home/nryeng/mysql-5.7.8-rc/extra/lz4
-I/home/nryeng/mysql-5.7.8-rc/storage/innobase/include
-I/home/nryeng/mysql-5.7.8-rc/storage/innobase/handler
-I/home/nryeng/mysql-5.7.8-rc/libbinlogevents/include
-I/home/nryeng/mysql-5.7.8-rc/include -I/home/nryeng/mysql-5.7.8-rc/sql
-I/home/nryeng/mysql-5.7.8-rc/sql/auth -I/home/nryeng/mysql-5.7.8-rc/regex
-I/home/nryeng/mysql-5.7.8-rc/extra/yassl/include
-I/home/nryeng/mysql-5.7.8-rc/extra/yassl/taocrypt/include
-I/home/nryeng/mysql-5.7.8-rc/zlib-DUNIV_LINUX -D_GNU_SOURCE=1 -o
CMakeFiles/innobase.dir/btr/btr0btr.cc.o -c
/home/nryeng/mysql-5.7.8-rc/storage/innobase/btr/btr0btr.cc
/home/nryeng/mysql-5.7.8-rc/storage/innobase/btr/btr0btr.cc: In function ‘bool
btr_validate_level(dict_index_t*, const trx_t*, ulint, bool)’:
/home/nryeng/mysql-5.7.8-rc/storage/innobase/btr/btr0btr.cc:4918:1: error:
could not split insn
}
^
(insn:TI 3427 11131 11145 (parallel [
(set (reg:DI 0 x0 [orig:493 D.102484 ] [493])
(plus:DI (mem/v:DI (reg/f:DI 28 x28 [1347]) [-1 S8 A64])
(const_int 536870912 [0x2000])))
(set (mem/v:DI (reg/f:DI 28 x28 [1347]) [-1 S8 A64])
(unspec_volatile:DI [
(mem/v:DI (reg/f:DI 28 x28 [1347]) [-1 S8 A64])
(const_int 536870912 [0x2000])
(const_int 5 [0x5])
] UNSPECV_ATOMIC_OP))
(clobber (reg:CC 66 cc))
(clobber (reg:SI 1 x1 [1439]))
]) /home/nryeng/mysql-5.7.8-rc/storage/innobase/include/sync0rw.ic:309
2499 {atomic_add_fetchdi}
(expr_list:REG_UNUSED (reg:CC 66 cc)
(expr_list:REG_UNUSED (reg:SI 1 x1 [1439])
(nil
/home/nryeng/mysql-5.7.8-rc/storage/innobase/btr/btr0btr.cc:4918:1: internal
compiler error: in final_scan_insn, at final.c:3020
0x9eadbf _fatal_insn(char const*, rtx_def const*, char const*, int, char const*)
../../src/gcc/rtl-error.c:110
0x80dfc7 final_scan_insn(rtx_insn*, _IO_FILE*, int, int, int*)
../../src/gcc/final.c:3020
0x80e287 final(rtx_insn*, _IO_FILE*, int)
../../src/gcc/final.c:2089
0x80e78f rest_of_handle_final
../../src/gcc/final.c:4488
0x80e78f execute
../../src/gcc/final.c:4563
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See file:///usr/share/doc/gcc-5/README.Bugs for instructions.
storage/innobase/CMakeFiles/innobase.dir/build.make:100: recipe for target
'storage/innobase/CMakeFiles/innobase.dir/btr/btr0btr.cc.o' failed
make[2]: [storage/innobase/CMakeFiles/innobase.dir/btr/btr0btr.cc.o] Error 1
(ignored)
/usr/bin/cmake -E cmake_progress_report
/home/nryeng/mysql-5.7.8-rc/build/CMakeFiles
[ 38%] Building CXX object
storage/innobase/CMakeFiles/innobase.dir/btr/btr0cur.cc.o
cd /home/nryeng/mysql-5.7.8-rc/build/storage/innobase /usr/bin/g++-5
-DCOMPILER_HINTS -DHAVE_CONFIG_H -DHAVE_FALLOC_PUNCH_HOLE_AND_KEEP_SIZE=1
-DHAVE_IB_ATOMIC_PTHREAD_T_GCC=1 -DHAVE_IB_GCC_ATOMIC_THREAD_FENCE=1
-DHAVE_IB_GCC_SYNC_SYNCHRONISE=1 -DHAVE_IB_LINUX_FUTEX=1 -DHAVE_LZ4=1
-DHAVE_NANOSLEEP=1 -DHAVE_SCHED_GETCPU=1 -DLINUX_NATIVE_AIO=1 -DMUTEX_EVENT
-D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -Wall -Wextra -Wformat-security -Wvla
-Woverloaded-virtual -Wno-unused-parameter -O3 -g -fabi-version=2
-fno-omit-frame-pointer -fno-strict-aliasing -DDBUG_OFF
-I/home/nryeng/mysql-5.7.8-rc/build/include
-I/home/nryeng/mysql-5.7.8-rc/extra/rapidjson/include
[Bug 1481333] Re: internal compiler error: in final_scan_insn, at final.c:3020
** Attachment added: Preprocessed source for btr0cur.cc https://bugs.launchpad.net/ubuntu/+source/gcc-5/+bug/1481333/+attachment/4440401/+files/btr0cur.cc.i -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1481333 Title: internal compiler error: in final_scan_insn, at final.c:3020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-5/+bug/1481333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1481333] Re: internal compiler error: in final_scan_insn, at final.c:3020
** Attachment added: Preprocessed source for gis0sea.cc https://bugs.launchpad.net/ubuntu/+source/gcc-5/+bug/1481333/+attachment/4440402/+files/gis0sea.cc.i -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1481333 Title: internal compiler error: in final_scan_insn, at final.c:3020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-5/+bug/1481333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1481333] Re: internal compiler error: in final_scan_insn, at final.c:3020
** Attachment added: Preprocessed source for btr0btr.cc https://bugs.launchpad.net/ubuntu/+source/gcc-5/+bug/1481333/+attachment/4440400/+files/btr0btr.cc.i -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1481333 Title: internal compiler error: in final_scan_insn, at final.c:3020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-5/+bug/1481333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1481333] [NEW] internal compiler error: in final_scan_insn, at final.c:3020
Public bug reported:
Seen with g++-5 (Ubuntu 5.1.1-4ubuntu12) 5.1.1 20150504 on aarch64 when
compiling MySQL 5.7.8-rc.
See also bug #1464234 for the same bug in g++ 4.9.
~$ lsb_release -rd
Description:Ubuntu 15.04
Release:15.04
~$ apt-cache policy g++-5
g++-5:
Installed: 5.1.1-4ubuntu12
Candidate: 5.1.1-4ubuntu12
Version table:
*** 5.1.1-4ubuntu12 0
500 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu/ vivid/main
arm64 Packages
100 /var/lib/dpkg/status
~/mysql-5.7.8-rc/build$ cmake .. -DCMAKE_C_COMPILER=gcc-5
-DCMAKE_CXX_COMPILER=g++-5 -DWITH_BOOST=~/boost
~/mysql-5.7.8-rc/build$ make VERBOSE=1 -i
[...]
[ 16%] Building CXX object
storage/innobase/CMakeFiles/innobase.dir/btr/btr0btr.cc.o
cd /home/nryeng/mysql-5.7.8-rc/build/storage/innobase /usr/bin/g++-5
-DCOMPILER_HINTS -DHAVE_CONFIG_H -DHAVE_FALLOC_PUNCH_HOLE_AND_KEEP_SIZE=1
-DHAVE_IB_ATOMIC_PTHREAD_T_GCC=1 -DHAVE_IB_GCC_ATOMIC_THREAD_FENCE=1
-DHAVE_IB_GCC_SYNC_SYNCHRONISE=1 -DHAVE_IB_LINUX_FUTEX=1 -DHAVE_LZ4=1
-DHAVE_NANOSLEEP=1 -DHAVE_SCHED_GETCPU=1 -DLINUX_NATIVE_AIO=1 -DMUTEX_EVENT
-D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -Wall -Wextra -Wformat-security -Wvla
-Woverloaded-virtual -Wno-unused-parameter -O3 -g -fabi-version=2
-fno-omit-frame-pointer -fno-strict-aliasing -DDBUG_OFF
-I/home/nryeng/mysql-5.7.8-rc/build/include
-I/home/nryeng/mysql-5.7.8-rc/extra/rapidjson/include
-I/home/nryeng/mysql-5.7.8-rc/build/libbinlogevents/include
-I/home/nryeng/mysql-5.7.8-rc/libbinlogevents/export
-I/home/nryeng/mysql-5.7.8-rc/extra/lz4
-I/home/nryeng/mysql-5.7.8-rc/storage/innobase/include
-I/home/nryeng/mysql-5.7.8-rc/storage/innobase/handler
-I/home/nryeng/mysql-5.7.8-rc/libbinlogevents/include
-I/home/nryeng/mysql-5.7.8-rc/include -I/home/nryeng/mysql-5.7.8-rc/sql
-I/home/nryeng/mysql-5.7.8-rc/sql/auth -I/home/nryeng/mysql-5.7.8-rc/regex
-I/home/nryeng/mysql-5.7.8-rc/extra/yassl/include
-I/home/nryeng/mysql-5.7.8-rc/extra/yassl/taocrypt/include
-I/home/nryeng/mysql-5.7.8-rc/zlib-DUNIV_LINUX -D_GNU_SOURCE=1 -o
CMakeFiles/innobase.dir/btr/btr0btr.cc.o -c
/home/nryeng/mysql-5.7.8-rc/storage/innobase/btr/btr0btr.cc
/home/nryeng/mysql-5.7.8-rc/storage/innobase/btr/btr0btr.cc: In function ‘bool
btr_validate_level(dict_index_t*, const trx_t*, ulint, bool)’:
/home/nryeng/mysql-5.7.8-rc/storage/innobase/btr/btr0btr.cc:4918:1: error:
could not split insn
}
^
(insn:TI 3427 11131 11145 (parallel [
(set (reg:DI 0 x0 [orig:493 D.102479 ] [493])
(plus:DI (mem/v:DI (reg/f:DI 28 x28 [1347]) [-1 S8 A64])
(const_int 536870912 [0x2000])))
(set (mem/v:DI (reg/f:DI 28 x28 [1347]) [-1 S8 A64])
(unspec_volatile:DI [
(mem/v:DI (reg/f:DI 28 x28 [1347]) [-1 S8 A64])
(const_int 536870912 [0x2000])
(const_int 5 [0x5])
] UNSPECV_ATOMIC_OP))
(clobber (reg:CC 66 cc))
(clobber (reg:SI 1 x1 [1439]))
]) /home/nryeng/mysql-5.7.8-rc/storage/innobase/include/sync0rw.ic:309
2499 {atomic_add_fetchdi}
(expr_list:REG_UNUSED (reg:CC 66 cc)
(expr_list:REG_UNUSED (reg:SI 1 x1 [1439])
(nil
/home/nryeng/mysql-5.7.8-rc/storage/innobase/btr/btr0btr.cc:4918:1: internal
compiler error: in final_scan_insn, at final.c:3020
0x9e83b7 _fatal_insn(char const*, rtx_def const*, char const*, int, char const*)
../../src/gcc/rtl-error.c:110
0x80c517 final_scan_insn(rtx_insn*, _IO_FILE*, int, int, int*)
../../src/gcc/final.c:3020
0x80c7d7 final(rtx_insn*, _IO_FILE*, int)
../../src/gcc/final.c:2089
0x80ccdf rest_of_handle_final
../../src/gcc/final.c:4488
0x80ccdf execute
../../src/gcc/final.c:4563
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See file:///usr/share/doc/gcc-5/README.Bugs for instructions.
storage/innobase/CMakeFiles/innobase.dir/build.make:100: recipe for target
'storage/innobase/CMakeFiles/innobase.dir/btr/btr0btr.cc.o' failed
make[2]: [storage/innobase/CMakeFiles/innobase.dir/btr/btr0btr.cc.o] Error 1
(ignored)
/usr/bin/cmake -E cmake_progress_report
/home/nryeng/mysql-5.7.8-rc/build/CMakeFiles
[ 16%] Building CXX object
storage/innobase/CMakeFiles/innobase.dir/btr/btr0cur.cc.o
cd /home/nryeng/mysql-5.7.8-rc/build/storage/innobase /usr/bin/g++-5
-DCOMPILER_HINTS -DHAVE_CONFIG_H -DHAVE_FALLOC_PUNCH_HOLE_AND_KEEP_SIZE=1
-DHAVE_IB_ATOMIC_PTHREAD_T_GCC=1 -DHAVE_IB_GCC_ATOMIC_THREAD_FENCE=1
-DHAVE_IB_GCC_SYNC_SYNCHRONISE=1 -DHAVE_IB_LINUX_FUTEX=1 -DHAVE_LZ4=1
-DHAVE_NANOSLEEP=1 -DHAVE_SCHED_GETCPU=1 -DLINUX_NATIVE_AIO=1 -DMUTEX_EVENT
-D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -Wall -Wextra -Wformat-security -Wvla
-Woverloaded-virtual -Wno-unused-parameter -O3 -g -fabi-version=2
-fno-omit-frame-pointer -fno-strict-aliasing -DDBUG_OFF
[Bug 1464234] [NEW] internal compiler error: in final_scan_insn, at final.c:2952
Public bug reported:
Seen with g++ (Ubuntu/Linaro 4.9.2-10ubuntu13) 4.9.2 on Ubuntu 15.04
when compiling MySQL 5.7.7-rc.
It compiles if I set -O1 for btr0btr.cc and -O0 for gis0sea.cc.
See bug #1353729 for a similar case that has been fixed.
~/mysql-5.7.7-rc/build$ cmake .. -DWITH_BOOST=~/boost ### Boost 1.57 headers,
unpack the tarball in ~/boost
~/mysql-5.7.7-rc/build$ make VERBOSE=1 -i
[...]
[ 38%] Building CXX object
storage/innobase/CMakeFiles/innobase.dir/btr/btr0btr.cc.o
cd /home/nryeng/mysql-5.7.7-rc/build/storage/innobase /usr/bin/c++
-DCOMPILER_HINTS -DHAVE_CONFIG_H -DHAVE_IB_ATOMIC_PTHREAD_T_GCC=1
-DHAVE_IB_GCC_ATOMIC_THREAD_FENCE=1 -DHAVE_IB_GCC_SYNC_SYNCHRONISE=1
-DHAVE_IB_LINUX_FUTEX=1 -DHAVE_NANOSLEEP=1 -DHAVE_SCHED_GETCPU=1
-DLINUX_NATIVE_AIO=1 -DMUTEX_EVENT -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -Wall
-Wextra -Wformat-security -Wvla -Woverloaded-virtual -Wno-unused-parameter -O3
-g -fabi-version=2 -fno-omit-frame-pointer -fno-strict-aliasing -DDBUG_OFF
-I/home/nryeng/mysql-5.7.7-rc/build/include
-I/home/nryeng/mysql-5.7.7-rc/extra/rapidjson/include
-I/home/nryeng/mysql-5.7.7-rc/build/libbinlogevents/include
-I/home/nryeng/mysql-5.7.7-rc/libbinlogevents/export
-I/home/nryeng/mysql-5.7.7-rc/storage/innobase/include
-I/home/nryeng/mysql-5.7.7-rc/storage/innobase/handler
-I/home/nryeng/mysql-5.7.7-rc/libbinlogevents/include
-I/home/nryeng/mysql-5.7.7-rc/include -I/home/nryeng/mysql-5.7.7-rc/sql
-I/home/nryeng/mysql-5.7.7-rc/sql/auth -I/home/nryeng/mysql-5.7.7-rc/regex
-I/home/nryeng/mysql-5.7.7-rc/extra/yassl/include
-I/home/nryeng/mysql-5.7.7-rc/extra/yassl/taocrypt/include
-I/home/nryeng/mysql-5.7.7-rc/zlib-DUNIV_LINUX -D_GNU_SOURCE=1 -o
CMakeFiles/innobase.dir/btr/btr0btr.cc.o -c
/home/nryeng/mysql-5.7.7-rc/storage/innobase/btr/btr0btr.cc
/home/nryeng/mysql-5.7.7-rc/storage/innobase/btr/btr0btr.cc: In function ‘bool
btr_validate_level(dict_index_t*, const trx_t*, ulint, bool)’:
/home/nryeng/mysql-5.7.7-rc/storage/innobase/btr/btr0btr.cc:5001:1: error:
could not split insn
}
^
(insn:TI 4049 12643 12652 (parallel [
(set (reg:DI 0 x0 [orig:840 D.96053 ] [840])
(plus:DI (mem/v:DI (reg/f:DI 28 x28 [2112]) [-1 S8 A64])
(const_int 536870912 [0x2000])))
(set (mem/v:DI (reg/f:DI 28 x28 [2112]) [-1 S8 A64])
(unspec_volatile:DI [
(mem/v:DI (reg/f:DI 28 x28 [2112]) [-1 S8 A64])
(const_int 536870912 [0x2000])
(const_int 5 [0x5])
] UNSPECV_ATOMIC_OP))
(clobber (reg:CC 66 cc))
(clobber (reg:SI 1 x1 [2201]))
]) /home/nryeng/mysql-5.7.7-rc/storage/innobase/include/sync0rw.ic:310
2409 {atomic_add_fetchdi}
(expr_list:REG_UNUSED (reg:CC 66 cc)
(expr_list:REG_UNUSED (reg:SI 1 x1 [2201])
(nil
/home/nryeng/mysql-5.7.7-rc/storage/innobase/btr/btr0btr.cc:5001:1: internal
compiler error: in final_scan_insn, at final.c:2952
Please submit a full bug report,
with preprocessed source if appropriate.
See file:///usr/share/doc/gcc-4.9/README.Bugs for instructions.
Preprocessed source stored into /tmp/ccLtmlZk.out file, please attach this to
your bugreport.
storage/innobase/CMakeFiles/innobase.dir/build.make:100: recipe for target
'storage/innobase/CMakeFiles/innobase.dir/btr/btr0btr.cc.o' failed
make[2]: [storage/innobase/CMakeFiles/innobase.dir/btr/btr0btr.cc.o] Error 1
(ignored)
[...]
[ 40%] Building CXX object
storage/innobase/CMakeFiles/innobase.dir/gis/gis0sea.cc.o
cd /home/nryeng/mysql-5.7.7-rc/build/storage/innobase /usr/bin/c++
-DCOMPILER_HINTS -DHAVE_CONFIG_H -DHAVE_IB_ATOMIC_PTHREAD_T_GCC=1
-DHAVE_IB_GCC_ATOMIC_THREAD_FENCE=1 -DHAVE_IB_GCC_SYNC_SYNCHRONISE=1
-DHAVE_IB_LINUX_FUTEX=1 -DHAVE_NANOSLEEP=1 -DHAVE_SCHED_GETCPU=1
-DLINUX_NATIVE_AIO=1 -DMUTEX_EVENT -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -Wall
-Wextra -Wformat-security -Wvla -Woverloaded-virtual -Wno-unused-parameter -O3
-g -fabi-version=2 -fno-omit-frame-pointer -fno-strict-aliasing -DDBUG_OFF
-I/home/nryeng/mysql-5.7.7-rc/build/include
-I/home/nryeng/mysql-5.7.7-rc/extra/rapidjson/include
-I/home/nryeng/mysql-5.7.7-rc/build/libbinlogevents/include
-I/home/nryeng/mysql-5.7.7-rc/libbinlogevents/export
-I/home/nryeng/mysql-5.7.7-rc/storage/innobase/include
-I/home/nryeng/mysql-5.7.7-rc/storage/innobase/handler
-I/home/nryeng/mysql-5.7.7-rc/libbinlogevents/include
-I/home/nryeng/mysql-5.7.7-rc/include -I/home/nryeng/mysql-5.7.7-rc/sql
-I/home/nryeng/mysql-5.7.7-rc/sql/auth -I/home/nryeng/mysql-5.7.7-rc/regex
-I/home/nryeng/mysql-5.7.7-rc/extra/yassl/include
-I/home/nryeng/mysql-5.7.7-rc/extra/yassl/taocrypt/include
-I/home/nryeng/mysql-5.7.7-rc/zlib-DUNIV_LINUX -D_GNU_SOURCE=1 -o
CMakeFiles/innobase.dir/gis/gis0sea.cc.o -c
/home/nryeng/mysql-5.7.7-rc/storage/innobase/gis/gis0sea.cc
/home/nryeng/mysql-5.7.7-rc/storage/innobase/gis/gis0sea.cc: In
[Bug 1437846] Re: akonadi mysql 5.6 crash with signal 11
In both error logs, I see this sequence (with varying timestamps and seq numbers, of course): 2015-03-29 15:03:37 2265 [Note] InnoDB: The log sequence numbers 10740390801 and 10740390801 in ibdata files do not match the log sequence number 11404279789 in the ib_logfiles! 2015-03-29 15:03:37 2265 [Note] InnoDB: Database was not shutdown normally! 2015-03-29 15:03:37 2265 [Note] InnoDB: Starting crash recovery. I think that's the core of the problem. 5.5 was not shut down properly before upgrading, so it's left to 5.6 to try to recover. For some reason it can't, and it crashes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1437846 Title: akonadi mysql 5.6 crash with signal 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1437846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1437846] Re: akonadi mysql 5.6 crash with signal 11
In both error logs, I see this sequence (with varying timestamps and seq numbers, of course): 2015-03-29 15:03:37 2265 [Note] InnoDB: The log sequence numbers 10740390801 and 10740390801 in ibdata files do not match the log sequence number 11404279789 in the ib_logfiles! 2015-03-29 15:03:37 2265 [Note] InnoDB: Database was not shutdown normally! 2015-03-29 15:03:37 2265 [Note] InnoDB: Starting crash recovery. I think that's the core of the problem. 5.5 was not shut down properly before upgrading, so it's left to 5.6 to try to recover. For some reason it can't, and it crashes. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1437846 Title: akonadi mysql 5.6 crash with signal 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1437846/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1433784] [NEW] mysql-5.5 fails to build in trusty-updates and trusty-security (outdated certificates)
On Wed, 18 Mar 2015 21:50:02 +0100, Matthias Klose d...@ubuntu.com wrote: Public bug reported: seen in a test rebuild with an updated toolchain, and verified in a clean trusty chroot. the next security update for mysql-5.5 will fail. https://launchpad.net/ubuntu/+archive/test-rebuild-20150317-security/+build/7070395 https://launchpad.net/ubuntu/+archive/test-rebuild-20150317-security/+build/7070392 notifying ubuntu-server and ubuntu-security. An upgrade to 5.5.42 (released 2015-02-02) will fix the expired SSL cert in the test suite. Regards, Norvald H. Ryeng -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1433784 Title: mysql-5.5 fails to build in trusty-updates and trusty-security (outdated certificates) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1433784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1423026] Re: Build fails due to test creation of test database that already exists
I did some detective work: mysql_install_db 5.5 was patched in
Debian/Ubuntu to not create the test database. In 5.6 packaging,
mysql_install_db isn't run during a normal install (the necessary lines
are part of postinst instead), so it was never necessary to patch it to
not create the test database.
If you need a line that works in both 5.5 and 5.6:
mysql --socket=${MYSQL_UNIX_PORT} --execute CREATE DATABASE
${DO_MYSQL_DBNAME} IF NOT EXISTS;
The last clause of the SQL string makes sure it doesn't fail if the
database already exists.
Another option is to patch mysql_install_db in 5.6 packaging.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1423026
Title:
Build fails due to test creation of test database that already exists
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ruby-mysql2/+bug/1423026/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1422391] Re: my-default.cnf missing
The file is indeed missing. It should've been in the mysql-server- core-5.6 package, but it's not. In ruby-mysql2: Add --keep-my-cnf to the mysql_install_db command line. Since the server is started with --no-defaults, it's not going to read the my.cnf file, and mysql_install_db doesn't need to create it. In mysql-server-core-5.6: Add usr/share/mysql/my-default.cnf to the package. mysql_install_db expects to find it. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1422391 Title: my-default.cnf missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1422391/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1422391] Re: my-default.cnf missing
The file is indeed missing. It should've been in the mysql-server- core-5.6 package, but it's not. In ruby-mysql2: Add --keep-my-cnf to the mysql_install_db command line. Since the server is started with --no-defaults, it's not going to read the my.cnf file, and mysql_install_db doesn't need to create it. In mysql-server-core-5.6: Add usr/share/mysql/my-default.cnf to the package. mysql_install_db expects to find it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1422391 Title: my-default.cnf missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1422391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1419262] Re: mysql-5.5 test suite no longer works because of timestamps in the past
This bug has been fixed in MySQL 5.5.42. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1419262 Title: mysql-5.5 test suite no longer works because of timestamps in the past To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1419262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396210] [NEW] Backporting the mysql_no_login plugin to 5.6
Public bug reported: As agreed with Robie Basak (racb), I'm filing this request for backporting a feature from 5.7 to the 5.6 stable branch so that it can be considered by the SRU Team and returned as input to upstream. Upstream is waiting for response from distros before deciding whether to backport or not. Background == There's a new plugin in MySQL 5.7 that makes it possible to have accounts that can't log in: CREATE USER foo@localhost IDENTIFIED WITH 'mysql_no_login'; The mysql_no_login plugin simply denies all login attempts. This is useful for users that are created, e.g., to serve as proxy users, or as owners of stored programs/functions, views or events. This new plugin doesn't fix known security defects in the server, but does provide new and better means to harden security. Best practices for security include application of least-required privileges, and in some cases, that means no client connections for privileged accounts. This new plugin provides means to implement such restrictions in a standard way. Because of the security benefits, upstream would proposes backporting it to 5.6. This does not fall under the existing micro-release exception for mysql-5.6, and so must be considered separately. In consideration of the micro-release exception requirements, upstream are interested in a decision for acceptance in an Ubuntu SRU before making the change upstream, so that any change made, or not made, is consistent across upstream, Ubuntu and any other distribution that wish to follow suit. We would like a +1 or a -1 from the SRU team (or Technical Board if appropriate) on 1) backporting the plugin into the 5.6 source code, and 2) for each of the options presented below. Impact == If backported, the plugin would at least be available in the source tarball. That doesn't mean it has to be distributed in Ubuntu: - A patch can be applied to remove the plugin from the source code before building (it's only a few lines of code). - Compilation of the plugin can be disabled. - It can be built but the resulting plugin binary can be left out of packages. - It can be built and packaged. The DBA still has to explicitly enable it and alter the user accounts to use it. Proposed development fix Either 1) Build and package the plugin, or 2) allow the plugin in source code, but don't package it (either by disabling it before compilation or skipping the binary in packaging). Fedora/Red Hat has +1'ed a backport: http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/2014-October/007195.html Proposed stable fix === Same as development fix. Regression potential Upstream considers the regression potential to be very low. - Since this is a plugin, it doesn't touch server code. - All new code is in a plugin that must be enabled explicitly by the DBA. - The code itself is very simple. It's only one line of real code (unconditionally return authentication failure), plus necessary plugin plumbing to fill out the plugin API. ** Affects: mysql-5.6 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1396210 Title: Backporting the mysql_no_login plugin to 5.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1396210/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1396210] [NEW] Backporting the mysql_no_login plugin to 5.6
Public bug reported: As agreed with Robie Basak (racb), I'm filing this request for backporting a feature from 5.7 to the 5.6 stable branch so that it can be considered by the SRU Team and returned as input to upstream. Upstream is waiting for response from distros before deciding whether to backport or not. Background == There's a new plugin in MySQL 5.7 that makes it possible to have accounts that can't log in: CREATE USER foo@localhost IDENTIFIED WITH 'mysql_no_login'; The mysql_no_login plugin simply denies all login attempts. This is useful for users that are created, e.g., to serve as proxy users, or as owners of stored programs/functions, views or events. This new plugin doesn't fix known security defects in the server, but does provide new and better means to harden security. Best practices for security include application of least-required privileges, and in some cases, that means no client connections for privileged accounts. This new plugin provides means to implement such restrictions in a standard way. Because of the security benefits, upstream would proposes backporting it to 5.6. This does not fall under the existing micro-release exception for mysql-5.6, and so must be considered separately. In consideration of the micro-release exception requirements, upstream are interested in a decision for acceptance in an Ubuntu SRU before making the change upstream, so that any change made, or not made, is consistent across upstream, Ubuntu and any other distribution that wish to follow suit. We would like a +1 or a -1 from the SRU team (or Technical Board if appropriate) on 1) backporting the plugin into the 5.6 source code, and 2) for each of the options presented below. Impact == If backported, the plugin would at least be available in the source tarball. That doesn't mean it has to be distributed in Ubuntu: - A patch can be applied to remove the plugin from the source code before building (it's only a few lines of code). - Compilation of the plugin can be disabled. - It can be built but the resulting plugin binary can be left out of packages. - It can be built and packaged. The DBA still has to explicitly enable it and alter the user accounts to use it. Proposed development fix Either 1) Build and package the plugin, or 2) allow the plugin in source code, but don't package it (either by disabling it before compilation or skipping the binary in packaging). Fedora/Red Hat has +1'ed a backport: http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/2014-October/007195.html Proposed stable fix === Same as development fix. Regression potential Upstream considers the regression potential to be very low. - Since this is a plugin, it doesn't touch server code. - All new code is in a plugin that must be enabled explicitly by the DBA. - The code itself is very simple. It's only one line of real code (unconditionally return authentication failure), plus necessary plugin plumbing to fill out the plugin API. ** Affects: mysql-5.6 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396210 Title: Backporting the mysql_no_login plugin to 5.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1396210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1076656] Re: mysql --ssl-capath option doesn't work
Despite have_openssl YES, the community edition of MySQL uses yaSSL, not OpenSSL (have_openssl is just an alias for have_ssl). You've probably stumbled upon this difference between OpenSSL and yaSSL (cut and pasted from http://dev.mysql.com/doc/refman/5.5/en/ssl-options.html #option_general_ssl-capath): MySQL distributions built with OpenSSL support the --ssl-capath option. Distributions built with yaSSL do not because yaSSL does not look in any directory and does not follow a chained certificate tree. yaSSL requires that all components of the CA certificate tree be contained within a single CA certificate tree and that each certificate in the file has a unique SubjectName value. To work around this yaSSL limitation, concatenate the individual certificate files comprising the certificate tree into a new file. Then specify the new file as the value of the --ssl-capath option. The reason this changed is probably that the build options used when packaging for Ubuntu changed. Earlier versions of MySQL in Ubuntu may have been linked against OpenSSL since it was built with the WITH_SSL=yes option. This made the build system pick up OpenSSL if it was installed on the system and use the bundled yaSSL library otherwise, so which library the package used depended on whether the system where the package was built happened to have OpenSSL installed or not. This is obviously not good, so in more recent builds this option has been set to WITH_SSL=bundled, wich means that the bundled yaSSL library will always be used. Regards, Norvald H. Ryeng -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.1 in Ubuntu. https://bugs.launchpad.net/bugs/1076656 Title: mysql --ssl-capath option doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.1/+bug/1076656/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1076656] Re: mysql --ssl-capath option doesn't work
Despite have_openssl YES, the community edition of MySQL uses yaSSL, not OpenSSL (have_openssl is just an alias for have_ssl). You've probably stumbled upon this difference between OpenSSL and yaSSL (cut and pasted from http://dev.mysql.com/doc/refman/5.5/en/ssl-options.html #option_general_ssl-capath): MySQL distributions built with OpenSSL support the --ssl-capath option. Distributions built with yaSSL do not because yaSSL does not look in any directory and does not follow a chained certificate tree. yaSSL requires that all components of the CA certificate tree be contained within a single CA certificate tree and that each certificate in the file has a unique SubjectName value. To work around this yaSSL limitation, concatenate the individual certificate files comprising the certificate tree into a new file. Then specify the new file as the value of the --ssl-capath option. The reason this changed is probably that the build options used when packaging for Ubuntu changed. Earlier versions of MySQL in Ubuntu may have been linked against OpenSSL since it was built with the WITH_SSL=yes option. This made the build system pick up OpenSSL if it was installed on the system and use the bundled yaSSL library otherwise, so which library the package used depended on whether the system where the package was built happened to have OpenSSL installed or not. This is obviously not good, so in more recent builds this option has been set to WITH_SSL=bundled, wich means that the bundled yaSSL library will always be used. Regards, Norvald H. Ryeng -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1076656 Title: mysql --ssl-capath option doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.1/+bug/1076656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Blueprint servercloud-r-mysql] MySQL Roundtable
Blueprint changed by Norvald H. Ryeng: Whiteboard changed: Things to discuss: * What to do about lack of unit tests in recent patch releases of MySQL * MariaDB and Percona Server in the distro * Upstream MariaDB and Pecona Server package compatibility w/ distro * Synchronizing packaging between Ubuntu and Debian * Collaboration on MySQL Juju charm * Adding Galera Support to Packaging * General HA solutions (Critical for OpenStack deployments) + * MySQL 5.6 + * MySQL release schedule User Stories: Risks: Test Plans: Release Note: -- MySQL Roundtable https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-mysql -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 555706] [NEW] gsat GUI unreadable after GTK2 fix
Public bug reported: Binary package hint: predict-gsat After the GTK2 fix, the GUI has become unreadable and unusable. Widgets are piled on top of each other in a big mess. The attached patch resizes and repositions the widgets in a non- overlapping way. At least it works with the default Lucid theme. Gsat uses fixed widget positioning, so this will probably vary between GTK themes. :-( ** Affects: predict (Ubuntu) Importance: Undecided Status: New -- gsat GUI unreadable after GTK2 fix https://bugs.launchpad.net/bugs/555706 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 555706] Re: gsat GUI unreadable after GTK2 fix
** Patch added: Fixes widget layout http://launchpadlibrarian.net/43155656/180_reworked_gui.diff -- gsat GUI unreadable after GTK2 fix https://bugs.launchpad.net/bugs/555706 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 553106] Re: hamlib plugins for gsat
** Attachment added: rigctld and rotctld plugins for gsat http://launchpadlibrarian.net/42758858/170_gsat_hamlib_plugins.diff -- hamlib plugins for gsat https://bugs.launchpad.net/bugs/553106 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 553106] [NEW] hamlib plugins for gsat
Public bug reported: Binary package hint: predict-gsat This patch adds two plugins to gsat: radio_rigctld: Controls a radio using rigctld rotor_rotctld: Controls a rotator using rotctld With these plugins, gsat can control all radios and rotators supported by hamlib. ** Affects: predict (Ubuntu) Importance: Undecided Status: New -- hamlib plugins for gsat https://bugs.launchpad.net/bugs/553106 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 553140] [NEW] predict-g1yyh crashes when printing predictions
Public bug reported: Binary package hint: predict A buffer overflow makes predict-g1yyh crash when printing predictions (p, v, s, n and o commands). The attached patch extends header line 2 (head2) with an extra byte for the terminating \0 and shortens two strings that were 1 byte too long. ** Affects: predict (Ubuntu) Importance: Undecided Status: New -- predict-g1yyh crashes when printing predictions https://bugs.launchpad.net/bugs/553140 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 553140] Re: predict-g1yyh crashes when printing predictions
** Patch added: Fixes buffer overflow http://launchpadlibrarian.net/42765838/141_buffer_overflow.diff -- predict-g1yyh crashes when printing predictions https://bugs.launchpad.net/bugs/553140 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 552568] [NEW] hamlib rotctld support
Public bug reported: Binary package hint: predict The attached patch adds support for hamlib's rotctld rotator control daemon. The original predict only supports the EasyComm protocol. With support for rotctld, all rotators in hamlib are supported. Four options are added: -A rotctld server -A1 rotctld server -P rotctld port number -h horizon The -A and -A1 options are similar to the -a and -a1, but take the server name or IP address as parameter. The -P option allows the use of a non-standard port (default is 4533). The -h option sets the horizon. E.g., -h -5.3 sets the horizon to be at -5.3 deg. Predict will send tracking output to the serial port and rotctld server as long as the satellite is above the horizon. ** Affects: predict (Ubuntu) Importance: Undecided Status: New -- hamlib rotctld support https://bugs.launchpad.net/bugs/552568 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 552568] Re: hamlib rotctld support
** Patch added: rotctld support and manual page http://launchpadlibrarian.net/42653396/150_rotctld.diff -- hamlib rotctld support https://bugs.launchpad.net/bugs/552568 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 552568] Re: hamlib rotctld support
The same patch for predict-g1yyh.c ** Patch added: rotctld support for predict-g1yyh http://launchpadlibrarian.net/42653545/160_rotctld-g1yyh.diff -- hamlib rotctld support https://bugs.launchpad.net/bugs/552568 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 552049] [NEW] predict crashes on startup with -s option
Public bug reported: Binary package hint: predict When starting predict or predict-g1yyh in server mode (-s) without specifying port number with -n, it results in buffer overflow. The problem is that char netport[6] is not big enough to contain the default port (predict). The buffer must be increased to at least 8 bytes. This must be done in both predict.c and predict-g1yyh.c ** Affects: predict (Ubuntu) Importance: Undecided Status: New -- predict crashes on startup with -s option https://bugs.launchpad.net/bugs/552049 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 552049] Re: predict crashes on startup with -s option
** Patch added: Extends netport to 8 bytes http://launchpadlibrarian.net/42552417/netport.patch -- predict crashes on startup with -s option https://bugs.launchpad.net/bugs/552049 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
