Yea it makes sense to use an empty file for 4.3. Actually, I think it makes sense to do it by default on 4.3. I will create the jira related to that.
Regards JB > Le 5 avr. 2021 à 20:56, Steinar Bang <s...@dod.no> a écrit : > > >> >>>>>> JB Onofré <j...@nanthrax.net>: > >> Hi >> That’s normal: karaf 4.2.x uses blacklist so it provides the file, >> especially to blacklist 4.3.x features repositories. > >> Karaf 4.3.x doesn’t use blacklist (as the version is newer). > > Yes, but that collided with the way I had decided to handle the etc > directory: to preserve as much of users' config modifications across > upgrades, as possible, the files in the etc directory are left on > uninstall. > > And since nothing replaced the 4.2.11 blacklist file, it was still > present after upgrade to 4.3.1. > > So what the 4.3.1 debian package now does is to include an empty > blacklist file, and then that will overwrite the 4.2.11 file. > > That worked, I have successfully tested upgrading from 4.2.11 to 4.3.1 > with "apt full-upgrade". > > But I won't release the 4.3.1 debian package, until I have bumped all of > my apps to karaf 4.3.1. > > Just recompiling after bumping the BoM would have been enough to make > things run on 4.3.1, but I started on a bigger dependency cleanup and > upgrade of dependencies, and that will take a little time to complete. >
