Bug: https://github.com/azerupi/mdBook/issues/271
Comment:
Use https://github.com/infinity0/mdBook/tree/debian to help you rebase the
patch on top of a newer version.
.
Make sure the paths here match the ones in debian/rust-doc.links
Comment: Use https://github.com/infinity0/mdBook/tree/debian to help you rebase the patch on top of a newer version. . Make sure the paths here match the ones in debian/rust-doc.links
Gbp-Pq: Name d-no-web-dependencies-in-doc.patch
Ximin Luo [Sat, 18 May 2019 19:18:25 +0000 (20:18 +0100)]
Don't download SHA256 if it's already available locally
Forwarded: not-needed
In Debian we provide the stage0 tarballs as a separate component so that the
buildds don't need to access the network during the build.
Forwarded: not-needed
Gbp-Pq: Name d-dont-download-stage0.patch
Angus Lees [Sat, 18 May 2019 19:18:25 +0000 (20:18 +0100)]
Set DT_SONAME when building dylibs
Forwarded: no
In Rust, library filenames include a version-specific hash to help
the run-time linker find the correct version. Unlike in C/C++, the
compiler looks for all libraries matching a glob that ignores the
hash and reads embedded metadata to work out versions, etc.
The upshot is that there is no need for the usual "libfoo.so ->
libfoo-1.2.3.so" symlink common with C/C++ when building with Rust,
and no need to communicate an alternate filename to use at run-time
vs compile time. If linking to a Rust dylib from C/C++ however, a
"libfoo.so -> libfoo-$hash.so" symlink may well be useful and in
this case DT_SONAME=libfoo-$hash.so would be required. More
mundanely, various tools (eg: dpkg-shlibdeps) complain if they don't
find DT_SONAME on shared libraries in public directories.
This patch passes -Wl,-soname=$outfile when building dylibs (and
using a GNU linker).
Josh Stone [Tue, 15 Jan 2019 23:14:17 +0000 (15:14 -0800)]
[PATCH] [rust-gdb] relax the GDB version regex
The pretty-printer script is checking `gdb.VERSION` to see if it's at
least 8.1 for some features. With `re.match`, it will only find the
version at the beginning of that string, but in Fedora the string is
something like "Fedora 8.2-5.fc29". Using `re.search` instead will find
the first location that matches anywhere, so it will find my 8.2.
Gbp-Pq: Name u-0001-rust-gdb-relax-the-GDB-version-regex.patch