Activity log for bug #1821361

Date Who What changed Old value New value Message
2019-03-22 14:30:53 Andreas Hasenack bug added bug
2019-03-22 20:26:05 Andreas Hasenack mongodb (Ubuntu): assignee Andreas Hasenack (ahasenack)
2019-03-22 20:26:09 Andreas Hasenack mongodb (Ubuntu): status New In Progress
2019-03-22 20:26:11 Andreas Hasenack mongodb (Ubuntu): importance Undecided Critical
2019-03-27 18:04:12 Launchpad Janitor merge proposal linked https://code.launchpad.net/~ahasenack/ubuntu/+source/mongodb/+git/mongodb/+merge/365188
2019-03-27 18:21:32 Andreas Hasenack nominated for series Ubuntu Cosmic
2019-03-27 18:21:32 Andreas Hasenack bug task added mongodb (Ubuntu Cosmic)
2019-03-27 18:22:39 Andreas Hasenack mongodb (Ubuntu Cosmic): importance Undecided Critical
2019-03-27 18:22:40 Andreas Hasenack mongodb (Ubuntu Cosmic): assignee Andreas Hasenack (ahasenack)
2019-03-27 18:22:44 Andreas Hasenack mongodb (Ubuntu): assignee Andreas Hasenack (ahasenack)
2019-03-27 18:23:05 Andreas Hasenack mongodb (Ubuntu): status In Progress Fix Released
2019-03-27 18:23:27 Andreas Hasenack mongodb (Ubuntu Cosmic): status New In Progress
2019-03-27 18:58:46 Andreas Hasenack description mongodb 3.6.3 is currently failing to build in cosmic. https://launchpadlibrarian.net/416133571/buildlog_ubuntu-cosmic-amd64.mongodb_1%3A3.6.3-0ubuntu1.18.10.1_BUILDING.txt.gz They all seem to be about Werror=class-memaccess. Example: src/mongo/db/pipeline/value_internal.h:194:42: error: 'void* memmove(void*, const void*, size_t)' writing to an object of type 'class mongo::ValueStorage' with no trivial copy-assignment; use copy-assignment or copy-initialization instead [-Werror=class-memaccess] memmove(this, &rhs, sizeof(*this)); ^ src/mongo/db/pipeline/value_internal.h:78:7: note: 'class mongo::ValueStorage' declared here And, of course: cc1plus: all warnings being treated as errors [Impact] Multiple FTBFS errors when building mongodb in cosmic. - new gcc8 warnings (format-truncation and class-memaccess) - -Wparentheses warning - incompatibility with boost1.66+ [Test Case] Rebuild mongodb in cosmic. Without these fixes, the build will fail. There is an additional fix needed for boost1.67 itself, which is being handled in bug #1821762 [Regression Potential] All bug the fix in boost1.67 mentioned above are due to new gcc8 checks, which suggests that mongodb was last built in cosmic before gcc8 became default. [Other Info] Mongo upstream nowadays has proper fixes for the format-truncation and class-memaccess warnings, but these were done[1] after the switch to the SSPL license[2] on October 16th, 2018. What I have done here is grab the fix we currently have in disco which was done by upstream[3] before that date. [Original Description] mongodb 3.6.3 is currently failing to build in cosmic. https://launchpadlibrarian.net/416133571/buildlog_ubuntu-cosmic-amd64.mongodb_1%3A3.6.3-0ubuntu1.18.10.1_BUILDING.txt.gz They all seem to be about Werror=class-memaccess. Example: src/mongo/db/pipeline/value_internal.h:194:42: error: 'void* memmove(void*, const void*, size_t)' writing to an object of type 'class mongo::ValueStorage' with no trivial copy-assignment; use copy-assignment or copy-initialization instead [-Werror=class-memaccess]          memmove(this, &rhs, sizeof(*this));                                           ^ src/mongo/db/pipeline/value_internal.h:78:7: note: 'class mongo::ValueStorage' declared here And, of course: cc1plus: all warnings being treated as errors 1. https://github.com/mongodb/mongo/commit/76b0fcea6960274d23a3bd1245a0e55e3cb08369 and https://github.com/mongodb/mongo/commit/f53ed89cef7c4356789114b2de1a5294e3d7a6f7 2. https://www.mongodb.com/licensing/server-side-public-license/faq 3. https://github.com/mongodb/mongo/commit/168c8d65556ab18b05e33b5f4006d1184c30f8f7
2019-03-27 18:59:04 Andreas Hasenack description [Impact] Multiple FTBFS errors when building mongodb in cosmic. - new gcc8 warnings (format-truncation and class-memaccess) - -Wparentheses warning - incompatibility with boost1.66+ [Test Case] Rebuild mongodb in cosmic. Without these fixes, the build will fail. There is an additional fix needed for boost1.67 itself, which is being handled in bug #1821762 [Regression Potential] All bug the fix in boost1.67 mentioned above are due to new gcc8 checks, which suggests that mongodb was last built in cosmic before gcc8 became default. [Other Info] Mongo upstream nowadays has proper fixes for the format-truncation and class-memaccess warnings, but these were done[1] after the switch to the SSPL license[2] on October 16th, 2018. What I have done here is grab the fix we currently have in disco which was done by upstream[3] before that date. [Original Description] mongodb 3.6.3 is currently failing to build in cosmic. https://launchpadlibrarian.net/416133571/buildlog_ubuntu-cosmic-amd64.mongodb_1%3A3.6.3-0ubuntu1.18.10.1_BUILDING.txt.gz They all seem to be about Werror=class-memaccess. Example: src/mongo/db/pipeline/value_internal.h:194:42: error: 'void* memmove(void*, const void*, size_t)' writing to an object of type 'class mongo::ValueStorage' with no trivial copy-assignment; use copy-assignment or copy-initialization instead [-Werror=class-memaccess]          memmove(this, &rhs, sizeof(*this));                                           ^ src/mongo/db/pipeline/value_internal.h:78:7: note: 'class mongo::ValueStorage' declared here And, of course: cc1plus: all warnings being treated as errors 1. https://github.com/mongodb/mongo/commit/76b0fcea6960274d23a3bd1245a0e55e3cb08369 and https://github.com/mongodb/mongo/commit/f53ed89cef7c4356789114b2de1a5294e3d7a6f7 2. https://www.mongodb.com/licensing/server-side-public-license/faq 3. https://github.com/mongodb/mongo/commit/168c8d65556ab18b05e33b5f4006d1184c30f8f7 [Impact] Multiple FTBFS errors when building mongodb in cosmic. - new gcc8 warnings (format-truncation and class-memaccess) - -Wparentheses warning - incompatibility with boost1.66+ [Test Case] Rebuild mongodb in cosmic. Without these fixes, the build will fail. There is an additional fix needed for boost1.67 itself, which is being handled in bug #1821762 [Regression Potential] All but the fix in boost1.67 mentioned above are due to new gcc8 checks, which suggests that mongodb was last built in cosmic before gcc8 became default. [Other Info] Mongo upstream nowadays has proper fixes for the format-truncation and class-memaccess warnings, but these were done[1] after the switch to the SSPL license[2] on October 16th, 2018. What I have done here is grab the fix we currently have in disco which was done by upstream[3] before that date. [Original Description] mongodb 3.6.3 is currently failing to build in cosmic. https://launchpadlibrarian.net/416133571/buildlog_ubuntu-cosmic-amd64.mongodb_1%3A3.6.3-0ubuntu1.18.10.1_BUILDING.txt.gz They all seem to be about Werror=class-memaccess. Example: src/mongo/db/pipeline/value_internal.h:194:42: error: 'void* memmove(void*, const void*, size_t)' writing to an object of type 'class mongo::ValueStorage' with no trivial copy-assignment; use copy-assignment or copy-initialization instead [-Werror=class-memaccess]          memmove(this, &rhs, sizeof(*this));                                           ^ src/mongo/db/pipeline/value_internal.h:78:7: note: 'class mongo::ValueStorage' declared here And, of course: cc1plus: all warnings being treated as errors 1. https://github.com/mongodb/mongo/commit/76b0fcea6960274d23a3bd1245a0e55e3cb08369 and https://github.com/mongodb/mongo/commit/f53ed89cef7c4356789114b2de1a5294e3d7a6f7 2. https://www.mongodb.com/licensing/server-side-public-license/faq 3. https://github.com/mongodb/mongo/commit/168c8d65556ab18b05e33b5f4006d1184c30f8f7
2019-03-27 19:00:34 Andreas Hasenack description [Impact] Multiple FTBFS errors when building mongodb in cosmic. - new gcc8 warnings (format-truncation and class-memaccess) - -Wparentheses warning - incompatibility with boost1.66+ [Test Case] Rebuild mongodb in cosmic. Without these fixes, the build will fail. There is an additional fix needed for boost1.67 itself, which is being handled in bug #1821762 [Regression Potential] All but the fix in boost1.67 mentioned above are due to new gcc8 checks, which suggests that mongodb was last built in cosmic before gcc8 became default. [Other Info] Mongo upstream nowadays has proper fixes for the format-truncation and class-memaccess warnings, but these were done[1] after the switch to the SSPL license[2] on October 16th, 2018. What I have done here is grab the fix we currently have in disco which was done by upstream[3] before that date. [Original Description] mongodb 3.6.3 is currently failing to build in cosmic. https://launchpadlibrarian.net/416133571/buildlog_ubuntu-cosmic-amd64.mongodb_1%3A3.6.3-0ubuntu1.18.10.1_BUILDING.txt.gz They all seem to be about Werror=class-memaccess. Example: src/mongo/db/pipeline/value_internal.h:194:42: error: 'void* memmove(void*, const void*, size_t)' writing to an object of type 'class mongo::ValueStorage' with no trivial copy-assignment; use copy-assignment or copy-initialization instead [-Werror=class-memaccess]          memmove(this, &rhs, sizeof(*this));                                           ^ src/mongo/db/pipeline/value_internal.h:78:7: note: 'class mongo::ValueStorage' declared here And, of course: cc1plus: all warnings being treated as errors 1. https://github.com/mongodb/mongo/commit/76b0fcea6960274d23a3bd1245a0e55e3cb08369 and https://github.com/mongodb/mongo/commit/f53ed89cef7c4356789114b2de1a5294e3d7a6f7 2. https://www.mongodb.com/licensing/server-side-public-license/faq 3. https://github.com/mongodb/mongo/commit/168c8d65556ab18b05e33b5f4006d1184c30f8f7 [Impact] Multiple FTBFS errors when building mongodb in cosmic. This prevents mongodb from being SRUed, and such an SRU need has appeared in bug #1821391. The FTBFS issues in cosmic are: - new gcc8 warnings (format-truncation and class-memaccess) - -Wparentheses warning - incompatibility with boost1.66+ There is an additional fix needed for boost1.67 itself, which is being handled in bug #1821762. [Test Case] Rebuild mongodb in cosmic. Without these fixes, the build will fail. [Regression Potential] All but the fix in boost1.67 mentioned above are due to new gcc8 checks, which suggests that mongodb was last built in cosmic before gcc8 became default. [Other Info] Mongo upstream nowadays has proper fixes for the format-truncation and class-memaccess warnings, but these were done[1] after the switch to the SSPL license[2] on October 16th, 2018. What I have done here is grab the fix we currently have in disco which was done by upstream[3] before that date. [Original Description] mongodb 3.6.3 is currently failing to build in cosmic. https://launchpadlibrarian.net/416133571/buildlog_ubuntu-cosmic-amd64.mongodb_1%3A3.6.3-0ubuntu1.18.10.1_BUILDING.txt.gz They all seem to be about Werror=class-memaccess. Example: src/mongo/db/pipeline/value_internal.h:194:42: error: 'void* memmove(void*, const void*, size_t)' writing to an object of type 'class mongo::ValueStorage' with no trivial copy-assignment; use copy-assignment or copy-initialization instead [-Werror=class-memaccess]          memmove(this, &rhs, sizeof(*this));                                           ^ src/mongo/db/pipeline/value_internal.h:78:7: note: 'class mongo::ValueStorage' declared here And, of course: cc1plus: all warnings being treated as errors 1. https://github.com/mongodb/mongo/commit/76b0fcea6960274d23a3bd1245a0e55e3cb08369 and https://github.com/mongodb/mongo/commit/f53ed89cef7c4356789114b2de1a5294e3d7a6f7 2. https://www.mongodb.com/licensing/server-side-public-license/faq 3. https://github.com/mongodb/mongo/commit/168c8d65556ab18b05e33b5f4006d1184c30f8f7
2019-03-29 10:27:21 Timo Aaltonen mongodb (Ubuntu Cosmic): status In Progress Fix Committed
2019-03-29 10:27:22 Timo Aaltonen bug added subscriber Ubuntu Stable Release Updates Team
2019-03-29 10:27:24 Timo Aaltonen bug added subscriber SRU Verification
2019-03-29 10:27:27 Timo Aaltonen tags verification-needed verification-needed-cosmic
2019-03-29 18:51:06 Andreas Hasenack tags verification-needed verification-needed-cosmic verification-done-cosmic verification-needed
2019-04-09 18:38:06 Launchpad Janitor mongodb (Ubuntu Cosmic): status Fix Committed Fix Released
2019-04-09 18:38:17 Brian Murray removed subscriber Ubuntu Stable Release Updates Team
2019-09-12 05:28:39 Chen-Han Hsiao (Stanley) bug added subscriber Chen-Han Hsiao (Stanley)