On Sun, 2018-07-01 at 17:41 +0200, Johannes Schauer wrote: > I'm unsure whether the sbuild build log is the right place for this. Look at > it > this way: .changes and .buildinfo are part of the log because they are the > *output* of running sbuild. The .dsc is the *input* for sbuild. Thus, whoever > runs sbuild already has a .dsc and does not need the build log to contain a > copy of it.
The build log is the one place that input and output are connected. Thus I think that is one place both input and output should be logged. > In your case, the buildd has the dsc and thus the actual problem seems to be, > that it is currently hard to retrieve the .dsc that was used from > buildd.debian.org. In my case the buildd has the dsc but buildd.debian.org does not, because the buildd admin created it on the buildd instead of using the dsc that buildd.debian.org sent to the buildd. > Thus, I suggest that you rather convince the maintainers of buildd.debian.org > to make it easier to find out what they were feeding sbuild with. buildd.debian.org never had the dsc that the buildd used to build the package so it cannot provide this feature in this case. I agree that it would be useful to have the log of the build requests that were sent to buildds include more information about the source. > Do you agree? Given the above, I do not agree. -- bye, pabs https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
