[website] 01/01: Add 'Backports with Git' section.
Bas Couwenberg
sebastic at debian.org
Sat Jul 9 23:17:36 UTC 2016
This is an automated email from the git hooks/post-receive script.
sebastic pushed a commit to branch master
in repository website.
commit d9c01281da7b6aa955ccd590a7be645b85d37894
Author: Bas Couwenberg <sebastic at xs4all.nl>
Date: Thu Dec 24 18:04:56 2015 +0100
Add 'Backports with Git' section.
Subsections:
* Creating a backport
* Updating a backport
* Building a backport
- Create pbuilder/cowbuilder chroot
* Pushing a backport
* Uploading a backport
* Tagging a backport
Add styling for blockquotes.
---
policy.xml | 508 +++++++++++++++++++++++++++++++++++++++++++++++++++---
policy/policy.css | 33 ++++
2 files changed, 518 insertions(+), 23 deletions(-)
diff --git a/policy.xml b/policy.xml
index 2ec9688..08e22ac 100644
--- a/policy.xml
+++ b/policy.xml
@@ -491,13 +491,15 @@ pkg-grass/
<listitem>
<para>
<literal>upstream/<replaceable><upstreamversion></replaceable></literal>
- for upstream releases
+ for upstream releases, e.g.
+ <literal>upstream/1.2.0</literal>
</para>
</listitem>
<listitem>
<para>
<literal>debian/<replaceable><debianversion></replaceable></literal>
- for Debian releases
+ for Debian releases, e.g.
+ <literal>debian/1.2.0-1</literal>
</para>
</listitem>
</itemizedlist>
@@ -509,26 +511,25 @@ pkg-grass/
<para>
<literal><replaceable><distribution></replaceable>/<replaceable><package_version></replaceable></literal>
</para>
- <itemizedlist>
- <listitem>
- <para>
- <literal>ubuntu/<replaceable><debianversion></replaceable>~ubuntu<replaceable><ubuntuversion></replaceable></literal>
- for UbuntuGIS backports based on the Debian GIS packaging
- </para>
- </listitem>
- <listitem>
- <para>
- <literal>osgeo/<replaceable><debianversion></replaceable>~osgeo<replaceable><osgeoversion></replaceable></literal>
- for OSGeo-Live releases based on the Debian GIS packaging, or
- </para>
- </listitem>
- <listitem>
- <para>
- <literal>osgeo/<replaceable><debianversion></replaceable>~ubuntu<replaceable><ubuntuversion></replaceable>-osgeo<replaceable><osgeoversion></replaceable></literal>
- for OSGeo-Live releases with changes on top of the UbuntuGIS packaging
- </para>
- </listitem>
- </itemizedlist>
+ <para>
+ Examples of the tagging convention for known derivatives:
+ <itemizedlist>
+ <listitem>
+ <para>
+ <literal>ubuntu/<replaceable><debian_version></replaceable>~<replaceable><ubuntu_codename><revision_number></replaceable></literal>
+ for UbuntuGIS backports based on the Debian GIS packaging, e.g.
+ <literal>ubuntu/1.2.0-1~trusty1</literal>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <literal>osgeo/<replaceable><debian_version></replaceable>~<replaceable><ubuntu_codename><revision_number></replaceable></literal>
+ for OSGeo-Live releases and backports based on the Debian GIS packaging, e.g.
+ <literal>osgeo/1.2.0-1~xenial1</literal>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
</sect3>
<sect3 id="git-upstream-repositories">
<title>Upstream Git repositories</title>
@@ -1707,6 +1708,463 @@ allowed_distributions = .*
to track changes from the shared repository on Alioth.
</para>
</sect3>
+ <sect3 id="git-backports">
+ <title>Backports with Git</title>
+ <para>
+ Backports are maintained in separate
+ <link linkend="git-package-branches">branches</link>
+ named after the distribution in question
+ (<literal>wheezy-backports</literal>,
+ <literal>jessie-backports</literal>, etc.).
+ </para>
+ <para>
+ For UbuntuGIS and OSGeo-Live
+ <link linkend="other-git-branches">their respective branches</link>
+ are used for the Ubuntu specific backports
+ (<literal>ubuntu/xenial</literal>,
+ <literal>osgeo/10.0</literal>, etc.).
+ </para>
+ <para>
+ The following sections document the workflow for
+ <link linkend="git-create-backport">creating</link>,
+ <link linkend="git-update-backport">updating</link>,
+ <link linkend="git-build-backport">building</link>,
+ <link linkend="git-push-backport">pushing</link>,
+ <link linkend="git-upload-backport">uploading</link> &
+ <link linkend="git-tag-backport">tagging</link>
+ backports.
+ </para>
+ <para>
+ The workflow for backports is not much different from the regular
+ workflow documented in the
+ <link linkend="git-walkthrough">Packaging walkthrough</link> section.
+ </para>
+ <para>
+ The backports workflow mostly includes the specific considerations
+ for backports, which are generally simple rebuilds of packages
+ available in Debian testing/unstable for a different distribution
+ release.
+ </para>
+ <sect4 id="git-create-backport">
+ <title>Creating a backport</title>
+ <para>
+ To create a backport, first create the branch from the release tag
+ of the version in testing:
+<programlisting>
+<command>git checkout</command> <option>-b</option> <replaceable>jessie-backports</replaceable> <replaceable>debian/1.2.3-1</replaceable>
+</programlisting>
+ </para>
+ <para>
+ Update the <literal>debian-branch</literal> option in
+ <link linkend="debian-gbp.conf"><filename>debian/gbp.conf</filename></link>
+ to have <command>git-buildpackage</command> use the backports
+ branch instead of <literal>master</literal>:
+<programlisting>
+<command>sed</command> <option>-i</option> <literal>'s/^debian-branch\s*=.*/debian-branch = <replaceable>jessie-backports</replaceable>/g'</literal> <filename>debian/gbp.conf</filename>
+</programlisting>
+ </para>
+ <para>
+ Also update the <literal>Vcs-Git</literal> URL in
+ <link linkend="debian-control"><filename>debian/control</filename></link>
+ for <command>debcheckout</command> to use the backports branch
+ instead of the default:
+<programlisting>
+<command>sed</command> <option>-i</option> <literal>'s/\(^Vcs-Git: .*\.git\).*/\1 -b <replaceable>jessie-backports</replaceable>/g'</literal> <filename>debian/control</filename>
+</programlisting>
+ </para>
+ <para>
+ Ensure that the proper version and distribution for the backport
+ are set in
+ <link linkend="debian-changelog"><filename>debian/changelog</filename></link>.
+ </para>
+ <para>
+ For packages to be uploaded to
+ <ulink url="https://backports.debian.org/Contribute/">backports.debian.org</ulink>
+ use <command>dch</command> <option>--bpo</option> to set the
+ version and distribution automatically:
+<programlisting>
+<command>dch</command> <option>--bpo</option> <literal>"Update branch in gbp.conf & Vcs-Git URL."</literal>
+</programlisting>
+ </para>
+ <para>
+ Backports for Ubuntu like those intended for UbuntuGIS and
+ OSGeo-Live should append the distribution codename with the tilde
+ prefix (as documented in the
+ <link linkend="ubuntugis-ppa">UbuntuGIS PPA</link> section) to the
+ version used for the last changelog entry:
+<programlisting>
+<command>dch</command> <option>-v</option> <literal>$(dpkg-parsechangelog -SVersion)~<replaceable>xenial1</replaceable></literal> <option>-m</option> <literal>"Rebuild for <replaceable>xenial</replaceable>."</literal> <option>-b</option>
+</programlisting>
+ </para>
+ <para>
+ Review and commit the changes for the backport, before continuing to
+ <link linkend="git-build-backport">build the package</link>:
+<programlisting>
+<command>git diff</command>
+<command>debcommit</command> <option>-a</option>
+</programlisting>
+ </para>
+ <para>
+ Simple backports don't require further changes than those for the
+ changelog.
+ </para>
+ <para>
+ More complex backports may need changes to (build) dependency
+ version requirements, patches to support older versions of
+ (build) dependencies, or disabling features for missing or unmet
+ (build) dependencies in the backports distribution.
+ Ideally only the (build) dependencies from the stable release are
+ used, but it's okay to use some backported (build) dependencies
+ from the backports archive.
+ </para>
+ </sect4>
+ <sect4 id="git-update-backport">
+ <title>Updating a backport</title>
+ <para>
+ To update an existing backport, checkout the backports branch and
+ merge the release tag of the version in testing:
+<programlisting>
+<command>git checkout</command> <replaceable>jessie-backports</replaceable>
+<command>git merge</command> <replaceable>debian/1.3.2-1</replaceable>
+</programlisting>
+ </para>
+ <para>
+ Resolve the merge conflict with a 3-way merge and keep the
+ changelog entry for the previous backport above its releated
+ release.
+ </para>
+ <para>
+ Commit the changes after resolving the conflicts and
+ adding the changed files:
+<programlisting>
+<command>git status</command>
+<command>vi debian/changelog</command>
+<command>git diff</command>
+<command>git add debian/changelog</command>
+...
+<command>git commit -a</command>
+</programlisting>
+ </para>
+ <para>
+ Add a new changelog entry for the updated backport:
+<programlisting>
+<command>dch</command> <option>--bpo</option>
+</programlisting>
+ If there were no further changes, only the
+ <literal>'Rebuild for <replaceable>distribution</replaceable>'</literal>
+ bulletpoint needs to be kept in the changelog.
+ </para>
+ <para>
+ Set the version explicitly if the backport is intended for Ubuntu
+ (e.g. UbuntuGIS or OSGeo-Live), <command>dch</command>
+ <option>--bpo</option> is only appropriate for Debian Backports:
+<programlisting>
+<command>dch</command> <option>-v</option> <literal>$(dpkg-parsechangelog -SVersion)~<replaceable>xenial1</replaceable></literal> <option>-m</option> <literal>"Rebuild for <replaceable>xenial</replaceable>."</literal> <option>-b</option>
+</programlisting>
+ </para>
+ <para>
+ Review and commit the changes for the updated backport, before continuing to
+ <link linkend="git-build-backport">build the package</link>:
+<programlisting>
+<command>git diff</command>
+<command>debcommit</command> <option>-a</option>
+</programlisting>
+ </para>
+ </sect4>
+ <sect4 id="git-build-backport">
+ <title>Building a backport</title>
+ <para>
+ The procedure to build a backport is nearly idential to
+ <link linkend="git-build-package">building a regular package</link>,
+ in addition to the <command>git-buildpackage</command>
+ <option>--git-pbuilder</option> option, the appropriate
+ distribution for the cowbuilder chroot needs to be specified with
+ the <option>--git-dist</option> option and the last version of the
+ package in the stable release or backports with the
+ <option>-v</option> option:
+<programlisting>
+<command>gbp buildpackage</command> <option>--git-pbuilder</option> <option>--git-dist</option>=<replaceable>jessie</replaceable> <option>-v</option><replaceable>1.2.0-1</replaceable>
+</programlisting>
+ </para>
+ <para>
+ If the build dependencies cannot be satisfied in the stable release,
+ use the backports chroot instead:
+<programlisting>
+<command>gbp buildpackage</command> <option>--git-pbuilder</option> <option>--git-dist</option>=<replaceable>jessie-backports</replaceable> <option>-v</option><replaceable>1.2.0-1</replaceable>
+</programlisting>
+ </para>
+ <para>
+ Specifying the version is one of the
+ <ulink url="https://backports.debian.org/Contribute/#index7h3">Basic Rules</ulink>
+ for Debian Backports:
+ <blockquote>
+ <para>
+ It is recommended to include all changelog entries since the
+ last version on debian-backports or since stable if it's the
+ first version.
+ You should do this by passing "<option>-v</option>" to
+ <command>dpkg-buildpackage</command>.
+ Eg:
+ "<command>debuild</command> <option>-v</option><replaceable>0.7.5-2</replaceable>",
+ where "<replaceable>0.7.5-2</replaceable>" is the version in stable.
+ If the package wasn't in stable or backports before you don't
+ have include the changelog entries (but you are free to do so).
+ It helps others to follow the changes introduced with the
+ backport (by reading the changes mailing list).
+ </para>
+ </blockquote>
+ </para>
+ <para>
+ Building backports for the Ubuntu PPAs need to use the
+ <option>-S</option> option to create a source-only upload:
+<programlisting>
+<command>gbp buildpackage</command> <option>--git-pbuilder</option> <option>--git-dist</option>=<replaceable>xenial-<ppa></replaceable> <option>-S</option>
+</programlisting>
+ If the package does not exist in the Ubuntu archive yet, the
+ <option>-sa</option> option needs to be used as well to include
+ the <literal>.orig.tar.gz</literal> in the upload too:
+<programlisting>
+<command>gbp buildpackage</command> <option>--git-pbuilder</option> <option>--git-dist</option>=<replaceable>xenial-<ppa></replaceable> <option>-S</option> <option>-sa</option>
+</programlisting>
+ Refer to the
+ <ulink url="https://help.launchpad.net/Packaging/PPA/BuildingASourcePackage#Options_when_building">Launchpad documentation</ulink>
+ for more information about building packages for Ubuntu PPAs.
+ </para>
+ <para>
+ Before the final build of backports intended for Ubuntu, the
+ appropriate distribution needs to be set in
+ <link linkend="debian-changelog"><filename>debian/changelog</filename></link>:
+<programlisting>
+<command>dch</command> <option>-rD</option> <replaceable>xenial</replaceable>
+<command>git commit</command> <option>-m</option> "Set distribution to <replaceable>xenial</replaceable>." <option>-a</option>
+</programlisting>
+ </para>
+ <para>
+ If the cowbuilder chroots for the backport are not available yet,
+ set those up first as documented in the
+ <link linkend="git-build-backport-chroot">next section</link>.
+ Otherwise you can continue to
+ <link linkend="git-push-backport">push</link> the changes for the
+ backport if it built successfully.
+ </para>
+ <sect5 id="git-build-backport-chroot">
+ <title>Setup the build environment for backports</title>
+ <para>
+ To quote another one of the
+ <ulink url="https://backports.debian.org/Contribute/#index7h3">Basic Rules</ulink>
+ from the Debian Backports documentation:
+ <blockquote>
+ <para>
+ Make sure that you have a proper build environment that only
+ contains the suite for which the backport is for (e.g. jessie
+ if you want to upload to jessie-backports) and no unneeded
+ backports. [...]
+ </para>
+ </blockquote>
+ </para>
+ <para>
+ Ideally only the (build) dependencies from the stable release are
+ used for the backport, but it's okay to use some backported (build)
+ dependencies from the backports archive if the dependencies cannot
+ be satisfied otherwise.
+ </para>
+ <para>
+ Backports should always be built in the appropriate cowbuilder
+ chroot, a plain stable chroot where possible, or one with the
+ backports repository enabled in addition otherwise.
+ </para>
+ <para>
+ Ensure that the
+ <link linkend="git-pbuilder-create">sudo configuration for cowbuilder</link>
+ is in place and the
+ <link linkend="git-pbuilder-hooks">lintian pbuilder hook</link>
+ is configured before creating the cowbuilder chroot for stable
+ updates and backports.
+ </para>
+ <para>
+ Plain stable cowbuilder chroots can be created with:
+<programlisting>
+<command>sudo cowbuilder</command> <option>--create</option> \
+ <option>--distribution</option>=<replaceable>jessie</replaceable> \
+ <option>--basepath</option>=/var/cache/pbuilder/base-<replaceable>jessie</replaceable>.cow \
+ <option>--hookdir=/var/cache/pbuilder/hook.d/</option>
+</programlisting>
+ </para>
+ <para>
+ To create a chroot with the backports repository enabled, use:
+<programlisting>
+<command>sudo cowbuilder</command> <option>--create</option> \
+ <option>--distribution</option>=<replaceable>jessie-backports</replaceable> \
+ <option>--basepath</option>=/var/cache/pbuilder/base-<replaceable>jessie-backports</replaceable>.cow \
+ <option>--hookdir=/var/cache/pbuilder/hook.d/</option>
+</programlisting>
+ </para>
+ <para>
+ For UbuntuGIS and OSGeo-Live their respective PPAs need to be
+ specified along with the regular Ubuntu mirror.
+ </para>
+ <para>
+ Creating a cowbuilder chroot with the
+ <literal>ubuntugis-unstable</literal> PPA enabled can be done
+ with:
+<programlisting>
+<command>sudo cowbuilder</command> <option>--create</option> \
+ <option>--distribution</option>=<replaceable>xenial</replaceable> \
+ <option>--basepath</option>=/var/cache/pbuilder/base-<replaceable>xenial-ubuntugis-unstable</replaceable>.cow \
+ <option>--hookdir=/var/cache/pbuilder/hook.d/</option> \
+ <option>--mirror</option>=http://<replaceable>nl</replaceable>.archive.ubuntu.com/ubuntu/ \
+ <option>--othermirror</option>="deb http://ppa.launchpad.net/ubuntugis/<replaceable>ubuntugis-unstable</replaceable>/ubuntu <replaceable>xenial</replaceable> main" \
+ <option>--components</option>="main universe"
+</programlisting>
+ Make sure to replace the Ubuntu mirror URL with the mirror
+ closest to your location.
+ </para>
+ <para>
+ A cowbuilder chroot with the OSGeo-Live <literal>nightly</literal>
+ PPA enabled can be created with:
+<programlisting>
+<command>sudo cowbuilder</command> <option>--create</option> \
+ <option>--distribution</option>=<replaceable>xenial</replaceable> \
+ <option>--basepath</option>=/var/cache/pbuilder/base-<replaceable>xenial-osgeolive</replaceable>.cow \
+ <option>--hookdir=/var/cache/pbuilder/hook.d/</option> \
+ <option>--mirror</option>=http://<replaceable>nl</replaceable>.archive.ubuntu.com/ubuntu/ \
+ <option>--othermirror</option>="deb http://ppa.launchpad.net/osgeolive/<replaceable>nightly</replaceable>/ubuntu <replaceable>xenial</replaceable> main" \
+ <option>--components</option>="main universe"
+</programlisting>
+ Also make sure to replace the Ubuntu mirror URL with the mirror
+ closest to your location.
+ </para>
+ </sect5>
+ </sect4>
+ <sect4 id="git-push-backport">
+ <title>Pushing a backport</title>
+ <para>
+ When the backports branch was created locally, e.g. for a
+ <link linkend="git-create-backport">new backported package</link>,
+ the <command>git push</command> <option>--set-upstream</option>
+ option needs to be used to track changes from the origin
+ repository on Alioth:
+<programlisting>
+<command>git push</command> origin <replaceable>jessie-backports</replaceable> <option>--set-upstream</option>
+</programlisting>
+ Plain <command>git push</command> is sufficient when the backports
+ branch was checked out from the origin repository on Alioth:
+<programlisting>
+<command>git push</command>
+</programlisting>
+ </para>
+ <para>
+ Depending on how the local git repository was created, the
+ protocol for git pushes may need to be changed to
+ <literal>ssh</literal>, and the host to
+ <literal>git.debian.org</literal>, because the
+ <literal>anonscm.debian.org</literal> host only provides
+ read-only services:
+<programlisting>
+<command>git remote set-url</command> <option>--push</option> origin ssh://<replaceable><username></replaceable>@git.debian.org/git/pkg-grass/<replaceable><package></replaceable>.git
+</programlisting>
+ The <replaceable><username></replaceable> doesn't have to be
+ specified if the appropriate username is configured in
+ <filename>~/.ssh/config</filename> as documented in the
+ <link linkend="ssh-config">SSH tips</link> section.
+ </para>
+ <para>
+ After pushing the changes for the backport to the repostitory on
+ Alioth, continue to
+ <link linkend="git-upload-backport">upload</link> the package and
+ <link linkend="git-tag-backport">tag</link> the release.
+ </para>
+ </sect4>
+ <sect4 id="git-upload-backport">
+ <title>Uploading a backport</title>
+ <para>
+ Only Debian Developers and Debian Maintainers who have been added
+ to the backports ACL can upload backported packages to the Debian
+ archive.
+ </para>
+ <para>
+ Folllow the instructions on the
+ <ulink url="https://backports.debian.org/Contribute/#index2h2">Debian Backports</ulink>
+ website to request addition to the backports ACL, or
+ <link linkend="sponsorship">request sponsorship</link> from a DD
+ in the team who is included in the backports ACL already.
+ </para>
+ <para>
+ Beside the ACL restriction, uploading a backport is not very
+ different from <link linkend="git-release-upload">uploading a new package release</link>.
+ </para>
+ <para>
+ The appropriate distribution and urgency are already set by
+ <command>dch</command> <option>--bpo</option>, leaving only the
+ need to sign the <filename>.changes</filename> file and upload it
+ to <literal>ftp-master</literal>.
+<programlisting>
+<command>debsign</command> <filename>../<replaceable><package></replaceable>_<replaceable><version></replaceable>_<replaceable><architecture></replaceable>.changes</filename>
+<command>dput</command> <filename>../<replaceable><package></replaceable>_<replaceable><version></replaceable>_<replaceable><architecture></replaceable>.changes</filename>
+</programlisting>
+ For UbuntuGIS and OSGeo-Live the appropriate distribution should
+ be set before the final build as documented in the
+ <link linkend="git-build-backport">Building a backport</link>
+ section.
+ </para>
+ <para>
+ Uploads to Launchpad also need to specify the appropriate PPA in
+ the <command>dput</command> command:
+<programlisting>
+<command>dput</command> ppa:<replaceable>your-lp-id/ppa</replaceable> <filename>../<replaceable><package></replaceable>_<replaceable><version></replaceable>_<replaceable><architecture></replaceable>.changes</filename>
+</programlisting>
+ Refer to the
+ <ulink url="https://help.launchpad.net/Packaging/PPA/Uploading">Uploading a package to a PPA</ulink>
+ documentation on Launchpad for more information.
+ </para>
+ <para>
+ After uploading the changes for the backport don't forget to
+ <link linkend="git-tag-backport">tag</link> the last commit and
+ push the changes to the git repository on Alioth.
+ </para>
+ </sect4>
+ <sect4 id="git-tag-backport">
+ <title>Tagging a backport</title>
+ <para>
+ Tagging a backport is also not very different from
+ <link linkend="git-tag-release">tagging a regular release</link>.
+ </para>
+ <para>
+ Use <command>debcommit</command> to create the tag from the version
+ in <link linkend="debian-changelog"><filename>debian/changelog</filename></link>
+ and push the tag to the git repository on Alioth.
+ </para>
+ <para>
+<programlisting>
+<command>debcommit</command> <option>-r</option>
+<command>git push</command> <option>--tags</option>
+</programlisting>
+ If the build modified the working directory, those modifications
+ need to be reverted before the release can be tagged.
+ </para>
+ <para>
+ Backports for UbuntuGIS and OSGeo-Live should use their respective
+ tag prefixes instead:
+<programlisting>
+# UbuntuGIS
+<command>git tag</command> ubuntu/$(dpkg-parsechangelog -SVersion | sed 's/~/./g')
+<command>git push</command> <option>--tags</option>
+
+# OSGeo-Live
+<command>git tag</command> osgeo/$(dpkg-parsechangelog -SVersion | sed 's/~/./g')
+<command>git push</command> <option>--tags</option>
+</programlisting>
+ Because the tilde is not a valid character in tags, all occurrences in
+ the package version need to replaced by dots as
+ <command>debcommit</command> does too.
+ </para>
+ <para>
+ Refer to the
+ <link linkend="git-tags">Tags for upstream and package releases</link>
+ section for some examples of the tagging convention for derivatives.
+ </para>
+ </sect4>
+ </sect3>
<sect3 id="git-patches">
<title>Patches</title>
<para>
@@ -1972,7 +2430,7 @@ lintian ../build-area/*changes
</para>
<para>
Backports of Debian GIS packages should be kept as branches in the
- package <link linkend="git-repository">Git</link> repository (e.g.
+ package <link linkend="git-repository">Git repository</link> (e.g.
<literal>wheezy-backports</literal>,
<literal>jessie-backports</literal>, etc.).
</para>
@@ -1982,6 +2440,10 @@ lintian ../build-area/*changes
<ulink url="https://backports.debian.org/Contribute/">Debian Backports ›› Contribute</ulink>
on the Backports website.
</para>
+ <para>
+ The workflow for packaging backports is documented in more detail in
+ the <link linkend="git-backports">Backports with Git</link> section.
+ </para>
</sect2>
<sect2 id="ubuntugis-ppa">
<title>PPA for Ubuntu by UbuntuGIS</title>
diff --git a/policy/policy.css b/policy/policy.css
index 370d5b7..0f23d66 100644
--- a/policy/policy.css
+++ b/policy/policy.css
@@ -82,3 +82,36 @@ ul.itemizedlist[compact="compact"] li p {
margin: 0;
}
+blockquote.blockquote {
+ background: #f9f9f9;
+ border-left: 10px solid #cccccc;
+ margin-left: 0.5em;
+ padding-top: 1.2em;
+ padding-right: 0.5em;
+ padding-bottom: 0em;
+ padding-left: 0.5em;
+ quotes: "\201C""\201D""\2018""\2019";
+}
+
+blockquote.blockquote:before {
+ color: #cccccc;
+ content: open-quote;
+ font-size: 4em;
+ line-height: 0.1em;
+ margin-right: 0.1em;
+ vertical-align: -0.4em;
+}
+
+blockquote.blockquote:after {
+ color: #cccccc;
+ content: close-quote;
+ font-size: 4em;
+ line-height: 0.1em;
+ margin-left: 0.1em;
+ vertical-align: -0.7em;
+}
+
+blockquote.blockquote p {
+ display: inline;
+}
+
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-grass/website.git
More information about the Pkg-grass-devel
mailing list