The patch "force-ssl-cert-verification.patch" was mistakenly included
in the last Midori release; this cased a regression because the user
cannot access a website that has a self-signed SSL/TLS certificate
anymore. This change removes the patch and allows the user to trust
self-signed certificates again.
Closes: #799337
The old manpage was too simple and did not cover many of the options
supported by Midori on the command line. Fixed that by rewriting it
almost completely, including many missing options, updating dates and
author, and improving the formatting.
Due to the way libraries (i.e., plugins) are built by Midori (without
a proper SONAME), it is necessary (or at least recommended) to provide
a shlibs file that contains trustworthy information about the
libraries being installed on the system.
Unfortunately, it is also necessary to provide a lintian-overrides
file in order to silence some lintian warnings (mostly about the
shlibs mentioned above). We'll have to work with upstream in order to
solve this problem.
Another lintian error that needed to be silenced was related to the
data/midori.swf file, present at the original tarball. This file is
used just for testing (i.e., it is not installed in the system), and
is actually generated using the png2swf utility (from the swftools
package), which means it can be verified.
- Update debian/rules, removing old stuff (from waf) and adding new,
simpler rules for the cmake-based build.
- Update debian/control, listing the new package maintainer and
reviewed dependencies.
- Delete debian/waf-unpack file.
- Rename debian/config/{Debian,Ubuntu}.h files to
debian/config/{Debian,Ubuntu}.conf.
With this change, it is now unnecessary to create a DFSG-modified
version of the package, because Waf is not used as the build system
anymore (for more details, see Bug 645191).
It is possible to build the package now, but it still has some lintian
warnings that will be fixed in the following changes.
Closes: #663185Closes: #758103Closes: #787878