Hi Daniel, I've fixed it again. However, I'm not sure how this FTBFS for you. It built fine before, and also on the buildds. Maybe you have some setting that turns lintian warnings into errors?
Regards, Lee On 18/05/18 20:55, Harlan Lieberman-Berg wrote: > Oh, I see what's happening. > > Lee, can you do a -2 and make sure to merge against git on salsa? > > On Fri, May 18, 2018 at 2:49 PM, Harlan Lieberman-Berg > <[email protected]> wrote: >> Hi Daniel, >> >> I'm a bit confused as well. I didn't upload any debs at all; I did a >> source-only upload. The buildd's successfully built -2 against the >> original tarball that was uploaded with -1... and I just rebuilt it >> again. >> >> Can you verify your source matches the sha256sum of >> 5e817a3e077565bc1ff294d5a4748fbd8d78435fa721ebf617945568e45d603a? You >> can retrieve the original source with pristine-tar against the git >> repository on salsa. >> >> On Fri, May 18, 2018 at 1:20 PM, Daniel Baumann >> <[email protected]> wrote: >>> reopen 898433 >>> found 898433 2.5.3+dfsg-1 >>> thanks >>> >>> Hi, >>> >>> thanks for fixing it, however, your last upload unfortunaly re-imports >>> the problem. >>> >>> I'm a bit confused on how the package could have been built at all. The >>> source package FTBFS'es, but you could upload the *_all.debs. Do you >>> build from different sources than what is included in the source package? >>> >>> Regards, >>> Daniel >> >> >> >> -- >> Harlan Lieberman-Berg >> ~hlieberman > > >
