On Thu, Jun 13, 2024 at 09:08:58AM -0300, Athos Ribeiro wrote:
I understand the pain there. How often did the issue occur back then
when the libldap-common was in Depends?
It's a few years ago now, so I don't remember exactly.
Initially it was a tightly versioned Depends. That caused a lot of
trouble when combined with some flaky tests that we had at the time.
There was a couple of uploads where my sponsor ended up doing a lot of
binary uploads to unstick things.
Switching to unversioned Depends improved things but didn't solve it
completely. I can't remember whether any binary uploads were done -
maybe none. I did one sourceful bootstrap upload, which you can still
see in the changelog.
Once I understood the issue, I tried to mitigate it by uploading when
the buildds were quiet, hoping the amd64 and arch:all builds would both
start before the next dinstall. That was mostly successful: if the
builds _finished_ at different times, the package might vanish
temporarily, but as long as they both _started_ in time, it would be ok
after they finished and published.
The Recommends workaround has made uploading a LOT less stressful, not
to mention safer for binNMUs etc.
