maintaining reproducible-notes over the long term
Mattia Rizzolo
mattia at debian.org
Fri Dec 18 17:29:22 GMT 2020
On Fri, Dec 18, 2020 at 09:13:21AM -0800, Vagrant Cascadian wrote:
> Ok. It was unclear to me which parts were automated and which parts were
> manual.
Oh, that's very clear. The automated ones are done at midnight UTC and
the commit author says "automatic commit from ..". Everything else is
me doing it by hand! ;)
> > Vagrant: did you perhaps notice that I (manually or automatically?)
> > removed notes for stuff that indeed shouldn't have been removed?
>
> Maybe these all fall into the categories you're saying (although dynare
> isn't reproducible on arm64, due to non-deterministic issues), although
> since they haven't propegated to bullseye yet, I would think it would be
> good to leave them open till the bugs are archived, or at least verified
> fixed in bullseye?
As I mentioned, it's mostly about the comments that I'm acting upon.
Those won't ever be removed manually, so if I see that recent upload
addresses whatever is written in the comments, plus I don't spot
anything else within the note that is not addressed I go ahead and
remove everything.
Why do you believe waiting for the testing migration is useful here? I
can't imagine a package reproducible in unstable but not in testing,
where we are changing _less_ stuff.
> e6adafa12eb7a9f0a9e4d79a4db7b468a5725d50
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/dynare.html
right, but then again, the nondetermism there is not related to what was
written in the note, is it?
One of the reason I remove those notes is that in case of unreproducible
packages they pop up in the "without notes" section(s), i.e.
https://tests.reproducible-builds.org/debian/unstable/amd64/index_no_notes.html
- instead of being drowned in (for example)
https://tests.reproducible-builds.org/debian/unstable/amd64/index_notes.html
> 4ecce9d22a41868b4d0ba2c81e0d25fe81838a2c
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/bowtie2.html
>
> a50358f1fe94ea5d2d62b57a716a3a120ef6aacd
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/cctools.html
these should be fine, did I drop anything that is not by now "obsolete"?
> Or maybe just had different expectations without the background of when
> some of these decisions were made. :)
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 :)
--
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 `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/reproducible-builds/attachments/20201218/6f052a4b/attachment.sig>
More information about the Reproducible-builds
mailing list