Ximin Luo wrote on Thu, Nov 10, 2016 at 18:55:00 +:
> Holger Levsen:
> > I'm sorry if this sounds dismissive, but this thread (and evaluation)
> > has shown me, that being decentralised is not a feature I desire in a
> > tracker, on the contrary, it seems that decentralised has downsides
> > ma
On 2016-11-10 11:33, Ian Jackson wrote:
> Cyril Brulebois writes ("Re: misleading timestamps in binnmus"):
> > Ian Jackson (2016-11-09):
> > > What version of sbuild do buildds run ? Ie, supposing that this is
> > > fixed in sbuild in stretch, will this be fixed on the buildds ? Or do
> > > we n
Package: sbuild
Version: 0.72.0-2
Severity: wishlist
X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org
Now that dpkg-buildpackage generates .buildinfo files by default, it
would be nice if sbuild included them in the build log like it does for
the .changes file and the binary package conte
Hi,
actually forwarding this to the bug.
And adding a small note that since August we now have
buildinfo.debian.net, so maybe for a start it would be sufficient if dak
would submit these .buildinfo files via curl/https to buildinfo.d.n!?!
- Forwarded message from Ximin Luo -
Date: Wed,
Holger Levsen:
> Hi,
>
> I'm sorry if this sounds dismissive, but this thread (and evaluation)
> has shown me, that being decentralised is not a feature I desire in a
> tracker, on the contrary, it seems that decentralised has downsides
> making me wish for a centralized tracker which I can use wi
Package: dpkg-dev
Version: 1.18.13
Severity: important
Dear Maintainer,
We would like dpkg-buildpackage to clearsign the buildinfo files that are
created. This allows them to be uploaded to services similar to keyservers,
for auditing and attestation purposes, that may be run independently of the
Hi,
On Thu, Nov 03, 2016 at 05:47:17PM +, Mattia Rizzolo wrote:
> This thread doesn't seem to make progress, anyway:
(it was still on my to-reply list…)
> On Tue, Oct 18, 2016 at 09:54:39PM +, Mattia Rizzolo wrote:
> > 4. figure out why the hell DDPO doesn't deal with that edit in the j
Hi,
I'm sorry if this sounds dismissive, but this thread (and evaluation)
has shown me, that being decentralised is not a feature I desire in a
tracker, on the contrary, it seems that decentralised has downsides
making me wish for a centralized tracker which I can use with a
webbrowser.
(or someo
Hi Adrian,
On Sun, Nov 06, 2016 at 09:38:24PM +0200, Adrian Bunk wrote:
> could you change the reproducible builds to find bugs like #843433,
probably, yes. I've added it to our TODO yesterday…
> ideally with a rebuild of everything that is currently building
> reproducibly?
if, I'd implement
Chris Lamb wrote on Thu, Nov 10, 2016 at 16:09:51 +:
> Daniel Shahaf wrote:
>
> > Revised to avoid the Python '_ variable' idiom as per feedback on IRC.
>
> Did you see:
>
Yes I did, but I didn't know (when I submitted the patch) that Holger
had been convinced by that.
> I highly recommend
Hi Daniel,
On Thu, Nov 10, 2016 at 03:58:14PM +, Daniel Shahaf wrote:
> Revised to avoid the Python '_ variable' idiom as per feedback on IRC.
> Also available as:
> git fetch ssh://git.debian.org/~danielsh-guest/src/jenkins.debian.net
> 5ec252e861de
thanks! took your patch now, just rew
On Mon, Nov 07, 2016 at 06:11:36PM -0500, Daniel Kahn Gillmor wrote:
> What if we only included the .buildinfo differences (clearly demarcated)
> if there was other stuff which should be fixed? And if nothing needs to
> be fixed, then don't show the buildinfo differences. That strikes me as
> pot
Daniel Shahaf wrote:
> Revised to avoid the Python '_ variable' idiom as per feedback on IRC.
Did you see:
< lamby > _ is really common (and useful) for deliberately pointing
out that you aren't going to use the variable.
< lamby > Especially useful as things like pylint will say "
---
Revised to avoid the Python '_ variable' idiom as per feedback on IRC.
Also available as:
git fetch ssh://git.debian.org/~danielsh-guest/src/jenkins.debian.net
5ec252e861de
Cheers,
Daniel
bin/reproducible_common.py| 6 ++
bin/reproducible_html_pkg_sets.py | 7 ++-
2 fi
Johannes Schauer:
> Hi,
>
> On Thu, 10 Nov 2016 05:54:13 -0200 Johannes Schauer wrote:
>> On Tue, 02 Aug 2016 22:49:00 +0200 Johannes Schauer wrote:
>>> But then on IRC, HW42 suggested to approach this problem differently.
>>> Instead of integrating the functionality of figuring out the right
>>
Hi,
On Thu, 10 Nov 2016 05:54:13 -0200 Johannes Schauer wrote:
> On Tue, 02 Aug 2016 22:49:00 +0200 Johannes Schauer wrote:
> > But then on IRC, HW42 suggested to approach this problem differently.
> > Instead of integrating the functionality of figuring out the right
> > repositories to reprodu
Hi,
Quoting Niko Tyni (2016-11-10 10:01:38)
> On Thu, Nov 10, 2016 at 10:34:33AM +, Holger Levsen wrote:
> > can someone please point at a real life/archive example of such a file?
> > (a binNMU .changes file with Binary-Only-Changes field…)
>
> That's in the .buildinfo file (not .changes), a
Source: haskell-cabal-install
Version: 1.24.0.1-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,
haskell-cabal-install fails to build from sour
Chris Lamb wrote:
> koji fails to build from source in unstable/amd64:
I can no longer reproduce this in today's sid so closing.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
___
Your message dated Thu, 10 Nov 2016 13:12:37 +
with message-id
<1478783557.3755462.783487289.13561...@webmail.messagingengine.com>
and subject line Re: koji: FTBFS: help2man: can't get `--help' info from
./cli/koji
has caused the Debian Bug report #843797,
regarding koji: FTBFS: help2man: can
On Thu, Nov 10, 2016 at 10:34:33AM +, Holger Levsen wrote:
> On Thu, Nov 10, 2016 at 08:24:38AM -0200, Johannes Schauer wrote:
> > > I certainly hope it's part of the .buildinfo file as well, else, for
> > > reproducing binNMUs we would also need to store the .changes files in an
> > > easily a
Cyril Brulebois writes ("Re: misleading timestamps in binnmus"):
> Ian Jackson (2016-11-09):
> > What version of sbuild do buildds run ? Ie, supposing that this is
> > fixed in sbuild in stretch, will this be fixed on the buildds ? Or do
> > we need to update jessie, or what ?
>
> sbuild on bui
Johannes Schauer writes ("Re: sbuild should use build date as binnmu changelog
date"):
> While "Pkg Start Time" might be a good default, I guess for to be able to
> reproduce a binNMU it would be necessary to also allow the user to pass a
> custom timestamp.
Not only a custom timestamp (although
Source: salt-formula-ceilometer
Version: 2016.4.1-3
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,
salt-formula-ceilometer fails to build from
Source: trash-cli
Version: 0.12.9.14-2
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,
trash-cli fails to build from source in unstable/amd64:
Source: photofloat
Version: 0~20120917+dfsg-3
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,
photofloat fails to build from source in unstable/
On Thu, Nov 10, 2016 at 08:24:38AM -0200, Johannes Schauer wrote:
> > I certainly hope it's part of the .buildinfo file as well, else, for
> > reproducing binNMUs we would also need to store the .changes files in an
> > easily accessable manner… (which we plan to do for .buildinfo files, but
> > no
Hi,
Quoiting Holger Levsen (2016-11-10 07:48:33)
> On Thu, Nov 10, 2016 at 10:38:45AM +0100, Emilio Pozuelo Monfort wrote:
> > > I see. And this changelog.$arch is neither part of the source package,
> > > the .changes file nor the .buildinfo file, it's just included in the
> > > binary packages?
On Thu, Nov 10, 2016 at 10:38:45AM +0100, Emilio Pozuelo Monfort wrote:
> > I see. And this changelog.$arch is neither part of the source package,
> > the .changes file nor the .buildinfo file, it's just included in the
> > binary packages? Or is it also part of the .changes file?
> It's in .change
On 10/11/16 10:33, Holger Levsen wrote:
> On Thu, Nov 10, 2016 at 10:01:55AM +0100, Emilio Pozuelo Monfort wrote:
>> These days, a changelog entry is added to a changelog.$arch. This is to avoid
>> problems when co-installing ma:same packages, as the changelog entries
>> will/may
>> differ between
On Thu, Nov 10, 2016 at 10:01:55AM +0100, Emilio Pozuelo Monfort wrote:
> These days, a changelog entry is added to a changelog.$arch. This is to avoid
> problems when co-installing ma:same packages, as the changelog entries
> will/may
> differ between different architectures.
I see. And this cha
On 10/11/16 00:53, Wouter Verhelst wrote:
> On Tue, Nov 08, 2016 at 10:41:09PM +, Ian Jackson wrote:
>> Is this a recommended recipe ? AIUI a buildd doing a binnmu will not
>> modify the debian/changelog file.
>
> Are you sure? When last I checked, this was not true (it may have
> changed sin
32 matches
Mail list logo
