date:20151003

[Reproducible-builds] Bug#800776: cluster-glue: please make the build reproducible

2015-10-03 Thread Reiner Herrmann

Source: cluster-glue
Version: 1.0.12~rc1+hg2777-1.2
Severity: wishlist
Tags: patch
User: reproducible-builds@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org

Hi!

While working on the "reproducible builds" effort [1], we have noticed
that cluster-glue could not be built reproducibly.
The build date is embedded into a manpage.

The attached patch fixes this by exporting the SOURCE_DATE_EPOCH variable.

Regards,
 Reiner

[1]: https://wiki.debian.org/ReproducibleBuilds

diff --git a/debian/rules b/debian/rules
index 40c7258..f9fda13 100755
--- a/debian/rules
+++ b/debian/rules
@@ -12,6 +12,8 @@ DEB_BUILD_GNU_TYPE  ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
 # enable hardening 
 export DEB_BUILD_HARDENING=1
 
+export SOURCE_DATE_EPOCH = $(shell date -d "$$(dpkg-parsechangelog -SDate)" +%s)
+
 DTMP:=$(CURDIR)/debian/tmp
 RELEASE := $(shell dpkg-parsechangelog | awk '/^Version: / { print $$2 }')
 UPSTREAM := $(shell echo "$(RELEASE)" | sed 's/:\?\([0-9\.]\+\)-[0-9].*/\1/')


signature.asc
Description: OpenPGP digital signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

[Reproducible-builds] adding a new PTS keyword (Re: Usefulness of periodic reproducible builds e-mails

2015-10-03 Thread Holger Levsen

Hi,

forwarding this question to -qa@ as it's more likely to get an answer there...

On Mittwoch, 30. September 2015, Mattia Rizzolo wrote:
> > I think there is value in receiving these notifications, they provide
> > timely feedback about the status of our packages.
> > 
> > Maybe we can setup a mailing list for this, something like
> > pkg-java-bui...@lists.alioth.debian.org? (we already have
> > pkg-java-commits, for example).
> 
> This wouldn't work with the current implementation, which is emailing
> $p...@packages.debian.org.  Anyway, I received a suggestion of setting up
> a new PTS keyword, so then people can go and subscribe there, maybe
> using the team facility of the new tracker to subscribe to the whole lot
> (i beliebe it works that way?).
> 
> Does anybody knows how to achive that?


cheers,
Holger



signature.asc
Description: This is a digitally signed message part.
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

[Reproducible-builds] exception found: ftbfs in testing, reproducible in sid (Re: Usefulness of periodic reproducible builds e-mails)

2015-10-03 Thread Holger Levsen

Hi,

On Samstag, 3. Oktober 2015, Holger Levsen wrote:
> If this doesnt happen it's almost certainly a bug in our test framework,
> but not a reproducibility issue in the package. And if the package ftbfs
> in testing, this is very sad, but IMO not appropriate to send a
> "reproducible builds project" notification for it - such problems should
> be detected elsewhere. It's nice if we gather that data, and we should
> also manually file bugs from that data, but I dont think we should
> generate automated notifications because as I tried to explain, if a
> package is fixed in sid, the fix will migrate to testing eventually. Thus
> we only really need to care about sid and testing will be good
> "automatically".

I still think the above is correct, even though there's already an exception 
found: https://reproducible.debian.net/palabos ftbfs in strech and is 
reproducible in sid.

I'm curious to understand why, but I still think this is very rare case, not 
justifying notifications for *all* (or any) ftbfs in testing. I do want them 
to be visible though, so I've just added this to TODO: "new page with packages 
which ftbfs in testing but build fine on sid".

cheers,
Holger

signature.asc
Description: This is a digitally signed message part.
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: [Reproducible-builds] adding a new PTS keyword (Re: Usefulness of periodic reproducible builds e-mails

2015-10-03 Thread Raphael Hertzog

Hello,

> On Mittwoch, 30. September 2015, Mattia Rizzolo wrote:
> > > I think there is value in receiving these notifications, they provide
> > > timely feedback about the status of our packages.
> > > 
> > > Maybe we can setup a mailing list for this, something like
> > > pkg-java-bui...@lists.alioth.debian.org? (we already have
> > > pkg-java-commits, for example).
> > 
> > This wouldn't work with the current implementation, which is emailing
> > $p...@packages.debian.org.  Anyway, I received a suggestion of setting up
> > a new PTS keyword, so then people can go and subscribe there, maybe
> > using the team facility of the new tracker to subscribe to the whole lot
> > (i beliebe it works that way?).
> > 
> > Does anybody knows how to achive that?

What kind of mails are we referring to?

In general, it's OK to use the package tracker to relay important data
about the packages... but I don't think that a dedicated keyword helps
here. We have a "build" keyword already and I believe that reproducible
mails should be sent via that keyword as well.

That said it depends on the mails... we really want only notifications
when something significant changes.

About the implementation it can be done simply by mailing a specific
email address that encodes both the package and the keyword.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/

___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

[Reproducible-builds] Bug#800808: django-sitetree: FTBFS: AttributeError: module 'html.parser' has no attribute 'HTMLParseError'

2015-10-03 Thread Chris Lamb

Source: django-sitetree
Version: 1.4.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-builds@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org

Dear Maintainer,

django-sitetree fails to build from source in unstable/amd64:

  [..]

  
  Importing tree `/tree2/` ...
  Destroying test database for alias 'default'...
  Traceback (most recent call last):
File "sitetree/runtests.py", line 39, in 
  main()
File "sitetree/runtests.py", line 27, in main
  setup()
File "/usr/lib/python3/dist-packages/django/__init__.py", line 18,
in setup
  from django.utils.log import configure_logging
File "/usr/lib/python3/dist-packages/django/utils/log.py", line 13,
in 
  from django.views.debug import ExceptionReporter,
  get_exception_reporter_filter
File "/usr/lib/python3/dist-packages/django/views/debug.py", line
10, in 
  from django.http import (HttpResponse, HttpResponseServerError,
File "/usr/lib/python3/dist-packages/django/http/__init__.py", line
4, in 
  from django.http.response import (
File "/usr/lib/python3/dist-packages/django/http/response.py", line
13, in 
  from django.core.serializers.json import DjangoJSONEncoder
File
"/usr/lib/python3/dist-packages/django/core/serializers/__init__.py",
line 23, in 
  from django.core.serializers.base import SerializerDoesNotExist
File
"/usr/lib/python3/dist-packages/django/core/serializers/base.py",
line 6, in 
  from django.db import models
File "/usr/lib/python3/dist-packages/django/db/models/__init__.py",
line 6, in 
  from django.db.models.query import Q, QuerySet, Prefetch  # NOQA
File "/usr/lib/python3/dist-packages/django/db/models/query.py",
line 13, in 
  from django.db.models.fields import AutoField, Empty
File
"/usr/lib/python3/dist-packages/django/db/models/fields/__init__.py",
line 18, in 
  from django import forms
File "/usr/lib/python3/dist-packages/django/forms/__init__.py", line
6, in 
  from django.forms.fields import *  # NOQA
File "/usr/lib/python3/dist-packages/django/forms/fields.py", line
18, in 
  from django.forms.utils import from_current_timezone,
  to_current_timezone
File "/usr/lib/python3/dist-packages/django/forms/utils.py", line
15, in 
  from django.utils.html import format_html, format_html_join,
  escape
File "/usr/lib/python3/dist-packages/django/utils/html.py", line 16,
in 
  from .html_parser import HTMLParser, HTMLParseError
File "/usr/lib/python3/dist-packages/django/utils/html_parser.py",
line 12, in 
  HTMLParseError = _html_parser.HTMLParseError
  AttributeError: module 'html.parser' has no attribute 'HTMLParseError'
  debian/rules:24: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 1
  make[1]: Leaving directory '/tmp/buildd/django-sitetree-1.4.0'
  debian/rules:9: recipe for target 'build' failed
  make: *** [build] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/django-sitetree_1.4.0-1.build1.log.gz


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Fri Oct  2 19:12:51 GMT+12 2015
I: pbuilder-time-stamp: 1443856371
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: Mounting /dev/shm
I: Mounting /sys
I: policy-rc.d already exists
I: Installing the build-deps
 -> Attempting to satisfy build-dependencies
 -> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team 
Description: Dummy package to satisfy dependencies with aptitude - created by 
pbuilder
 This package was created automatically by pbuilder to satisfy the
 build-dependencies of the package being currently built.
Depends: debhelper (>= 9), dh-python, python-all, python-babel, python-django 
(>= 1.4.2), python-mock, python-setuptools, python-sphinx (>= 1.0.7+dfsg), 
python3-all, python3-babel, python3-django, python3-mock, python3-setuptools
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in 
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20299 files and directories currently installed.)
Preparing to unpack

[Reproducible-builds] Bug#800810: openslide-python: Missing Build-Depends on python3-pil and libopenslide-dev

2015-10-03 Thread Chris Lamb

Source: openslide-python
Version: 1.0.1-5
Severity: serious
Justification: fails to build from source
User: reproducible-builds@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org
Tags: patch

Dear Maintainer,

openslide-python fails to build from source in unstable/amd64 due
to missing Build-Depends on python3-pil and libopenslide-dev:

  [..]

  I: pybuild base:170: cd
  /tmp/buildd/openslide-python-1.0.1/.pybuild/pythonX.Y_3.5/build;
  python3.5 -m unittest discover -v 
  openslide (unittest.loader._FailedTest) ... ERROR
  
  ==
  ERROR: openslide (unittest.loader._FailedTest)
  --
  ImportError: Failed to import test module: openslide
  Traceback (most recent call last):
File "/usr/lib/python3.5/unittest/loader.py", line 462, in
_find_test_path
  package = self._get_module_from_name(name)
File "/usr/lib/python3.5/unittest/loader.py", line 369, in
_get_module_from_name
  __import__(name)
File

"/tmp/buildd/openslide-python-1.0.1/.pybuild/pythonX.Y_3.5/build/openslide/__init__.py",
line 27, in 
  from PIL import Image
  ImportError: No module named 'PIL'
  
  
  --
  Ran 1 test in 0.001s
  
  FAILED (errors=1)
  E: pybuild pybuild:262: test: plugin distutils failed with: exit
  code=1: cd
  /tmp/buildd/openslide-python-1.0.1/.pybuild/pythonX.Y_3.5/build;
  python3.5 -m unittest discover -v 
  dh_auto_test: pybuild --test -i python{version} -p 3.5 3.4 --dir .
  returned exit code 13
  debian/rules:6: recipe for target 'build' failed
  make: *** [build] Error 25
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/openslide-python_1.0.1-5.build1.log.gz


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Fri Oct  2 20:25:05 GMT+12 2015
I: pbuilder-time-stamp: 1443860705
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: Mounting /dev/shm
I: Mounting /sys
I: policy-rc.d already exists
I: Installing the build-deps
 -> Attempting to satisfy build-dependencies
 -> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team 
Description: Dummy package to satisfy dependencies with aptitude - created by 
pbuilder
 This package was created automatically by pbuilder to satisfy the
 build-dependencies of the package being currently built.
Depends: debhelper (>= 9), dh-python, python-all, python3-all, 
python-setuptools, python3-setuptools
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in 
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20299 files and directories currently installed.)
Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ...
Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ...
dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring 
anyway as you requested:
 pbuilder-satisfydepends-dummy depends on dh-python; however:
  Package dh-python is not installed.
 pbuilder-satisfydepends-dummy depends on python-all; however:
  Package python-all is not installed.
 pbuilder-satisfydepends-dummy depends on python3-all; however:
  Package python3-all is not installed.
 pbuilder-satisfydepends-dummy depends on python-setuptools; however:
  Package python-setuptools is not installed.
 pbuilder-satisfydepends-dummy depends on python3-setuptools; however:
  Package python3-setuptools is not installed.

Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ...
Reading package lists...
Building dependency tree...
Reading state information...
Initializing package states...
Writing extended state information...
Building tag database...
pbuilder-satisfydepends-dummy is already installed at the requested version 
(0.invalid.0)
pbuilder-satisfydepends-dummy is already installed at the requested version 
(0.invalid.0)
The following NEW packages will be installed:
  dh-python{a} libexpat1{a} libmpdec2{a} libpython-stdlib{a} 
  libpython2.7-minimal{a} libpython2.7-stdlib{a} libpython3-stdlib{a} 
  libpython3.4-minimal{a} libpython3.4-stdlib{a} libpython3.5-minimal{a} 
  libpython3.5-stdlib{a} libssl1.0.0{a} mime-support{a} python{a}

[Reproducible-builds] Bug#800809: django-sitetree: FTBFS: AttributeError: module 'html.parser' has no attribute 'HTMLParseError'

2015-10-03 Thread Chris Lamb

Source: django-sitetree
Version: 1.4.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-builds@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org

Dear Maintainer,

django-sitetree fails to build from source in unstable/amd64:

  [..]

  
  Importing tree `/tree2/` ...
  Destroying test database for alias 'default'...
  Traceback (most recent call last):
File "sitetree/runtests.py", line 39, in 
  main()
File "sitetree/runtests.py", line 27, in main
  setup()
File "/usr/lib/python3/dist-packages/django/__init__.py", line 18,
in setup
  from django.utils.log import configure_logging
File "/usr/lib/python3/dist-packages/django/utils/log.py", line 13,
in 
  from django.views.debug import ExceptionReporter,
  get_exception_reporter_filter
File "/usr/lib/python3/dist-packages/django/views/debug.py", line
10, in 
  from django.http import (HttpResponse, HttpResponseServerError,
File "/usr/lib/python3/dist-packages/django/http/__init__.py", line
4, in 
  from django.http.response import (
File "/usr/lib/python3/dist-packages/django/http/response.py", line
13, in 
  from django.core.serializers.json import DjangoJSONEncoder
File
"/usr/lib/python3/dist-packages/django/core/serializers/__init__.py",
line 23, in 
  from django.core.serializers.base import SerializerDoesNotExist
File
"/usr/lib/python3/dist-packages/django/core/serializers/base.py",
line 6, in 
  from django.db import models
File "/usr/lib/python3/dist-packages/django/db/models/__init__.py",
line 6, in 
  from django.db.models.query import Q, QuerySet, Prefetch  # NOQA
File "/usr/lib/python3/dist-packages/django/db/models/query.py",
line 13, in 
  from django.db.models.fields import AutoField, Empty
File
"/usr/lib/python3/dist-packages/django/db/models/fields/__init__.py",
line 18, in 
  from django import forms
File "/usr/lib/python3/dist-packages/django/forms/__init__.py", line
6, in 
  from django.forms.fields import *  # NOQA
File "/usr/lib/python3/dist-packages/django/forms/fields.py", line
18, in 
  from django.forms.utils import from_current_timezone,
  to_current_timezone
File "/usr/lib/python3/dist-packages/django/forms/utils.py", line
15, in 
  from django.utils.html import format_html, format_html_join,
  escape
File "/usr/lib/python3/dist-packages/django/utils/html.py", line 16,
in 
  from .html_parser import HTMLParser, HTMLParseError
File "/usr/lib/python3/dist-packages/django/utils/html_parser.py",
line 12, in 
  HTMLParseError = _html_parser.HTMLParseError
  AttributeError: module 'html.parser' has no attribute 'HTMLParseError'
  debian/rules:24: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 1
  make[1]: Leaving directory '/tmp/buildd/django-sitetree-1.4.0'
  debian/rules:9: recipe for target 'build' failed
  make: *** [build] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/django-sitetree_1.4.0-1.build1.log.gz


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

[Reproducible-builds] Bug#800797: docbook-utils: please generate reproducible manpages

2015-10-03 Thread Reiner Herrmann

Source: docbook-utils
Version: 0.6.14-3
Severity: wishlist
Tags: patch
User: reproducible-builds@lists.alioth.debian.org
Usertags: toolchain timestamps locale
X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org

Hi!

While working on the "reproducible builds" effort [1], we have noticed
that docbook-utils doesn't generate reproducible manpages.
The embedded timestamp is using the build date and also varies depending
on the configured locale.

The attached patch adds support for the SOURCE_DATE_EPOCH environment
variable [2] and uses the C locale for the human-readable month
(which also fixes #214982).

Regards,
 Reiner

[1]: https://wiki.debian.org/ReproducibleBuilds
[2]: https://reproducible-builds.org/specs/source-date-epoch/

diff --git a/debian/patches/series b/debian/patches/series
index 6e5630a..795b9d1 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -4,3 +4,4 @@ bug_212088.patch
 bug_214982.patch
 bug_394511.patch
 bug_528334.patch
+support_source_date_epoch.patch
diff --git a/debian/patches/support_source_date_epoch.patch b/debian/patches/support_source_date_epoch.patch
new file mode 100644
index 000..ce5559c
--- /dev/null
+++ b/debian/patches/support_source_date_epoch.patch
@@ -0,0 +1,29 @@
+Author: Reiner Herrmann 
+Description: Support SOURCE_DATE_EPOCH for timestamps
+ To allow generating documents in a reproducible way,
+ allow overriding the timestamp through the environment.
+ .
+ See also: https://reproducible-builds.org/specs/source-date-epoch/
+
+Index: docbook-utils-0.6.14/helpers/docbook2man-spec.pl
+===
+--- docbook-utils-0.6.14.orig/helpers/docbook2man-spec.pl
 docbook-utils-0.6.14/helpers/docbook2man-spec.pl
+@@ -57,6 +57,7 @@ Software Foundation, 675 Mass Ave, Cambr
+ use SGMLS;			# Use the SGMLS package.
+ use SGMLS::Output;		# Use stack-based output.
+ use SGMLS::Refs;
++use POSIX qw(strftime setlocale LC_TIME);
+ 
+ 
+ # SGMLSPL script produced automatically by the script sgmlspl.pl
+@@ -278,7 +279,8 @@ sgml('', sub {
+ .\\" etc. to Steve Cheng .
+ _END_BANNER
+ 
+-	my $date = `date "+%d %B %Y"`;
++	setlocale(LC_TIME, "C");
++	my $date = strftime("%d %B %Y", gmtime($ENV{SOURCE_DATE_EPOCH} || time));
+ 	my $manpage_date = $manpage_date || $date ;
+ 
+ 	output '.TH "';


signature.asc
Description: OpenPGP digital signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: [Reproducible-builds] adding a new PTS keyword (Re: Usefulness of periodic reproducible builds e-mails

2015-10-03 Thread Mattia Rizzolo

On Sat, Oct 03, 2015 at 09:13:19PM +0200, Raphael Hertzog wrote:
> Hello,
> 
> > On Mittwoch, 30. September 2015, Mattia Rizzolo wrote:
> > > > I think there is value in receiving these notifications, they provide
> > > > timely feedback about the status of our packages.
> > > > 
> > > > Maybe we can setup a mailing list for this, something like
> > > > pkg-java-bui...@lists.alioth.debian.org? (we already have
> > > > pkg-java-commits, for example).
> > > 
> > > This wouldn't work with the current implementation, which is emailing
> > > $p...@packages.debian.org.  Anyway, I received a suggestion of setting up
> > > a new PTS keyword, so then people can go and subscribe there, maybe
> > > using the team facility of the new tracker to subscribe to the whole lot
> > > (i beliebe it works that way?).
> > > 
> > > Does anybody knows how to achive that?
> 
> What kind of mails are we referring to?

We are talking about very short mails, actually one-liners like

2015-10-03 11:43 https://reproducible.debian.net/unstable/amd64/derby changed 
from FTBFS -> unreproducible

(this one will be sent out this evening)

> In general, it's OK to use the package tracker to relay important data
> about the packages... but I don't think that a dedicated keyword helps
> here. We have a "build" keyword already and I believe that reproducible
> mails should be sent via that keyword as well.
> 
> That said it depends on the mails... we really want only notifications
> when something significant changes.

Well, we'd like a dedicate keywoard exactly because for a lot of people
this is not significant.
The current implementation of sending mails to $pkg@packages.d.o makes
the mail use the "contact" keyword, and imho this is bad, usually people
interested in contact only are not interested in this kind of info.

> About the implementation it can be done simply by mailing a specific
> email address that encodes both the package and the keyword.

Yes, but I guess this require something "qa side", or is it enough to
just start sending mails to package_reproduci...@packages.qa.debian.org
(or package_reproduci...@tracker.debian.org, but that way old PTS user
wouldn't get those mails)
??

> -- 
> Raphaël Hertzog ◈ Debian Developer
> 
> Support Debian LTS: http://www.freexian.com/services/debian-lts.html
> Learn to master Debian: http://debian-handbook.info/get/
> 

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

[Reproducible-builds] Bug#800816: plinth: please make the build reproducible

2015-10-03 Thread Reiner Herrmann

Source: plinth
Version: 0.5-1
Severity: wishlist
Tags: patch
User: reproducible-builds@lists.alioth.debian.org
Usertags: locale
X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org

Hi!

While working on the "reproducible builds" effort [1], we have noticed
that plinth could not be built reproducibly.
While generating a TODO list by grepping files, it also greps in .pyc files
(which produces varying grep output depending on the locale).

The attached patch filters pyc files while generating this list.

Regards,
 Reiner

[1]: https://wiki.debian.org/ReproducibleBuilds

diff --git a/debian/patches/0005-dont-grep-pyc.patch b/debian/patches/0005-dont-grep-pyc.patch
new file mode 100644
index 000..57167c5
--- /dev/null
+++ b/debian/patches/0005-dont-grep-pyc.patch
@@ -0,0 +1,12 @@
+Index: plinth-0.5/doc/Makefile
+===
+--- plinth-0.5.orig/doc/Makefile
 plinth-0.5/doc/Makefile
+@@ -50,6 +50,7 @@ $(SOURCES):
+ 	grep -ro --exclude=.git* --exclude=plinth.1 --exclude=*.tex --exclude=*.html \
+ 	 --exclude=README.mdwn --exclude=INSTALL.mdwn --exclude-dir=build \
+ 	 --exclude=TODO.mdwn --exclude=COPYING.mdwn --exclude-dir=debian \
++	 --exclude=*.pyc \
+ 	 "TODO\:.*" ../* 2>/dev/null | \
+ 	 sed -e "s/TODO\://g" | \
+ 	 sed -e "s/^..\//* /g" | \
diff --git a/debian/patches/series b/debian/patches/series
index d23a99b..1f699f7 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,3 +1,4 @@
 0002-remove-upstream-install-doc.patch
 0003-enable-javascript-common-conf.patch
 0004-disable-privileged-actions-test.patch
+0005-dont-grep-pyc.patch


signature.asc
Description: OpenPGP digital signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

[Reproducible-builds] Bug#800776: cluster-glue: please make the build reproducible

[Reproducible-builds] adding a new PTS keyword (Re: Usefulness of periodic reproducible builds e-mails

[Reproducible-builds] exception found: ftbfs in testing, reproducible in sid (Re: Usefulness of periodic reproducible builds e-mails)

Re: [Reproducible-builds] adding a new PTS keyword (Re: Usefulness of periodic reproducible builds e-mails

[Reproducible-builds] Bug#800808: django-sitetree: FTBFS: AttributeError: module 'html.parser' has no attribute 'HTMLParseError'

[Reproducible-builds] Bug#800810: openslide-python: Missing Build-Depends on python3-pil and libopenslide-dev

[Reproducible-builds] Bug#800809: django-sitetree: FTBFS: AttributeError: module 'html.parser' has no attribute 'HTMLParseError'

[Reproducible-builds] Bug#800797: docbook-utils: please generate reproducible manpages

Re: [Reproducible-builds] adding a new PTS keyword (Re: Usefulness of periodic reproducible builds e-mails

[Reproducible-builds] Bug#800816: plinth: please make the build reproducible

10 matches

Site Navigation

Mail list logo

Footer information