Re: [Reproducible-builds] How to react on "the second build failed, even though the first build was successful" ?

Hi, most often packages fail to do the 2nd build because they cannot deal with UTF-8 locales, which we have enabled in the 2nd but not the 1st build. See https://reproducible.debian.net/reproducible.html#variation to learn how 1st+2nd build differ. cheers, Holger signature.asc

Re: [Reproducible-builds] How to react on "the second build failed, even though the first build was successful" ?

Hi Thomas, On Montag, 14. Dezember 2015, Thomas Schmitt wrote: > The warning is still on display at > https://tracker.debian.org/pkg/libisoburn > No new attempt of building is shown on > https://reproducible.debian.net/rb-pkg/unstable/amd64/libisoburn.html I've triggered a test of libisoburn

Re: [Reproducible-builds] How to react on "the second build failed, even though the first build was successful" ?

Hi, > I've triggered a test of libisoburn in unstable/amd64 Sunshine ! One stain less on the package. Have a nice day :) Thomas ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org

Re: [Reproducible-builds] How to react on "the second build failed, even though the first build was successful" ?

On Sat, Dec 12, 2015 at 6:14 PM, Chris Lamb wrote: > I've lost my scrollback apologies but IIRC it wasn't anything beyond > acknowledgement of the issue which I felt was enough to share with Thomas to > prevent him thinking it was "his" issue to debug. OK, no problem. I was

Re: [Reproducible-builds] How to react on "the second build failed, even though the first build was successful" ?

On Fri, Dec 11, 2015 at 11:09 PM, Chris Lamb wrote: > There is some issue (discussed on IRC earlier) with the second build Is this IRC discussion archived somewhere? If not, could you summarize it on the mailing list? ___

Re: [Reproducible-builds] How to react on "the second build failed, even though the first build was successful" ?

Hi Thomas, Thanks for getting in touch. Replying quickly so we don't use up too much of your time: > "dpkg-buildpackage: binary-only upload (no source included)" There is some issue (discussed on IRC earlier) with the second build so, in this case, there is nothing to react to - the above