doc: fix some redirected links reported by "build-doc linkcheck"

Signed-off-by: Kefu Chai <kchai@redhat.com>
(cherry picked from commit 776329abe17987bcc021dac2b444fc7ab24c1b28)

diff --git a/doc/dev/blkin.rst b/doc/dev/blkin.rst
index 8e0320fe15f34a8869818e6881f056e1ab9d06b7..12f79cb227ebb69d0bfd2bb5491e175a5dfa92c2 100644 (file)
--- a/doc/dev/blkin.rst
+++ b/doc/dev/blkin.rst
@@ -16,7 +16,7 @@ in realtime. The LTTng traces can then be visualized with Twitter's
 Zipkin_.
 
 .. _Dapper: http://static.googleusercontent.com/media/research.google.com/el//pubs/archive/36356.pdf
-.. _Zipkin: http://zipkin.io/
+.. _Zipkin: https://zipkin.io/
 
 
 Installing Blkin

diff --git a/doc/dev/documenting.rst b/doc/dev/documenting.rst
index 63e1f191f7bb758c3aa59030c8ca9a005c4430aa..5ed6f7fc691f514b66a0283b7c83cbef1f62ed08 100644 (file)
--- a/doc/dev/documenting.rst
+++ b/doc/dev/documenting.rst
@@ -106,8 +106,8 @@ declarative language for drawing things, and includes:
 - `network diagrams`_: hosts, LANs, IP addresses etc (with `Cisco
   icons`_ if wanted)
 
-.. _Blockdiag: http://blockdiag.com/
-.. _`Cisco icons`: http://pypi.python.org/pypi/blockdiagcontrib-cisco/
+.. _Blockdiag: http://blockdiag.com/en/
+.. _`Cisco icons`: https://pypi.org/project/blockdiagcontrib-cisco/
 .. _`block diagrams`: http://blockdiag.com/en/blockdiag/
 .. _`sequence diagrams`: http://blockdiag.com/en/seqdiag/index.html
 .. _`activity diagrams`: http://blockdiag.com/en/actdiag/index.html
@@ -118,7 +118,7 @@ Inkscape
 --------
 
 You can use Inkscape to generate scalable vector graphics.
-http://inkscape.org for restructedText documents.
+https://inkscape.org/en/ for restructedText documents.
 
 If you generate diagrams with Inkscape, you should
 commit both the Scalable Vector Graphics (SVG) file and export a

diff --git a/doc/dev/generatedocs.rst b/doc/dev/generatedocs.rst
index 6badef0fb6a3eef2b9591b8c84e526e523928809..37c5697bd9cb816844556322556fd01b738562f3 100644 (file)
--- a/doc/dev/generatedocs.rst
+++ b/doc/dev/generatedocs.rst
@@ -2,7 +2,7 @@ Building Ceph Documentation
 ===========================
 
 Ceph utilizes Python's Sphinx documentation tool. For details on
-the Sphinx documentation tool, refer to `The Sphinx Documentation Tool <http://sphinx.pocoo.org/>`_.
+the Sphinx documentation tool, refer to `The Sphinx Documentation Tool <https://www.sphinx-doc.org/en/master/>`_.
 
 To build the Ceph documentation set, you must:
 

diff --git a/doc/dev/index.rst b/doc/dev/index.rst
index baf4e147f30b84f9f506b5ccfbb774aab9f2726c..616ba0d7ec6fe059d4794d42df21d1d922014796 100644 (file)
--- a/doc/dev/index.rst
+++ b/doc/dev/index.rst
@@ -23,8 +23,8 @@ object store and file system designed to provide excellent performance,
 reliability and scalability). If not, please refer to the `project website`_
 and especially the `publications list`_.
 
-.. _`project website`: http://ceph.com
-.. _`publications list`: https://ceph.com/resources/publications/
+.. _`project website`: https://ceph.com
+.. _`publications list`: https://ceph.com/publications/
 
 Since this document is to be consumed by developers, who are assumed to
 have Internet access, topics covered elsewhere, either within the Ceph
@@ -93,7 +93,7 @@ the `Ceph "organization"`_.
 To make a meaningful contribution to the project as a developer, a working
 knowledge of git_ is essential.
 
-.. _git: https://git-scm.com/documentation
+.. _git: https://git-scm.com/doc
 
 Although the `Ceph "organization"`_ includes several software repositories,
 this document covers only one: https://github.com/ceph/ceph.