Re: [Reproducible-builds] On expiring packages and issues
On Samstag, 17. Oktober 2015, Jérémy Bobbio wrote: > I believe this is done in the monthly reports. _weekly_ (had to correct this, as it's sooo totally awesome that they are weekly! :-) signature.asc Description: This is a digitally signed message part. ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Re: [Reproducible-builds] On expiring packages and issues
Santiago Vila: > On Fri, Oct 16, 2015 at 03:22:34PM +0200, Jérémy Bobbio wrote: > > I think it's sound to also remove issues due to Debian-specific > > toolchain once it has been fixed. I don't think there's much value in > > keeping tabs on something like ordering problems in debhelper the > > required `sort` has been added. > > What do you mean by "Debian-specific"? We have lots of derived distros. > In case they are interested in their own reproducibility, it would be nice > for them that we do not expire issues so happily. Good point. > We are not even tracking anywhere which version fixed the different > issues. I believe this is done in the monthly reports. -- Lunar.''`. lu...@debian.org: :Ⓐ : # apt-get install anarchism `. `'` `- signature.asc Description: Digital signature ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Re: [Reproducible-builds] On expiring packages and issues
On Fri, Oct 16, 2015 at 03:22:34PM +0200, Jérémy Bobbio wrote: > I think it's sound to also remove issues due to Debian-specific > toolchain once it has been fixed. I don't think there's much value in > keeping tabs on something like ordering problems in debhelper the > required `sort` has been added. What do you mean by "Debian-specific"? We have lots of derived distros. In case they are interested in their own reproducibility, it would be nice for them that we do not expire issues so happily. We are not even tracking anywhere which version fixed the different issues. ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Re: [Reproducible-builds] On expiring packages and issues
Santiago Vila: > On Fri, Oct 16, 2015 at 01:40:22PM +0200, Jérémy Bobbio wrote: > > I would say that it's better to keep any issue which other free software > > projects might bump into. > > Agreed. > > > I know it's far from a clear guideline. In any > > cases, we have the history, as Holger said. > > I'd like to avoid having to recover an old issue from git history, if > possible. > > So I propose this simple guideline to remove issues: Do it only when > they were due to bugs in our CI. I think it's sound to also remove issues due to Debian-specific toolchain once it has been fixed. I don't think there's much value in keeping tabs on something like ordering problems in debhelper the required `sort` has been added. -- Lunar.''`. lu...@debian.org: :Ⓐ : # apt-get install anarchism `. `'` `- signature.asc Description: Digital signature ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Re: [Reproducible-builds] On expiring packages and issues
On Fri, Oct 16, 2015 at 01:40:22PM +0200, Jérémy Bobbio wrote: > I would say that it's better to keep any issue which other free software > projects might bump into. Agreed. > I know it's far from a clear guideline. In any > cases, we have the history, as Holger said. I'd like to avoid having to recover an old issue from git history, if possible. So I propose this simple guideline to remove issues: Do it only when they were due to bugs in our CI. For example, I was going to add an issue like this: hardlink_becomes_regular_file hardlinks in build1 become regular files in build2 but in the end I decided that it was better to reschedule the affected packages. This issue was probably an artifact of disorderfs, and it is an example of the kind of issue that I would consider safe to remove (or even desirable, for cleanup). ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Re: [Reproducible-builds] On expiring packages and issues
On Fri, Oct 16, 2015 at 01:15:33PM +0200, Holger Levsen wrote: > On Freitag, 16. Oktober 2015, Santiago Vila wrote: > > Hi. Do we expire issues (not packages) when no package currently have them? > > https://reproducible.debian.net/index_issues.html -> scroll down to the > bottom. I think you refer to this: Notes are stored in notes.git and are targeted at packages in 'unstable/amd64' (unless they say otherwise). However, issues are not really "targeted" as such. They are just properties that packages may or may not have. It's the specific note in packages.yml for a specific package version what is really targeted. ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Re: [Reproducible-builds] On expiring packages and issues
Holger Levsen: > On Freitag, 16. Oktober 2015, Santiago Vila wrote: > > Hi. Do we expire issues (not packages) when no package currently have them? > > https://reproducible.debian.net/index_issues.html -> scroll down to the > bottom. > > > (I would prefer to keep them). > > it depends, i'd say. they also stay in git history. Packages we definitly > remove once they are fixed or removed from sid. I would say that it's better to keep any issue which other free software projects might bump into. I know it's far from a clear guideline. In any cases, we have the history, as Holger said. -- Lunar.''`. lu...@debian.org: :Ⓐ : # apt-get install anarchism `. `'` `- signature.asc Description: Digital signature ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Re: [Reproducible-builds] On expiring packages and issues
Hi, On Freitag, 16. Oktober 2015, Santiago Vila wrote: > Hi. Do we expire issues (not packages) when no package currently have them? https://reproducible.debian.net/index_issues.html -> scroll down to the bottom. > (I would prefer to keep them). it depends, i'd say. they also stay in git history. Packages we definitly remove once they are fixed or removed from sid. cheers, Holger signature.asc Description: This is a digitally signed message part. ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] On expiring packages and issues
Hi. Do we expire issues (not packages) when no package currently have them? (I would prefer to keep them). Thanks. ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
