Commit 2e8eea43 authored by Jan Dittberner's avatar Jan Dittberner

patch docs/conf.py to use a fixed your to support reproducible builds

parents bdb0e842 b0a4c7c8
# see git-dpm(1) from git-dpm package
9f5ee4d88503024479c3d6828c59aebb4b48090b
9f5ee4d88503024479c3d6828c59aebb4b48090b
b0a4c7c816eb3338112b999e203db3fcbd611e8f
b0a4c7c816eb3338112b999e203db3fcbd611e8f
6dcf67af033c32dc78cacc93ae8ed126a6d36817
6dcf67af033c32dc78cacc93ae8ed126a6d36817
python-releases_1.0.0.orig.tar.gz
......
......@@ -16,6 +16,7 @@ python-releases (1.0.0-1) UNRELEASED; urgency=medium
* Add myself to copyright file, bump copyright years
* patch README.rst to avoid privacy breach caused by included travis-ci
image
* patch docs/conf.py to use a fixed your to support reproducible builds
-- Jan Dittberner <jandd@debian.org> Sat, 30 Jan 2016 18:02:20 +0100
......
From b0a4c7c816eb3338112b999e203db3fcbd611e8f Mon Sep 17 00:00:00 2001
From: Jan Dittberner <jandd@debian.org>
Date: Sat, 30 Jan 2016 19:58:55 +0100
Subject: Remove calculated date from docs/conf.py to support reproducible
builds
---
docs/conf.py | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/docs/conf.py b/docs/conf.py
index 6b6ff31..6964763 100644
--- a/docs/conf.py
+++ b/docs/conf.py
@@ -1,4 +1,3 @@
-from datetime import datetime
import os
import sys
@@ -11,7 +10,7 @@ source_suffix = '.rst'
master_doc = 'index'
project = u'Releases'
-year = datetime.now().year
+year = 2015
copyright = u'%d Jeff Forcier' % year
# Ensure project directory is on PYTHONPATH for version, autodoc access
0001-Remove-travis-ci-image-and-link-to-avoid-privacy-bre.patch
0002-Remove-calculated-date-from-docs-conf.py-to-support-.patch
from datetime import datetime
import os
import sys
......@@ -11,7 +10,7 @@ source_suffix = '.rst'
master_doc = 'index'
project = u'Releases'
year = datetime.now().year
year = 2015
copyright = u'%d Jeff Forcier' % year
# Ensure project directory is on PYTHONPATH for version, autodoc access
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment