lbcd fails to migrate from 3.5.2-3 to 3.5.2-4

Don't ask me why, but disabling lto (link time optimization) solves the failure.

Passing build in a PPA [1]. Download source package:
$ dget https://launchpad.net/~dviererbe/+archive/ubuntu/lbcd/+sourcefiles/lbcd/3.5.2-4ubuntu1~ppa1/lbcd_3.5.2-4ubuntu1~ppa1.dsc

[1] https://launchpad.net/~dviererbe/+archive/ubuntu/lbcd

LGTM. Although it FTBFS locally, it passes in PPA (probably due to skipping tests that require network access):

```
Failed Set Fail/Total (%) Skip Stat Failing Tests
-------------------------- -------------- ---- ---- ------------------------
portable/getaddrinfo 1/75 1% 0 0 68

Failed 1/1750 tests, 99.94% okay, 10 tests skipped.
```

For next time, please consider providing a proper merge-proposal against the git-ubuntu repository, which makes it so much easier to review the changes (instead of .dsc file from PPA):

https://git.launchpad.net/ubuntu/+source/lbcd

Sponsored: https://launchpad.net/ubuntu/+source/lbcd/3.5.2-4ubuntu1

$ dput ubuntu ../lbcd_3.5.2-4ubuntu1_source.changes
Uploading lbcd using ftp to ubuntu (host: upload.ubuntu.com; directory: /ubuntu)
running placeholderbug: Stop if using common placeholder numbers as bug reference.
running gitubuntu: Warn if uploading without git-ubuntu Vcs-* entries.
running updatemaintainer: Stop if ubuntu changes are without ubuntu maintainer.
running suite-mismatch: check the target distribution for common errors
running required-fields: check whether a field is present and non-empty in the changes file
running check-debs: makes sure the upload contains a binary package
running gpg: check GnuPG signatures before the upload
running releasemismatch: Warn about mismatching suffixesg e.g. focal with a XX.YY not being 20.04
running badauthor: Stop if uploading with root@ or ubuntu@ email adresses.
running ppaforppaonly: Stop uploads to the archive with or to ppa without ~ppa suffix.
running nobug: Stop if uploading without any bug reference.
running supported-distribution: check whether the target distribution is currently supported (using distro-info)
{'allowed': ['release', 'proposed', 'backports', 'security'], 'known': ['release', 'proposed', 'updates', 'backports', 'security']}
running checksum: verify checksums before uploading
Uploading lbcd_3.5.2-4ubuntu1.dsc
Uploading lbcd_3.5.2-4ubuntu1.debian.tar.xz
Uploading lbcd_3.5.2-4ubuntu1_source.buildinfo
Uploading lbcd_3.5.2-4ubuntu1_source.changes

You should also consider forwarding the patch to Debian ("submittodebian") and raising the LTO issue with the upstream project: https://github.com/rra/lbcd

> You should also consider forwarding the patch to Debian

My rationale was that debian does not enable lto and therefore does not need that change.

> and raising the LTO issue with the upstream project

I will do that.

Upstream Bug: https://github.com/rra/lbcd/issues/1

Note: Upstream project is no longer maintained.

This bug was fixed in the package lbcd - 3.5.2-4ubuntu1

---------------
lbcd (3.5.2-4ubuntu1) noble; urgency=medium

  * debian/rules: disable lto (LP: #2058410)

 -- Dominik Viererbe <email address hidden> Tue, 19 Mar 2024 19:24:28 +0200