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 http://lists.alioth.debian.org/cgi-bin/

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, Holger Levsen wrote: > See https://reproducible.debian.net/reproducible.html#variation to learn how > 1st+2nd build differ. The second setup should be no problem. (The use of two different message languages quite devalues the diff, though.) The reason for my post is/was that i cannot spot a

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 Descr

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 just wondering if an

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

> Is this IRC discussion archived somewhere? No. > If not, could you summarize it on the mailing list? 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 de

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? ___ Reproducible-builds mailing l

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

Hi, > so we don't use up too much of your time: Probably yours is more prescious than mine. :)) > there is nothing to react to I will patiently wait until this is sorted out and the ugly warning vanishes from the package tracker. > Regarding Perl: I just wanted to emphasize my i-didn't-do-i

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 me

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

Hi, (please Cc me with replies) On https://tracker.debian.org/pkg/libisoburn i see under "action needed" a link to https://reproducible.debian.net/rb-pkg/unstable/amd64/libisoburn.html with the statement that it would FTBS on second try. Now what action is needed here ? Both builds look fla