[git] gnupg-doc - branch, master, updated. c688116d697686cdcdd5cdee4f10d10965ad7472
by Werner Koch
cvs at cvs.gnupg.org
Tue Apr 14 15:25:29 CEST 2015
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "The GnuPG website and other docs".
The branch, master has been updated
via c688116d697686cdcdd5cdee4f10d10965ad7472 (commit)
via c0103b977e2a2e040cb05972fc2069d03fd4af0f (commit)
from 4f0218d1ed51e25c8e8cef193a231ba45fda03a4 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit c688116d697686cdcdd5cdee4f10d10965ad7472
Author: Werner Koch <wk at gnupg.org>
Date: Tue Apr 14 15:23:49 2015 +0200
web: Fix last release news entry.
diff --git a/web/index.org b/web/index.org
index 64ed27a..98fda69 100644
--- a/web/index.org
+++ b/web/index.org
@@ -65,7 +65,7 @@ The latest release news:\\
# point or paste the [[news.en.rss][RSS file]] into your aggregator.
-** GnuPG 2.1.4 released (2015-04-11)
+** GnuPG 2.1.3 released (2015-04-11)
This is another release of the /modern/ branch of GnuPG. It fixes
a lot of bugs. Read the full [[https://lists.gnupg.org/pipermail/gnupg-announce/2015q2/000365.html][anouncement mail]].
diff --git a/web/swdb.mac b/web/swdb.mac
index 917f1b9..acf6e8e 100644
--- a/web/swdb.mac
+++ b/web/swdb.mac
@@ -22,9 +22,9 @@
#+macro: gnupg21_size 4762k
#+macro: gnupg21_sha1 091e69ec1ce3f0032e6b135e4da561e8d46d20a7
#
-#+macro: gnupg21_w32_ver 2.1.1_20141216
-#+macro: gnupg21_w32_size 6364k
-#+macro: gnupg21_w32_sha1 fb541b8685b78541c9b2fadb026787f535863b4a
+#+macro: gnupg21_w32_ver 2.1.3_20150413
+#+macro: gnupg21_w32_size 2539k
+#+macro: gnupg21_w32_sha1 d5630904b3d68eddc2730a00bfc67d52658cbe7e
#
@@ -61,10 +61,10 @@
#
# GPGME
#
-#+macro: gpgme_ver 1.5.3
+#+macro: gpgme_ver 1.5.4
#+macro: gpgme_branch master
-#+macro: gpgme_size 946k
-#+macro: gpgme_sha1 8dd7711a4de117994fe2d45879ef8a9900d50f6a
+#+macro: gpgme_size 953k
+#+macro: gpgme_sha1 8cf1bcce8603bd7d006065f08059cf85462828c4
#
commit c0103b977e2a2e040cb05972fc2069d03fd4af0f
Author: Werner Koch <wk at gnupg.org>
Date: Tue Apr 14 15:23:03 2015 +0200
bugs.gnupg.org: Add used HTML files
diff --git a/misc/bugs.gnupg.org/index.html b/misc/bugs.gnupg.org/index.html
new file mode 100644
index 0000000..4b45f1a
--- /dev/null
+++ b/misc/bugs.gnupg.org/index.html
@@ -0,0 +1,153 @@
+<!doctype html public "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head><title>g10 Code's bug tracker</title>
+<link rev="made" href="mailto:webmaster at g10code.de">
+</head>
+<body bgcolor="#ffffff" text="#000000" link="#1f00ff" alink="#ff0000" vlink="#9900dd">
+<div align="left">
+<img src="pagehead.png"
+ alt="[g10 Code Logo]" width="1065" height="100">
+</div>
+
+
+<h1><a name="intro">Bug tracker for GnuPG and related projects</a></h1>
+
+<p>
+
+
+<ul>
+ <li>Goto to the list of <a
+href="https://bugs.gnupg.org/gnupg/issue?%40sort=id&%40sortdir=on&%40group=category&%40columns=id%2Cactivity%2Ctitle%2Ccreator%2Cassignedto%2Cstatus&%40filter=status&status=-1%2C1%2C2%2C3%2C4%2C5%2C6%2C7&%40pagesize=50&%40startwith=0"
+>GnuPG related bugs</a>.
+</ul>
+
+
+<h2>Becoming a registered user</h2>
+<p>
+To enter a bug into our bug tracker you need to be a registered user.
+A registered user will be assigned a <em>provisional user role</em>
+which allows to enter new bugs and to edit these bugs. The <em>user
+role</em> will be granted by an administrator on demand. Just add
+remark to your bug report that you wish to work more with the bug
+tracker. We have these strict rules to avoid spam and keep trolls
+away from the tracker.
+<p>
+Note that some actions (e.g. closing a bug) are even restricted from
+regular users. A developer account is required for these actions.
+The rationale is that only a developer will be able to fix things and
+thus decides whether a bug is to be closed. A bug may be re-opened at
+any time.
+
+
+<h2>How to add a new bug</h2>
+<p>
+Please note that this bug tracker is a public resource and everything
+you enter there will be available for the whole networked world. It
+is similar to a public mailing list and there is no easy way to
+retract any information.
+<p>
+You should follow these steps to enter a new bug (issue):
+<p>
+<ul>
+ <li>Review the documentation and the mailing list archives to see
+ whether your problem has already been addressed. Often bugs are
+ mere configuration problems.
+ <p>
+ <li>Check that the bug has not yet been entered and that there is no
+ similar bug in the tracker. Use the search option for this. It
+ is best to also look through the already closed
+ (<em>resolved</em>) issue.
+ <p>
+
+ <li>Select the <em>Create New</em> menu entry. An empty page will be
+ presented.
+ <p>
+
+ <li>Come up with a meaningful short description of the bug and enter
+ this into the <em>title</em> field.
+ <p>
+
+ <li>Assign a priority for the bug. These priorities are
+ defined:
+ <p>
+ <dl>
+ <dt>bug<dd>Use this for a regular bug.
+ <dt>urgent<dd>Use this if you believe that the problem should
+ be fixed soon.
+ <dt>critical<dd>Use this if your problem is really severe and inhibits
+ you from working with the software. Do not use it if you can
+ find a workaround for the problem.
+ <dt>minor-bug<dd>Use this for a minor bug
+ <dt>feature<dd>Use this for a technical feature requests.
+ <dt>wish<dd>Use this for everything else, for example to
+ request better documentation or a new FAQ entry.
+ </dl>
+ <p>
+
+ <li>See whether you can assign category to the bug. There is a drop
+ down list with all available categories. A category is in
+ general the name of the application with the bug, but might also
+ be a library. If you can't figure out the category, keep it at
+ <em>- no selection -</em>. The <em>dirmngr</em> category is only
+ used for the old standalone package; since GnuPG 2.1 dirmngr
+ is part of GnuPG proper; thus use <em>gnupg</em> as category and
+ add <em>dirmngr</em> to the topic field.
+ <p>
+
+ <li>Now for the most important field: The description of the problem.
+ You enter this information into the <em>Change Note</em> field.
+ Please take care to use hard line breaks and format the report
+ as you would do by mail. No HTML please.
+ <p>
+ Make sure that you describe the bug as good as possible and try
+ to come up with a minimal recipe on how to replicate the bug. We
+ need to know <strong>the version of the software</strong> and if
+ you are using a non-released version the GIT commit id. The type
+ and version of your operating system is usually important, so
+ please tell us. In particular tell us if you are problem occurs
+ on a non Unix system, i.e. MS Windows.
+ <p>
+
+ <li>If you need to enter more information, you may upload any kind of
+ file. However, please do this only if you are sure that these
+ information are important and that they do not contain
+ confidential data. This file will be public and it won't be
+ possible to retract it anymore. Avoid screen shots unless you
+ are asked for them.
+ <p>
+ The problem with screen shots or, worse, screen casts is that we
+ would need to transcript them to text for evaluating the problem.
+ That takes away time we better spend solving the problem; it
+ is easy to help us by providing a transcription
+ <p>
+
+ <li>If you are sure that your bug is MS Windows specific, please
+ enter the string "w32" into the <em>Topics</em> field. You do
+ not need to do it if you select a Windows specific category (like
+ "gpgol").
+ <p>
+
+ <li>If you want to refer to an external bug description (for example
+ a similar entry in Debian's bug tracker), enter the URL into the
+ <em>ExtLink</em> field.
+ <p>
+
+ <li>If everything is as you want it, select the <em>Submit New
+ Entry</em> button. This entry as well as all future changes will
+ also be mailed to you.
+ <p>
+</ul>
+
+
+
+
+<hr>
+<div><font size="-1"> Contact information available at the <a
+href="http://www.g10code.com">g10 Code main pages</a>.
+<p>
+Copyright (C) 2006 g10 Code GmbH, Erkrath-Hochdahl.<br>
+Verbatim copying and distribution of this entire article is
+permitted in any medium, provided this notice is preserved.
+</font></div>
+</body>
+</html>
diff --git a/misc/bugs.gnupg.org/pagehead.png b/misc/bugs.gnupg.org/pagehead.png
new file mode 100644
index 0000000..ec9b4d3
Binary files /dev/null and b/misc/bugs.gnupg.org/pagehead.png differ
diff --git a/misc/bugs.gnupg.org/roundup-topics.html b/misc/bugs.gnupg.org/roundup-topics.html
new file mode 100644
index 0000000..edf8b4a
--- /dev/null
+++ b/misc/bugs.gnupg.org/roundup-topics.html
@@ -0,0 +1,106 @@
+<!doctype html public "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head><title>g10 Code's bug tracker - Topics</title>
+<link rev="made" href="mailto:webmaster at g10code.de">
+</head>
+<body bgcolor="#ffffff" text="#000000" link="#1f00ff" alink="#ff0000" vlink="#9900dd">
+<div align="left">
+<img src="pagehead.png"
+ alt="[g10 Code Logo]" width="1065" height="100">
+</div>
+
+
+<h1><a name="intro">Topics used in the GnuPG tracker</a></h1>
+
+<p>
+Roundup has a feature named "Topics" which allows to assign one or
+more keywords to a certain bug ("issue" in Roundup parlance). These
+keywords may for example be used in a search. As keywords are
+usually short, there meaning and suggested usage ist not always
+clear. This list shall help to make sensible use of the keywords.
+</p>
+
+<table cellpadding="5" cellspacing="1" border="1" >
+ <caption>Topics used in the GnuPG bug tracker</caption>
+ <thead>
+ <tr><th>Name</th><th>Description</th></tr>
+ </thead>
+
+ <tbody>
+ <tr><th colspan="2">Keywords describing the location</th></tr>
+ <tr><td>agent</td> <td>Related to the gpg-agent</td></tr>
+ <tr><td>keyserver</td> <td>Keyserver or keyserver protocol
+ related
+ </td></tr>
+ <tr><td>scd</td> <td>Related to the scd-daemon or general
+ smart card access problem
+ </td></tr>
+ <tr><td>pinentry</td> <td>Related to the Pinentry</td></tr>
+ <tr><td>ssh</td> <td>Related to gpg-agent's ssh-agent
+ implementation
+ </td></tr>
+ <tr><td>gpgtar</td> <td>Related to gpgtar</td></tr>
+ <tr><td>iobuf</td> <td>Related to gpg's iobuf mechanism</td></tr>
+ <tr><td>openpgp</td> <td>OpenPGP protocol</td></tr>
+ <tr><td>smime</td> <td>S/MIME (CMS, X.509) protocol</td></tr>
+ <tr><td>gpg4win</td> <td>Related to the Gpg4win installer</td></tr>
+ <tr><td>uiserver</td> <td>Related to the UI-Server (cf. gpg4win)</td></tr>
+ <tr><td>doc</td> <td>Related to documentation</td></tr>
+ <tr><td>gpg14</td> <td>Related to GnuPG 1.4.</td></tr>
+ <tr><td>gpg20</td> <td>Related to GnuPG 2.0.</td></tr>
+ <tr><td>gpg21</td> <td>Related to GnuPG 2.1.</td></tr>
+ <tr><td>i18n</td> <td>Related to internationalization</td></tr>
+ <tr><td>ipc</td> <td>Related to inter process communication</td></tr>
+ <tr><td>npth</td> <td>Related to nPth</td></tr>
+
+ </tbody>
+
+ <tbody>
+ <tr><th colspan="2">Keywords describing the environment</th></tr>
+ <tr><td>asm</td> <td>Problem with low-level assembler code
+ </td></tr>
+ <tr><td>cross</td> <td>Bug pertaining to cross-compiling</td></tr>
+ <tr><td>osx</td> <td>Mac OS/X specific problem</td></tr>
+ <tr><td>w32</td> <td>MS Windows specific problem</td></tr>
+ <tr><td>w64</td> <td>MS Windows 64 bit specific problem</td></tr>
+ </tbody>
+
+ <tbody>
+ <tr><th colspan="2">Keywords describing the action taken</th></tr>
+ <tr><td>backport</td> <td>This needs to be ported to older branches.
+ </td></tr>
+ <tr><td>forwardport</td> <td>This needs to be ported to newer branches.
+ </td></tr>
+ <tr><td>faq</td> <td>This should be made an entry into the
+ FAQ or is already answered there.
+ </td></tr>
+ <tr><td>patch</td> <td>Patch included</td></tr>
+ <tr><td>noinfo</td> <td>Not enough information given</td></tr>
+ <tr><td>notdup</td> <td>Problem duplicating the bug</td></tr>
+
+ <tr><td>dup</td> <td>A similar bug report already exists</td></tr>
+
+ <tr><td>nobug</td> <td>This is not a bug (maybe even a feature).
+ Note that there is also a category of
+ the same name.
+ </td></tr>
+ <tr><td>tooold</td> <td>The report is too old. Spending time
+ on it is not justified.
+ </td></tr>
+ <tr><td>wontfix</td> <td>The bug will not be fixed.</td></tr>
+ <tr><td>mistaken</td> <td>Empty report or unrelated to GnuPG.</td></tr>
+ <tr><td>endoflife</td> <td>Software version has reached EOL status.</td></tr>
+ </tbody>
+</table>
+
+
+<hr>
+<div><font size="-1"> Contact information available at the <a
+href="http://www.g10code.com">g10 Code main pages</a>.
+<p>
+Copyright (C) 2006 g10 Code GmbH, Erkrath-Hochdahl.<br>
+Verbatim copying and distribution of this entire article is
+permitted in any medium, provided this notice is preserved.
+</font></div>
+</body>
+</html>
diff --git a/misc/bugs.gnupg.org/upload b/misc/bugs.gnupg.org/upload
new file mode 100755
index 0000000..1927599
--- /dev/null
+++ b/misc/bugs.gnupg.org/upload
@@ -0,0 +1,16 @@
+#!/bin/sh
+
+set -e
+
+user=$USER
+host=kerckhoffs.g10code.com
+
+if [ "$(pwd | awk -F/ '{print $NF}')" != "bugs.gnupg.org" ]; then
+ echo "upload: not invoked from the bugs.gnupg.org directory" >&2;
+ exit 1
+fi
+
+rsync -vr --links --exclude '*~' --exclude upload \
+ . ${user}@${host}:/var/www/all/bugs.gnupg.org/htdocs/
+
+#eof
-----------------------------------------------------------------------
Summary of changes:
misc/bugs.gnupg.org/index.html | 153 ++++++++++++++++++++++++++++++++
misc/bugs.gnupg.org/pagehead.png | Bin 0 -> 2635 bytes
misc/bugs.gnupg.org/roundup-topics.html | 106 ++++++++++++++++++++++
misc/bugs.gnupg.org/upload | 16 ++++
web/index.org | 2 +-
web/swdb.mac | 12 +--
6 files changed, 282 insertions(+), 7 deletions(-)
create mode 100644 misc/bugs.gnupg.org/index.html
create mode 100644 misc/bugs.gnupg.org/pagehead.png
create mode 100644 misc/bugs.gnupg.org/roundup-topics.html
create mode 100755 misc/bugs.gnupg.org/upload
hooks/post-receive
--
The GnuPG website and other docs
http://git.gnupg.org
More information about the Gnupg-commits
mailing list