[SCM] pkg-kde.alioth.debian.org website branch, master, updated. 569442b59bfdf03499cb9ed64975ce80b3c4af12
Eshat Cakar
eshat-guest at alioth.debian.org
Mon Jun 6 11:13:34 UTC 2011
The following commit has been merged in the master branch:
commit 569442b59bfdf03499cb9ed64975ce80b3c4af12
Author: Eshat Cakar <info at eshat.de>
Date: Mon Jun 6 13:13:04 2011 +0200
Make most pages validated XHTML Code and add W3C icon to bottom
---
pages/bottom | 14 ++++++++----
pages/bugs | 2 +-
pages/experimental_linking | 12 +++++-----
pages/faq | 6 ++--
pages/faq4 | 2 +-
pages/gitguidelines | 50 ++++++++++++++++++++++----------------------
pages/index | 2 +-
pages/kde4 | 4 +-
pages/kdebuggraph | 2 +-
pages/kdeextras | 2 +-
pages/qtkde | 2 +-
pages/symbolfiles | 2 -
pages/todo | 1 +
pages/top | 4 +-
pages/usertags | 4 +-
pages/web-maintenance | 2 +-
16 files changed, 57 insertions(+), 54 deletions(-)
diff --git a/pages/bottom b/pages/bottom
index a21978f..c7ce2c7 100644
--- a/pages/bottom
+++ b/pages/bottom
@@ -1,16 +1,14 @@
</div>
<div id="sidebar">
- <h2><a href="index.html">Home/News</h2>
+ <h2><a href="index.html">Home/News</a></h2>
<br />
- <h2><a href="kde4.html"><img src="../images/kde4_32.png" style="float:right; margin:-8px 0 0 0;" alt="KDE4 Logo" />KDE SC 4.6</a> in </br>testing/unstable</h2>
- <ul>
- </ul>
+ <h2><a href="kde4.html"><img src="../images/kde4_32.png" style="float:right; margin:-8px 0 0 0;" alt="KDE4 Logo" />KDE SC 4.6</a> in <br />testing/unstable</h2>
<br />
- <h2><a href="kde4.html"><img src="../images/kde4_32.png" style="float:right; margin:-8px 0 0 0;" alt="KDE4 Logo" />KDE SC 4.4</a> in </br>Squeeze 6.0 (stable)</h2>
+ <h2><a href="kde4.html"><img src="../images/kde4_32.png" style="float:right; margin:-8px 0 0 0;" alt="KDE4 Logo" />KDE SC 4.4</a> in <br />Squeeze 6.0 (stable)</h2>
<ul>
<li><a href="kaboom.html" title="Kaboom, the Debian KDE settings migration wizard">Kaboom, the settings migration wizard</a></li>
<li><a href="faq4.html">FAQ about the migration to KDE 4</a></li>
@@ -63,6 +61,12 @@
</div>
<div id="footer">
+ <p style="float:left;">
+ <a href="http://validator.w3.org/check?uri=referer">
+ <img src="http://www.w3.org/Icons/valid-xhtml11" alt="Valid XHTML 1.1" height="31" width="88" />
+ </a>
+ </p>
+
<p><a href="mailto:debian-kde at lists.debian.org">Contact us</a> | <a href="#header">Back to top</a><br />Based on <a href="http://andreasviklund.com/">Andreas Viklund</a>'s Design
</p>
</div>
diff --git a/pages/bugs b/pages/bugs
index 69cdca9..8c3f8a0 100644
--- a/pages/bugs
+++ b/pages/bugs
@@ -1,4 +1,4 @@
-<h2>Bug triaging<img src="../images/bug_64.png" style="float:right; margin:-8px 0 0 0;" /></h2>
+<h2>Bug triaging<img alt="bug_icon" src="../images/bug_64.png" style="float:right; margin:-8px 0 0 0;" /></h2>
<p>
The following strategy is the one mostly used on bug triaging among the kde packagers:<br />
</p>
diff --git a/pages/experimental_linking b/pages/experimental_linking
index 53d2fed..174ce1e 100644
--- a/pages/experimental_linking
+++ b/pages/experimental_linking
@@ -15,19 +15,20 @@
<p>Use the autofixtll script to automatically find most linking problems and generate a patch to fix them.</p>
<ul>
<li>Download the script from <a href="http://svn.debian.org/viewsvn/*checkout*/pkg-kde/scripts/autofixtll"> our SVN</a></li>
-<li>From the root of your unpacked source, run :</li>
+<li>From the root of your unpacked source, run:<br />
<code>$ mkdir build<br/>
$ cd build<br/>
$ cmake .. -DCMAKE_VERBOSE_MAKEFILE=ON<br/>
$ cd ..<br/>
$ autofixtll -i -c make -d build -q none</code>
+</li>
<li>If autofixtll doesn't do the trick, you can finish with the manual way below.</li>
<li>For more help on using autofixtll, just read <tt>autofixtll --help</tt>.</li>
</ul>
<h5>3-Manually find and repair linking problems :</h5>
<ul>
-<li>We assume <tt>cmake</tt> runs well, and that <tt>make</tt> fails with this kind of message :</li>
+<li>We assume <tt>cmake</tt> runs well, and that <tt>make</tt> fails with this kind of message :<br />
<code>CMakeFiles/kcm_krunner_spellcheck.dir/spellcheck_config.o:(.data.rel.ro._ZTV13ConfigFactory[vtable for ConfigFactory]+0x44):
undefined reference to `<b>KPluginFactory::create</b>(char const*, QWidget*, QObject*, QList<QVariant> const&, QString const&)'<br/>
[...]<br/>
@@ -35,12 +36,11 @@ collect2: ld returned 1 exit status<br/>
make[2]: *** [lib/kcm_krunner_spellcheck.so] Error 1<br/>
make[1]: *** [<b>runners/spellchecker</b>/CMakeFiles/<b>kcm_krunner_spellcheck</b>.dir/all] Error 2<br/>
make: *** [all] Error 2<br/>
-xavier at kawet:~/tmp/compile/svn/plasma/build$</code>
+xavier at kawet:~/tmp/compile/svn/plasma/build$</code></li>
<li>locate the unresolved function (here <b>KPluginFactory::create</b>)</li>
<li>locate the failing build target (here <b>kcm_krunner_spellcheck</b> in <b>directory runners/spellchecker</b>)</li>
<li>find the library providing it : the best way to do this is to search <a href="http://api.kde.org">api.kde.org</a>. Googling <a href="http://www.google.com/search?q=KPluginFactory+site:api.kde.org/4.1-api">KPluginFactory site:api.kde.org/4.1-api</a>, you can see it's in kdecore. For Qt modules, you can search in <a href="http://doc.trolltech.com/4.4">doc.trolltech.com/4.4</a>.</li>
-<li>edit the relevant CMakeLists.txt file and locate the target_link_libraries line corresponding to the build target and add the relevant ${KDE4_*_LIBS} or ${QT_*_library} tag. Here is a list of the available ones :</li>
-
+<li>edit the relevant CMakeLists.txt file and locate the target_link_libraries line corresponding to the build target and add the relevant ${KDE4_*_LIBS} or ${QT_*_library} tag. Here is a list of the available ones :<br />
<ul style="float: left; width: 35%">
<li>KDE4_KDECORE_LIBS</li>
<li>KDE4_KDEUI_LIBS</li>
@@ -114,7 +114,7 @@ xavier at kawet:~/tmp/compile/svn/plasma/build$</code>
<li>QT_PHONON_LIBRARY</li>
</ul>
-<br clear="both"/>
+<br clear="both" /></li>
<li>For the example in runners/spellchecker/CMakeLists.txt, replace<br/>
<code>target_link_libraries(krunner_spellcheckrunner ${KDE4_KDEUI_LIBS} ${PLASMA_LIBS})</code><br/>
with<br/>
diff --git a/pages/faq b/pages/faq
index 0094419..e201cc2 100644
--- a/pages/faq
+++ b/pages/faq
@@ -1,5 +1,5 @@
- <h2>Frequently Asked Questions (FAQ)<img src="../images/helpbook_64.png" style="float:right; margin:-8px 0 0 0;" /></h2>
+ <h2>Frequently Asked Questions (FAQ)<img alt="faq icon" src="../images/helpbook_64.png" style="float:right; margin:-8px 0 0 0;" /></h2>
<h4 id="q1">1. What is KDE?</h4>
<p>
@@ -30,7 +30,7 @@
<p>A very common problem when compiling KDE programs (or other ones which use
Qt), is that the configure script, is unable to find where Qt is, and failing
- with a message like this:
+ with a message like this:</p>
<p><samp>checking for Qt... configure: error: Qt (>= Qt 3.1.0) (headers and
libraries) not found. Please check your installation!</samp></p>
@@ -51,7 +51,7 @@
<p>If configure still fails with the same error, this means is failing to
find where Qt is installed. You can pass the exact path to the configure script
- this way:
+ this way:</p>
<p><kbd>--with-qt-dir=/usr/share/qt3</kbd></p>
diff --git a/pages/faq4 b/pages/faq4
index 6f3517a..1e49b03 100644
--- a/pages/faq4
+++ b/pages/faq4
@@ -1,5 +1,5 @@
- <h2>Frequently Asked Questions (FAQ)<img src="../images/helpbook_64.png" style="float:right; margin:-8px 0 0 0;" /></h2>
+ <h2>Frequently Asked Questions (FAQ)<img alt="help_icon" src="../images/helpbook_64.png" style="float:right; margin:-8px 0 0 0;" /></h2>
<h4 id="q0">0. I have a question and it is not in the FAQ. Where I do ask?</h4>
<p>
diff --git a/pages/gitguidelines b/pages/gitguidelines
index f0cebe0..b0e65fa 100644
--- a/pages/gitguidelines
+++ b/pages/gitguidelines
@@ -39,9 +39,9 @@ section above.
<ul>
<li> Work-in-progress debian/changelog entry must have its distribution field set to
- UNRELEASED. That's DEBCHANGE_RELEASE_HEURISTIC=changelog setting for dch.
+ UNRELEASED. That's DEBCHANGE_RELEASE_HEURISTIC=changelog setting for dch.</li>
<li> New packaging changes must be committed together with the change description
- in the debian/changelog entry (if applicable). Sentences should end with dots.
+ in the debian/changelog entry (if applicable). Sentences should end with dots.</li>
<li> The guidelines below are *highly* recommended to follow in order to reduce
conflicts in debian/changelog when cherry-picking and merging between
branches:
@@ -61,7 +61,7 @@ section above.
As a result, dch --release should be used to update the date in the trailer
when releasing the package to Debian.
</li>
- </ul>
+ </ul></li>
<li>
Commit message must be meaningful (typically, debcommit is OK). The first
commit message line must be short (up to 72-80 characters) and end with a
@@ -129,15 +129,15 @@ requirements:
The tag must be annotated and preferably signed with the key of uploader.
</li>
<li>
- The tag must be named like "debian/<version>" where <version> is a full
+ The tag must be named like "debian/<version>" where <version> is a full
debian package version without epoch. All occurrences of the ~ character in
- <version> should be replaced with the - character because Git does not
+ <version> should be replaced with the - character because Git does not
support ~ character in tag names.
</li>
<li>
The tag must be assigned the message with content like
- "<version>/<distribution>" where <version> is a full debian version of the
- package (without any modifications including epoch) and <distribution>
+ "<version>/<distribution>" where <version> is a full debian version of the
+ package (without any modifications including epoch) and <distribution>
is the distribution this package is uploaded to (as per the latest debian
changelog entry).
</li>
@@ -147,7 +147,7 @@ For example, in order to tag the tip of current packaging branch as upload of
the package version 4:4.6.0~beta1-1 to experimental, the following command may
be used:
-<br><br>
+<br /><br />
<pre>
$ git tag debian/4.6.0-beta1-1 -sm "4:4.6.0~beta1-1/experimental"
</pre>
@@ -159,7 +159,7 @@ number (number of commits since the latest tag) that `git describe` returns at
the tip of the upstream snapshot being packaged.
For example, if:
-<br><br>
+<br /><br />
<pre>
$ git describe
v1.2-beta1-45-67890abc
@@ -173,7 +173,7 @@ then Debian package upstream version part of this snapshot could be
<pre> $ git clone git.debian.org:/git/path/to/the/remote/repository.git</pre>
<h4>For anonymous users:</h4>
- <pre>$ git clone <Vcs-Git URL from debian/control></pre>
+ <pre>$ git clone <Vcs-Git URL from debian/control></pre>
Wait a bit. You will end up with full clone of the public repository and a
local branch master will be setup to track remote master branch
@@ -181,13 +181,13 @@ then Debian package upstream version part of this snapshot could be
In order to track another packaging branch (e.g. lenny) locally, run:
- <br><br>
+ <br /><br />
<pre>$ git checkout -b lenny origin/lenny</pre>
Now let's setup `git push` to push all packaging branches and debian tags by
default:
- <br><br>
+ <br /><br />
<pre>
$ git config --add remote.origin.push "refs/heads/master"
$ git config --add remote.origin.push "refs/heads/lenny"
@@ -200,7 +200,7 @@ In order to avoid pointless merge commits, it is recommended to use --rebase
option to `git pull` when pulling changes from the remote repository if your
local master contains not-yet-pushed and rather trivial commits:
- <br><br>
+ <br /><br />
<pre>
$ git checkout master
$ git pull --rebase
@@ -217,7 +217,7 @@ local master contains not-yet-pushed and rather trivial commits:
<li> Original source is extracted to the packaging branch working tree from
the tarball:
- <br><br>
+ <br /><br />
<pre>
# (only once) Ignore everything (upstream source) but files under debian/.
$ git config core.excludesfile debian/upstreamignore
@@ -244,7 +244,7 @@ local master contains not-yet-pushed and rather trivial commits:
maintained in the local 'upstream' branch. When creating such a new
disjoint upstream branch, execute:
- <br><br>
+ <br /><br />
<pre>
# Switch HEAD to not-yet-created upstream branch
$ git symbolic-ref HEAD refs/heads/upstream
@@ -252,7 +252,7 @@ local master contains not-yet-pushed and rather trivial commits:
When updating an existing upstream branch to a new release, just do:
- <br><br>
+ <br /><br />
<pre>
# Clean current branch before checkout
$ git clean -xdff
@@ -261,7 +261,7 @@ local master contains not-yet-pushed and rather trivial commits:
Then do something like this:
- <br><br>
+ <br /><br />
<pre>
# Remove all tracked files (e.g. old sources)
$ git rm -r '*'
@@ -278,7 +278,7 @@ local master contains not-yet-pushed and rather trivial commits:
Original source can be fetched from the remote upstream repository.
For example, let's define a new remote 'qt' for original Qt sources.
- <br><br>
+ <br /><br />
<pre>
$ git remote add qt git://gitorious.org/qt/qt.git
$ git remote update
@@ -289,7 +289,7 @@ local master contains not-yet-pushed and rather trivial commits:
</ol>
Finally, read upstream tree to the packaging branch working tree, do:
- <br><br>
+ <br /><br />
<pre>
# (only once) Ignore everything (upstream source) but files under
# debian/.
@@ -320,7 +320,7 @@ local master contains not-yet-pushed and rather trivial commits:
<ol>
<li> Committing to master directly:
- <br><br>
+ <br /><br />
<pre>
$ git checkout build # (or git checkout -b build upstream)
$ git merge upstream # (or git reset --hard upstream)
@@ -341,7 +341,7 @@ local master contains not-yet-pushed and rather trivial commits:
<li> Cherry-picking (or rebasing) from build branch:
- <br><br>
+ <br /><br />
<pre>
$ git checkout build # (or git checkout -b build upstream)
$ git merge upstream # (or git reset --hard upstream)
@@ -381,9 +381,9 @@ local master contains not-yet-pushed and rather trivial commits:
subdirectory hence it won't track changes made by `quilt push`. This way you
can always be sure that `git commit -a` won't pick up any raw patches to
upstream source regardless if anything is quilt pushed or not.
-<br><br>
-<a name="footnote1">[1]</a> Available in the quilt package on Debian based
+<br /><br />
+[1] Available in the quilt package on Debian based
systems. quilt must be invoked with QUILT_PATCHES environment variables set to
-debian/patches.<br>
-<a name="footnote2">[2]</a> Available in the git-core package on Debian based
+debian/patches.<br />
+[2] Available in the git-core package on Debian based
systems.
diff --git a/pages/index b/pages/index
index 6f5295d..b5983bb 100644
--- a/pages/index
+++ b/pages/index
@@ -1,6 +1,6 @@
<h2>Welcome</h2>
<p>This is the home page of two closely related teams:
- <a href="qtkde.html">Debian Qt/KDE Maintainers</a></li> and
+ <a href="qtkde.html">Debian Qt/KDE Maintainers</a> and
<a href="kdeextras.html">Debian KDE Extras Team</a>.<br />
We are a group of people with a common goal in mind: bringing the best KDE possible to Debian.
</p>
diff --git a/pages/kde4 b/pages/kde4
index 34e3c42..95b0d6f 100644
--- a/pages/kde4
+++ b/pages/kde4
@@ -20,7 +20,7 @@
</tr>
<tr>
<td style="width:15em;">
- <a href="http://packages.debian.org/unstable/plasma-desktop"><code>plasma-desktop</code></a> or<br>
+ <a href="http://packages.debian.org/unstable/plasma-desktop"><code>plasma-desktop</code></a> or<br />
<a href="http://packages.debian.org/unstable/plasma-netbook"><code>plasma-netbook</code></a>
</td>
<td><i>The KDE plasma workspace for desktops/laptops or netbooks.</i></td>
@@ -124,7 +124,7 @@
<p>This is useful if you want to keep your KDE 3 enviroment but want to use a KDE 4 application like okular or even konsole. But remember KDE 4 apps will not integrate in your KDE 3 desktop so well as the current KDE 3 do.</p>
<br />
- <h3 style="clear:both; padding-top:3em;"><img src="../images/info_48.png" style="float:right; margin:-15px 0 0 0;" />Notes for KDE 4 packages</h3>
+ <h3 style="clear:both; padding-top:3em;"><img src="../images/info_48.png" alt="info_icon" style="float:right; margin:-15px 0 0 0;" />Notes for KDE 4 packages</h3>
<p>If you run into a problem and need help, you can send a mail to the
<a href="http://lists.debian.org/debian-kde/">Debian KDE support list.</a>
diff --git a/pages/kdebuggraph b/pages/kdebuggraph
index 4932d00..0091ddc 100644
--- a/pages/kdebuggraph
+++ b/pages/kdebuggraph
@@ -1,5 +1,5 @@
- <h2>Bug graph<img src="../images/graph_64.png" style="float:right; margin:-8px 0 0 0;" /></h2>
+ <h2>Bug graph<img alt="bug_icon" src="../images/graph_64.png" style="float:right; margin:-8px 0 0 0;" /></h2>
<h3>Evolution of the numbers of bugs in the last week</h3>
<img src="http://users.alioth.debian.org/~pusling-guest/pkg-kde-buggraphs/_ALL__week.png" alt="bug graph last week"/>
<h3>Evolution of the numbers of bugs in the last month</h3>
diff --git a/pages/kdeextras b/pages/kdeextras
index 215b5e1..1f2901a 100644
--- a/pages/kdeextras
+++ b/pages/kdeextras
@@ -1,4 +1,4 @@
- <h2>Debian KDE Extras Team<img src="../images/extrasteam_64.png" style="float:right; margin:-8px 0 0 0;" /></h2>
+ <h2>Debian KDE Extras Team<img alt="extrasteam_icon" src="../images/extrasteam_64.png" style="float:right; margin:-8px 0 0 0;" /></h2>
<p>This team maintains KDE applications.</p>
<p>Mailing list: <a href="mailto:pkg-kde-extras at lists.alioth.debian.org">pkg-kde-extras at lists.alioth.debian.org</a></p>
<p>Mailing list archives: <a href="http://lists.alioth.debian.org/mailman/listinfo/pkg-kde-extras">http://lists.alioth.debian.org/mailman/listinfo/pkg-kde-extras</a></p>
diff --git a/pages/qtkde b/pages/qtkde
index 9cf5878..7caca37 100644
--- a/pages/qtkde
+++ b/pages/qtkde
@@ -1,4 +1,4 @@
- <h2>Debian Qt/KDE Maintainers<img src="../images/qtkdeteam_64.png" style="float:right; margin:-8px 0 0 0;" /></h2>
+ <h2>Debian Qt/KDE Maintainers<img alt="QT KDE icon" src="../images/qtkdeteam_64.png" style="float:right; margin:-8px 0 0 0;" /></h2>
<p>This team maintains all the official <a href="http://www.kde.org">KDE</a> modules.</p>
<p>Mailing list: <a href="mailto:debian-qt-kde at lists.debian.org">debian-qt-kde at lists.debian.org</a></p>
<p>If you are a user and want to get in contact with us, come around in <a href="irc://irc.oftc.net/debian-kde">#debian-kde</a> on OFTC, or mail <a href="mailto:debian-kde at lists.debian.org">debian-kde at lists.debian.org</a>.</p>
diff --git a/pages/symbolfiles b/pages/symbolfiles
index 33fbc0d..6530fc1 100644
--- a/pages/symbolfiles
+++ b/pages/symbolfiles
@@ -106,8 +106,6 @@ not exist in any public header.</li>
</ul>
<p>
-
-<p>
If your library is C++, you will probably need a way to translate symbols to human-readable C++
identifiers. To do this, you can use the c++filt command, passing it as a first argument the symbol,
striping anything after the first @ character (usually symbols end with @Base). For example, if the
diff --git a/pages/todo b/pages/todo
index f5d5e42..7fea88d 100644
--- a/pages/todo
+++ b/pages/todo
@@ -2,6 +2,7 @@
Please take a look on the <a href="http://wiki.debian.org/PkgKde">PkgKde Wiki</a> page for forther information.
<p>
There is also the actual <a href="http://wiki.debian.org/KDETodo">ToDo list</a>
+</p>
<pre>
- Close all the bugs.
diff --git a/pages/top b/pages/top
index 7e2cf14..d320e29 100644
--- a/pages/top
+++ b/pages/top
@@ -17,8 +17,8 @@
<div id="wrap">
<div id="header">
- <a href="index.html"><img src="images/kdedebianlogo3_64.png" alt="A logo" /></br>
- <h1>Debian <span class="fade">KDE Team</span></h1></a>
+ <a href="index.html"><img src="images/kdedebianlogo3_64.png" alt="A logo" /></a>
+ <h1><a href="index.html">Debian <span class="fade">KDE Team</span></a></h1>
<!--<p id="slogan">packaging the best Desktop Enviroment...</p> -->
</div>
diff --git a/pages/usertags b/pages/usertags
index 80b7aaa..f7c7752 100644
--- a/pages/usertags
+++ b/pages/usertags
@@ -1,4 +1,4 @@
-<h2>Usertags<img src="../images/tag_64.png" style="float:right; margin:-8px 0 0 0;" /></h2>
+<h2>Usertags<img alt="tag icon" src="../images/tag_64.png" style="float:right; margin:-8px 0 0 0;" /></h2>
<p>
Usertags is a new nice feature in the bug tracking system that can be used to tag bugs how you like to do it.
The tags are bound to a user, and a user is in this case an email address. Usertags can be used to create different views on bugs and it can also be used to track stuff across packages.
@@ -45,7 +45,7 @@ With these arguments, most views are created. A couple of examples:
</dl>
-<h3><a name="used"></a>The usertags used by the KDE packagers</h3>
+<h3>The usertags used by the KDE packagers</h3>
<p>Some usertags are in the KDE packages only used in specific source packages. Other usertags are used across all source packages.</p>
<h4>kdepim</h4>
<dl>
diff --git a/pages/web-maintenance b/pages/web-maintenance
index aa45ea1..b467f09 100644
--- a/pages/web-maintenance
+++ b/pages/web-maintenance
@@ -1,4 +1,4 @@
- <h2>Debian KDE Team Web Maintenance<img src="../images/webmaint_64.png" style="float:right; margin:-8px 0 0 0;" /></h2>
+ <h2>Debian KDE Team Web Maintenance<img alt="webmaint_icon" src="../images/webmaint_64.png" style="float:right; margin:-8px 0 0 0;" /></h2>
<ol>
<li>Edit/create pages in folder `pkg-kde/www/v2/pages/'.<br />
--
pkg-kde.alioth.debian.org website
More information about the pkg-kde-commits
mailing list