RBSummit 2022! Tentative planning dates

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 .''`.

Re: hope help reproducible-build to support Debian riscv64 arch

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

Bug#1011635: Diff between {,sticky} Debian binary package fails

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

Re: reproducible-notes: update status of Ada packages

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 .''

Bug#1012318: diffoscope 214 produced no output and was killed after running into timeout after 150m

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:

Bug#1012318: diffoscope 214 produced no output and was killed after running into timeout after 150m

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,

Bug#1012318: diffoscope 214 produced no output and was killed after running into timeout after 150m

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

Re: hope help reproducible-build to support Debian riscv64 arch

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

Re: Please review the draft for June's report

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:

Bug#1019742: reprotest: add a variation that sets DEB_BUILD_OPTIONS=nocheck

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

Re: -ffile-prefix-map option and reproducibility

"-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

Bug#1034504: diffoscope: Wrong binary called for the Procyon Java decompiler

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

stretch is now archived

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

Re: Heads-up: New upstream version of src:file in experimental

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

Re: tests.r-b.o/debian: archiving buster and bullseye

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,

Re: [buildd-tools-devel] Some Debian package upgrades are corrupting rsync "quick check" backups

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

Re: Some Debian package upgrades are corrupting rsync "quick check" backups

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

Re: deprecation of buildinfo.debian.net (NOT buildinfos.debian.net)

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

<    1   2