I also think that experiment is over, if anything because it turns out that
our original concept never really took flight.
I'm always a big fan of "eternal archival", so I'd say to keep it
somewhere, possibly tougher with the original code of the service and a bit
of accompanying text. Just how b
t, 24
Dec 2016) after a fairly long and annoying discussion in debian-devel:
* For binNMUs, instead of copying the timestamp of the last changelog entry,
generate a new one (closes: #843773)
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B
the timestamp of the last changelog entry,
generate a new one (closes: #843773)
In version 0.73.0-1.
> b) Will this affect stretch? If so, what do we need to do now?
Yes.
IMHO, nothing.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B94
stay in the postgresql database,
> and I will also backup the generated diffoscope diffs, though on
> a different host.
That's already done, but the old data are still on jenkins. what were
you thinking about? I don't think the stretch tarball takes too much
space?
--
regards,
ght for diffscope.
I'd say go ahead. I'm currently at DebCamp so I can handle problems, as
well as my collegues we are normally fairly fast in handling this kind
of regressions. :)
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B9
he json is also kept outside of the backup at
https://tests.reproducible-builds.org/debian/stretch/reproducible.json.bz2
o/
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More about
decompiler":
https://salsa.debian.org/reproducible-builds/diffoscope/-/commit/d7ec9965e12efb76d88b8423cebccc59f53118d8
Can you please give us more informations on what you are experiencing,
or are you just notifying us of that stackoverflow post?
--
regards,
Mattia
"-O2 -fno-strict-aliasing -fwrapv -pthread
-fPIC -g -O2 -ffile-prefix-map=/build/ocaml-xz3WL7/ocaml-4.13.1=.
-fstack-protector-strong -Wformat -Werror=format-security");
makes me believe that many options have been stripped out…)
--
regards,
Mattia Rizzolo
G
variations are defined in reprotest/build.py (each variation is a
function) and listed in VARIATIONS.
Then __init__.py will pull them in with some magic.
Overall I don't consider this format particularly programmer-friendly.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A F
covid too, and I hope you are
making some swift recovery!
Also thank you for working on this while down as well!
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More about me:
blocker for testing migration,
Ahem, I'd really love if that was the case, but it really isn't at the
moment.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
Mor
s reaching the
> timeout in the first place. (For instance, improving the overall
> speed of ELF handling.)
But I agree with this, so my musing above are probably better discarded
at this time, and consider this bug closed :)
--
regards,
Mattia Rizzolo
to treat TERM
(and/or probably other signals too?) in a way that makes it at least
terminating its current task (i.e. killing subprocesses, and start to
render the output). But indeed, should diffoscope really do that?
Overall, I agree we don't have a bug here.
--
regards,
han 6 minutes. If somebody looks into the point above
I can change jenkins to wait 12 minutes (or 18) before KILLing after the
TERM signal.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More about me:
Actually IIRC I should have already configured the repository in a way
that all DD can freely push to it! :)
So yes, please do go ahead directly for such simple changes!
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''
7;s not actually an
attribute of the file but rather of the underlying file system.
That said, changing all regex with have to prepend
'(?:(?:setuid|setgid|sticky) )?' or such feels… suboptimal :)
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18
ins.debian.net/userContent/thanks.html, with that much we
are hanging on, and we don't really have much spare resources, so we'd
need something on a similar scale.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540
ou'd rather not make your
schedule public.
Also, please consider forwarding this email to anybody you think might
be interested!
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
cially?) when a build fails.
I tried to talk with Guillem about this some months ago (to see if dpkg
could/should be involved), but then I dropped the ball.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944
we
don't keep build old logs so I can't confirm.
I can also add that the very same couple of builders was successfully
used to build this package on 2021-10-29, and AFAIK since then nothing
interesting happend on our infrastracture.
--
regards,
Mattia Rizzolo
(just dumping a quick point else I'm sure I'll forget by the time I get to
this mail when on the computer..)
A build process really must not create random files in HOME, and possibly
not even try to access them...
If having a nonexistent home dir (which... Isn't the case of boh default
pbuilder a
t I expect, and which is what I see in, say, the amd64
build.
> The first run retrieves the inventories just fine, the second run
> always fails. This then leads to sphinx generating different output,
> causing the reproducibility failure.
Well, it's a RC bug even trying to do that
raph on my thoughts about the potential solutions; I'm
happy to implement what you think would be best.
On Fri, Oct 08, 2021 at 12:07:36PM +0200, Mattia Rizzolo wrote:
> Source: acorn
> Version: 8.0.5+ds+~cs19.19.27-3
> Severity: serious
> Control: fixed -1 8.5.0+ds+~cs23.9.6-2
&g
t* DEB_BUILD_OPTIONS in d/rules. Instead, they
should set DEB_BUILD_MAINT_OPTIONS, which (according to
dpkg-buildflags(1)) overrides DEB_BUILD_OPTIONS by also merging its
non-conflicting values.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B0
onfig` complains about `FATAL: kernel too old` and aborts the build.
|
| Avoid sudo(1) password prompts
| ==
Besides potentially better identifying which versions of ldconfig are
effectively broken, I don't think we could do much else.
--
regards,
Mattia Rizzolo
salsa.debian.org/lucas/collab-qa-tools/-/merge_requests/12
with a script that, as I expect, should be enough to run this test.
It's similar in spirit on how vagrant run the last test rebuild,
`sed`ing a "live" file instead of providing a patched package, as I
understand that's a
ak quite a few things here and there. Rather, it
would be perfect for aws' comparative rebuilds. Now, who is the
contact for those these days?
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More about me:
them.
Thank you for handling the addition of bookworm!
Hopefully it was easy enough to follow what we did last time with
buster.
Shall we officially drop stretch now? (perhaps move them to some r/o
place, or drop the completely?)
--
regards,
Mattia Rizzolo
GPG Key: 66AE
pe shouldn't crash, just the
timeout wrapper exiting.)
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More about me: https://mapreri.org : :' :
Launchpad user: https
it would need an explicit
unblock as it's a key package (being in the pseudo-build-essential set).
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More about me: https://mapreri.org
s independent of timezone (it might be fine as is).
>
> Sure
Incidentally, instead of using SOURCE_DATE_EPOCH, please also double
check if you couldn't just get rid of the timestamp at all.
In my experience most timestamps are just useless and don't really
provide anything valuable, so
heck before running it
:)
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
how stuff build with cmake get a full path in there,
whereas stuff built with make gets a path relative to the Makefile.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More about me: https://mapreri
with the notes (not just clean-notes and edit-notes)
hardcode "amd64" and look only at that (indeed the note pages do say
"Our notes […] are targeted at packages in Debian in 'unstable/amd64'
(unless they say otherwise).").
--
regards,
Mattia Ri
de. :)
That might be so, but I'm very much willing to adapt what I do to much
your expectations. If you believe I am losing data let's try to figure
a way to help me figure it out so that I won't do that anymore, while at
the same time try to somehow keep the notes a tad tidier :)
-
ically?)
removed notes for stuff that indeed shouldn't have been removed?
> I just don't remember where exactly they live... Mattia?
That's `clean-notes` in reproducible-misc.git :)
--
regards,
Mattia Rizzolo
GPG K
gs 875704 - filesystemordering
> usertags 872729 + filesystem
> usertags 875700 + filesystem
> usertags 875704 + filesystem
> thanks
these should all be "fileordering", the later "filesystem" is bogus.
did you find it somewhere?
All the others
k you for your comments!
We'll get it sorted soon! For tracking porpuses, I copied your mail
here:
https://salsa.debian.org/reproducible-builds/diffoscope/-/issues/224
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540
ays) agree, I can take care of doing the needing packaging
changes.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More about me: https://mapreri.org : :' :
Launchpad use
054689>
> Covenant Concepts <https://covenantconcepts.org/>
> ___
> Reproducible-builds mailing list
> Reproducible-builds@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/reproducible-builds
--
regards,
On Thu, Sep 10, 2020 at 02:14:57PM +0200, Aurelien Jarno wrote:
> On 2020-09-10 11:58, Holger Levsen wrote:
> > Hi,
> >
> > On Thu, Sep 10, 2020 at 01:45:31PM +0200, Mattia Rizzolo wrote:
> > > On Wed, Sep 09, 2020 at 11:01:01AM +0200, Aurelien Jarno wrote:
> >
o give the policy-rcd-declarative
maintainer some context without being shoved a bugload of comments ^^
https://bugs.debian.org/970027
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More about me: https://m
age (which, IMHO,
src:policy-rcd-declarative could do, i.e. provide a
"policy-rcd-declarative-deny-all" binary; or do fancy things with a
debconf option sbuild-craetechroot could inject but that would be too
dirty for me).
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B
will
> still be there and it might affect other packages.
sigh, apparently it still timeouts :(
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More about me: https://mapreri.org : :' :
L
his means it can very easily cause shifts in the compiled binaries even
after stripping (see the very recent bug open against debhelper to avoid
saving RPATH when using cmake).
Such thing won't happen during regular rebuilds, as the build path
lenght is usually the same even when slighly different, and
good idea).
I know I tried to catch Josh attention via IRC in the past, but he was
also basically lost on how to tackle this matter.
In the latter case, it would basically mean that Aurelien and Colin
needs to think together instead.
--
regards,
Mattia Rizzolo
GPG Key:
been a relevant thread in debian-devel a few months back,
spawned off the debian/.build thread started by Niels Thykier.
I'm not quite clear what's the best way forward: I could go and
implement whatever feels best to me in pbuilder, and then hope the rest
of the tooling with catch up
s between architectures.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri
here, please download them today, as they will then be deleted:
https://tests.reproducible-builds.org/debian/artifacts/r00t-me/mariadb-10.3_bullseye_amd64_tmp-bRl4s/
On Mon, Jan 20, 2020 at 12:40 PM Mattia Rizzolo wrote:
> On Sun, Jan 19, 2020 at 11:57:05PM -, Chris Lamb wrote:
> >
build, for an easier start.
And thank you for taking up on Otto's request! :)
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More about me: https://mapreri.org :
Hi,
I just shared the notes repository¹ with the "Debian" group, therefore
giving all DDs write access to it.
It's my attempt to invite more direct contributions instead of MRs :)
¹ https://salsa.debian.org/reproducible-builds/reproducible-notes
--
regards,
to unstable in a week from now.
Thank you for the heads up!
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More about me: https://mapreri.org : :' :
Laun
should make diffoscope non-native.
strip-nd is non-native, and in my experience is so much of a pain to do
a new upstream release that I really don't want to do them anymore...
Compared to that, this one issue with diffoscope is such a triviality
that I can't even start compare them.
--
guess it's safe enough.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `.
ll.
> - Instead of shipping a .cmi file in the source package, generate one
> at build time.
That's https://salsa.debian.org/reproducible-builds/diffoscope/issues/66
and it's somewhat tricky (as the built files have to have the difference
we expect them to).
--
regards,
7;m somewhat
worried about relaxing the check to "just allow all suffixes".
That said, it has also been annoying for ubuntu, where every time they
have to to do a change they also have to tweak this check (usually it's
me so it's not that much of a hassle, but I can see other develo
rgram version.
How can we distinguish the previous squashfs-tools with the new one?
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Lau
dea and should be removed, instead of normalized.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~m
I think the reason we were not varying the length of the build path was
because it can generate huge diffs, as it may translate in offsets all over
the binaries.
I can't imagine any other surprise other than that.
On Fri, 9 Aug 2019, 12:22 am Vagrant Cascadian, <
vagr...@reproducible-builds.org>
to look at.
Indeed, if there are still failing weirdly like glibc was, I'd be
interested in seeing what else they might be missing.
> Clearly, someone, somewhere, and some
> time used "Apple" to refer to this list...
:>
--
regards,
Mattia Rizzo
he conclusion that is the chroot's manager job to provide a useful
/etc/hosts, i.e. pbuilder's job in this case.
https://salsa.debian.org/pbuilder-team/pbuilder/commit/775e8fe1e7c142b14edbd8a19973f03912b548b9
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3
ild (for unstable
only at this time).
Let's see.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri
On Fri, 12 Jul 2019, 6:09 pm Chris Lamb, wrote:
> * DIFFOSCOPE_FAIL_TESTS_ON_MISSING_TOOLS=''
> → Fails; the required version is missing and unlisted.
>
> * DIFFOSCOPE_FAIL_TESTS_ON_MISSING_TOOLS="foo bar"
> → Fails; the required version is missing and unlisted.
>
These shouldn't fai
_TOOLS is not set.
>
> I think we need to add "file" to the DIFFOSCOPE_TESTS_MISSING_TOOLS
> list in debian/tests/pytest. Mattia, can you confirm?
>
>
> Regards,
>
> --
> ,''`.
> : :' : Chris Lamb
> `. `'` la...@debian.org 🍥 chris-lamb.co.
e package pages (as IMHO it's already crowded enough) and keep
everything there, without rebuilding anything anymore)
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more
x27;t
upload a .buildinfo for an arch that you aren't uploading, and humans
can't upload binaries, so you can't upload .buildinfo for binaries at
all).
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
mor
e, I understand that things works like that, I'm just showing a few
design points that could potentially be done differently.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org
x27;} = 'UTC';
@@ -35,7 +35,7 @@
sub _get_file_type($) {
my $file=shift;
open(FILE, '-|') # handle all filenames safely
- || exec('file', $file)
+ || exec('file', '--', $file)
|| die "can't exec file: $!";
iting for SRM
to approve the upload). If it still fails, I'd be interested in the
full log.
For convinience, this is the (unsigned) source package built by me:
https://volatile.mapreri.org/2019-03-21/0626fb90b70be4fe0d8c9b7c59d9af16/diffoscope_78+deb9u1.dsc
indexing is disabled, but `dget
erkill, especially at this point in the buster release cycle…?
>
> Fancy pinging the SRMs on this? Not had to deal with this before.
Cherry-picked the related patches, and uploaded. Also, pu bug opened
for tracking at #925161 .
--
regards,
Mattia Rizzolo
GPG Key: 66A
t
they will approve it directly.
tbh I totally forgot about stretch itself while fixing that bug…
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org
[03:02:13 PM] 2030 josch: one reason for not removing that feature
completely, is that it can be hard to create a .chnages file if all you have
are the .debs, and there are good reason for diffoscope to import the debug
information while running objdump
[03:02:38 PM] 2030 for sure we could at l
p.
I'd propose introducing something to configure at "built time" what
normalizers to disable/enable, coupled with a revert of the change you
mentioned.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .'
t 'filetype from file(1)' == 'dir/text'
E - filetype from file(1)
E + dir/text
tests/comparators/test_zip.py:106: AssertionError
= 1 failed, 11 passed in 1.41 seconds ======
--
regards,
Mattia Rizzolo
GPG Ke
libarchive raises its exception?
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri
r/lib/python3/dist-packages/PyPDF2/generic.py", line 66, in
readObject
return DictionaryObject.readFromStream(stream, pdf)
File "/usr/lib/python3/dist-packages/PyPDF2/generic.py", line 589, in
readFromStream
% (utils.hexStr(stream.tell()), key))
PyPDF2.utils.PdfReadError:
nce.details) > 0
E AssertionError
difference =
fixture= <
/builds/reproducible-builds/diffoscope/tests/data/test1.cmi>
has_details = True
has_null_source = False
monkeypatch = <_pytest.monkeypatch.MonkeyPatch object at 0x7f8e93627e80>
tests/utils/nonexisting.py:32: AssertionErro
#x27;m adding a Build-Conflicts:graphicsmagick-imagemagick-compat to
diffoscope to prevent resolvers from picking up this package, as it
would cause tests to be skipped.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''
BTS,
> including all the magic headers, bug template etc?
> Like the "reply" one existing already on BTS (I'm using it right now, I
> even get quoted message I reply to!).
I just added such a link in https://diffoscope.org/ - what do you all
think? :)
--
regards,
owever.
(now updated)
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri
On Wed, Sep 26, 2018 at 10:50:30PM +0200, Holger Levsen wrote:
> < KGB-1> | Mattia Rizzolo master 4860753 jenkins.debian.net
> bin/reproducible_build.sh * https://deb.li/v57l
> < KGB-1> reproducible debian: enable all the reproducible-related build flags
>
t) to FTBFS.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `
, thanks for tracking this down!
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri
diffoscope to FTBFS with
nocheck… (as v99 did, but nobody noticed).
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad u
2-1~exp3)
ii llvm-7-runtime (1:7~+rc2-1~exp3)
ii llvm-runtime (1:7.0-43ubuntu1)
But I have no reasons to be believe it's ubuntu-specific, so I'm
reporting this bug.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944
the
package is built with nocheck or not.
This accidentally caused the FTBFS of version 100 (about to be
reported).
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more
those :)
I'm not exactly sure how we should handle the various other
@skip_unless_tool_is_* and friends though...
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org :
fs), so it's
harder to check.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri
e build id is something that I've
never seen done anywhere, and I wouldn't be confidend nothing will
notice… To me it seems something that random tools could take as a
given.
And as dkg said, I would find it better to figure what causes it to
vary, rather than hide it :)
--
regards,
=none, given
that the debug symbols are placed next to the build-id? (not sure,
maybe there is a fallback, I haven't actually checked).
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri
I'm supposed to be on vacation!), so I'd need somebody else to
expand that.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :&
ail/reproducible-builds/Week-of-Mon-20180723/010464.html
I'll test diffoscope and if you don't hear from me (in the form of bug
reports), everything is fine ^^
BTW, for diffoscope a test build using the new version of file is enough
of a test (in case you want to just do it yourself :)).
On Tue, Jul 10, 2018 at 10:15:57AM +0200, Mattia Rizzolo wrote:
>
> Thu Jul 5 10:46:13 UTC 2018 I: diffoscope 98 will be used to compare the
> two builds:
> Traceback (most recent call last):
…
> File "/usr/lib/python3/dist-packages/jsondiff/__init__.py", line 491, i
On Tue, Jul 10, 2018 at 03:44:21PM +0200, Mattia Rizzolo wrote:
> On Tue, Jul 10, 2018 at 10:12:45AM +0200, Mattia Rizzolo wrote:
> > AttributeError: 'list' object has no attribute 'items'
> >
> >
> > I can totally reproduce this locally; artifact
On Tue, Jul 10, 2018 at 10:12:45AM +0200, Mattia Rizzolo wrote:
> AttributeError: 'list' object has no attribute 'items'
>
>
> I can totally reproduce this locally; artifacts will be available till
> tomorrow
This is caused by the two attached very small .json
s/jsondiff/__init__.py", line 372, in
_list_diff_0
d, s = self._obj_diff(X[i-1], Y[j-1])
File "/usr/lib/python3/dist-packages/jsondiff/__init__.py", line 491, in
_obj_diff
elif a != b:
RecursionError: maximum recursion depth exceeded in comparison
I don't ha
, line
73, in compare_details
diff = {repr(x): y for x, y in jsondiff.diff(a, b).items()}
AttributeError: 'list' object has no attribute 'items'
I can totally reproduce this locally; artifacts will be available till
tomorrow on
https://tests.reproducible-builds.org/deb
85, in check_int
raise archive_error(args[0], retcode)
File "/usr/lib/python3/dist-packages/libarchive/ffi.py", line 69, in
archive_error
raise ArchiveError(msg, errno(archive_p), retcode, archive_p)
libarchive.exception.ArchiveError: Unrecognized archive format (errno=84,
retc
_magic_signature_files
files += [os.path.join(user_dir, x) for x in os.listdir(user_dir)]
FileNotFoundError: [Errno 2] No such file or directory:
'/var/lib/jenkins/.binwalk/magic'
Interestingly, I couldn't reproduce this locally, so it might have
something to do with the envi
produce them, so I'm thinking
tomorrow to fix up some other things and release nonetheless,
hopefully somebody can look at GitLab CI at another time.
--
regards,
Mattia Rizzolo
GPG Key: 4096R/B9444540 http://goo.gl/I8TMB
more about me: http://mapreri.org
Launchpad User: https://
1 - 100 of 118 matches
Mail list logo
