Mike Hommey [Sun, 18 Aug 2019 11:19:35 +0000 (20:19 +0900)]
Bug 1531309 - Don't use __PRETTY_FUNCTION__ or __FUNCTION__ as format strings. r?sylvestre
__PRETTY_FUNCTION__ and __FUNCTION__ are not guaranteed to be a string
literal, and only string literals should be used as format strings. GCC
9 complains about this with -Werror=format-security.
Gbp-Pq: Topic fixes
Gbp-Pq: Name Bug-1531309-Don-t-use-__PRETTY_FUNCTION__-or-__FUNCTION__.patch
Reduce memory usage while linking on arm{el,hf} platforms
The build even on armhf is failing while linking mostly due exhausted
memory usage. Reduce the memory usage on arm{el,hf} platform by telling
the linker to not hold used memory.
The build is requiring a installed SQlite3 version of >= 3.28.0 which is
quite a recent upstream version.
Typically Thunderbird isn't using the most recent functions from SQlite
and we can safely downgrade the build requirement for SQlite.
Downgrading the version the version which is available on unstable.
Gbp-Pq: Topic debian-hacks
Gbp-Pq: Name Downgrade-SQlite-version-to-3.27.2.patch
Upstream doesn't really care about big endian platforms and so also don't
care about a needed file icudt??b.dat on big endian platforms. Changing
the m4 macro for ICU so the needed file will be depended on the build
platform exported and let later the configure run automatically use the
correct name for the ICU *.dat file so we not only depend on the
prebuild *.dat file for little endian.
The `case foo in ...` loop could be obviously more compressed with only
one case entry for all architectures which are all big endian.
---%<---
case $host in
dnl big endian architectures
hppa-*|m68k-*|...)
--->%---
For more readability the more exclusive extra list of all possible
architectures with big endianness in Debian was choosen.
Gbp-Pq: Topic debian-hacks
Gbp-Pq: Name use-icudt-b-l-.dat-depending-on-architecture.patch
Origin: not yet exist
Bug-Debian: https://bugs.debian.org/859271
Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1325771
Applied-Upstream: TBD
All patches have been reviewed by positively by upstream with the
exception of the alignment fixes where upstream wants to use a
C++11 solution instead of the other suggestions I made. This patch
currently uses __attribute__((aligned(4))) to ensure the alignment
is at least 4 bytes. This method is safe and works on gcc and clang
and unlike the suggested alignas() from C++11 does not break on
architectures which require stricter alignment (e.g. alignas(4)
would break on x86_64 while __attribute__((aligned(4))) does not
as it still allows for 8 bytes alignment.
On the Hurd platform the build failed in
js/src/jit/AsmJSSignalHandlers.cpp:131 because of unsupported
mode for reading / writing thead state with following message.
# error "Don't know how to read/write to the thread state via the mcontext_t."
The original patch comes from Richard Brown <rbraun@sceen.net>
https://lists.alioth.debian.org/pipermail/pkg-mozilla-maintainers/2014-March/015565.html
After release of Thunderbird 44 there are additional changes made as the
various configuration files where split into more files.
Gbp-Pq: Topic porting-kfreebsd-hurd
Gbp-Pq: Name FTBFS-hurd-fixing-unsupported-platform-Hurd.patch
Christoph Goehre [Wed, 31 Oct 2012 17:27:07 +0000 (13:27 -0400)]
ipc/chromium: fix #if define() for kFreeBSD and Hurd
The kFreeBSD and Hurd platforms need some other macros to include
the correct needed headers.
Depended on this some minor changes to call the correct functions
also needed. Also the list of the cpp source file for the chromium
things needs to expanded.
The changes is an adoption of the previous dropped patch 'Fix
ipc/chromium on kFreeBSD and Hurd' from the version 17.
Gbp-Pq: Topic porting-kfreebsd-hurd
Gbp-Pq: Name ipc-chromium-fix-if-define-for-kFreeBSD-and-Hurd.patch
* [093b080] New upstream version 68.11.0
Fixed CVE issues in upstream version 68.11.0 (MFSA 2020-35):
CVE-2020-15652: Potential leak of redirect targets when loading scripts
in a worker
CVE-2020-6514: WebRTC data channel leaks internal address to peer
CVE-2020-6463: Use-after-free in ANGLE gl::Texture::onUnbindAsSamplerTexture
CVE-2020-15659: Memory safety bugs fixed in Thunderbird 68.11
Mike Hommey [Sun, 18 Aug 2019 11:19:35 +0000 (20:19 +0900)]
Bug 1531309 - Don't use __PRETTY_FUNCTION__ or __FUNCTION__ as format strings. r?sylvestre
__PRETTY_FUNCTION__ and __FUNCTION__ are not guaranteed to be a string
literal, and only string literals should be used as format strings. GCC
9 complains about this with -Werror=format-security.
Gbp-Pq: Topic fixes
Gbp-Pq: Name Bug-1531309-Don-t-use-__PRETTY_FUNCTION__-or-__FUNCTION__.patch
Reduce memory usage while linking on arm{el,hf} platforms
The build even on armhf is failing while linking mostly due exhausted
memory usage. Reduce the memory usage on arm{el,hf} platform by telling
the linker to not hold used memory.
The build is requiring a installed SQlite3 version of >= 3.28.0 which is
quite a recent upstream version.
Typically Thunderbird isn't using the most recent functions from SQlite
and we can safely downgrade the build requirement for SQlite.
Downgrading the version the version which is available on unstable.
Gbp-Pq: Topic debian-hacks
Gbp-Pq: Name Downgrade-SQlite-version-to-3.27.2.patch
Upstream doesn't really care about big endian platforms and so also don't
care about a needed file icudt??b.dat on big endian platforms. Changing
the m4 macro for ICU so the needed file will be depended on the build
platform exported and let later the configure run automatically use the
correct name for the ICU *.dat file so we not only depend on the
prebuild *.dat file for little endian.
The `case foo in ...` loop could be obviously more compressed with only
one case entry for all architectures which are all big endian.
---%<---
case $host in
dnl big endian architectures
hppa-*|m68k-*|...)
--->%---
For more readability the more exclusive extra list of all possible
architectures with big endianness in Debian was choosen.
Gbp-Pq: Topic debian-hacks
Gbp-Pq: Name use-icudt-b-l-.dat-depending-on-architecture.patch
Origin: not yet exist
Bug-Debian: https://bugs.debian.org/859271
Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1325771
Applied-Upstream: TBD
All patches have been reviewed by positively by upstream with the
exception of the alignment fixes where upstream wants to use a
C++11 solution instead of the other suggestions I made. This patch
currently uses __attribute__((aligned(4))) to ensure the alignment
is at least 4 bytes. This method is safe and works on gcc and clang
and unlike the suggested alignas() from C++11 does not break on
architectures which require stricter alignment (e.g. alignas(4)
would break on x86_64 while __attribute__((aligned(4))) does not
as it still allows for 8 bytes alignment.
On the Hurd platform the build failed in
js/src/jit/AsmJSSignalHandlers.cpp:131 because of unsupported
mode for reading / writing thead state with following message.
# error "Don't know how to read/write to the thread state via the mcontext_t."
The original patch comes from Richard Brown <rbraun@sceen.net>
https://lists.alioth.debian.org/pipermail/pkg-mozilla-maintainers/2014-March/015565.html
After release of Thunderbird 44 there are additional changes made as the
various configuration files where split into more files.
Gbp-Pq: Topic porting-kfreebsd-hurd
Gbp-Pq: Name FTBFS-hurd-fixing-unsupported-platform-Hurd.patch
Christoph Goehre [Wed, 31 Oct 2012 17:27:07 +0000 (13:27 -0400)]
ipc/chromium: fix #if define() for kFreeBSD and Hurd
The kFreeBSD and Hurd platforms need some other macros to include
the correct needed headers.
Depended on this some minor changes to call the correct functions
also needed. Also the list of the cpp source file for the chromium
things needs to expanded.
The changes is an adoption of the previous dropped patch 'Fix
ipc/chromium on kFreeBSD and Hurd' from the version 17.
Gbp-Pq: Topic porting-kfreebsd-hurd
Gbp-Pq: Name ipc-chromium-fix-if-define-for-kFreeBSD-and-Hurd.patch
* [7537684] New upstream version 68.10.0
Fixed CVE issues in upstream version 68.10.0 (MFSA 2020-26):
CVE-2020-12417: Memory corruption due to missing sign-extension for
ValueTags on ARM64
CVE-2020-12418: Information disclosure due to manipulated URL object
CVE-2020-12419: Use-after-free in nsGlobalWindowInner
CVE-2020-12420: Use-After-Free when trying to connect to a STUN server
MFSA-2020-0001: Automatic account setup leaks Microsoft Exchange login
credentials
CVE-2020-12421: Add-On updates did not respect the same certificate trust
rules as software updates
Mike Hommey [Sun, 18 Aug 2019 11:19:35 +0000 (20:19 +0900)]
Bug 1531309 - Don't use __PRETTY_FUNCTION__ or __FUNCTION__ as format strings. r?sylvestre
__PRETTY_FUNCTION__ and __FUNCTION__ are not guaranteed to be a string
literal, and only string literals should be used as format strings. GCC
9 complains about this with -Werror=format-security.
Gbp-Pq: Topic fixes
Gbp-Pq: Name Bug-1531309-Don-t-use-__PRETTY_FUNCTION__-or-__FUNCTION__.patch
Reduce memory usage while linking on arm{el,hf} platforms
The build even on armhf is failing while linking mostly due exhausted
memory usage. Reduce the memory usage on arm{el,hf} platform by telling
the linker to not hold used memory.
projects / thunderbird.git / log