What happened is none of the plugin control file wxwidget3 depends or build depends had versions. I built them with stock repos and installed all 37 of them in a clean stock vm without issue and they pulled in wxwidgets3-3.0.2. Once they got into the repo they wanted 3.0.4 which is in test. Tim indicated it has something to do with shlibs determining what version it wants. I just sent Tim a rebuilt test package with all of the wxwidget3 depends & build depends versions set to (>= 3.0.2). Once he gets that one up, I'll do a test install from synaptic to make sure it comes down OK. And if it does, I'll send a complete new set of +2 debs. If it fails, we'll need to move them all to test.Stevo wrote: ↑Sat Aug 17, 2019 3:17 pmWait...where did you see that? Debian didn't update it. We have 3.04 in our test repo, but I didn't build the main opencpn 5.0.0 packages with the test repo enabled. I'm fairly sure you don't need the test repo enabled to build the plugins, either, but you will get that newer 3.0.4 if you have the test repo enabled in pbuilder. My philosophy is to keep from adding the test repo unless it's absolutely necessary--instead I just add the extra backports needed in my pbuilder's local repo to avoid unplanned entanglements like this.
I installed & tested every stinkin' one of them in a stock VM to make sure they didn't need anything from test before sending them up. Since there were 37 plugins, I was trying to avoid having them go into test and then later move them into main. So much for that idea