reproducible builds Debian usertags?

[Mattia Rizzolo]

Hi Paul!

On Sun, Dec 06, 2020 at 06:14:13PM +0800, Paul Wise wrote:
> As part of my efforts to do some QA on Debian usertags, I noticed a few
> typos and other issues with the reproducible builds Debian usertags,
> which I fixed using a script and the attached commands to the bts bot.
> 
> https://salsa.debian.org/pabs/qa/-/compare?from=master&to=usertags

Thank you for doing so!

> I also noticed that the index of bugs is missing several usertags, I've
> included below the missing usertags and bugs/counts for each of them.
> 
> https://tests.reproducible-builds.org/debian/index_bugs.html

Note that the formal explenation for those usertags is at
https://reproducible-builds.org/contribute/#how-to-report-bugs-in-debian
and https://wiki.debian.org/ReproducibleBuilds/UserCategory (though I'm
not sure anymore if they are properly in sync, plus the latter is not
linked anywhere)

>    padding 1: #881231
>    ASLR 1: #881231
>    permissions 1: #858333
>    ordering 2: #825406 #835263
>    kernel 5: #849968 #858152 #884256 #970130 #976071
>    timezones 1: #831583
>    timezone 11: #834537 #835143 #840847 #841532 #841784 #843469 #855909 #872460 #968627 #974911 #976359
> 
> It seems to me that:
> 
>  * ASLR tag should be removed since the bug is about padding/randomness
>  * padding bug should maybe be removed in favour of randomness?

depends on what that padding is about.  If it's due to different lenght
of the build paths, then it should be "buildpath", IMHO.

>  * permissions bug should either stay or maybe move to umask?

umask it is.

>  * timezones bugs should move to timezone

not quite, see below.

>  * ordering bugs should move to fileordering

well, depends.  fileordering is specifically about readdir().  if it's,
say, perl hashes not being ordered, that would be randomeness.

>  * the kernel and timezone bugs should become official

not quite IMHO.  "kernel" is already tracked under "uname", whereas
"timezone" likely falls into "timestamps"

> PS: the typo or other fixes can be done by the usertags-fixes cron job
> automatically if wanted, for now I elected to do them just the once,
> but if they recur then I will notice them via another cron job.

I believe that some of the type you found is safe to fix, but in your
proposal control@ mail I notice an oddity.

> user reproducible-builds at lists.alioth.debian.org
> usertags 848136 - fileorder
> usertags 848136 + fileordering
> usertags 872729 - filesystemordering
> usertags 875700 - filesystemordering
> usertags 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 are good to be pushed from what I see, thank you!

-- 
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/20201206/fcb394ea/attachment.sig>