From 705da1eb23aef92c42d6d657b20a0984b104f72f Mon Sep 17 00:00:00 2001 From: Daniel Kahn Gillmor Date: Thu, 18 May 2017 15:05:57 -0400 Subject: [PATCH] docs: Point to https://dev.gnupg.org/ . Replace mentions of bugs.gnupg.org with https://dev.gnupg.org/. Since the project has transitioned to a better workflow for supporting contributions, we should ensure that our documentation points to the right place. Signed-off-by: Daniel Kahn Gillmor --- AUTHORS | 4 ++-- README | 2 +- configure.ac | 2 +- doc/announce-2.1.txt | 2 +- doc/faq.org | 31 +++++++++++++++---------------- doc/gpg.texi | 2 +- tests/fake-pinentries/README.txt | 2 +- 7 files changed, 22 insertions(+), 23 deletions(-) diff --git a/AUTHORS b/AUTHORS index ec4b742d3..fc2ee9bc1 100644 --- a/AUTHORS +++ b/AUTHORS @@ -1,8 +1,8 @@ Program: GnuPG Homepage: https://www.gnupg.org -Download: ftp://ftp.gnupg.org/gcrypt/gnupg/ +Download: https://gnupg.org/ftp/gcrypt/gnupg/ Repository: git://git.gnupg.org/gnupg.git -Bug reports: https://bugs.gnupg.org +Bug reports: https://dev.gnupg.org Security related bug reports: Maintainer: Werner Koch License: GPLv3+ diff --git a/README b/README index 8be43d70e..e0c5d7174 100644 --- a/README +++ b/README @@ -227,7 +227,7 @@ https://www.gnupg.org/documentation/mailing-lists.html for archives of the mailing lists. - Please direct bug reports to http://bugs.gnupg.org or post them + Please direct bug reports to http://dev.gnupg.org or post them direct to the mailing list . Please direct questions about GnuPG to the users mailing list or one diff --git a/configure.ac b/configure.ac index da341d0bd..5ab8a53b1 100644 --- a/configure.ac +++ b/configure.ac @@ -47,7 +47,7 @@ m4_define([mym4_version], m4_argn(4, mym4_verslist)) m4_define([mym4_revision], m4_argn(7, mym4_verslist)) m4_define([mym4_revision_dec], m4_argn(8, mym4_verslist)) m4_esyscmd([echo ]mym4_version[>VERSION]) -AC_INIT([mym4_package],[mym4_version], [https://bugs.gnupg.org]) +AC_INIT([mym4_package],[mym4_version], [https://dev.gnupg.org]) NEED_GPG_ERROR_VERSION=1.24 diff --git a/doc/announce-2.1.txt b/doc/announce-2.1.txt index eccd0e762..137f0b19a 100644 --- a/doc/announce-2.1.txt +++ b/doc/announce-2.1.txt @@ -236,7 +236,7 @@ Support Please consult the archive of the gnupg-users mailing list before reporting a bug . We suggest to send bug reports for a new release to this list in favor -of filing a bug at . For commercial support +of filing a bug at . For commercial support requests we keep a list of known service companies at: https://gnupg.org/service.html diff --git a/doc/faq.org b/doc/faq.org index f03850804..5619faa6d 100644 --- a/doc/faq.org +++ b/doc/faq.org @@ -6,9 +6,8 @@ #+LANGUAGE: en #+TITLE: GnuPG Frequently Asked Questions #+OPTIONS: H:3 num:nil toc:t \n:nil @:t ::t |:t ^:{} -:t f:t *:t TeX:t LaTeX:t skip:nil d:(HIDE) tags:not-in-toc -#+LINK: gnupgweb http://www.gnupg.org/ -#+LINK: roundup https://bugs.g10code.com/gnupg/issue -#+STYLE: +#+LINK: gnupgweb https://www.gnupg.org/ +#+STYLE: # FIXME: This FAQ needs a heavy cleanup. For now I only switched to # org-mode format for easier maintenance. @@ -29,9 +28,9 @@ update this FAQ in the next month. See the section "Changes" for recent updates :END: Welcome to the GnuPG FAQ. The latest HTML version is available at\\ - [[http://www.gnupg.org/faq/GnuPG-FAQ.html]]; \\ - a plain text Gversion at \\ - ftp://ftp.gnupg.org/gcrypt/gnupg/GnuPG-FAQ.txt. + [[https://www.gnupg.org/faq/GnuPG-FAQ.html]]; \\ + a plain text version at \\ + https://gnupg.org/ftp/gcrypt/gnupg/GnuPG-FAQ.txt . See the end of this file for the release date. @@ -89,7 +88,7 @@ update this FAQ in the next month. See the section "Changes" for recent updates communication and data storage. It can be used to encrypt data and to create digital signatures. It includes an advanced key management facility and is compliant with the proposed OpenPGP - Internet standard as described in [[http://www.rfc-editor.org/rfc/rfc4880.txt][RFC-4880]]. As such, it is aimed + Internet standard as described in [[https://www.rfc-editor.org/rfc/rfc4880.txt][RFC-4880]]. As such, it is aimed to be compatible with PGP from PGP Corp. and other OpenPGP tools ** Is GnuPG compatible with PGP? @@ -158,8 +157,8 @@ update this FAQ in the next month. See the section "Changes" for recent updates :CUSTOM_ID: where-do-i-get-gnupg :END: - You can download the GNU Privacy Guard from its primary FTP server - [[ftp://ftp.gnupg.org/gcrypt/gnupg/][ftp.gnupg.org]] or from one of its [[gnupgweb:download/mirrors.html][mirrors]]. + You can download the GNU Privacy Guard from its primary server + [[https://gnupg.org/ftp/gcrypt/gnupg/][ftp.gnupg.org]] or from one of its [[gnupgweb:download/mirrors.html][mirrors]]. The current stable version is FIXME. Please upgrade to this version as it includes additional features, functions and security @@ -1139,8 +1138,8 @@ update this FAQ in the next month. See the section "Changes" for recent updates lists? Did you have a look at the bug list (you'll find a link to the list of reported bugs on the documentation page). If you're not sure about it being a bug, you can send mail to the - gnupg-devel list. Otherwise, use the bug tracking system - [[http://bugs.gnupg.org][bugs.gnupg.org]]. + gnupg-devel list. Otherwise, use the bug tracking system at + [[https://dev.gnupg.org][dev.gnupg.org]]. ** Why doesn't GnuPG support X.509 certificates? :PROPERTIES: @@ -1177,7 +1176,7 @@ update this FAQ in the next month. See the section "Changes" for recent updates There is a small bug in 1.0.6 which didn't parse trust packets correctly. You may want to apply this patch if you can't upgrade: - [[http://www.gnupg.org/developer/gpg-woody-fix.txt]]. + [[https://www.gnupg.org/developer/gpg-woody-fix.txt]]. ** I upgraded to GnuPG version 1.0.7 and now it takes longer to load my keyrings. What can I do? :PROPERTIES: @@ -1203,7 +1202,7 @@ update this FAQ in the next month. See the section "Changes" for recent updates More information and a patch for a some pre-1.2.2 versions of GnuPG can be found at: - [[http://lists.gnupg.org/pipermail/gnupg-announce/2003q2/000268.html]]. + [[https://lists.gnupg.org/pipermail/gnupg-announce/2003q2/000268.html]]. ** I just compiled GnuPG from source on my GNU/Linux RPM-based system and it's not working. Why? :PROPERTIES: @@ -1480,7 +1479,7 @@ assignment to the FSF. Without such an assignment we may only accept trivial patches. As a rule of thumb the sum of all changed lines by one contributor may not exceed about 15 lines. Exceptions are typo corrections and translations. See -http://www.gnu.org/prep/maintain/html_node/Copyright-Papers.html for +https://www.gnu.org/prep/maintain/html_node/Copyright-Papers.html for details. ** U.S. export restrictions @@ -1504,8 +1503,8 @@ email changed, so I just sent "www.gnupg.org" and haven't bothered with the email since. #+end_quote -The rules: http://www.bis.doc.gov/encryption/pubavailencsourcecodenofify.html -The 2004 rule change: http://edocket.access.gpo.gov/2004/04-26992.htm +The rules: https://www.bis.doc.gov/encryption/pubavailencsourcecodenofify.html +The 2004 rule change: https://edocket.access.gpo.gov/2004/04-26992.htm * Acknowledgements diff --git a/doc/gpg.texi b/doc/gpg.texi index 1a0ea55ae..fbe636734 100644 --- a/doc/gpg.texi +++ b/doc/gpg.texi @@ -3777,7 +3777,7 @@ may be recoverable from it later. Before you report a bug you should first search the mailing list archives for similar problems and second check whether such a bug has -already been reported to our bug tracker at http://bugs.gnupg.org . +already been reported to our bug tracker at https://dev.gnupg.org . @c ******************************************* @c *************** ************** diff --git a/tests/fake-pinentries/README.txt b/tests/fake-pinentries/README.txt index 9272ae515..0654f56bc 100644 --- a/tests/fake-pinentries/README.txt +++ b/tests/fake-pinentries/README.txt @@ -35,4 +35,4 @@ Troubleshooting If you have any trouble with this technique, please drop a line to the GnuPG development mailing list or open a -report on the GnuPG bug tracker at https://bugs.gnupg.org/gnupg +report on the GnuPG bug tracker at https://dev.gnupg.org/gnupg