Ximin Luo wrote:
> Axel Beckert:
> > Even "--fuzzy-threshold 0" to disable any "fuzzy-matching" (whatever
> > that is in the context of diffoscope) didn't make a difference.
> >
>
> Actually, the problem is the other way round - control.tar.{g
more existing transitional package
heirloom-mailx.
│ │ │ │ +
│ │ │ │ + -- Axel Beckert Thu, 16 Nov 2017 18:48:45 +0100
│ │ │ │ +
│ │ │ │ aptitude-robot (1.5.2-1) unstable; urgency=medium
│ │ │ │
│ │ │ │* Version 1.5.2 (only bug fixes and documentation updates)
│ │ │ │ + Use mktemp
s (and not weeks) to get this
fix into unstable. But that's just my wish. :-)
Regards, Axel
--
,''`. | Axel Beckert , https://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' |
Hi Mattia,
Mattia Rizzolo wrote:
> On Sat, Oct 28, 2017 at 02:21:37PM +0200, Axel Beckert wrote:
> > Do I understand it correctly that with "Rules-Requires-Root: no" the
> > root:root ownership is only set by dh_builddeb?
>
> Well, by dpkg-deb of course :)
> C
omments on that idea.
> For me, the proper solution is 1) while 2) and 3) are work-arounds and
> hacks. But 2) makes the package build slightly faster and shows a
> higher confidence in the reproducible properties of the package, where
> 3) makes it a bit slower and punts the strip-no
Control: tag -1 - moreinfo + confirmed
Control: found -1 5.4.2-1
Control: found -1 5.3.1-4
Control: retitle -1 zsh: FTBFS with noatime mounts (e.g. on reproducible builds
armhf nodes)
Hi,
Axel Beckert wrote:
> Thorsten Glaser wrote:
> > ../../Test/C02cond.ztst: test failed.
> >
ture currently only lists AOSP as available for
the Hikey960 while you also can get Linaro and "Debian" images for
the Hikey620.
So far for today. More maybe tomorrow.
Regards, Axel
--
,''`. | Axel Beckert , http://people.debian.org/~abe/
: :' :
needed?
As a power supply e.g. this one might suffice:
http://www.pollin.de/shop/dt/MjUyODQ2OTk-/Stromversorgung/Ladegeraete/USB_Ladegeraete/4_fach_USB_Lader_LOGILINK_PA0096_weiss.html
Regards, Axel
--
,''`. | Axel Beckert , http://people.debian.org/~abe/
: :'
r) slightly
modified to my .procmailrc.
Thanks Santiago!
(And yes, reproducible-builds mails go directly in my inbox.)
Regards, Axel
--
,''`. | Axel Beckert , http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096
#x27;s so helpful to quickly notice
which bug reports came in via (which) mailing list and which are ones
for packages I'm interested in.
TIA!
Regards, Axel
--
,''`. | Axel Beckert , http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.or
Hi Daniel,
Daniel Kahn Gillmor wrote:
> On Tue 2016-08-30 06:49:30 -0400, Axel Beckert wrote:
> > Daniel Kahn Gillmor wrote:
> >> However, if your next upload of php-crypt-gpg can't be built or run
> >> against modern versions of GnuPG, then you probably n
en nowadays?
Regards, Axel
--
,''`. | Axel Beckert , http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`-|
ojects runs at full speed.
So IMHO the reproducible builds projects has taken over the task of
reporting FTBFS noticed by rebuilding packages -- independent of being
planned to do so or not.
Regards, Axel
--
,''`. | Axel Beckert , http://people.debian.org/~abe/
: :
turn the same value. :-)
Note to myself: A nice test which often different values is this:
$ perl -E 'say ""x15' | nice -n 20 mp4h | tail -3
Regards, Axel
--
,''`. | Axel Beckert , http://people.debian.org/~abe/
: :' : | Debian D
to determine
> why it's using linux-x86_64 in the build path in that case.
Me neither, sorry.
Regards, Axel
--
,''`. | Axel Beckert , http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6
Hi,
Jérémy Bobbio wrote:
> Axel Beckert:
> > Running
> >
> > $ reprotest 'dpkg-buildpackage -b'
> > ../debian-paketmanagement-buch_0\~2016.06.29_all.deb
> >
> > from a git checkout of commit 5f069a920df4e6f20a8eb9309c20c39ad60e6132
> > un
Hi,
Axel Beckert wrote:
>* What was the outcome of this action?
>
> Two GUI popups from ebook-convert (from the package calibre) moaning
> about non-existent $HOME and hence unreadable $HOME/.config/…
Here's an example of the first of these popups.
Package: diffoscope
Version: 54
Dear Maintainer,
running reprotest (It's there now, yay! :-) over my very recently
accepted package dpmb (from git commit
5f069a920df4e6f20a8eb9309c20c39ad60e6132) with
reprotest 'dpkg-buildpackage -b'
../debian-paketmanagement-buch_0\~2016.06.29_all.deb
caused
Package: reprotest
Version: 0.1
Dear Maintainer,
* What led up to the situation?
Testing my package dpmb with reprotest.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Running
$ reprotest 'dpkg-buildpackage -b'
../debian-paketmanagement-buch_0\~2016.06.
Hi again,
Axel Beckert wrote:
> > It's actually related to the shell...
> >
> > $ touch aD bD cD dD eD AD BD
> > $ dash -c "ls *[a-z]D"
> > aD bD cD dD eD
> > $ bash -c "ls *[a-z]D"
> > aD AD bD BD cD dD eD
&g
!elf! ;-)
> So yes, I guess we can remove this document.
>
> Implemented in git; I'm holding off with a second hasty upload, sorry
> for the first one.
Oh, meh.
Reiner Herrmann wrote:
> On Sun, Jun 26, 2016 at 05:07:54PM +0200, Axel Beckert wrote:
> > I currently f
fail to see why this can catch Embperl::Syntax::POD in one
build, but not in another. IMHO this should happen with every build.
Will investigate.
Regards, Axel
--
,''`. | Axel Beckert , http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org
oducible-builds mailing list back in May:
https://lists.alioth.debian.org/pipermail/reproducible-builds/Week-of-Mon-20160509/005463.html
Regards, Axel
--
,''`. | Axel Beckert , http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`.
Hi again,
Axel Beckert wrote:
> could someone more python-savvy than me have a look at this claim that
> our SOURCE_DATE_EPOCH example for Python on
> https://wiki.debian.org/ReproducibleBuilds/TimestampsProposal#Examples
> is wrong.
>
> The claim is here:
> https://git
- Forwarded message from Brian May -
Date: Tue, 17 May 2016 09:16:36 +1000
From: Brian May
To: Axel Beckert , 824...@bugs.debian.org
Subject: Re: [Python-modules-team] Bug#824266: mkdocs: Please support
SOURCE_DATE_EPOCH specification for build time stamps
Sender: Brian May
Organization: Debian
Hi Brian,
Brian May wrote:
> Axel Beckert writes:
> > mkdocs integrates build time stamps into the documentation it is
> > generating. This makes at least unburden-home-dir no more reproducibly
> > building because it now uses mkdocs to generate HTML documentation at
> &g
Package: mkdocs
Version: 0.15.3-3
Severity: wishlist
User: reproducible-builds@lists.alioth.debian.org
Usertags: timestamps toolchain
Control: affects -1 unburden-home-dir djangorestframework
Hi,
mkdocs integrates build time stamps into the documentation it is
generating. This makes at least unbu
ingful when TL2016 will be released and reach debian.
It actually has reached Debian about a month ago, but just in
Experimental:
https://packages.qa.debian.org/t/texlive-base/news/20160417T170437Z.html
Regards, Axel
--
,''`. | Axel Beckert , http://pe
f what has been tried. Cool!
> So, yes, we are not varying the build path, and we're aware of it :)
Thanks again for all the details. That makes it much easier to
understand the general issue.
Looking forward to what will happen next on that topic. :-)
Regards, Axel
--
le répertoire « /build/libdevel-cover-perl-1.21 »
Meh. Is it really that bad if we also take the build path into
account?
I think also using different build paths would really dig up some real
bugs like the one I fought with last night.
Regards, Axel
--
,''`.
also make the second build
differ in the build directory name to catch such issues.
In case the latter is already done, I'm out of ideas why that package
counts as reproducibly buildable.
Regards, Axel
--
,''`. | Axel Beckert , http://people.debian.or
Hi Holger,
Holger Levsen wrote:
> On Sonntag, 6. März 2016, Axel Beckert wrote:
> > I now wonder if a bunch of Raspberry Pi 3 -- since they have 64-bit
> > CPUs (IIRC an Allwinner A53T) -- would make us able to check
> > reproducible-builds for Debian arm64, too.
>
> a
(IIRC an Allwinner A53T) -- would make us able to check
reproducible-builds for Debian arm64, too.
Regards, Axel
--
,''`. | Axel Beckert , http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA
Hi again,
Axel Beckert wrote:
> > /usr/share/doc/autotools-dev/README.Debian.gz says:
> >
> > >> Do NOT use dh-autoreconf and dh_autotools-dev_* helpers at the same
> > >> time, dh-autoreconf takes care of updating config.sub and
> > >> config.gue
rg/698765
for the bug which argues that the text cited above is not entirely
correct.
Regards, Axel
--
,''`. | Axel Beckert , http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61
clearly related as they emitted the same error.
p4vasp also FTBFS since the recent fltk1.3 upload (#809712), but with
different linking issues.
I concur with the p4vasp maintainer that these issues are likely all
related to each other via #809825 (libfltk1.3-dev: fltk-config setting
hardening fl
Hi,
there seems to be a missing "" on https://diffoscope.org/ behind
the link to http://brew.sh/. Well, actually it's a "" which
behaves like a missing one.
Regards, Axel
--
,''`. | Axel Beckert , http://people.debian.org/~abe/
: :' :
ers of that module won't be happy if canonical=1 is hardcoded
that way, e.g. for (guessed) performance reasons as the above likely
includes sorting which always has an performance impact at some scale.
Regards, Axel
--
,''`. | Axel Beckert , http://people.debian.
Thanks. I'll likely apply the patch once
https://ftp-master.debian.org/new/fte_0.50.2b6-7.html has been accepted.
Regards, Axel
--
,''`. | Axel Beckert , http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R:
I've added some SOURCE_DATE_EPOCH support, I can maybe
get rid of faketime and still get many of the issues fixed. Then
again, in the upload from yesterday I didn't seem to catch all
timestamps inside the documentation fixed.
Regards, Axel
--
,''`. |
d
all chroots are set up the very same way (changes between build1 and
build2 are done at run-time, the underlying chroot is the same)"
He also scheduled a new build of mp4h and it no more FTBFS'ed:
https://reproducible.debian.net/history/mp4h.html
So this was a non-deterministic issue as it see
Regards, Axel
--
,''`. | Axel Beckert , http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`-| 1024D: F067
Hi,
it seems that the Recommends of diffoscope are generated dynamically
and all lost with the upload of version 32. Is this on purpose? If
not, feel free to open a bug report in my name with this mail.
Regards, Axel
--
,''`. | Axel Beckert , http://people.debia
h may not be
> desirable. Having debhelper set POD_MAN_DATE would affect only Debian
> packages, which would be a less controversial change.
Sounds sane to me.
I'd volunteer to implement that in debhelper if there's no opposition.
Regards, Axel
--
,
le
time stamps to that date?
Cc'ing the reproducible builds project as well as the debhelper
maintainers for input.
Regards, Axel
--
,''`. | Axel Beckert , http://people.debian.org/~abe/
: :' : | Debian Developer,
Hi,
Holger Levsen wrote:
> On Dienstag, 31. März 2015, Axel Beckert wrote:
> > So where is the difference between
> >
> > * setting all files in a binary package to the time stamp defined by
> > the package's changelog entry, and
> >
> > * run
log entry's time stamp also includes a time zone.
So where is the difference between
* setting all files in a binary package to the time stamp defined by
the package's changelog entry, and
* running a build under a timezone defined by the package's changelog
entry -- or under UT
eneratedByLaTeX)
Regards, Axel
--
,''`. | Axel Beckert , http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
`-| 4096R: 2517 B724 C5F6
Package: faketime
Version: 0.9.6-3
Severity: important
User: reproducible-builds@lists.alioth.debian.org
Usertags: toolchain timestamps
Control: affects -1 zsh
Dear Daniel,
running faketime in a Jessie or Sid chroot on a Wheezy installation
fails as follows:
# lsb_release -a
No LSB modules are a
Package: perl
Version: 5.20.1-5
User: reproducible-builds@lists.alioth.debian.org
Usertags: toolchain, randomness
Affects: wml
Dear Perl Package Maintainers,
Dear Russ,
> What led up to the situation?
Trying to make my package "wml" building reproducibly:
https://reproducible.debian.net/rb-pkg/w
nas would do that as well. :-)
> The issues I have are a) pulling in 28.8MB on my system, and b)
> introducing an editor that messes with system priorities among editors.
Yeah, here, too...
Regards, Axel
--
,''`. | Axel Beckert , http://people.debian.org/~a
51 matches
Mail list logo
