Debian Patches

Status for thrift/0.13.0-6

Patch Description Author Forwarded Bugs Origin Last update
node_is_nodejs.patch node is called nodejs in Debian Use the proper binary name. Laszlo Boszormenyi (GCS) <gcs@debian.org> no 2019-10-23
no_bundler_use.patch do not use bundler as per Ruby policy . Laszlo Boszormenyi (GCS) <gcs@debian.org> no debian 2019-10-23
golang_dependency_installed.patch golang dependencies already installed as build dependency Laszlo Boszormenyi (GCS) <gcs@debian.org> no 2019-12-01
broken_boost_1.62.patch <short summary of the patch> Laszlo Boszormenyi (GCS) <gcs@debian.org> no 2019-01-09
disable_TLSv1_0_and_TLSv1_1.patch Disable TLS v1.0 and TLS v1.1 connection tests TLS v1.0 and TLS v1.1 protocols are disabled as of OpenSSL 1.1.0f-4, see:
https://packages.qa.debian.org/o/openssl/news/20170806T233554Z.html
Laszlo Boszormenyi (GCS) <gcs@debian.org> no debian 2017-09-10
no_shmem.patch don't test servers that need shmem As buildd's don't have shmem enabled / mounted, tests would fail. Laszlo Boszormenyi (GCS) <gcs@debian.org> no 2017-09-11
disable_failing_tests.patch disable failing tests . Laszlo Boszormenyi (GCS) <gcs@debian.org> no 2019-10-05
no_composer_install.patch <short summary of the patch> TODO: Put a short summary on the line above and replace this paragraph
with a longer explanation of this change. Complete the meta-information
with other relevant fields (see below for details). To make it easier, the
information below has been extracted from the changelog. Adjust it or drop
it.
.
thrift (0.12.0-1) experimental; urgency=medium
.
* New major upstream release.
Laszlo Boszormenyi (GCS) <gcs@debian.org> no
disable_php_testing.patch PHP tests are not phpunit 8 compatible Disable those for now. Laszlo Boszormenyi (GCS) <gcs@debian.org> no 2019-09-22
no_go_race.patch run simple Go test only Race testing is available on amd64, ppc64le and arm64 only. Laszlo Boszormenyi (GCS) <gcs@debian.org> no 2019-10-05
no_gradlew.patch don't use gradlew in any way Not enabled for compilation, but clean would like to use it anyway. Laszlo Boszormenyi (GCS) <gcs@debian.org> no 2019-10-23
add_missing_test_files.patch put back files used for testing Needs for testing and while present up to 0.12.0 and in Git, missed from
the source of 0.13.0 release.
Laszlo Boszormenyi (GCS) <gcs@debian.org> no 2019-10-23
missing_go_test.patch don't try missing NewMockThriftTest test Upstream doesn't ship NewMockThriftTest hence don't try to use it. Laszlo Boszormenyi (GCS) <gcs@debian.org> no 2019-11-30
link_tests_atomic.patch fix tests FTBFS with atomic link On armel and at least mipsel needs atomic to link with. Laszlo Boszormenyi (GCS) <gcs@debian.org> no 2019-12-08
Fix_wrong_int_to_string_conversions.patch [PATCH] THRIFT-5270: Fix wrong int to string conversions

Starting from go 1.15, go test starts to complain about wrongly used int
to string conversions:

./field.go:58:83: conversion from int to string yields a string of one rune, not a string of digits (did you mean fmt.Sprint(x)?)
./numeric.go:72:12: conversion from int64 to string yields a string of one rune, not a string of digits (did you mean fmt.Sprint(x)?)
./json_protocol_test.go:612:92: conversion from int to string yields a string of one rune, not a string of digits (did you mean fmt.Sprint(x)?)
./simple_json_protocol_test.go:685:96: conversion from int to string yields a string of one rune, not a string of digits (did you mean fmt.Sprint(x)?)

json_protocol_test and simple_json_protocol_test usages are actually
already in format arg so just remove the conversion is good enough.
field is no longer used anywhere so just removed it (there's one line of
commented out code in compact_protocol so remove that line as well). The
one in numeric.go is actually a bug. We didn't set sValue correctly in
NewNumericFromI64 and NewNumericFromI32 functions.
Yuxuan 'fishy' Wang <yuxuan.wang@reddit.com> no 2020-08-28
THRIFT-5322.patch [PATCH] THRIFT-5322: Guard against large string/binary lengths in Go

In TBinaryProtocol.ReadString, TBinaryProtocol.ReadBinary,
TCompactProtocol.ReadString, and TCompactProtocol.ReadBinary, use
safeReadBytes to prevent from large allocation on malformed sizes.

$ go test -bench=SafeReadBytes -benchmem
BenchmarkSafeReadBytes/normal-12 625057 1789 ns/op 2176 B/op 5 allocs/op
BenchmarkSafeReadBytes/max-askedSize-12 545271 2236 ns/op 14464 B/op 7 allocs/op
PASS
Yuxuan 'fishy' Wang <yuxuan.wang@reddit.com> no 2020-12-10

All known versions for source package 'thrift'

Links