Re: Hamlib 4.0 in experimental
Hey -
I built and tested using my normal git-pbuilder method, which would have used Hamlib4, but I wasn’t able to upload the resultant .changes, I guess as it was binary only. Advice in the email was:
> If the orig tarball is missing, the -sa flag for dpkg-buildpackage will be your friend.
Which worked nicely and gave me something I could test locally and upload. It was only this afternoon I connected the dots of the error I mentioned previously, dpkg-buildpackage and a lack of hamlib4 being on my system...
I am still trying to get on top of how I’m building and uploading - I’ve been quite happy with my git-pbuilder workflow, but I’ve not yet managed to research the equivalent to the above command so I can keep using what I’m used to - I do quite like pbuilder being it’s own contained environment to avoid these problems.
Of course I’m open to learning new things and suggestions, I’m still clearing off the rust in my brain.
DH
> On 28 Jan 2021, at 18:43, Christoph Berg <myon@debian.org> wrote:
>
> Re: Dave Hibberd
>> I've updated to hamlib4 on my desktop and have built & tested qsstv with it, everything seems okay.
>> However, looking at the problems in the source package I uploaded yesterday, I see that it depends on libhamlib2 - I guess this is what it found on my build machine at the time https://qa.debian.org/debcheck.php?dist=unstable&package=qsstv
>> Other architecture builds have been fine and built with libhamlib4, but the amd64 build is showing this error...
>> Is this going to cause any issues once it transitions from Unstable to testing?
>
> It will not transition because it's plain broken now. Are you sure you
> tested with hamlib4?
>
> Why didn't you do a source-only upload? (This is also an issue that
> will prevent transitioning.)
>
> Christoph
Reply to: