On 2015-07-27, Vagrant Cascadian wrote:
> The current specs:
>
> bpi0-armhf-rb.debian.net:
> Banana PI, dual-core, 1GB ram, ~20GB mSATA.
> ssh port:
> ssh fingerprints:
> 2048 8f:0a:d0:77:a8:59:c0:bb:d0:76:de:14:13:5b:a6:56 (RSA)
> 256 af:b4:13:04:21:30:46:b3:e8:79:ff:7d:99:20:86:f0 (ECDSA)
>
Source: ruby-omniauth-github
Version: 1.1.2-1
Severity: serious
Tags: sid stretch
Justification: fails to build from source
User: reproducible-builds@lists.alioth.debian.org
Usertags: ftbfs
Dear Maintainer,
The package fails to build:
1) OmniAuth::Strategies::GitHub client options should have
Source: ruby-org
Version: 0.9.1-2
Severity: serious
Tags: sid stretch
Justification: fails to build from source
User: reproducible-builds@lists.alioth.debian.org
Usertags: ftbfs
Dear Maintainer,
The package fails to build:
2) Orgmode::Headline should understand a single tag
Failure/Error:
Source: ruby-mocha
Version: 1.1.0-1
Severity: serious
Tags: sid stretch
Justification: fails to build from source
User: reproducible-builds@lists.alioth.debian.org
Usertags: ftbfs
Dear Maintainer,
The package fails to build:
Finished in 0.775961s, 796.4319 runs/s, 1177.8945 assertions/s.
1) F
Source: ruby-multi-xml
Version: 0.5.5-1
Severity: serious
Tags: sid stretch
Justification: fails to build from source
User: reproducible-builds@lists.alioth.debian.org
Usertags: ftbfs
Dear Maintainer,
The package fails to build:
Failures:
1) MultiXml LibXML parser behaves like a parser .parse
Source: ruby-mkrf
Version: 0.2.3+dfsg-5
Severity: serious
Tags: sid
Justification: fails to build from source
User: reproducible-builds@lists.alioth.debian.org
Usertags: ftbfs
Dear Maintainer,
The package fails to build:
In file included from /usr/include/ruby-2.1.0/ruby/encoding.h:23:0,
Source: ruby-mercenary
Version: 0.3.4-1
Severity: serious
Tags: sid stretch
Justification: fails to build from source
User: reproducible-builds@lists.alioth.debian.org
Usertags: ftbfs
Dear Maintainer,
The package fails to build:
Failures:
1) Mercenary::Option compares itself with other option
Source: ruby-messagebus-api
Version: 3.0.7+git.20130130.97b34ece-1
Severity: serious
Tags: sid
Justification: fails to build from source
User: reproducible-builds@lists.alioth.debian.org
Usertags: ftbfs
Dear Maintainer,
The package fails to build:
FFF..FF
Failures:
1)
Source: ruby-merb-assets
Version: 1.1.3-2
Severity: serious
Tags: sid
Justification: fails to build from source
User: reproducible-builds@lists.alioth.debian.org
Usertags: ftbfs
Dear Maintainer,
The package fails to build:
/usr/bin/ruby2.1 /usr/bin/rspec --pattern ./spec/\*_spec.rb
~ No Gemfil
On Fri, Jul 31, 2015 at 11:14:51AM +, Mattia Rizzolo wrote:
> If the point is finding out whether the package FTBFS or not I suggest looking
> at https://wiki.debian.org/qa.debian.org/ArchiveTesting (even if the results
> are presented in a less shiny format than ours)
No, the point is that if
Source: ruby-mail
Version: 2.6.1+dfsg1-1
Severity: serious
Tags: sid
Justification: fails to build from source
User: reproducible-builds@lists.alioth.debian.org
Usertags: ftbfs
Dear Maintainer,
The package fails to build:
Failures:
1) Utilities Module token safe checking should return true if
Source: ruby-literati
Version: 0.0.4~git.20130318.3b3ea30-2
Severity: serious
Tags: sid stretch
Justification: fails to build from source
User: reproducible-builds@lists.alioth.debian.org
Usertags: ftbfs
Dear Maintainer,
The package fails to build:
/usr/bin/ruby2.1 -I"lib:lib:test" -I"/usr/lib/r
Source: ruby-jwt
Version: 1.0.0-2
Severity: serious
Tags: sid
Justification: fails to build from source
User: reproducible-builds@lists.alioth.debian.org
Usertags: ftbfs
Dear Maintainer,
The package fails to build:
/usr/bin/ruby2.1 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb
.
Source: ruby-jsonify
Version: 0.4.1-2
Severity: serious
Tags: sid stretch
Justification: fails to build from source
User: reproducible-builds@lists.alioth.debian.org
Usertags: ftbfs
Dear Maintainer,
The package fails to build:
/usr/bin/ruby2.1 /usr/bin/rspec --pattern ./spec/\*_spec.rb
.
Source: ruby-haml-magic-translations
Version: 4.0.3-2
Severity: serious
Tags: sid
Justification: fails to build from source
User: reproducible-builds@lists.alioth.debian.org
Usertags: ftbfs
Dear Maintainer,
The package fails to build:
..poparser.ry:244: warning: IO#lines is deprecated; use #each
Hi,
This week I finished my work on ghostscript: I updated the ghostscript
patch I was working on last week to match newest version (9.15~dfsg-1).
In the version update, some patched files where moved and now the
Document ID generated by ghostscript uses localtime so I replaced the
function by gp_
Source: cortado
Version: 0.6.0-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 cortado could not be bui
Source: whizzytex
Version: 1.3.2-1.3
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 whizzytex could not
Hi!
On Fri, 2015-07-31 at 16:49:13 +0200, Holger Levsen wrote:
> so yesterday I tried to build
> http://reproducible.alioth.debian.org/debian/dpkg_1.18.1.0~reproducible5.dsc
> with pbuilder on sid/armhf and that failed _exactly_ like
> https://reproducible.debian.net/rbuild/unstable/amd64/dpkg_
Source: cdbs
Version: 0.4.130
Severity: wishlist
Tags: patch
User: reproducible-builds@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org
Hi!
The Debian reproducible builds team [1] recently proposed a new
environment variable $SOURCE_DATE_EPOCH
Hi,
so yesterday I tried to build
http://reproducible.alioth.debian.org/debian/dpkg_1.18.1.0~reproducible5.dsc
with pbuilder on sid/armhf and that failed _exactly_ like
https://reproducible.debian.net/rbuild/unstable/amd64/dpkg_1.18.1.0~reproducible5.rbuild.log
I then tried to build dpkg_1.18.
Source: zipios++
Version: 0.1.5.9+cvs.2007.04.28-5.1
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 zipi
Source: libsyncml
Version: 0.5.4-2.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 libsyncml could not
Hi,
On Freitag, 31. Juli 2015, Mattia Rizzolo wrote:
> [...] We already vary a lot of stuff between builds, and soon we'll vary
> even more (the date).
>
> For what I'm concerned we should defer more variation once more patches
> land in the archive
I disagree, the more we know, the better. I al
On Fri, Jul 31, 2015 at 12:56:32PM +0200, Holger Levsen wrote:
> Hi Clint,
>
> On Freitag, 31. Juli 2015, Clint Adams wrote:
> > I suggest comparing builds with and without the Recommends of the
> > Build-Depends installed.
>
> I think thats out of scope for our project currently: buildds don't i
Hi Clint,
On Freitag, 31. Juli 2015, Clint Adams wrote:
> I suggest comparing builds with and without the Recommends of the
> Build-Depends installed.
I think thats out of scope for our project currently: buildds don't install
recommends, so we also don't install them.
It's probably still worth
On 31/07/15 07:25, Chris Packham wrote:
> The problem is that date -u implies UTC. So + is right if you do
> want the time to be displayed in UTC (for me living at +12/+13 UTC
> makes my head hurt because all the dates are yesterday).
>
One of the main problems with human-readable date/time i
Your message dated Fri, 31 Jul 2015 11:53:17 +0200
with message-id <20150731095317.GA32590@loar>
and subject line Re: Bug#789003: debbindiff: should not try to create device
files
has caused the Debian Bug report #789003,
regarding debbindiff: should not try to create device files
to be marked as
Your message dated Fri, 31 Jul 2015 09:34:30 +
with message-id
and subject line Bug#785777: fixed in debbindiff 27
has caused the Debian Bug report #785777,
regarding debbindiff: hexdump output when text encoding of file has changed
to be marked as done.
This means that you claim that the pro
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 31 Jul 2015 08:38:10 +
Source: debbindiff
Binary: debbindiff
Architecture: source all
Version: 27
Distribution: unstable
Urgency: low
Maintainer: Reproducible builds folks
Changed-By: Jérémy Bobbio
Descripti
debbindiff_27_amd64.changes uploaded successfully to localhost
along with the files:
debbindiff_27.dsc
debbindiff_27.tar.gz
debbindiff_27_all.deb
Greetings,
Your Debian queue daemon (running on host franck.debian.org)
___
Reproducible-bui
debbindiff_27_amd64.changes uploaded successfully to ftp-master.debian.org
along with the files:
debbindiff_27.dsc
debbindiff_27.tar.gz
debbindiff_27_all.deb
Greetings,
Your Debian queue daemon (running on host coccia.debian.org)
___
Repr
32 matches
Mail list logo
