Thanks, Andreas.
The html link and your mail both suggest the same approach. But when I do
this and build new 3.11.10 packages and try to upgrade a system with 3.11.9
installed using the same recipe I've been using for decades, namely
# dpkg -i *.deb
in the directory where all the new packages are made, I get this ...
Unpacking libpcp-pmda3 (3.11.10) over (3.11.9) ...
dpkg: regarding .../libpcp-pmda3-dev_3.11.10_amd64.deb containing
libpcp-pmda3-dev:
libpcp-pmda3-dev breaks libpcp3-dev (<< 3.11.10~)
libpcp3-dev (version 3.11.9) is present and installed.
dpkg: error processing archive build/deb/libpcp-pmda3-dev_3.11.10_amd64.deb
(--install):
installing libpcp-pmda3-dev would break libpcp3-dev, and
deconfiguration is not permitted (--auto-deconfigure might help)
I must be doing something obviously wrong, ...
In desperation, I tried dpkg -i -B (I've never used -B before), and that
seemed to do the trick. Is that correct?
Do the dpkg front-ends like apt-get use the -B option, so this is what a
punter will see when they upgrade PCP 3.11.10 packages from a distro's
repository?
And as to your question "why is that a native package anyway?", the answers
are some combination of
(a) ignorance on our part,
(b) no one ever asked before,
(c) no Debian-based distro has had to re-package the pcp packages because
the upstream developers are so responsive ... 8^)
