Skip to content
Commits on Source (5)
mapproxy (1.11.0-2) UNRELEASED; urgency=medium
mapproxy (1.11.0-2) unstable; urgency=medium
* Update Vcs-* URLs for Salsa.
* Bump Standards-Version to 4.1.5, no changes.
* Drop ancient X-Python-Version field.
* Strip trailing whitespace from control & rules files.
* Add patch to rename async.py to async_.py for Python 3.7 compatibility.
* Add lintian overrides for embedded JS & fonts.
* Remove documentation outside usr/share/doc.
* Fix 'every time' typo.
-- Bas Couwenberg <sebastic@debian.org> Sat, 31 Mar 2018 12:25:13 +0200
-- Bas Couwenberg <sebastic@debian.org> Fri, 20 Jul 2018 19:11:25 +0200
mapproxy (1.11.0-1) unstable; urgency=medium
......
# libjs-twitter-bootstrap is not compatible
embedded-javascript-library usr/share/doc/mapproxy/html/_static/bootstrap-*/js/bootstrap.js please use libjs-twitter-bootstrap
font-in-non-font-package usr/share/doc/mapproxy/html/_static/boot*/fonts/*
font-outside-font-dir usr/share/doc/mapproxy/html/_static/boots*/fonts/*
# libjs-jquery is not compatible
embedded-javascript-library usr/share/doc/mapproxy/html/_static/js/jquery* please use libjs-jquery
This diff is collapsed.
offline-tests.patch
disable-tag_date.patch
skip-tests-for-missing-files.patch
python3.7-async.patch
spelling-errors.patch
Description: Fix spelling errors
* everytime -> every time
Author: Bas Couwenberg <sebastic@debian.org>
Forwarded: https://github.com/mapproxy/mapproxy/pull/373
--- a/doc/mapproxy_util_autoconfig.rst
+++ b/doc/mapproxy_util_autoconfig.rst
@@ -78,7 +78,7 @@ Write MapProxy configuration with caches
Overwrites
==========
-It's likely that you need to tweak the created configuration – e.g. to define another coverage, disable featureinfo, etc. You can do this by editing the output file of course, or you can modify the output by defining all changes to an overwrite file. Overwrite files are applied everytime you call ``mapproxy-util autoconfig``.
+It's likely that you need to tweak the created configuration – e.g. to define another coverage, disable featureinfo, etc. You can do this by editing the output file of course, or you can modify the output by defining all changes to an overwrite file. Overwrite files are applied every time you call ``mapproxy-util autoconfig``.
Overwrites are YAML files that will be merged with the created configuration file.
--- a/doc/seed.rst
+++ b/doc/seed.rst
@@ -411,9 +411,9 @@ Example: Background seeding
The ``--duration`` option allows you run MapProxy seeding for a limited time. In combination with the ``--continue`` option, you can resume the seeding process at a later time.
You can use this to call ``mapproxy-seed`` with ``cron`` to seed in the off-hours.
-However, this will restart the seeding process from the begining everytime the is seeding completed.
+However, this will restart the seeding process from the begining every time the is seeding completed.
You can prevent this with the ``--reeseed-interval`` and ``--reseed-file`` option.
-The follwing example starts seeding for six hours. It will seed for another six hours, everytime you call this command again. Once all seed and cleanup tasks were proccessed the command will exit immediately everytime you call it within 14 days after the first call. After 14 days, the modification time of the ``reseed.time`` file will be updated and the re-seeding process starts again.
+The follwing example starts seeding for six hours. It will seed for another six hours, every time you call this command again. Once all seed and cleanup tasks were proccessed the command will exit immediately every time you call it within 14 days after the first call. After 14 days, the modification time of the ``reseed.time`` file will be updated and the re-seeding process starts again.
::
......@@ -113,3 +113,5 @@ override_dh_auto_install:
override_dh_install:
dh_install --list-missing
$(RM) debian/*/usr/share/python*-mapproxy/test/schemas/*/*/ReadMe.txt