On 2017-04-09 08:33, Ken McDonell wrote: > 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 ...
> I must be doing something obviously wrong, ... > 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? First of all, apt groups and orders the packages it passes to dpkg s.t. the dependencies are satisfied. If needed, it also uses --auto-deconfigure. Globbing *.deb does not neccessarily give such an order :-) To test your upgrade, you could do the following (I'd recommend using throwaway chroots, e.g. pbuilder login) to use apt-get for installing/upgrading the packages, you can also easily test subsets of the packages if you had initially installed only a subset. mkdir /tmp/pcp cp *.deb /tmp/pcp cd /tmp/pcp dpkg-scanpackages . > Packages apt-get install pkg1 pkg2 pkg3 # install what you want to upgrade echo deb file:///tmp/pcp ./ > /etc/apt/sources.list.d/tmp.list apt-get update # do the actual upgrade apt-get install/upgrade/dist-upgrade ... # accept to install the unauthenticated packages > And as to your question "why is that a native package anyway?", the answers you should consider changing that at some point, makes it easier if someone else would ever want work with it ... and looking at your RC bug (#805955), the packaging is very nonstandard, otherwise that would have been an easy fix... Andreas PS: and of course I forgot the easiest option: nowadays (since apt 1.1) you can even use apt-get to install debs: apt-get install ./*.deb
